http://bugs.winehq.org/show_bug.cgi?id=30451
Bug #: 30451 Summary: Wine 1.4 under Ubuntu 11.10 Linux 3.0.0-19-generic can't run Locomotion any more Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: mmays@arrowhead.net Classification: Unclassified
Locomotion worked great under Wine on Linux Ubuntu Oceiric 11.10. I run executable "Loco.exe" which is modded to not ask for a CD. I recently ran an update to kernel 3.0.0-19-generic. I think that Wine was upgraded, also. Locomotion now fails and offers dump information in a backtrace, which is attached.
http://bugs.winehq.org/show_bug.cgi?id=30451
--- Comment #1 from Mark Mays mmays@arrowhead.net 2012-04-15 17:12:53 CDT --- Created attachment 39810 --> http://bugs.winehq.org/attachment.cgi?id=39810 backtrace.txt from failure of Loco.exe under Wine 1.4 and Linux 3.0.0-19
http://bugs.winehq.org/show_bug.cgi?id=30451
Vitaliy Margolen vitaliy-bugzilla@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|unspecified |1.4 Summary|Wine 1.4 under Ubuntu 11.10 |Locomotion fails to start |Linux 3.0.0-19-generic | |can't run Locomotion any | |more |
--- Comment #2 from Vitaliy Margolen vitaliy-bugzilla@kievinfo.com 2012-04-15 18:50:34 CDT --- First please upgrade to wine-1.5.2 and retest. If problem persists, attach complete terminal output as described here: http://wiki.winehq.org/FAQ#get_log
Also try enabling virtual desktop.
http://bugs.winehq.org/show_bug.cgi?id=30451
--- Comment #3 from Mark Mays mmays@arrowhead.net 2012-04-15 19:06:35 CDT --- Created attachment 39814 --> http://bugs.winehq.org/attachment.cgi?id=39814 upgrade to wine 1.5.2, added Gecko, similar error - backtrace
Was asked to upgrade to Wine 1.5.2 and reproduce the error. Backtrace is included as a second attachment.
http://bugs.winehq.org/show_bug.cgi?id=30451
--- Comment #4 from Vitaliy Margolen vitaliy-bugzilla@kievinfo.com 2012-04-15 19:24:40 CDT --- I've asked for the complete terminal output not just a crash backtrace.
http://bugs.winehq.org/show_bug.cgi?id=30451
--- Comment #5 from Mark Mays mmays@arrowhead.net 2012-04-15 19:58:13 CDT --- Created attachment 39815 --> http://bugs.winehq.org/attachment.cgi?id=39815 console output showing failure
Looks like a video driver error. Will try to update to NVIDIA 2.95 next.
http://bugs.winehq.org/show_bug.cgi?id=30451
--- Comment #6 from Mark Mays mmays@arrowhead.net 2012-04-15 20:57:25 CDT --- Upgrade to Wine 1.5.2 and installation of NVIDIA 295.40 drivers resolved this problem.
Thanks for your help!
http://bugs.winehq.org/show_bug.cgi?id=30451
Vitaliy Margolen vitaliy-bugzilla@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #7 from Vitaliy Margolen vitaliy-bugzilla@kievinfo.com 2012-04-15 21:30:10 CDT --- Invalid then
http://bugs.winehq.org/show_bug.cgi?id=30451
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED Resolution|INVALID |UPSTREAM
--- Comment #8 from Austin English austinenglish@gmail.com 2012-04-15 22:30:55 CDT --- (In reply to comment #7)
Invalid then
No, UPSTREAM.
http://bugs.winehq.org/show_bug.cgi?id=30451
Vitaliy Margolen vitaliy-bugzilla@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|UPSTREAM |INVALID
--- Comment #9 from Vitaliy Margolen vitaliy-bugzilla@kievinfo.com 2012-04-15 22:54:34 CDT --- When did not installing proper drivers became an upstream bug? Also please add definition of the "upstream" to this page: http://bugs.winehq.org/page.cgi?id=fields.html
http://bugs.winehq.org/show_bug.cgi?id=30451
--- Comment #10 from Austin English austinenglish@gmail.com 2012-04-15 23:24:54 CDT --- (In reply to comment #9)
Sorry, didn't read the backtrace, I thought it was fixed by a driver upgrade, not incorrectly installed drivers.