http://bugs.winehq.org/show_bug.cgi?id=30156
Bug #: 30156 Summary: LeagueOfLegends launcher crashes with nvidia 295.20 drivers Product: Wine Version: 1.3.35 Platform: x86-64 URL: http://leagueoflegends.com/ OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: spindler.matej@gmail.com Classification: Unclassified
I'm on arch x86-64 and running self compiled wine-1.4.
Before driver update launcher started without any problems. Downgrading driver (packages nvidia, nvidia-utils and lib32-nvidia-utils) to 290.10 is still working OK. With new driver it crashes after clicking play button, with:
wine: Unhandled page fault on write access to 0x0000000c at address 0x7e6a1ea3 (thread 000c), starting debugger...
I'm attaching +relay,seh,tid log compressed as it is ~43Mb.
To reproduce: I copied game files from windows install (used to work without problems). Launcher needs native vcrun2005 Workaround bug26924 - go to : "GameDir"/RADS/system - launch with: wine "rads_user_kernel.exe" run lol_launcher $(ls ../projects/lol_launcher/releases/) LoLLauncher.exe - wait for updates to finish and click PLAY.
http://bugs.winehq.org/show_bug.cgi?id=30156
--- Comment #1 from Matej Spindler spindler.matej@gmail.com 2012-03-13 05:54:17 CDT --- Created attachment 39337 --> http://bugs.winehq.org/attachment.cgi?id=39337 +relay,tid,seh log
http://bugs.winehq.org/show_bug.cgi?id=30156
Dmitry Timoshkov dmitry@baikal.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.3.35 |1.4
http://bugs.winehq.org/show_bug.cgi?id=30156
--- Comment #2 from Dmitry Timoshkov dmitry@baikal.ru 2012-03-13 06:33:21 CDT --- Start with attaching full terminal output including a backtrace without any debug switches.
http://bugs.winehq.org/show_bug.cgi?id=30156
--- Comment #3 from Matej Spindler spindler.matej@gmail.com 2012-03-13 07:00:57 CDT --- Created attachment 39338 --> http://bugs.winehq.org/attachment.cgi?id=39338 terminal output without winedebug switches
Here it is.
That is everything no backtraces. It just ends there until I ctrl-C out.
http://bugs.winehq.org/show_bug.cgi?id=30156
Dmitry Timoshkov dmitry@baikal.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #39338|application/octet-stream |text/plain mime type| |
http://bugs.winehq.org/show_bug.cgi?id=30156
Dmitry Timoshkov dmitry@baikal.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- URL|http://leagueoflegends.com/ |
http://bugs.winehq.org/show_bug.cgi?id=30156
Frédéric Delanoy frederic.delanoy@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |frederic.delanoy@gmail.com
--- Comment #4 from Frédéric Delanoy frederic.delanoy@gmail.com 2012-03-15 14:26:25 CDT --- (In reply to comment #3)
Created attachment 39338 [details] terminal output without winedebug switches
Here it is.
That is everything no backtraces. It just ends there until I ctrl-C out.
Haven't you got the wine crash dialog? If you had, it gives you the possibily to save the backtrace to a file-
http://bugs.winehq.org/show_bug.cgi?id=30156
--- Comment #5 from Matej Spindler spindler.matej@gmail.com 2012-03-15 16:13:58 CDT --- Created attachment 39386 --> http://bugs.winehq.org/attachment.cgi?id=39386 backtrace from winedbg
(In reply to comment #4)
Haven't you got the wine crash dialog? If you had, it gives you the possibily to save the backtrace to a file-
There is no crash dialog. CPU goes to 100% (1 core) and that's it.
I did some exerimenting with winedbg and somehow got the attached backtrace. I't was my first time using winedbg so don't laugh if did something stupid :p.
http://bugs.winehq.org/show_bug.cgi?id=30156
Frédéric Delanoy frederic.delanoy@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |UPSTREAM
--- Comment #6 from Frédéric Delanoy frederic.delanoy@gmail.com 2012-03-15 16:35:09 CDT --- Looks like the same issue as bug 29931. Issue with the drivers; I've also had a similar bug with another application.
http://bugs.winehq.org/show_bug.cgi?id=30156
--- Comment #7 from Austin English austinenglish@gmail.com 2012-03-15 16:38:12 CDT --- (In reply to comment #4)
(In reply to comment #3)
Created attachment 39338 [details] terminal output without winedebug switches
Here it is.
That is everything no backtraces. It just ends there until I ctrl-C out.
Haven't you got the wine crash dialog? If you had, it gives you the possibily to save the backtrace to a file-
The application may catch the crash itself.
http://bugs.winehq.org/show_bug.cgi?id=30156
--- Comment #8 from Rosanne DiMesio dimesio@earthlink.net 2012-03-18 10:29:19 CDT --- If it's the same driver bug, shouldn't this be marked as a duplicate of bug 29931?
http://bugs.winehq.org/show_bug.cgi?id=30156
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|UPSTREAM |DUPLICATE
--- Comment #9 from Austin English austinenglish@gmail.com 2012-03-18 10:35:57 CDT --- (In reply to comment #8)
If it's the same driver bug, shouldn't this be marked as a duplicate of bug 29931?
Yes.
*** This bug has been marked as a duplicate of bug 29931 ***
http://bugs.winehq.org/show_bug.cgi?id=30156
Frédéric Delanoy frederic.delanoy@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #10 from Frédéric Delanoy frederic.delanoy@gmail.com 2012-03-19 17:34:06 CDT --- Closing duplicate bugs
-
wine-bugs＠winehq.org