Bug 252783

Summary: Panels on secondary monitor are moved to primary monitor when secondary monitor is disconnected.
Product: [Unmaintained] plasma4 Reporter: Synthetic451 <bugs.kde.org.facelift226>
Component: panelAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: aseigo, asraniel, post
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Synthetic451 2010-09-29 19:19:24 UTC 
Version:           unspecified (using KDE 4.5.1) 
OS:                Linux

I have an extra panel placed on my secondary monitor to keep track of tasks on that monitor. Whenever I disconnect my secondary monitor and/or disable it, its panel is moved to my primary monitor, resulting in two panels overlapping each other on the same screen.

Reproducible: Always

Steps to Reproduce:
1.) Place extra panel on secondary monitor
2.) Disable secondary monitor or reboot with it already disconnected.
3.) Observe that the secondary panel is now placed on primary monitor, overlapping the existing panel.

Actual Results:  
Secondary panel is moved to primary monitor and overlaps existing primary panel when secondary monitor is disabled.

Expected Results:  
Secondary panel is not displayed when secondary monitor is disabled and reappears on secondary monitor when it is reenabled.

I am using TwinView for my dual monitor setup.

Both of my panels are placed on the bottom of their respective screens.
Comment 1 Beat Wolf 2010-09-29 20:09:11 UTC 
i think that is probably because of the changes in 4.5 for people that only had a panel on the second screen.
Comment 2 Synthetic451 2010-09-30 11:40:32 UTC 
Well that behavior is a bit strange to me. Desktop screens shouldn't have content/widgets randomly moved into them. It gets really chaotic.
Comment 3 Ralf Jung 2010-10-25 15:55:01 UTC 
This is a duplicate of bug 248828, isn't it?
Comment 4 Synthetic451 2010-10-25 19:53:26 UTC 
Yes it does seem to be a dupe. Setting as so.

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