When running world of warcraft in fullscreen mode none of the graphics are
rendered except for the cursor. This only seems to happen when running WoW at a
resolution other than it's default (800x600)
Steps to Reproduce:
1. run WoW in fullscreen mode
The game launches, but all that loads is a black screen and the cursor.
The game should be rendered instead of a black screen.
The game seems to load properly as sounds are working, including sounds when
mousing over buttons (even though you can't see the buttons).
The problem goes away if xfdesktop is killed before running WOW.
I have tested this with both gnome and kde, so I believe the problem can be
pinpointed to xfdesktop.
I have found a problem relating to another cedega app. When running halflife 2,
again, only when the game is not running at it's default res, keyboard input
This behavior likewise disappears when xfdesktop is not running, and does not
happen in gnome/kde.
I'm not sure that this has anything to do with Xfce. Do you have the X
composite extension enabled? This has been known to cause problems with GL apps.
(In reply to comment #2)
> I'm not sure that this has anything to do with Xfce. Do you have the X
> composite extension enabled? This has been known to cause problems with GL apps.
I don't have composite enabled, anything else I can do to check if this is an
xfce problem or not?
this is not a problem in gnome, which is why I assumed it was an xfce problem.
I'm affraid that I will not be able to reproduce that (I don't have that game)
There are a couple of things you can try though:
1) Use metacity instead of xfwm4 in Xfce
From a terminal, "killall xfwm4 && metacity&" - Does that fix the issue?
2) From GNOME or KDE, run xfdesktop - Does the problem shows there?
Okay, so I tried running metacity, and that fixed the problem. The weird thing
is though, that switching back to xfwm4, the problem seems to have disappeared
there as well.
So maybe this really isn't a problem, I don't know.
The keyboard input problem in halflife 2 has not gone away however.
Another thing I have noticed with xfwm4, is that I believe when running a full
screen app in xinerama mode. The second monitor shuts off, but I believe a
virtual desktop of full size is still being drawn.
The reason I think this is that, when running saw WoW (or any game), my second
display shuts off, like it should, but the xfce desktop is still displayed until
I drag the mouse to the right of the screen (just as if there were a virtual
size of both screens, in my case 2560x1024). and the game is drawn on the right
This is just a guess, but I have also noticed a framerate drop when using xfwm4
as compared to other window managers, this seems logical if the above it true.
WoW does give metacity this error, though, perhaps it has something to do with
Window manager warning: Window 0x1c00004 (World of W) sets an MWM hint
indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x
2147483647; this doesn't make much sense.
although it seems to handle the situation alright.
Okay, one additional piece of info. The keyboard problem I was seeing in
halflife 2, does not go away when switching to metacity in xfce4. But the
problem does show up when running xfdesktop under gnome.
Okay here are some more errors, I get these in both WoW and halflife 2:
** (xfwm4:7449): WARNING **: Unmanaged net_wm_state (window 0x2800004)
And these just with halflife 2:
(xfdesktop:7445): Gdk-CRITICAL **: gdk_screen_get_monitor_geometry: assertion
`monitor_num < GDK_SCREEN_X11 (screen)->num_monitors' failed
(xfdesktop:7445): GdkPixbuf-CRITICAL **: gdk_pixbuf_copy_area: assertion `dest_x
>= 0 && dest_x + width <= dest_pixbuf->width' failed
From what I saw, cedega (winex as it was called by that time) does odd things
with windows to emulate the ActiveX behaviour. This breaks on many window
managers, and mostly works with Xfce, but I'm affraid I couldn't get things
working any better (looks like there are race conditions in the application
itself, maybe I'm wrong)
All I can suggest is to try the latest snapshots from
but I doubt that will fix that specific problem.
Okay, I will give that a try. If that doesn't work perhaps I will do some more
debugging and see if I can't pin point this problem further.
(In reply to comment #11)
> Okay, I will give that a try. If that doesn't work perhaps I will do some more
> debugging and see if I can't pin point this problem further.
No reply since 2005-03-30... Assuming this is fixed...