Wine 1.1.44 and WoW 3.3.5 crash

[Altair]

Similar case with the other recent post about this.

World of Warcraft 3.3.5, just after install the new game patch
Graphics: nVidia Corporation GeForce 7600 GT (rev a2)
Driver: NVIDIA-Linux-x86-195.36.31-pkg1.run, the more recent now
WIne 1.1.44, more recent versions have graphics errors for me
Debian Lenny

The console output after the crash is VERY long:

wine: Unhandled page fault on write access to 0x00000000 at address 0x9668253 (thread 0009), starting debugger...
Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x09668253).
Register dump:
CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b
EIP:09668253 ESP:0195ede4 EBP:0195ee08 EFLAGS:00210246( R- -- I Z- -P- )
EAX:00000000 EBX:00000000 ECX:002001c2 EDX:00000000
ESI:09668298 EDI:00000002
Stack dump:
0x0195ede4: 00000002 00dced40 00000001 00000000
0x0195edf4: 3d04a13f 3d6ba420 3ce699d1 009c250d
0x0195ee04: 009c2851 0195ee24 009c0a61 0195ee40
0x0195ee14: 09668298 00000002 0195f288 09667080
0x0195ee24: 0195f578 008c7aa2 096199b0 0195ee40
0x0195ee34: 00b6aa40 09667080 00000000 00000020
Backtrace:
=>0 0x09668253 (0x0195ee08)
1 0x009c0a61 in wow (+0x5c0a60) (0x0195ee24)
2 0x008c7aa2 in wow (+0x4c7aa1) (0x0195f578)
3 0x008c9041 in wow (+0x4c9040) (0x0195f608)
4 0x006b2ba9 in wow (+0x2b2ba8) (0x0195fb1c)
5 0x004d8b2f in wow (+0xd8b2e) (0x0195fb3c)
6 0x004dc2a6 in wow (+0xdc2a5) (0x0195fb50)
7 0x0085651c in wow (+0x45651b) (0x0195fb6c)
8 0x0085898a in wow (+0x458989) (0x0195fbf8)
9 0x008567e7 in wow (+0x4567e6) (0x0195fc14)
10 0x0084ec46 in wow (+0x44ec45) (0x0195fc28)
11 0x00855b33 in wow (+0x455b32) (0x0195fc84)

200 lines only in this section of errors. Other parts:

Modules:
Module Address Debug info Name (112 modules)
PE 400000- dfd000 Export wow
PE 10000000-10069000 Deferred divxdecoder
PE 3c8f0000-3d7e3ee1 Deferred battle.net
PE 78130000-781cb000 Deferred msvcr80
ELF 78e90000-78f23000 Deferred crypt32<elf>
\-PE 78ea0000-78f23000 \ crypt32
ELF 78f23000-78fa6000 Deferred msvcrt<elf>
\-PE 78f30000-78fa6000 \ msvcrt
ELF 7a94f000-7a974000 Deferred winhttp<elf>
\-PE 7a960000-7a974000 \ winhttp
ELF 7a974000-7a99a000 Deferred wldap32<elf>
\-PE 7a980000-7a99a000 \ wldap32
ELF 7bc75000-7bc89000 Deferred libresolv.so.2
ELF 7bc89000-7bcc6000 Deferred wineoss<elf>
\-PE 7bc90000-7bcc6000 \ wineoss
ELF 7bdc6000-7bf00000 Deferred wined3d<elf>

etc, and other parts:

Threads:
process tid prio (all id:s are in hex)
00000008 (D) Z:\home\user\World of Warcraft\Wow.exe
00000031 0
00000030 0
0000002f 0
0000002e 0
0000002d 2
0000002c 15
0000002b 15
00000029 0
00000028 0
00000027 2
00000026 15
00000023 2
00000022 15
0000001f 15
0000001c 0
0000001b 0
00000009 0 <==
0000000e services.exe
00000016 0
00000015 0
00000014 0
00000010 0
0000000f 0
00000011 winedevice.exe
00000018 0
00000017 0
00000013 0
00000012 0
00000019 explorer.exe
0000001a 0

[James McKenzie]

Altair wrote:

Similar case with the other recent post about this.

World of Warcraft 3.3.5, just after install the new game patch
Graphics: nVidia Corporation GeForce 7600 GT (rev a2)
Driver: NVIDIA-Linux-x86-195.36.31-pkg1.run, the more recent now
WIne 1.1.44, more recent versions have graphics errors for me
Debian Lenny

The console output after the crash is VERY long:

THIS IS A KNOWN PROBLEM. Please folks, try what is in the forums BEFORE
you post a message like this. nVidia video drivers 195.27 and up ARE
BROKEN UNDER WINE. You have to back level them to 195.26 OR LOWER.

If, after doing this, problems still appear, please look through our
Bugzilla. Then and ONLY THEN post messages here.

NOT TO BYTE YOUR HEAD OFF, BUT THIS THE FIFTH MESSAGE LIKE THIS IN THE
LAST 24 HOURS.

James McKenzie

[Jim Hall]

This is kind of strange. Mine is also Lenny, Nvidia 9600 GT, driver

256.35.

Wine version is 1.1.42. Game works just fine. Wish I could tell you why.

Interesting as well. Seems this appears with a certain combination of
'stuff'.
One: The lastest/greatest kernel beta build.
Two: Wine 1.1.44 or higher.
Three: The lack of a package built about a month ago.
Four: nVidia video card drivers 256.35. The older 195 drivers work.

However, I do stand by my statement to PLEASE look through the forum and
bugzilla BEFORE posting a 'me too' message. This is highly irritating and
shows absolutely NO EFFORT on the part of the poster to try and get their
problem fixed. Maybe this is the Microsoft mentality, but come on folks we
are volunteers and we would really love to fix bugs rather than answer the
same question for the fifth, tenth or even twentith time in a day (yes, it
was that bad...)

Maybe another sticky in is in for this problem....

James McKenzie

Sorry about the reply mix-up

However, mine seems to be a bit off on your list.

One: "The lastest/greatest kernel beta build." **Lenny is certainly not
that - so I'm safe there.
Two: " Wine 1.1.44 or higher." **I never saw 1.1.44, Still using 1.1.42 - so
I'm safe there.
Three: "The lack of a package built about a month ago." **I don't know
which package you're reffereing to, so I don't know if I have it or not.
Four: "nVidia video card drivers 256.35. The older 195 drivers work." **I
use 256.35. What is different about my system that I can use it?

Does any one of these prevent the problem? Is my One and Two the key, or is
Three alone the key? Does the combination of One, Two, and Three allow me to
do Four? I wish I had the answer.

Jim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-us ... chment.htm>

[James McKenzie]

Jim Hall wrote:

This is kind of strange. Mine is also Lenny, Nvidia 9600 GT, driver

256.35.

Wine version is 1.1.42. Game works just fine. Wish I could tell you why.

Interesting as well. Seems this appears with a certain combination of
'stuff'.
One: The lastest/greatest kernel beta build.
Two: Wine 1.1.44 or higher.
Three: The lack of a package built about a month ago.
Four: nVidia video card drivers 256.35. The older 195 drivers work.

However, I do stand by my statement to PLEASE look through the forum and
bugzilla BEFORE posting a 'me too' message. This is highly irritating and
shows absolutely NO EFFORT on the part of the poster to try and get their
problem fixed. Maybe this is the Microsoft mentality, but come on folks we
are volunteers and we would really love to fix bugs rather than answer the
same question for the fifth, tenth or even twentith time in a day (yes, it
was that bad...)

Maybe another sticky in is in for this problem....

James McKenzie

Sorry about the reply mix-up

However, mine seems to be a bit off on your list.

One: "The lastest/greatest kernel beta build." **Lenny is certainly not
that - so I'm safe there.
Two: " Wine 1.1.44 or higher." **I never saw 1.1.44, Still using 1.1.42 - so
I'm safe there.
Three: "The lack of a package built about a month ago." **I don't know
which package you're reffereing to, so I don't know if I have it or not.
Four: "nVidia video card drivers 256.35. The older 195 drivers work." **I
use 256.35. What is different about my system that I can use it?

Does any one of these prevent the problem? Is my One and Two the key, or is
Three alone the key? Does the combination of One, Two, and Three allow me to
do Four? I wish I had the answer.

Jim:

I picked this up on a different thread and may only apply to Ubuntu:

dimesio wrote:

... be caused by not having installed the necessary 32 bit parts on a 64 bit system.

It was not the problem, we all have the 32 libs installed, it was just a bug with the package (apparently). With the 5th release lib32-nvidia-utils, it works >
great.

Looks like Cr0k may have found one of many solutions....

James McKenzie

[dimesio]

Interesting as well. Seems this appears with a certain combination of
'stuff'.
One: The lastest/greatest kernel beta build.
Two: Wine 1.1.44 or higher.
Three: The lack of a package built about a month ago.
Four: nVidia video card drivers 256.35. The older 195 drivers work.

It is not a combination. You are conflating unrelated problems.

One: A kernel bug exposed by Wine and a recent WoW patch
http://bugs.winehq.org/show_bug.cgi?id=23323
https://bugzilla.kernel.org/show_bug.cgi?id=16315

Two: A change in winex11 in 1.1.43 that exposed a bug in the nVidia 185.xx.xx drivers. The fix for that is to upgrade to the 195 or later drivers. http://bugs.winehq.org/show_bug.cgi?id=22426

Three: I have no idea what package you are talking about, unless it's the lib32-nvidia-utils package that caused problems for Arch Linux users. Lots of people report problems caused by various missing packages. They are not all related.

Four: I have seen no evidence of this on the forum, and I read it every day. The only report of any problem with this driver came from the aforementioned Arch Linux users, and that was a distro package problem. If Wine were really "broken" under the 256 driver I would expect to see a lot of posts about it.

[Jim Hall]

Jim:

I picked this up on a different thread and may only apply to Ubuntu:

dimesio wrote:

... be caused by not having installed the necessary 32 bit parts on a 64
bit system.

It was not the problem, we all have the 32 libs installed, it was just a

bug with the package (apparently). With the 5th release lib32-nvidia-utils,
it works >
great.

Looks like Cr0k may have found one of many solutions....

James McKenzie

Yes, I saw that. I checked and I don't have that installed (it's not even in
repository). I run plain vanilla 32 bit, so that wouldn't have come up for
me, especially if it turns out to be Ubuntu only. Curious

Jim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-us ... chment.htm>

[James McKenzie]

Jim Hall wrote:

Jim:

I picked this up on a different thread and may only apply to Ubuntu:

dimesio wrote:

... be caused by not having installed the necessary 32 bit

parts on a 64 bit system.




It was not the problem, we all have the 32 libs installed, it
was just a bug with the package (apparently). With the 5th
release lib32-nvidia-utils, it works >
great.


Looks like Cr0k may have found one of many solutions....

James McKenzie




Yes, I saw that. I checked and I don't have that installed (it's not
even in repository). I run plain vanilla 32 bit, so that wouldn't have
come up for me, especially if it turns out to be Ubuntu only. Curious

Interesting. Rosanne Dimensio has brought up a few things and I agree
that they may make a difference:

1. There is a kernel version that broke things. There is a patch on
www.kernel.org that fixes the problem and it is scheduled for
incorporation into a to-be-published kernel real-soon-now.
2. There was a problem that started with Wine 1.1.43 that affects WoW
(and I suspect other games.)
3. There have been reports of problems with the latest release of
nVidia's Linux Drivers. I remember that Ubuntu and Arch Linux users
were affected, but this may affect Fedora and other releases.
4. The lib32-nvidia-utils package I mentioned. This may not come with
Debian or even Fedora.

Any or one of these could cause breakage. The key is to try one (say
backing down kernel levels, trying an older version of Wine, trying a
different version of video drivers, etc.) and see what happens. In your
case, you are using Wine 1.1.42. Maybe upgrading to Wine 1.2-rc6 (when
it becomes available) might cause breakage. Maybe updating the Linux
Kernel will cause breakage. Maybe it won't.

The key is that one should be very careful when upgrading and ALWAYS
have a backup of a working system to fall back on and to restore to.
(Macs sort of make this easy, its called Time Machine and I use it.)

The point that I'm trying to get across is that this information is
contained in several threads and that this needs to be consolidated into
one message and that the message be accurate. Mine was confusing and
contained missing facts. I'll own up to that. However, three of the
four items I mentioned did come from other threads and the last one I
found today. The fixes may or may not apply to your system, but it
never hurts to try some of them. You would be amazed at what I've found
fixes things.

WOW Users:

For those who are experiencing World of Warcraft errors, or problems
with other Blizzard games, please do a little research before posting.
WoW 3.3.5 update broke things and makes the game unplayable on some
systems. Earlier versions of WoW do work, but may encounter problems
connecting to some servers and some servers will automatically update
you. Please do search through and read some of the lengthy threads for
ideas on how to attempt to get WoW working with the latest versions of Wine.

Thank you.

[emsy]

Hello, i'm just throwing a little more info about what's happening to me

Gentoo: 2.6.31-gentoo-r10 - 2.6.33-gentoo-r2 (didn't seem to affect the game)
Card: nVidia 9800GTX+
WoW: 3.3.2-3.3.3a (no effect on performance)
Wine: 1.2-rc* (no effect on performance)
Nvidia drivers (http://packages.gentoo.org/package/x11- ... ia-drivers) 190.53-r1 works just fine, upgrading to 195.* makes my X freeze at random time after launching and playing WoW. Mouse and keyboard do not respond, killing X through remote ssh doesn't help either. I did not try 256.35 yet, since those are hardmasked atm, but i'm hoping that this bug is not present in this "new generation"

all in all it looks like (as staed in the first reply in this post) the only problem are drivers 195.27+ which broke more than just 3.3.5 version of wow