Bug 42911

Summary: fullscreen doesn't work in non-kde apps
Product: [Plasma] kwin Reporter: Anonymous Coward <coward>
Component: generalAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Mandrake RPMs   
OS: Linux   
Latest Commit: Version Fixed In:

Description Anonymous Coward 2002-05-21 23:06:16 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           kwin
Version:           KDE 3.0.0 
Severity:          normal
Installed from:    Mandrake RPMs
Compiler:          gcc 3.0.4
OS:                Linux
OS/Compiler notes: Not Specified

KWin behaves a bit weirdly when non-KDE app will try to maximize itself to fullscreen. What happens is that the window is maximized to full desktop size but window decorations are not hidden (even though the app properly sets MWM hints!) and the window is placed *under* Kicker. This affects for example Galeon or MPlayer  (i.e. both based on GTK+). It seems that KWin ignores the hints once the window was created (say when the window is hidden hints changed and the window shown again which is what happens in GTK+).

I understand fullscreening is not standardized but all other WMs I tried behave correctly (WindowMaker Sawfish IceWM Blackbox). It would be really nice if KWin could be nicer in this respect...

(Submitted via bugs.kde.org)
Comment 1 Lubos Lunak 2002-10-24 19:23:39 UTC
 #49350 is maybe a duplicate of this. 
 
Comment 2 Anonymous Coward 2002-10-24 21:55:18 UTC
I don't think so: #49350 submitter mentions it didn't happen before, when he had
KDE 3.0.3. This one happens in all KDE 3.x versions.
Comment 3 Lubos Lunak 2003-07-01 18:00:52 UTC
xprop shows on difference between normal and fullscreened Galeon-1.2.8, and it doesn't work 
with gnome-2.2 either. GMPlayer-0.90rc4 works fine with KDE-3.1.2. 
-> closing 
 
 
Comment 4 David Cornish 2003-07-05 12:23:23 UTC
What about Mozilla Firebird then?  This distinctly doesn't seem to work with 
KDE which seems to be a KDE problem - see comment #15 on
http://bugzilla.mozilla.org/show_bug.cgi?id=179043