Bug 2818 - maximizing a window in current kde moves titlebar off-screen
Summary: maximizing a window in current kde moves titlebar off-screen
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
: 3305 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-09-23 16:05 CEST by Frank Griffin
Modified: 2011-12-16 18:42 CET (History)
5 users (show)

See Also:
Source RPM: kde
CVE:
Status comment:


Attachments
screenshot of maximized window exhibiting the problem (182.69 KB, image/png)
2011-09-28 15:10 CEST, Frank Griffin
Details
screenshot of desktop to the right (758.91 KB, image/jpeg)
2011-09-28 15:21 CEST, Frank Griffin
Details
screenshot of VLC *not* exhibiting the problem (77.83 KB, image/png)
2011-09-28 15:30 CEST, Frank Griffin
Details
rpmdrake maximised (236.33 KB, image/png)
2011-09-28 15:30 CEST, John Balcaen
Details

Description Frank Griffin 2011-09-23 16:05:07 CEST
As per summary.  In the current cauldron KDE, maximizing a window embeds the application window in a frame larger than the screen.  The frame has grey space between the titlebar and the top of the application window which forces the titlebar off-screen, and grey space to the left and right of the window which spills into adjacent desktops.

What actually seems to have happened is that the titlebar is now vertically larger than the single line needed for the title and min/max/close widgets.  The portion still on the screen is blank, but can be "grabbed" by the mouse and dragged down to make the top of the titlebar visible.

I'm not KDE-knowledgeable enough to know the component name of the KDE window manager, which is probably where this should be assigned.  

This behavior is new in the past 2 weeks.  I didn't update from Sep 9 - Sep 16, and then when I did, getting the new grey titlebars that don't change color when the window gets focus, this behavior showed up as well.

My guess is that the maximize request is (1) expanding the insets around the application window for some reason, and (2) telling the application that it now owns the entire screen for itself, rather than accounting for the enclosing frame.
Comment 1 Frank Griffin 2011-09-23 22:03:38 CEST
It seems this doesn't happen unilaterally.  It happens with firefox, thunderbird, dolphin, and konsole, but not (for some reason) with vlc.
Remco Rijnders 2011-09-28 10:35:56 CEST

CC: (none) => balcaen.john

Comment 2 John Balcaen 2011-09-28 12:07:26 CEST
could you provides us a screenshot, the graphic card used & eventually if graphics effects are enable or not ?
Comment 3 Frank Griffin 2011-09-28 12:57:35 CEST
The video card is a  âRadeon HD 3300 Graphics, but I  don't think tat's pertinent, because further testing shows that this does *not* happen on a laptop with a  âRadeon HD 3200 Graphics chip.  The difference is that the laptop X configuration specifies "Automatic" screen detection, something like 1400x900, while the desktop machine where the problem occurs uses an old 19" flatscreen through a KVM, and specifies Flat Screen 1024x1280 for the monitor type.

This has been the case for a while; the problem only showed up with the new KDE motif (grey titlebars).

Graphics effects are enabled.  I'll get a screenshot later today.
Comment 4 John Balcaen 2011-09-28 13:06:49 CEST
Well the graphic card is pertinent because it could be a bug in a foss driver (which can be fixed) or in a proprietary driver (for example nvidia or fglrx) which can't always be fixed that's why i'm asking.
And what's this « new kde motif » you're talking about ?
Comment 5 Frank Griffin 2011-09-28 13:24:37 CEST
I meant "pertinent" only as regards this issue, since the problem doesn't occur on a system with a virtually identical card using the same driver (which, of course, you couldn't know when you posed the question).

As for the "new motif", the prior KDE WM used a window titlebar that turned blue when the window had focus, and used "_" for minimize and two superimposed rectangles for maximize.  The current WM has more of a grey metal look, doesn't change when the window gets focus, and uses ^ and its downward pointing equivalent for maximize and minimize.

Sorry to be so ignorant of KDE component terminology, but I only fled to KDE when GNOME3 arrived.
Comment 6 Frank Griffin 2011-09-28 15:10:50 CEST
Created attachment 850 [details]
screenshot of maximized window exhibiting the problem

Note that the top edge has no title or window manipulation widgets.  These are actually above the visible portion.  You can see this if you grab what there is of the titlebar and drag it downward; the left top and right top of the window are pinned, but the titlebar and window deform under compiz to have the actual title string and widgets dragged to the visible part of the screen.

Unfortunately, screenshot doesn't work while I hold the window deformed with the mouse, and when I release it, it snaps back to the original state.
Comment 7 Frank Griffin 2011-09-28 15:21:36 CEST
Created attachment 851 [details]
screenshot of desktop to the right

Note that the left side of the screen contains a grey area which is spillover from the right side of the maximized window.  

Oddly enough, this happens differently with the left side of the maximized window.  If you switch to the desktop to the left, you will see a similar grey area on the right side of the screen, but it disappears almost immediately.
Comment 8 Frank Griffin 2011-09-28 15:30:00 CEST
Created attachment 852 [details]
screenshot of VLC *not* exhibiting the problem

I have no idea why VLC should be immune.  It's the only thing so far that is.
Comment 9 John Balcaen 2011-09-28 15:30:39 CEST
Created attachment 853 [details]
rpmdrake maximised

i can't reproduce here.
I do have the the window manipulation widgets too in a maximized window.
Also i read that you mention compiz, are you using compiz in fact instead of kwin here ?
I did noticed also from your screenshot that you do have plf media available.
On a sidenote I'm not sure it's wise to use plf media on mageia since buildsystem used quite different (Mageia is quite different than mandriva 2011 for the BS environnement)
Comment 10 John Balcaen 2011-09-28 15:32:31 CEST
Are you able to reproduce with the xguest user ?
Because it might be a problem with your configuration( now why? i don't know :/ )
Comment 11 Frank Griffin 2011-09-28 15:38:06 CEST
(In reply to comment #9)

> Also i read that you mention compiz, are you using compiz in fact instead of
> kwin here ?

I think I'm using them both.  In addition to the compiz effects, I also see "exploding window" effects.  I'll try turning one or the other off.

> I did noticed also from your screenshot that you do have plf media available.
> On a sidenote I'm not sure it's wise to use plf media on mageia since
> buildsystem used quite different (Mageia is quite different than mandriva 2011
> for the BS environnement)

Yes, I haven't reinstalled this system since before tainted was available/populated.  I've since changed my post-install stuff to eliminate plf.
Comment 12 John Balcaen 2011-09-28 15:53:26 CEST
(In reply to comment #11)
> (In reply to comment #9)
> 
> > Also i read that you mention compiz, are you using compiz in fact instead of
> > kwin here ?
> 
> I think I'm using them both.  In addition to the compiz effects, I also see
> "exploding window" effects.  I'll try turning one or the other off.
> 
Well if you're using compiz as windows manager the kwin's effect should not work at all since you can have only one windows manager running so either you're using compiz effects either you're using kwin's one not both.
Anyway i'm not sure it should affect this problem here because your screenshot of rpmdrake for example is really different than mine.
Also attachement 851 is quite strange & probably not related with compiz/kwin issue.
it's really strange and would be nice to know if if you can reproduce with the xguest user or eventually it's just a user configuration problem.
Comment 13 Frank Griffin 2011-09-28 16:19:14 CEST
The culprit is compiz, with or without KDE compatibility checked in the CompizConfiguration.

I also tried using a fresh account and had the same result: compiz on, problem occurs, compiz off, no problem.

I didn't realize compiz was a full WM; I thought it just layered 3D on top of whatever WM you were using.  It's odd that the appearance of the titlebar and titlebar widgets is the same whether compiz is on or off.  I thought that the new titlebar motif was related to KDE.

Should compiz work with KDE ?  If so, is this a compiz bug or a KDE bug ?  The compiz RPM is dated Sep13, so a change there would be in the correct timeframe for this bug.
Comment 14 John Balcaen 2011-09-28 17:06:44 CEST
Do you have the same problem regarding attachement 851 with compiz ?
I would not expect to be compiz related for this one.

Regarding the titlebar it's a compiz bug/functionnality not a kde one since compiz is working here as the windows manager.

I'm adding compiz maintainer in cc so he can give his opinion

One more thing how did you configure compiz in kde ?
via systemsettings ? or via drak3d ?

CC: (none) => julien.moragny

Comment 15 Frank Griffin 2011-09-29 16:06:32 CEST
I didn't configure it at all, just turned it on in drak3d.

It appears to me that compiz is working in tandem with kwin, because if I turn compiz off, open kwin configuration, and turn on Exploding Windows, I get a popup when I click Apply that says the Exploding Windows plugin can't be activated.  If I turn compiz back on, no error results.  So I'm guessing that kwin expects to be using the compiz 3d stuff if available.

Re 851,this only happens with compiz on.  I suspect that what is happening is that the inset size for the full window in which the application window is embedded is being computed incorrectly, and that all four sides have too much inset space.  You can't see it on the bottom because the bottom doesn't spill into another desktop.  Nor does the top, but it's obvious there because the titlebar text has been pushed off the screen.  On the left and right it spills into the adjacent desktops.
Comment 16 Julien Moragny 2011-09-29 22:09:22 CEST
Hi,

I can reproduce the problem with a fresh profile on a fully updated cauldron.

It seems linked to oxygen theme, with other kwin theme such as ia_ora or plastik, the window maximize fine.
Yann Lejeune 2011-10-14 20:09:28 CEST

CC: (none) => yann

Comment 17 Marja Van Waes 2011-12-11 09:14:07 CET
(In reply to comment #16)
> Hi,
> 
> I can reproduce the problem with a fresh profile on a fully updated cauldron.
> 
> It seems linked to oxygen theme, with other kwin theme such as ia_ora or
> plastik, the window maximize fine.

oxygen-gtk?

@ anyone who experiences this bug in cauldron

Because of another theme bug, bug 2679, Thierry added a new feature to drakbug in cauldron, it now shows your theme.

Please go to your console and type:

drakbug

and report here which theme it says you use

CC: (none) => marja11

Comment 18 Frank Griffin 2011-12-11 15:28:45 CET
Ia Ora Smooth for me.

BTW, I've had compiz turned off since I last posted here, so I can't swaer that this still reproduces.
Comment 19 Marja Van Waes 2011-12-11 15:55:10 CET
(In reply to comment #18)
> Ia Ora Smooth for me.
> 
> BTW, I've had compiz turned off since I last posted here, so I can't swaer that
> this still reproduces.

Thanks, Frank :)

Anyone still experiencing this issue, please let us know!

Keywords: (none) => NEEDINFO

Comment 20 Julien Moragny 2011-12-15 14:48:22 CET
Hi,

couldn't reproduce on cauldron with latest update (compiz and oxygen notably)
Comment 21 Marja Van Waes 2011-12-15 16:06:26 CET
(In reply to comment #20)
> Hi,
> 
> couldn't reproduce on cauldron with latest update (compiz and oxygen notably)

Thx, Julien, so some update seems to have fixed it :)

Closing this bug.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 22 Julien Moragny 2011-12-16 18:42:26 CET
*** Bug 3305 has been marked as a duplicate of this bug. ***

CC: (none) => ezequiel_partida


Note You need to log in before you can comment on or make changes to this bug.