https://bugs.winehq.org/show_bug.cgi?id=37959
Bug ID: 37959 Summary: Guild Wars 2 freezes on startup Product: Wine Version: 1.7.33 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: emailofchris@gmail.com Distribution: ---
Created attachment 50572 --> https://bugs.winehq.org/attachment.cgi?id=50572 Terminal output when running Guild Wars 2.
The launcher starts, but when I login and click Play, the music from the game begins to play but nothing is visible. Also I can't alt-tab out as GW2 keeps the focus, so I have to switch to a new tty in order to terminate it. With a virtual desktop, as recommended on the AppDB, it still won't start, but it does become easier to terminate it without a tty switch.
Using Arch Linux with KDE Plasma 5.
https://bugs.winehq.org/show_bug.cgi?id=37959
YAOMTC emailofchris@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |ArchLinux
https://bugs.winehq.org/show_bug.cgi?id=37959
Guillaume R guillaumeraffin@free.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |guillaumeraffin@free.fr
--- Comment #1 from Guillaume R guillaumeraffin@free.fr --- I've never had a problem like that (with wine 1.7.38). Is this still an issue ?
https://bugs.winehq.org/show_bug.cgi?id=37959
super_man@post.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |super_man@post.com
--- Comment #2 from super_man@post.com --- $ wine .wine/drive_c/Program\ Files\ (x86)/Guild\ Wars\ 2/Gw2.exe
You are not executing the program from the installed directory? Are you reusing the prefix created?
https://bugs.winehq.org/show_bug.cgi?id=37959
oneflame@windandflame.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |oneflame@windandflame.com
--- Comment #3 from oneflame@windandflame.com ---
--------------- Temporary Workaround: ---------------
Start winecfg, got to graphics, and select the "emulate desktop" option. (I used 1920x1080) ...
Launch the Guild Wars 2 launcher.
Once the "Play Button" is pressed, the latency issue disappears.
--------------- I have the same issue: --------------- wine 1.8 and 1.9 .... (staging w/CSMT enabled)
Fedora Workstation: Linux 4.2.8-300.fc23.x86_64 #1 SMP Tue Dec 15 16:49:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Fedora 23 x 64 Gnome 3.18 (Not Wayland) NVidia Proprietary Driver 361.16 Guild Wars 2 x 64
glxinfo | grep "OpenGL version" OpenGL version string: 4.5.0 NVIDIA 361.16
--------------- Perhaps Related Log Error: --------------- I haven't really noticed any unusual log entries that may explain the issue.
wine: Unhandled exception 0x80000003 in thread de at address 0x100a8f59 (thread 00de), starting debugger... p11-kit: couldn't load module: /usr/lib/pkcs11/p11-kit-trust.so: /usr/lib/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory p11-kit: couldn't load module: /usr/lib/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
https://bugs.winehq.org/show_bug.cgi?id=37959
sworddragon2@aol.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sworddragon2@aol.com
--- Comment #4 from sworddragon2@aol.com --- I'm also noticing freezes while the Launcher is visible. But this happens because something causes at this point the X.Org server to have a cpu usage of 100% on one core and nearly locking up until the Launcher closes and stays closed for a while (for example by starting the game and waiting a few seconds, depending on how long the Launcher was visible). Maybe somebody affected by such a freezing issue can check the cpu usage of the X.Org server for example by switching to the console.
https://bugs.winehq.org/show_bug.cgi?id=37959
Xen wine@xenhideout.nl changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wine@xenhideout.nl
--- Comment #5 from Xen wine@xenhideout.nl --- The Freeze-during launcher bug was solved for me with using 32-bit prefix and 32-bit program.
With 64-bit prefix the launcher uses 100% of one core in Xorg and 50% in another from gw2-64.exe and it stops refreshing the screen - the entire screen stops being redrawn. You can still launch the program by typing and clicking in the fields if you know where they are.
With 32-bit prefix, Xorg still uses a lot of CPU, but not 100%, and the system gets to be slow, but not so slow that nothing refreshes or redraws anymore.
https://bugs.winehq.org/show_bug.cgi?id=37959
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com
--- Comment #6 from winetest@luukku.com --- The (In reply to sworddragon2 from comment #4)
I'm also noticing freezes while the Launcher is visible. But this happens because something causes at this point the X.Org server to have a cpu usage of 100% on one core and nearly locking up until the Launcher closes and stays closed for a while (for example by starting the game and waiting a few seconds, depending on how long the Launcher was visible). Maybe somebody affected by such a freezing issue can check the cpu usage of the X.Org server for example by switching to the console.
This is bug 32010. Unless you all agree that this is actually the same bug.
https://bugs.winehq.org/show_bug.cgi?id=37959
--- Comment #7 from sworddragon2@aol.com --- (In reply to winetest from comment #6)
This is bug 32010. Unless you all agree that this is actually the same bug.
The issue I have noticed appeared much later than the linked reported issue and also that issue claims that the GW2 launcher causes the problematic cpu usage while in my case it is the X.org server which causes it. The last 2 comments of that ticket seem to be just appending to the X.org issue.
But I can't tell if they have maybe the same cause or if they are indeed 2 different issues and if the issue the creator of this ticket claims talks maybe about another total different issue.
Currently I would think that we have 3 issues cross-posted in 2 tickets. No idea if this is true and what should be done now.
https://bugs.winehq.org/show_bug.cgi?id=37959
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #8 from joaopa jeremielapuree@yahoo.fr --- Is still a bug in current wine (3.19)?
https://bugs.winehq.org/show_bug.cgi?id=37959
Yao Mitachi yaomtcmail@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED
--- Comment #9 from Yao Mitachi yaomtcmail@gmail.com --- Yup, looks like it was fixed at some point in the past few years. Forgot about this.
https://bugs.winehq.org/show_bug.cgi?id=37959
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #10 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 3.21.
-
wine-bugs＠winehq.org