Created attachment 1573478 [details] Program Error Details Description of problem: Upgrading from 5.0.9-200.FC29 to 5.0.17.FC29 a windows program running under WINE no longer works. Been using this program for years under WINE without problems before today Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Invoke command to bring up the application 2. Error occurs 3. Application closes Actual results: closes Expected results: Additional info: see attached, I'm not a coder so don't understand what it tells me
Hi, Yes - i am on Fedora 29, and the update to wine yesterday has caused the program to fail - using LTSpiceXVII. Has always worked. Starting from the command line : [richard@localhost LTspiceXVII]$ winecfg 000b:fixme:winediag:start_process Wine Staging 4.8 is a testing version containing experimental patches. 000b:fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org. 000d:err:menubuilder:init_xdg error looking up the desktop directory [richard@localhost LTspiceXVII]$ I have used Wine Config to autodetect all drives - still the same issue. Regards, Richard.
Hi, Tried the older kernel - still same issue. Tried 32bit applications - they work. All 64bit applications fail. I have installed 64bit WINE from day one - so not sure if the update yesterday has overwritten the config, or other. Regards, Richard.
Hi, Seems to be a known bug : https://bugs.winehq.org/show_bug.cgi?id=47207 Tried to downgrade, but not able to - as downgrade works for others. Regards, Richard.
Yup, the 64-bit applications fail and the single 32-bit one works fine
Commanded dnf downgrade wine, wine got downgraded, the 64-bit application works again. Temporary workaround is good, hope someone finds outs whats broken in the last upgrade
Hi, I attempted to downgrade to v4.7, but it seems this is not on the repository. Regards, Richard.
Hi, If you check the WINE bugs link, this has been an issue on other distro's for over 1 week, and it does not seem as if they are urgently correcting it. Therefore, proposal is for Fedora to allow for the downgrade to WINE v4.7 on the repository. Regards, Richard.
Hmmm, Richard - downgrade worked for me. As far as other distro's I was at a convention in Xenia OH last week and then Gettysburg for some sightseeing, so if you mean Fedora distro's, maybe the same one
Hi, When i select the downgrade option, all files are v3.16. Unable to select v4.71 as previous version before 25/05/2019. dnf --showduplicates list wine lists the same versions, 4.8 and 3.16. Regards, Richard.
Hi, Wine bug reporting has the following bug listed for this issue : https://bugs.winehq.org/show_bug.cgi?id=47224 States that with mingw installed, the issue does not occur - so i installed anything related to mingw64 and wine : dnf install mingw64-qt5-qtwinextras After 0.5GByte of files installed, still does not work. Regards, Richard.
Hi, As an update : https://bugs.winehq.org/show_bug.cgi?id=47224 States "This is a packaging bug; if you are not using the WineHQ packages, your problem does not belong here." As such, this points to Fedora 29 distro issue. Regards, Richard.
>this points to Fedora 29 distro issue Agree; now to get someone at Fedora to pay attention to it. Good detective work
This seems to have been filed using the wrong component, reassigning.
Please file a bug against "wine-staging" in the wine bugzilla. Do not create bugs for wine packaging or "plain" wine. It is important to do it against "wine-staging". The recent move that Wine now supports compiling PE binaries does not do anything regarding 64-bit apps or Battle.net. It appears to be a staging bug. https://bugs.winehq.org/enter_bug.cgi?product=Wine-staging Once you have created the correct bug report please link the URL here. - Include version - Include application name - Include link to a download for the application Essentially follow their guidelines laid out here: https://wiki.winehq.org/Bugs
Hi, JD Delancy raised a bug : https://bugs.winehq.org/show_bug.cgi?id=47297 I think i am getting the run-around, since i have replicated using PlayOnLinux that v4.8 staging fails, yet v4.7, v4.8, v4.7 staging, and 4.9 work no issue, yet i am now being asked to test on v4.9 staging which is not available on PlayOnLinux. Other people have reported v4.8 staging fails for Battle.net, so i do not understand their reticence to explore the bug. Maybe others can try to prompt WineHQ, as any evidence seems to be ignored. Else we can wait until v4.9/v4.9 staging to appear. Regards, Richard.
The bug you linked to is the improper bug report. Please re-file a brand new bug against wine-staging. The Fedora wine-staging 4.9 update is available in Fedora 30 stable: https://bodhi.fedoraproject.org/updates/FEDORA-2019-ebc4e90494 The same update for Fedora 29 is still in the testing repo: https://bodhi.fedoraproject.org/updates/FEDORA-2019-278fd8fb2a
Hi, As an update, Fedora 29 deployed v4.9 staging and the 64bit functions are now working. As long as people update the build on their PC, then this is now, not an issue. Regards, Richard.