Hi, I just updated my environment to Fedora 19. After updating I noticed that wine doesn't work correctly any more. When attempting to create a new wine prefix not all files are installed in it. The Fedora 18 package of wine does work correctly so my guess is that the real cause is not inside wine, but in a different component (perhaps gcc itself?). [erik@localhost ~]$ sudo yum -y --releasever=18 downgrade wine\* --exclude=wine-mono <snip> Downgrading: wine-common noarch 1.5.25-1.fc18 updates-testing 92 k wine-core i686 1.5.25-1.fc18 updates-testing 17 M wine-core x86_64 1.5.25-1.fc18 updates-testing 16 M wine-filesystem noarch 1.5.25-1.fc18 updates-testing 70 k wine-wow i686 1.5.25-1.fc18 updates-testing 220 k wine-wow x86_64 1.5.25-1.fc18 updates-testing 222 k <snip> [erik@localhost ~]$ rm -rf ~/.wine [erik@localhost ~]$ winecfg wine: created the configuration directory '/home/erik/.wine' fixme:storage:create_storagefile Storage share mode not implemented. err:mscoree:LoadLibraryShim error reading registry key for installroot err:mscoree:LoadLibraryShim error reading registry key for installroot err:mscoree:LoadLibraryShim error reading registry key for installroot err:mscoree:LoadLibraryShim error reading registry key for installroot fixme:storage:create_storagefile Storage share mode not implemented. err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. fixme:iphlpapi:NotifyAddrChange (Handle 0xf8e338, overlapped 0xf8e350): stub fixme:storage:create_storagefile Storage share mode not implemented. err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. fixme:iphlpapi:NotifyAddrChange (Handle 0xf0e910, overlapped 0xf0e91c): stub wine: configuration in '/home/erik/.wine' has been updated. >>> winecfg is shown correctly here (Fedora 18) [erik@localhost ~]$ sudo yum -y --releasever=19 update wine\* <snip> Updating: wine-common noarch 1.5.25-1.fc19 fedora 92 k wine-core i686 1.5.25-1.fc19 fedora 16 M wine-core x86_64 1.5.25-1.fc19 fedora 16 M wine-filesystem noarch 1.5.25-1.fc19 fedora 70 k wine-wow i686 1.5.25-1.fc19 fedora 219 k wine-wow x86_64 1.5.25-1.fc19 fedora 221 k <snip> [erik@localhost ~]$ rm -rf ~/.wine [erik@localhost ~]$ winecfg wine: created the configuration directory '/home/erik/.wine' err:process:start_wineboot failed to start wineboot, err 1359 err:winecfg:WinMain failed to restart 64-bit L"C:\\windows\\system32\\winecfg.exe", err 1359 [erik@localhost ~]$ find ~/.wine /home/erik/.wine /home/erik/.wine/user.reg /home/erik/.wine/dosdevices /home/erik/.wine/dosdevices/c: /home/erik/.wine/dosdevices/z: /home/erik/.wine/drive_c /home/erik/.wine/drive_c/windows /home/erik/.wine/drive_c/windows/system32 /home/erik/.wine/drive_c/windows/win.ini /home/erik/.wine/drive_c/windows/syswow64 /home/erik/.wine/system.reg >>> winecfg doesn't show up here (Fedora 19) Have you got any idea what might be going wrong here?
Hm, not quite sure whats going on there. I will have a look next week when I am back at my workstation (only have f18 laptop and netbook around atm).
I've narrowed it down to a compiler optimization problem. It has been reported upstream. http://bugs.winehq.org/show_bug.cgi?id=33307
*** Bug 953030 has been marked as a duplicate of this bug. ***
Happening to me on F18 as well with 1.5.25-1. Goes away when I downgrade to 1.5.24.
(In reply to comment #4) > Happening to me on F18 as well with 1.5.25-1. Goes away when I downgrade to > 1.5.24. Jonathan, your issue is not the same as this bug. Please file a separate bug for your issue. This issue is specific to GCC 4.8.0 and Wine. Thanks.
*** Bug 953970 has been marked as a duplicate of this bug. ***
The upstream bug report has just been closed. It turned out to be an issue in gcc 4.8. A fix for it has just been applied upstream: http://gcc.gnu.org/viewcvs/gcc?view=revision&revision=198321 This fix hasn't propagated yet to the Fedora gcc package. @gcc maintainers: could you please update gcc in Fedora 19 and rawhide so we can get wine working again?
An updated gcc was recently pushed to Fedora 19 and Rawhide. I just performed a scratch build of wine against this updated gcc and it indeed resolves the issues mentioned in this bug report: http://koji.fedoraproject.org/koji/taskinfo?taskID=5352637 @Andreas: could you please rebuild/update wine in Fedora 19 and rawhide? After that this bug can be closed
When I run winecfg, I get the following. $ winecfg http://ur1.ca/duw7w Is this the same problem?
(In reply to comment #9) > When I run winecfg, I get the following. > $ winecfg > > http://ur1.ca/duw7w > > Is this the same problem? I'm using F19 x86_64 with wine 1.5.27. I'm not sure that this is the same problem, but it may be.
The fix was in gcc and a rebuilt Wine. The Wine 1.5.29 will work correctly. I noticed you gave a -1 karma on the Wine 1.5.29 update. Please do not give karma on updates that you do not have installed. Install Wine 1.5.29 for the fix.
From the paste: err:process:init_windows_dirs directory L"dows\\syste\\syswow64" could not be created, error 3 This indeed sounds like the memory corruption which was caused by a gcc bug. It is fixed with wine 1.5.29 in f19 (version 1.5.27 was built with an older gcc and therefore is buggy)
Issue is resolved for some time already in f19 and rawhide. Closing bug