Bug 433840

Summary: Panel appears on secondary screen after returning to X11 from Wayland
Product: [Plasma] plasmashell Reporter: Dan Dascalescu <ddascalescu+kde>
Component: generic-multiscreenAssignee: Aleix Pol <aleixpol>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nate, plasma-bugs
Priority: NOR Keywords: wayland
Version: 5.21.1   
Target Milestone: 1.0   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Screenshot of the dual-monitor setup

Description Dan Dascalescu 2021-03-02 07:50:25 UTC 
Created attachment 136312 [details]
Screenshot of the dual-monitor setup

My laptop is connected to an external monitor, which I have set as the primary screen. The taskbar (panel) was appearing correctly onto that screen, until (I think) I tried out Wayland. Under Wayland, the panel appeared on the laptop. I might have disconnected the laptop from the monitor; I don't recall precisely. After learning that Wayland doesn't have the concept of a "primary screen" (to the chagrin of many users[1]), I edited the panel and dragged it onto the external monitor.

Due to numerous glitches in Wayland, I decided to go back to X11. I rebooted and logged in under X11. Now the panel appears on the laptop, even though the external monitor is set as primary. If I set the laptop as primary, the panel moves onto the external monitor.

[1]:
https://www.reddit.com/r/kde/comments/k7wa2d/how_do_i_set_the_primary_monitor_on_kde_wayland/
https://www.reddit.com/r/kde/comments/ae8czw/plasma_wayland_works_great_but_how_do_i_set_a/
https://www.reddit.com/r/kde/comments/ak3gfa/primary_monitor_with_wayland/
Comment 1 Nate Graham 2021-03-21 16:54:17 UTC 
I've had this happen too. BTW you can drag panels across screens while in panel edit mode. Grab from the "Screen edge" button and move it wherever you want it, on any screen.
Comment 2 Nate Graham 2021-08-16 23:16:25 UTC 

*** This bug has been marked as a duplicate of bug 356225 ***
Comment 3 Nate Graham 2021-10-06 19:11:30 UTC 

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