http://bugs.winehq.org/show_bug.cgi?id=22500
Summary: Steam causes Xorg to exit, new to wine 1.1.43 Product: Wine Version: 1.1.43 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: michael@araneidae.co.uk
Running steam (after the 26th April update) on wine 1.1.43 causes Xorg to exit. Sometimes the outline of the GUI has time to appear, sometimes not.
Reverting to wine 1.1.42 avoids the problem, and steam appears to work fine.
The only error message in /var/log/Xorg.0.log.old is:
Backtrace: 0: /usr/bin/X(xorg_backtrace+0x3b) [0x8133d6b] 1: /usr/bin/X(xf86SigHandler+0x55) [0x80c7d35] 2: [0xe91400] Saw signal 11. Server aborting.
This is on Ubuntu 9.10 with NVIDA driver version 185.18.36.
http://bugs.winehq.org/show_bug.cgi?id=22500
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |dank@kegel.com Resolution| |INVALID
--- Comment #1 from Dan Kegel dank@kegel.com 2010-04-26 17:01:41 --- If the X server crashes, that's an X server problem (or possibly a driver problem), not a wine problem. Please report this to the folks who built your X server.
http://bugs.winehq.org/show_bug.cgi?id=22500
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #2 from Austin English austinenglish@gmail.com 2010-04-26 17:50:36 --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=22500
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Steam causes Xorg to exit, |Steam causes Xorg to exit |new to wine 1.1.43 |
http://bugs.winehq.org/show_bug.cgi?id=22500
--- Comment #3 from Michael Abbott michael@araneidae.co.uk 2010-04-27 05:02:29 --- Unimpressed. Just because Xorg exits doesn't mean that Wine has nothing to do with it. Also, most bugs involve bugs in more than one place, it's part of Wine's job to try to avoid triggering bugs elsewhere.
I may do a regression, in which case I'll reopen if the result is helpful.
http://bugs.winehq.org/show_bug.cgi?id=22500
--- Comment #4 from Henri Verbeet hverbeet@gmail.com 2010-04-27 05:18:59 --- You'll probably end up with a53a3f50ad02997167de0438f12ea992d6236e27 or a related commit, which would make this a duplicate of bug 22426. If you try with current git though, you'll probably find that 11c7a67ac317130ecd980a5880fb1a2974570f33 works around the issue.
Either way though, this is a known bug in 185.18.36, and anything that kills your X server is by definition not a Wine bug.
http://bugs.winehq.org/show_bug.cgi?id=22500
--- Comment #5 from Dan Kegel dank@kegel.com 2010-04-27 07:57:53 --- X must be bulletproof, or it's not worth the bits it's printed on. This bug is invalid for Wine, it must be fixed in X.
Now, if X doesn't crash, and Steam doesn't work because Wine does something stupid to X, that might be a Wine bug, but you'd need to file a separate bug for that.