Bug 466340 - Second monitor occasionally loses containment on login
Summary: Second monitor occasionally loses containment on login
Status: RESOLVED NOT A BUG
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-multiscreen (show other bugs)
Version: 5.27.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-24 09:59 UTC by Jaap Geurts
Modified: 2023-03-06 17:08 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
kscreen-doctor, kscreen-console, appletsrc (6.57 KB, application/gzip)
2023-02-24 09:59 UTC, Jaap Geurts
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jaap Geurts 2023-02-24 09:59:47 UTC
Created attachment 156666 [details]
kscreen-doctor, kscreen-console, appletsrc

STEPS TO REPRODUCE
1. Start computer from boot
2. Login as a normal user
3. Wait until plasma desktop has loaded.

OBSERVED RESULT
The second monitor occasionally is black. There seems to be no containment because there is no wallpaper, no widgets and the context menu on right click doesn't do anything. Logging out and back in resolves to the correct old state. Windows are restored on the correct monitor.

EXPECTED RESULT
Wallpaper, widgets and context menu working correctly.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
KDE Plasma Version: 5.27
KDE Frameworks Version:  5.103.0
Qt Version: 5.15.8
Kernel version: 6.1.12-1

ADDITIONAL INFORMATION
Plasma/KDE on X11
This happens on the second (non-primary) monitor)
The computer is a laptop with two external monitors through a docking station with the laptop lid closed and the laptop screen disabled.
Comment 1 Nate Graham 2023-02-24 22:02:21 UTC
Does the laptop have an NVIDIA GPU by any chance?
Comment 2 Jaap Geurts 2023-02-25 10:42:35 UTC
No. it doesn't have an NVIDIA GPU.
This is the inxi -G output:

Graphics:
  Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel
  Device-2: Chicony Integrated Camera type: USB driver: uvcvideo
  Display: x11 server: X.Org v: 21.1.7 with: Xwayland v: 22.1.8 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 resolution:
    1: 1920x1080~60Hz 2: 1920x1080~60Hz 3: N/A
  API: OpenGL v: 4.6 Mesa 22.3.5 renderer: Mesa Intel Xe Graphics (TGL GT2)
Comment 3 Nate Graham 2023-02-27 16:15:25 UTC
If you enter edit mode and click on the "Manage Desktops and Panels" button that live son the toolbars which drops down from the top of the screen, can you use the window that appears to find your missing containment and move it back to the correct screen?

And if you can successfully do that, does it remain persistently working after a reboot? Or does it break again?
Comment 4 Jaap Geurts 2023-02-28 19:46:11 UTC
(In reply to Nate Graham from comment #3)
It hasn't happened for the past few days. When I see it again, I'll report it here. If it takes too long I'll let you know too.
Comment 5 Jaap Geurts 2023-03-02 12:58:20 UTC
> If you enter edit mode and click on the "Manage Desktops and Panels" button that live son the toolbars which drops down from the top of the screen, can you use the window that appears to find your missing containment and move it back to the correct screen?

Today I had the black screen again(again on the second monitor) After opening "manage desktops and panels". The missing containment is there. Before doing or moving anything: It showed the containment as thumbnails in the correct position. The thumbnail showed as if the containment was visible normally on the second monitor however the monitor itself was black. After that I moved the containment to another position and then the monitor containment showed correctly. After reboots things are normal.

Extra information: I'm using activities. I noticed that an activity was lost (the activity monitor also didn't show my second activity). Rebooting resolved it and it returned back to normal. Because I lost the activity all the window placements were on both activities after reboot.
Comment 6 Nate Graham 2023-03-02 15:43:39 UTC
So is the system in stable state now that persists after rebooting?

If so, it sounds like your setup might have gotten messed up by the migration code for the new system for mapping Plasma desktops and panels to screens we implemented in Plasma 5.27 that is fundamentally more correct by design, and as a result much more robust. Unfortunately, due to the non-determinism baked into the old system, we've seen a few reports that sometimes panels or desktops are swapped or missing, as a result of the old settings being in an inconsistent state at the moment of migration.
Comment 7 Jaap Geurts 2023-03-02 19:34:11 UTC
It's only stable in the sense that the next few reboots will probably be fine until I reconnect some other monitors. Your suggestion about my state being messed up could be the case. I will start afresh with new settings and see what happens. I'll consider it not a bug. Thanks a lot for the quick responses!
Comment 8 Nate Graham 2023-03-06 17:08:23 UTC
You're welcome!