Description of problem: winecfg won't start up successfully winecfg wine: created the configuration directory '/home/pam/.wine' fixme:winediag:start_process Wine Staging is a testing version containing experimental patches. err:module:attach_process_dlls "gdi32.dll" failed to initialize, aborting err:module:LdrInitializeThunk Main exe initialization for L"C:\\windows\\system32\\rundll32.exe" failed, status c0000005 wine: Unhandled page fault on read access to 0x00000008 at address 0x7fbc1f54beb9 (thread 0013), starting debugger... err:seh:start_debugger Couldn't start debugger ("winedbg --auto 18 100") (2) Read the Wine Developers Guide on how to set up winedbg or another debugger wine: Unhandled page fault on read access to 0x00000008 at address 0x7fc454e63eb9 (thread 000b), starting debugger... err:seh:start_debugger Couldn't start debugger ("winedbg --auto 10 104") (2) Read the Wine Developers Guide on how to set up winedbg or another debugger wine: Unhandled page fault on read access to 0x00000008 at address 0x7f1af11aceb9 (thread 0015), starting debugger... err:seh:start_debugger Couldn't start debugger ("winedbg --auto 20 80") (2) Read the Wine Developers Guide on how to set up winedbg or another debugger wine: Unhandled page fault on read access to 0x00000008 at address 0x7f52c7987eb9 (thread 0017), starting debugger... err:seh:start_debugger Couldn't start debugger ("winedbg --auto 22 100") (2) Read the Wine Developers Guide on how to set up winedbg or another debugger Version-Release number of selected component (if applicable): 1.7.36-1.fc22.noarch on x86_64
I cannot reproduce this on f21 x86_64 (don't have a rawhide box here today). Do you have any further information?
Downgrading to wine-1.7.35-3.fc22.x86_64 got things working again. Could this be related to the gcc changes in rawhide?
One other note is that things were working better when there was an existing .wine directory from before.
After upgrading back to wine-1.7.36-1.fc22.x86_64, winecfg doesn't work regardless of whether or not .wine was setup previously.
Thanks for the feedback. I will try on rawhide tomorrow.
If you change your wineserver alternatives config to point to the 32-bit one, wine should start working. (Thanks to Erik's debugging) Since most Windows apps are still 32-bit this should get things working. # alternatives --config wineserver Most likely the 64-bit breakage is due to gcc 5.0, but I am trying to get a rawhide VM setup to debug further.
With wine-1.7.37-1.fc22.x86_64, using a clean account (rm -rf .wine) - 32bit wineserver -> winecfg starts - 64bit wineserver -> winecfg does not start Account with preexisting .wine installation: - 32bit wineserver: winecfg won't start complaining about 64bit installation - 64bit wineserver: winecfg does not start Is it a separate bug or related if I cannot start any other graphical wine programs that have previously worked? cli programs still work.
It's the same bug. Thanks.
This lookd like it might be fixed with wine-1.7.38-2.fc23.
It's not fixed, yet, as the bug is not closed. The issue involves a gcc optimization and I haven't been able to determine it yet. Fedora 22 and 23 wine have optimizations disabled as a temporary workaround.
One things that would help greatly would be to start narrowing down the scope of the bug. ie, is there one file (or better yet one function) that, when compiled with gcc-5 is causing wine to malfunction. It's been eons since I looked at Wine, so I don't recall how feasible it is to build it twice (into different directories) with different compilers, then copy files between the directories until an offending .o is found. But that's how I'd approach the problem.
@Bruno, et. al: Please try this scratch build and let me know how your applications run. http://koji.fedoraproject.org/koji/taskinfo?taskID=9275552
I installed the wine from task 9275552, double checked that alternatives was set to use wineserver64 and ran winecfg. It seemed to work OK.
Thanks. I have found more regressions in testing and can only enable -O1 level optimizations at this time. I'm going to push a 1.7.39 build, but continue to leave this open as there are many, many issue still remaining and we can't use -O2 yet.
I cannot start wine in F22: $ rpm -qa|grep wine wine-twain-1.7.39-1.fc22.x86_64 wine-capi-1.7.39-1.fc22.i686 wine-core-1.7.39-1.fc22.i686 wine-symbol-fonts-1.7.39-1.fc22.noarch wine-common-1.7.39-1.fc22.noarch wine-marlett-fonts-1.7.39-1.fc22.noarch wine-desktop-1.7.39-1.fc22.noarch wine-small-fonts-1.7.39-1.fc22.noarch wine-openal-1.7.39-1.fc22.x86_64 wine-ldap-1.7.39-1.fc22.i686 wine-filesystem-1.7.39-1.fc22.noarch wine-arial-fonts-1.7.39-1.fc22.noarch wine-systemd-1.7.39-1.fc22.noarch wine-alsa-1.7.39-1.fc22.x86_64 wine-opencl-1.7.39-1.fc22.x86_64 wine-cms-1.7.39-1.fc22.i686 wine-opencl-1.7.39-1.fc22.i686 wine-mono-4.5.6-2.fc22.noarch wine-courier-fonts-1.7.39-1.fc22.noarch mingw32-wine-gecko-2.36-1.fc22.noarch wine-fixedsys-fonts-1.7.39-1.fc22.noarch wine-ms-sans-serif-fonts-1.7.39-1.fc22.noarch wine-core-1.7.39-1.fc22.x86_64 wine-ldap-1.7.39-1.fc22.x86_64 wine-openal-1.7.39-1.fc22.i686 wine-twain-1.7.39-1.fc22.i686 wine-system-fonts-1.7.39-1.fc22.noarch wine-pulseaudio-1.7.39-1.fc22.x86_64 wine-wingdings-fonts-1.7.39-1.fc22.noarch mingw64-wine-gecko-2.36-1.fc22.noarch wine-1.7.39-1.fc22.x86_64 wine-fonts-1.7.39-1.fc22.noarch wine-cms-1.7.39-1.fc22.x86_64 wine-pulseaudio-1.7.39-1.fc22.i686 wine-tahoma-fonts-1.7.39-1.fc22.noarch wine-capi-1.7.39-1.fc22.x86_64 $ winecfg wine: created the configuration directory '/home/juan/.wine' fixme:winediag:start_process Wine Staging is a testing version containing experimental patches. fixme:winediag:start_process Please report bugs at http://bugs.wine-staging.com (instead of winehq.org). wine: Unhandled page fault at address 0x7fe30921782c (thread 0011), starting debugger... A wine window appears, saying "Wine configuration at "/home/juan/.wine" is being updated, please wait..." ...but it never ends.
Yes, we know. Please update to 1.7.40. https://admin.fedoraproject.org/updates/FEDORA-2015-5679/wine-1.7.40-1.fc22
(In reply to Michael Cronenworth from comment #17) > Yes, we know. > > Please update to 1.7.40. > https://admin.fedoraproject.org/updates/FEDORA-2015-5679/wine-1.7.40-1.fc22 It fixes the problem. Thank you.
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
Good discussion , I was enlightened by the analysis - Does anyone know where my company could get ahold of a fillable a form document to work with ?
(In reply to madge gafford from comment #20) > Good discussion , I was enlightened by the analysis - Does anyone know where > my company could get ahold of a fillable a form document to work with ? Hi Madge, my work colleague accessed a fillable a form form at this place https://goo.gl/HfRACA.