The latest wine 1.5.18 breaks ynab 4 (budgeting software www.ynab.com) but previous version of wine 1.5 it was running great, the program still runs fine on wine 1.4 but earlier versions of wine 1.5 improved things like the inbuilt ynab updater working and better integration with unity (the ynab icon shows up in the unity launcher instead of the generic one).
i'm not sure what's changed between earlier version of wine 1.5 and the current one but ynab hasn't changed it's version?
Latest wine 1.5 breaks ynab 4
Re: Latest wine 1.5 breaks ynab 4
Please run a regression test and file a bug. http://wiki.winehq.org/RegressionTesting
Re: Latest wine 1.5 breaks ynab 4
I want to help but i am using ubuntu 12.10 64 bit and got stuck trying to build wine from git so i will just wait for the next version of wine 1.5 to be released and try again.
Re: Latest wine 1.5 breaks ynab 4
Does the demo version of ynab have the same problem?
Re: Latest wine 1.5 breaks ynab 4
Yes the program displays but comes up with this when running from terminal
gap@Q:~$ env WINEARCH=win32 WINEPREFIX=~/.wine32 wine "C:\Program Files\YNAB 4\YNAB 4.exe"
fixme:lsa:LsaGetLogonSessionData 0x32ebf4 0x32ec04 stub
fixme:win:EnumDisplayDevicesW ((null),0,0x32e6ac,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x32e69c,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x32d818,0x00000000), stub!
fixme:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request: stub
fixme:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request: stub
fixme:imm:ImmReleaseContext (0x1006e, 0x5497080): stub
If someone more knowledgeable has a 32bit version of ubuntu and can try running a regression test on the trial to see what's wrong that would be great.
gap@Q:~$ env WINEARCH=win32 WINEPREFIX=~/.wine32 wine "C:\Program Files\YNAB 4\YNAB 4.exe"
fixme:lsa:LsaGetLogonSessionData 0x32ebf4 0x32ec04 stub
fixme:win:EnumDisplayDevicesW ((null),0,0x32e6ac,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x32e69c,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x32d818,0x00000000), stub!
fixme:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request: stub
fixme:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request: stub
fixme:imm:ImmReleaseContext (0x1006e, 0x5497080): stub
If someone more knowledgeable has a 32bit version of ubuntu and can try running a regression test on the trial to see what's wrong that would be great.