[Bug 22415] New: WolfR4 Launcher (closed beta): Catches major wine bug, locks down entire OS

http://bugs.winehq.org/show_bug.cgi?id=22415

Summary: WolfR4 Launcher (closed beta): Catches major wine bug,
                    locks down entire OS
           Product: Wine
           Version: 1.1.42
          Platform: x86-64
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

Created an attachment (id=27449)
 --> (http://bugs.winehq.org/attachment.cgi?id=27449)
strace of wine and blah.txt log...

The WolfR4 is a launcher for Re-Volt racing game, since it's closed beta I'm
not going to provide a download link. As requested by IRC I ran an strace on
while whine was running, attached is that log. I also tested this with a clean
wine prefix and it affects no other applications.

[Bug 22415] WolfR4 Launcher (closed beta): Catches major wine bug, locks down entire OS

http://bugs.winehq.org/show_bug.cgi?id=22415

--- Comment #1 from Andrew Nguyen   2010-04-18 21:28:26 ---
If you're saying that running the launcher causes a hard system freeze stemming
from a kernel panic then that doesn't sound like a Wine bug, but rather a
problem with your (graphics) drivers or kernel.

[Bug 22415] WolfR4 Launcher (closed beta): Catches major wine bug, locks down entire OS

http://bugs.winehq.org/show_bug.cgi?id=22415

--- Comment #2 from Vitaliy Margolen   2010-04-18 23:08:18 ---
Start from actually describing the problem you are having.

Don't post straces - they are 100% useless. Attach complete terminal output
without any WINEDEBUG flags set.

[Bug 22415] WolfR4 Launcher (closed beta): Catches major wine bug, locks down entire OS

http://bugs.winehq.org/show_bug.cgi?id=22415

--- Comment #3 from Luke   2010-04-19 08:37:21 ---
Well, when I launch the program in wine it causes what I believe to be a kernel
panic as Andrew mentioned. As soon as revolt.exe is launched into memory, my
keyboard and mouse go completely unusable. Resulting in my only option which is
to hard shutdown the PC. I've already contacted #ubuntu about this, they don't
understand why I've been unable to get to a terminal using their emergency
keyboard command and therefor blame it on wine as the problematic program. I'm
unable to get a very good log for this very reason since as soon as the program
is launched my computer freezes up entirely and all windows simply become
non-responsive (including the terminal and virtual desktop window).

I'm not going to say it's not my graphics card, since I've had nothing but
trouble with ATI, but I've not had this with any of my other programs in or out
of wine and they all work perfectly. Blah.txt should be the non-debug you were
looking for, and that doesn't say much other than re-volt has a few minor
fixmes and it locks up.

I'm curious to see how I could get a debug on this due to the fact I will loose
control of my desktop as soon as the program is launched. The only option is
some type of logging parameter in the the terminal before the launch such as
"wine program.exe 2> foo.txt" (which doesn't really tell us much since it
crashes before completing the run of the program.

[Bug 22415] WolfR4 Launcher (closed beta): Catches major wine bug, locks down entire OS

http://bugs.winehq.org/show_bug.cgi?id=22415

--- Comment #4 from Austin English   2010-04-19 11:34:20 ---
Run your program with:
$ wine program.exe &> ~/log.txt

and attach the log.

[Bug 22415] WolfR4 Launcher (closed beta): Catches major wine bug, locks down entire OS

http://bugs.winehq.org/show_bug.cgi?id=22415

--- Comment #5 from Luke   2010-04-19 12:39:45 ---
Created an attachment (id=27459)
 --> (http://bugs.winehq.org/attachment.cgi?id=27459)
log.txt

Adding log as you mentioned, but I really don't see it as very helpful. After a
bit more testing I know it always crashes directly at the game menu only. I
also tried running a few debugs of wine itself with gdb, but I'm going to need
to get debugging symbols for wine which I haven't got at the moment. I'll try
to get them on my next install of wine. This also crashes winedbg without any
output, so whatever is going on I'm not able to get a readout before the kernel
stops logging...

[Bug 22415] WolfR4 Launcher (closed beta): Catches major wine bug, locks down entire OS

http://bugs.winehq.org/show_bug.cgi?id=22415

Jeff Zaroyko  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID

--- Comment #6 from Jeff Zaroyko   2010-04-19 20:44:50 ---
Resolving invalid.

If your system freezes, it's usually Wine triggering a bug in your video
driver.  Try updating to a newer version, if the problem still persists
consider filing a bug with nvidia.

You could also look at your dmesg or xorg log from the previous boot to see if
anything was written which may give a hint.

[Bug 22415] WolfR4 Launcher (closed beta): Catches major wine bug, locks down entire OS

http://bugs.winehq.org/show_bug.cgi?id=22415

Jeff Zaroyko  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #7 from Jeff Zaroyko   2010-04-19 20:45:04 ---
Closing invalid.