Bug 70804 - Wine games not properly maximized
Summary: Wine games not properly maximized
Status: RESOLVED DUPLICATE of bug 73509
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-12-19 05:10 UTC by cnlobracco
Modified: 2004-02-07 21:13 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Demonstration of the problem (99.91 KB, image/jpeg)
2003-12-19 19:49 UTC, cnlobracco
Details

Note You need to log in before you can comment on or make changes to this bug.
Description cnlobracco 2003-12-19 05:10:27 UTC
Version:            (using KDE KDE 3.1.94)
Installed from:    Gentoo Packages
Compiler:          gcc version 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r3, propolice) 
OS:          Linux

Whenever a game is run in Wine/WineX in KDE 3.2 beta 2, it is not maximized to the entire screen.  It only occupies the upper left corner of the screen, and often fails to receive mouse input.  This issue is unrelated to Wine/WineX, as the games work correctly in twm and Gnome.  This worked correctly in KDE 3.1.4.  This happens consistently when attempting to a game using Wine.  The version of WineX used is 3.2.1, though it did not work with 3.1.1 either.
Comment 1 Lubos Lunak 2003-12-19 13:10:34 UTC
Just because it works with twm and gnome it's is no proof it's not the app's fault, especially when the app is Wine. Could you please post a screenshot of the problem, and provide a list of games which exhibit this problem (freely available ones preferably)?
Comment 2 cnlobracco 2003-12-19 19:49:38 UTC
Created attachment 3783 [details]
Demonstration of the problem
Comment 3 cnlobracco 2003-12-19 20:24:25 UTC
I have tested with these games:
Half-Life and mods of it are as seen in the screenshot posted.
WarCraft III, Frozen Throne, and StarCraft work correctly. (Fullscreen)
For GTA3:VC, the display appears to go between fullscreen and Windowed.  I was unable to find my CD to test it completely.  However, another interesting thing:  When the game was closed by pressing Escape, Wine closed succesfully but the KDE window was maintained and was unable to be closed.  It closed itself when another Wine game was run.
I regret that none of these games are free in either sense of the word.  The different actions of differing applications don't give a clear picture of which component is working unexpectedly.  However, this was not an issue in 3.1.4, and nothing else has changed in my configuration.
Comment 4 cnlobracco 2003-12-20 03:52:01 UTC
Follow up:  GTA3 Vice does work correctly.
Comment 5 cnlobracco 2003-12-20 06:38:52 UTC
Interestingly, in order for the Half-Life window to come up at all, the script to run WineX on the windows executable must be run twice.  The first time it prints debug info and weights.  If invoked again while already running, it comes up as seen in the screenshot.  This is the log that is produced by running the script twice, that yields the non-fullscreen window.

fixme:midi:OSS_MidiInit Synthesizer support MIDI in. Not supported yet (please report)
fixme:reg:RegFlushKey (64): stub
fixme:ddraw:Main_DirectDraw_SetCooperativeLevel (0x403b2b6c)->(00000000,00000008)
fixme:ddraw:Main_DirectDraw_SetCooperativeLevel (0x403b312c)->(00000000,00000008)
fixme:ddraw:Main_DirectDraw_SetCooperativeLevel (0x403b312c)->(00000000,00000013)
fixme:ddraw:Main_DirectDraw_SetCooperativeLevel (0x403b312c)->(00000000,00000008)
fixme:ddraw:Main_DirectDraw_SetCooperativeLevel (0x403b312c)->(00010021,00000013)
fixme:dc:LockWindowUpdate (10021), stub!
fixme:dc:LockWindowUpdate (0), stub!
fixme:dc:LockWindowUpdate (10021), stub!
fixme:dc:LockWindowUpdate (10021), stub!
fixme:dc:LockWindowUpdate (0), stub!
fixme:dc:LockWindowUpdate (0), stub!
fixme:dc:LockWindowUpdate (10021), stub!
fixme:dc:LockWindowUpdate (0), stub!

The second run only produces the first two lines of this.
Comment 6 Lubos Lunak 2004-02-07 21:13:56 UTC
I belive this has been fixed for KDE3.2.1, please reopen if you'll be able to reproduce the problem with that version.


*** This bug has been marked as a duplicate of 73509 ***