http://bugs.winehq.org/show_bug.cgi?id=31413
GyB gyebro69@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gyebro69@gmail.com
--- Comment #4 from GyB gyebro69@gmail.com 2012-08-06 10:50:27 CDT --- If the application used to work with previous Wine versions, you should perform a regression test: http://wiki.winehq.org/RegressionTesting/
Is this the application in question? http://getnightingale.com/
Current version: Nightingale_1.11.0-2223_windows-i686.exe md5sum: f31b0bb6a3f3c06af5e2455f5fa876df
I'm also on Fedora 17, but this is the 32-bit variant. I tested the application with Wine 1.5.8, 1.5.9, 1.5.10, but couldn't reproduce the crash. I must add that there is a regression in usp10 which affects Nightingale since 1.5.9, but that's likely not the problem here.
I'm not familiar with 64-bit setups, maybe I'm on the wrong tracks, but you should check the followings:
1. since the application is 32-bit only, you need a 32-bit Wine. Do you have the wine.i686 packages installed from the F17 repos? 2. create a 32-bit wineprefix: WINEARCH=win32 winecfg, and install the application into that.
3. this is only a wild guess: do other applications/games start for you without crashing? Don't you get alerts from SeLinux when starting anything in Wine?
If all the above fail, please attach the whole terminal output (not just the backtrace).
Fedora 17 x86 Kernel 3.5.0-2.fc17.i686.PAE