Bug 482618 - Panels on two monitors were switched after update to Plasma 6.0.0 in Wayland, not x.
Summary: Panels on two monitors were switched after update to Plasma 6.0.0 in Wayland,...
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Desktop Containment (show other bugs)
Version: 6.0.0
Platform: Neon Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: multiscreen
Depends on:
Blocks:
 
Reported: 2024-03-06 23:57 UTC by Anon
Modified: 2024-03-10 22:32 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Config (24.13 KB, text/plain)
2024-03-09 04:22 UTC, Anon
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Anon 2024-03-06 23:57:42 UTC
SUMMARY
***

Panels on two monitors were switched after update to Plasma 6.0.0 in Wayland (not X). NOTE: it's possible that it was happening before 6.0.0 in Wayland (I didn't use Wayland, but the update to 6.0.0 overrode my default session on the login screen so I logged into a Wayland session against my will).

***


STEPS TO REPRODUCE
1. Use a laptop with an external 4k monitor
2. Make the laptop screen primary and external monitor secondary
3. Add a panel to the external monitor
4. Update Plasma 5.x (latest) to 6.0.0 with pkcon update
5. Log in to a Wayland session and see the panels have switched (or maybe the external monitor has been made primary; I didn't think to check that possibility) 

OBSERVED RESULT

Panel from primary monitor in 5.x is now on the secondary, and vice versa, in Wayland only, after 6.0.0 update.

EXPECTED RESULT

Panels are not changed / primary vs secondary monitors are not flipped.

SOFTWARE/OS VERSIONS

Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-21-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
Memory: 46.7 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics
Manufacturer: LENOVO
Product Name: 20RYS0M100
System Version: ThinkPad T490

ADDITIONAL INFORMATION

This did not happen in X, only Wayland. I did not use Wayland prior to the 6.0.0 update, so I don't know if it was already happening before.
Comment 1 Marco Martin 2024-03-07 15:37:12 UTC
was an update from 5.27 or an older one? (screen mapping changed in 5.27 and in 6.0 is still the logic introduced there)
Comment 2 Marco Martin 2024-03-07 15:42:40 UTC
can you attach the file ~/.config/plasma-org.kde.plasma.desktop-appletsrc  ?
Comment 3 Nate Graham 2024-03-07 18:00:02 UTC
> (or maybe the external monitor has been made primary; I didn't think to check that possibility) 
Can you do it and report back on which one of the two options is the correct one?
Comment 4 Anon 2024-03-09 04:15:47 UTC
(In reply to Nate Graham from comment #3)
> > (or maybe the external monitor has been made primary; I didn't think to check that possibility) 
> Can you do it and report back on which one of the two options is the correct
> one?

That's what happened. In X, the laptop screen is primary. In Wayland (fresh session after 6.0.0 update. I had never used Wayland before) the external screen is primary.
Comment 5 Anon 2024-03-09 04:16:47 UTC
(In reply to Marco Martin from comment #1)
> was an update from 5.27 or an older one? (screen mapping changed in 5.27 and
> in 6.0 is still the logic introduced there)

It was the most recent one prior to 6.0.0. I update every 1-2 days to stay current and get all the great new features in Plasma.
Comment 6 Anon 2024-03-09 04:22:23 UTC
Created attachment 166771 [details]
Config
Comment 7 Anon 2024-03-09 04:22:55 UTC
(In reply to Marco Martin from comment #2)
> can you attach the file ~/.config/plasma-org.kde.plasma.desktop-appletsrc  ?

Added. I just replaced file and directory names with fake data, Everything else is as is.
Comment 8 Nate Graham 2024-03-10 22:24:13 UTC
Have the panels reversed again when logging out of a Wayland session and back into it, or out of a Wayland session and into an X session, or out of an X session and into a Wayland session?

If not, then there's probably no way to debug this, and we'll unfortunately have to chalk it up to "expected upgrade issues" :(
Comment 9 Anon 2024-03-10 22:26:54 UTC
Logging in and out to/from x11 and Wayland doesn't change anything, I.e. x11 screens are always correct and Wayland screens are always wrong.

I can't test whether changing primary/secondary screen settings in Wayland "sticks" because I nuked the installation so I can get work done :(
Comment 10 Nate Graham 2024-03-10 22:32:00 UTC
Sorry to hear it. Unfortunately that means the investigation just ended, since if you don't still have en environment in which you can reproduce the bug, and none of us can reproduce it either, there's really no chance it can be fixed. :(