Bug 295784

Summary: disabling second screen puts panel on the primary screen
Product: [Unmaintained] plasma4 Reporter: Leonardo <leonardo.guilherme>
Component: panelAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: bugs.kde.org.id324, dimitrios.tanis, l12436.tw, nate, pmdumuid, rhansen, simgunz, steffenjost, thiago.bauermann, Wout.mertens
Priority: NOR    
Version: 4.8.80 (beta1)   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Leonardo 2012-03-11 18:57:49 UTC
This bug is simmilar to 248828, but I don't know if it is a duplicate.

Basically, it happens when you have dual screens and put a panel on a secondary screen. if you disconnect the second screen, the pannel you've added comes back to the primary screen. This does not happen with widgets (plasmoids) and i remember that it wasn't like this before SC 4.8, thats why I have my doubts if its a duplicate of 248828 (which was reported more than a year ago).
Comment 1 Steffen Jost 2012-03-13 13:50:31 UTC
Same problem since updating to KDE 4.8.1:
The panel I placed on the second screen is permanently moved to the first screen, if I boot once without the second screen attached.

Before the update, with KDE 4.7 and earlier, booting without the second screen simply meant that the panel was not there and inaccessible, but once I booted with the second screen attached again, the panel was available again at the position where I had placed it. All as one would expect.

Note that I never change the screen resolution manually. If I attach or detach the second screen, I always log out of KDE or reboot (since changing screen resolution messes up widget placement badly, as noted in other bugs).

My setup as shown in the KDE system settings (all 5 checkboxes are ticked):
Screen 1:        0 0 1920 1080
Screen 2: 1920 0 1920 1200

The first screen is my laptop's built-in screen, the second is a monitor connected to the docking station by DVI cable. I am using openSuse12.1 and nvidia's binary driver. Docking/undocking is almost always done cold, i.e. shutting the machine down before docking/undocking.
Comment 2 Leonardo 2012-03-13 17:09:12 UTC
(In reply to comment #1)
> Same problem since updating to KDE 4.8.1:
> The panel I placed on the second screen is permanently moved to the first
> screen, if I boot once without the second screen attached.
> 
> Before the update, with KDE 4.7 and earlier, booting without the second
> screen simply meant that the panel was not there and inaccessible, but once
> I booted with the second screen attached again, the panel was available
> again at the position where I had placed it. All as one would expect.
> 
> Note that I never change the screen resolution manually. If I attach or
> detach the second screen, I always log out of KDE or reboot (since changing
> screen resolution messes up widget placement badly, as noted in other bugs).
> 

I do change my screen on-the-fly. But that worked previously.

> My setup as shown in the KDE system settings (all 5 checkboxes are ticked):
> Screen 1:        0 0 1920 1080
> Screen 2: 1920 0 1920 1200
> 
> The first screen is my laptop's built-in screen, the second is a monitor
> connected to the docking station by DVI cable. I am using openSuse12.1 and
> nvidia's binary driver. Docking/undocking is almost always done cold, i.e.
> shutting the machine down before docking/undocking.

I am using fglrx (ati binary drivers), so i guess this is not video-card related.
Comment 3 Thiago Jung Bauermann 2012-06-17 03:20:25 UTC
I just tested this and it still happens on 4.9 Beta.
Comment 4 Myriam Schweingruber 2012-06-20 06:31:10 UTC
Confirmed by other users.
Comment 5 Leonardo 2012-08-20 15:46:49 UTC
Is there anyone looking into this? I liked kde more when this feature worked properly :)

Can someone point us in the right direction so we can try to produce a patch? A source file or a method or something... I am willing to try to fix it myself.
Comment 6 Dimitrios T Tanis 2013-01-05 12:38:35 UTC
Sorry if it's an overkill. Same case here.

Panel placed on second screen, comes back on primary when disconnecting.
Primary screen -> laptop LCD
Secondary -> External HDMI

OpenSUSE 12.2 x64, KDE 4.8.5
Comment 7 TOM Harrison 2013-10-28 09:33:19 UTC
according to my environment
i have the same problem.
when i disconnect the secondary monitor.
logout and login, the widget in secondary monitor will at the primary monitor.
it seems like there is no separate config or widget settings.
the widget i place just a default control panel with task manager etc.

the same problem also occur in my notebook and another desktop too.

my environment:
kubuntu 13.10 
kde 4.11.2
DVI-I-0 connected primary 1280x1024+0+0 (normal left inverted right x axis y axis) 338mm x 270mm
   1280x1024      60.0*+   75.0  
DVI-I-1 connected 1280x1024+1280+0 (normal left inverted right x axis y axis) 338mm x 270mm
   1280x1024      60.0*+   75.0  
nvidia 304.88
Comment 8 TOM Harrison 2013-10-28 09:36:09 UTC
the widget will not move when the screen did not disconnect when logout and login.

i think the plasma config with the widget did not compare that the widget is in this screen or not, just place on the original place in the current screen.
Comment 9 Wout Mertens 2014-03-03 11:19:08 UTC
Still happening on Kubuntu 14.04, KDELibs 4.12.2

I have 2 external monitors connected via docking station. One is in landscape and the other in portrait, very nice. They each have a panel optimized for the screen.

When I un-dock my laptop it of course unplugs the external monitors and the panels are moved to the primary screen. When I re-dock the laptop the panels do not move back to the external screens.

I would expect a panel to be bound to a screen and if the screen is not attached, the panel is removed until the screen is back.
Comment 10 Victor B. Gonzalez 2015-09-03 18:11:54 UTC
This used to work and was a very welcome feature to have. I too experience the problem of secondary panels clobbering the primary monitor in certain cases. If I can provide logs, just ask, thanks!
Comment 11 Nate Graham 2018-01-23 21:53:14 UTC
Essentially the same (Or at least the same root cause) as Bug 356225

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