Bug 188505 - Panel not maximized on resolution change
Summary: Panel not maximized on resolution change
Status: RESOLVED DUPLICATE of bug 188728
Alias: None
Product: plasma4
Classification: Plasma
Component: containment-panel (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-30 22:20 UTC by Wanderer
Modified: 2009-05-15 18:40 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wanderer 2009-03-30 22:20:39 UTC
Version:            (using KDE 4.2.1)
OS:                Linux
Installed from:    Ubuntu Packages

I have both kubuntu 8.10 and Fedora 10 installed in virtual machines under VMWare 1.x for Windows. In both OSs, i have installed VMWare tools (so the VMware display driver is installed) and i have noticed the following behavior in both of them.

Upon startup, the resolution of the OS is smaller than the resolution that can be supported by the VMWare window. I have selected VMWare's option "Autofit Guest" so when i minimize VMware and restore it, it resizes the client OS to the resolution of the VMWare window. Everything works normally, the background image is "scaled" as it should, except that the panel is not horizontally expanded to the width of the new resolution. I have to manually go to "panel settings \ more settings" and select "maximize panel" in order for it to expand to the full width of the new resolution. If the resolution is manually changed via "system settings \ display" though, the panel is resized to fit the new resolution's width.
Comment 1 clcevboxvjeo 2009-04-12 18:23:47 UTC
The 'maximize panel' setting is not remembered when I connect an external monitor with larger resolution after restart.
Comment 2 clcevboxvjeo 2009-05-09 15:29:24 UTC
Still present in KDE 4.2.3
Comment 3 Dario Andres 2009-05-15 18:40:48 UTC
Marking as duplicate of bug 188728
Thanks

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