By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 555 - Resize and Rotate and KMenu
Summary: Resize and Rotate and KMenu
Status: REOPENED
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: 3.5.13.x [Trinity]
Hardware: All Linux
: P5 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks: 2968
  Show dependency tree / graph
 
Reported: 2011-10-26 10:48 CDT by Tiago Marques
Modified: 2018-08-30 02:52 CDT (History)
2 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tiago Marques 2011-10-26 10:48:14 CDT 
Hi,

It seems that when I boot Trinity with a resolution on my laptop and then connect an external screen and change the resolution, KMenu doesn't pick up the new height settings and doesn't show up next to the taskbar but instead floats 200+ pixies away. I would capture a screenshot but it's one of those situations where it can't capture the menu.

I have the laptop screen turned off when the bug is noticeable.
Comment 1 Timothy Pearson 2011-10-26 11:29:42 CDT 
According to this bug report you are using Trinity 3.5.12; this is a known Qt3/kdelibs bug in 3.5.12 and should be fixed in 3.5.13.
Comment 2 Tiago Marques 2011-10-26 16:00:35 CDT 
Do you recall when was the fix submitted? I pulled SVN builds a few days ago, it is not 3.5.12, I should have not selected that.
Comment 3 Timothy Pearson 2011-10-26 16:54:38 CDT 
It was submitted some time ago, so I am going to treat this as a new bug.

Can you do a regression test and see if the same problem exists on 3.5.12?

Thanks!

Tim
Comment 4 Tiago Marques 2011-10-27 16:43:44 CDT 
I don't have any machine with 3.5.12 and little way of testing it right now. I can confirm it is indeed now gone in the latest builds from nightly.
Comment 5 Timothy Pearson 2011-10-27 16:58:28 CDT 
(In reply to comment #4)
> I don't have any machine with 3.5.12 and little way of testing it right now. I
> can confirm it is indeed now gone in the latest builds from nightly.

The bug is gone or the feature is gone?
Comment 6 Tiago Marques 2011-10-27 18:58:53 CDT 
The bug :)
Comment 7 Tiago Marques 2011-10-28 12:38:36 CDT 
Hi again,

Today it is happening again. It seems this happens when I already have started the desktop only with the laptop screen and then plug the external monitor. If I have both plugged at boot it doesn't seem to occur.
Comment 8 Timothy Pearson 2011-10-28 21:17:22 CDT 
This bug is probably in Qt then, and that is the last thing that should be tampered with 4 days from a release. ;-)

Specifically I suspect that the desktop resize signal is either not being sent or is being sent before XRandR has updated the monitor information structures.
Comment 9 Sergey Frolov 2013-03-24 02:58:10 CDT 
This bug is still present as of R14.
Comment 10 Sergey Frolov 2013-03-31 02:40:49 CDT 
I have upgraded my external monitor to 1920x1200 resolution and things went from weird to ugly (built-in panel has only 1024x600).

Workaround:
Calling kicker.Panel.configure() via DCOP fixes this problem. As of today krandrtray does not take advantage of system notifications framework so one must seek different ways of automating this workaround. For the time being I have placed the following trigger on kpowersave action 'Lid close': "dcop kicker Panel configure".

See also bug relevant to this workaround:
http://bugs.trinitydesktop.org/show_bug.cgi?id=1428