I have a problem with the dual screen setup on my T410 laptop. My laptop screen is set up to be the primary display. The second screen has a large resolution and is set up to be on the left of the primary laptop screen. Reproducible: Always Steps to Reproduce: 1. connect the second screen and set it up to be left of the primary screen, that contains a panel the configuration should correspond to xrandr --output LVDS-1 --mode 1440x900 --pos 1680x267 --rotate normal --primary --output DP-3 --mode 1680x1050 --pos 0x0 --rotate normal 2. log out and disconnect the second screen 3. log in 4. connect second screen during the session Actual Results: The panel from the primary (right) screen is moved to the secondary screen on the left as soon as is becomes available, the alignment setting, that I thought to be the culprit has no effect. Expected Results: The panel should stay on the primary screen no matter what. machine: TinkPad T410 gpu: NVIDIA Corporation GT218M [NVS 3100M] (rev a2) driver: nouveau kernel: 4.3.5-300.fc23.x86_64
Created attachment 97281 [details] xrandr output for the failing configuration
I am experiencing the same issue, I have 3 monitors and the panel always goes to the left monitor, my primary output is set to the middle monitor over DVI-I. I am on arch linux plasma-desktop 5.6.0-1 ,plasma-workspace 5.6.0-1) after a reboot the panel will appear on the left screen. If I remove it and create a panel on the middle screen it does not keep it there after a reboot.
It seems that cleaning the config files out. And upgradin to Qt5.6 fixed the issue for me. I removed all plasma and kde config. Similar to creating a new account. Now my Panel sticks to the screen I created it to.
Seems that if the panel crashed and I need to kill plasma shell , the panel will be back to the left most screen. If I set the primary output to the left screen (HDMI) then the panel appears on the middle screen for some reason. If I set the primary output the the middle screen (DVI-I) the panel is on the left screen.
Is this bug still reproducible?
This should be fixed today with Plasma 5.27 4. We've made a *lot* of changes to improve this use case.