http://bugs.winehq.org/show_bug.cgi?id=23592
Summary: EverQuest II: Crashes when full-screen mode is enabled Product: Wine Version: 1.2-rc7 Platform: x86 URL: http://everquest2.com/freeTrial.vm OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: cww@denterprises.org
If, when playing EverQuest II, the display mode is switched from windowed mode to full-screen mode, EverQuest II crashes.
If the game starts in full-screen mode, it does not crash, but the screen remains black until the user alt-tabs. At which point, EverQuest II window-ifys itself, and the game begins.
http://bugs.winehq.org/show_bug.cgi?id=23592
--- Comment #1 from Colin Wetherbee cww@denterprises.org 2010-07-10 03:42:41 --- Created an attachment (id=29492) --> (http://bugs.winehq.org/attachment.cgi?id=29492) Wine output
This is the very basic Wine output and crash log from EQ2. It probably won't help too much; please let me know what else is required to start debugging this.
http://bugs.winehq.org/show_bug.cgi?id=23592
--- Comment #2 from Jeff Zaroyko jeffz@jeffz.name 2010-07-10 03:46:19 --- looks like bug 18746?
http://bugs.winehq.org/show_bug.cgi?id=23592
--- Comment #3 from Vitaliy Margolen vitaliy@kievinfo.com 2010-07-10 10:18:11 --- err:x11settings:X11DRV_ChangeDisplaySettingsEx No matching mode found 1920x1080x32 @0! (XRandR)
Please post output of 'xrandr' command.
http://bugs.winehq.org/show_bug.cgi?id=23592
--- Comment #4 from Colin Wetherbee cww@denterprises.org 2010-07-10 16:18:19 --- (In reply to comment #3)
err:x11settings:X11DRV_ChangeDisplaySettingsEx No matching mode found 1920x1080x32 @0! (XRandR)
Please post output of 'xrandr' command.
I run a dual-head configuration, managed by the NVIDIA utilities. 3840x1080 represents my full desktop.
Screen 0: minimum 3840 x 1080, current 3840 x 1080, maximum 3840 x 1080 default connected 3840x1080+0+0 0mm x 0mm 3840x1080 50.0*
http://bugs.winehq.org/show_bug.cgi?id=23592
--- Comment #5 from Colin Wetherbee cww@denterprises.org 2010-07-10 16:19:36 --- (In reply to comment #2)
looks like bug 18746?
I believe this is a different issue. I am able to change the window size at will.
http://bugs.winehq.org/show_bug.cgi?id=23592
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #6 from Vitaliy Margolen vitaliy@kievinfo.com 2010-07-10 16:49:48 --- Invalid - your config does not support required resolution. Refer to Nvidia readme/Xorg documentation on how to properly set them up so they show all resolutions.
http://bugs.winehq.org/show_bug.cgi?id=23592
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #7 from Vitaliy Margolen vitaliy@kievinfo.com 2010-07-10 16:49:59 --- Closing - invalid configuration.
http://bugs.winehq.org/show_bug.cgi?id=23592
--- Comment #8 from Colin Wetherbee cww@denterprises.org 2010-07-10 18:41:40 --- (In reply to comment #6)
Invalid - your config does not support required resolution. Refer to Nvidia readme/Xorg documentation on how to properly set them up so they show all resolutions.
Shouldn't the application be trying to switch to 3840x1080 instead of 1920x1080, though?
I guess I'm not completely familiar with the magic of dual-head configurations.
http://bugs.winehq.org/show_bug.cgi?id=23592
--- Comment #9 from Colin Wetherbee cww@denterprises.org 2010-07-10 18:44:14 --- Also, this apparently happens to those who are *not* running dual-head configurations. Their logs may show some more telling evidence than mine.
http://appdb.winehq.org/commentview.php?iAppId=9400&iVersionId=20511&...
http://bugs.winehq.org/show_bug.cgi?id=23592
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |INVALID
--- Comment #10 from Dmitry Timoshkov dmitry@codeweavers.com 2010-07-11 02:47:22 --- Invalid, not fixed.