Bug 242662 - Second panel on second desktop on with dual monitors moves to first desktop when using one monitor [KDE 4.4.85 (KDE 4.5 Beta2)]
Summary: Second panel on second desktop on with dual monitors moves to first desktop w...
Status: RESOLVED DUPLICATE of bug 241332
Alias: None
Product: plasma4
Classification: Unmaintained
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: 2010-06-24 10:02 UTC by G Cohen
Modified: 2010-06-24 14:37 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description G Cohen 2010-06-24 10:02:06 UTC
Version:           unspecified (using Devel) 
OS:                Linux

I have a laptop with a docking station using two monitors when docked and the laptop's LCD when undocked. 
Up until KDE 4.5 Beta1 the behaviour of the panels was that once I use my laptop undocked the second desktop and its panel are hidden, while they are shown when using a dual monitor setup.
Since KDE 4.5 Beta1 when I use one monitor the second panels moves the first desktop on top of the existing panel only smaller. When I go back back to using dual monitors it stays on the first desktop.
It would be great if it could work like it previously did since that means I can use one account both when docked and when undocked.

Golan.

Reproducible: Always

Steps to Reproduce:
Use a laptop with dual monitors. Add a panel on the secondary screen. Shut down, undock and restart.

Actual Results:  
Panel from secondary screen moves to primary screen, shrinks and covers parts of the existing panel.

Expected Results:  
As previously, when a second screen is not connected the second desktop and its content should be hidden.
Comment 1 Marco Martin 2010-06-24 14:17:51 UTC
this iirc was intentional to fix another bug
Comment 2 Marco Martin 2010-06-24 14:37:35 UTC

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