Red Hat Bugzilla – Bug 1280488
wine not working at all
Last modified: 2015-12-02 13:21:31 EST
Description of problem:
Everything run with wine crashes on my machine after the last update from wine-1.7.52-1 to wine-1.7.53-1
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. run e.g. winecfg
fixme:winediag:start_process Wine Staging 1.7.53 is a testing version containing experimental patches.
fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org.
err:winedevice:ServiceMain driver L"Null" failed to load
wine: Unhandled page fault on read access to 0x00000010 at address 0x7e61c2ea (thread 0009), starting debugger...
winedbg: Internal crash at 0x7bc5cca5
winecfg running just fine
Please try a fresh wine prefix.
(In reply to Michael Cronenworth from comment #1)
> Please try a fresh wine prefix.
> WINEPREFIX=~/winetest winecfg
That works as expected. Is there a way to identify what's wrong in the default prefix or at least just remove the config without losing data from there? Maybe something got mangled somehow during the update? An interesting fact is that when I copied my whole /home/user folder (including ~/.wine) to a fresh F23 installation, everything works fine there.
You can try debugging with "winegdb" or delete $WINEPREFIX/.update-timestamp to attempt to regenerate the wine prefix.
If it is working on newer versions of wine I'm going to close this. F21 is going EOL very soon and I'm not pushing any updates for it.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.