I'm guessing at Clutter for this, but IMBW. I've been trying to run the PokerStars software in wine, both 1.3.6-1 and 1.3.7-1 - 32-bit wine on 64-bit system, running in GNOME Shell, with nouveau driver.
With the installer, it starts off running fine, but when I hit the 'where to install' stage, the 'Next' button is missing and the default value has a variable in it - %SYSTEM_DRIVE or something. If I hit Browse and select a location that exists, as soon as I leave that dialog, the wine window disappears from view. At first I thought it had crashed, but it's still running, and when I go to the Activities view, I can actually see its thumbnail there - but I can't switch to it. Switching to it makes it pop up for a tiny amount of time (like a tenth of a second) and then disappear again; everything behaves as if it's there, the window I can actually see in its place is shown as inactive and clicks don't go to it; it's like the window is there, but invisible.
If I install the software in real Windows and then try to run it with wine from Fedora, it exhibits the same behaviour almost immediately - I see it log in, then when the login process is complete, the lobby window does the exact same disappearing trick. Again, I can see it in the thumbnail view on the Activities screen.
Nothing in /var/log/messages or /var/log/Xorg.0.log , but .xsession-errors has this:
Window manager warning: Log level 8: meta_display_unregister_x_window: assertion `g_hash_table_lookup (display->window_ids, &xwindow) != NULL' failed
Window manager warning: Log level 8: meta_display_register_x_window: assertion `g_hash_table_lookup (display->window_ids, xwindowp) == NULL' failed
(mutter:1922): GLib-GIO-WARNING **: Missing callback called fullpath = /home/adamw/.config/menus/settings.menu
(mutter:1922): GLib-GIO-WARNING **: Missing callback called fullpath = /home/adamw/.config/menus/gs-applications.menu
I think this is in fact gnome-shell (or possibly mutter) as the window manager is responsible for the positioning/painting of windows etc.
in that case, since f14 is using an ancient gnome-shell, I'll re-test with Rawhide soon and let you know if it still happens there.
Looks like it, indeed. In Rawhide, it's fine.
Are you interested in fixing this in F14 for the benefit of people who're running that release, or is it not worth the effort?
(In reply to comment #4)
> Looks like it, indeed. In Rawhide, it's fine.
> Are you interested in fixing this in F14 for the benefit of people who're
> running that release, or is it not worth the effort?
No, F14 is an (old) preview, and we won't be updating it.