Bug 467835 - On login, containment for left-most screen is placed on right-most screen overlapping its containment, and left-most screen gets a black background
Summary: On login, containment for left-most screen is placed on right-most screen ove...
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Desktop Containment (show other bugs)
Version: 5.27.4
Platform: Manjaro Linux
: VHI major
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: multiscreen
Depends on:
Blocks:
 
Reported: 2023-03-26 23:37 UTC by miranda
Modified: 2023-09-24 03:46 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
video of blank background (1.57 MB, video/mp4)
2023-03-26 23:37 UTC, miranda
Details
journal log during login (119.95 KB, text/x-log)
2023-03-26 23:38 UTC, miranda
Details
screenshot of the bug (1.04 MB, image/png)
2023-05-04 11:40 UTC, aeneid
Details

Note You need to log in before you can comment on or make changes to this bug.
Description miranda 2023-03-26 23:37:24 UTC
Created attachment 157607 [details]
video of blank background

SUMMARY
Randomly, on login, I'll get a black background on one of my monitors that cannot be clicked or interacted with. The attached video should show what I'm talking about.


STEPS TO REPRODUCE
1. Log in
2. ???

OBSERVED RESULT
- Instead of each desktop appearing on each display, both are shoved over to the same (in this case rightmost) display. My monitors are slightly ajar (one raised by 100px), and in the attached video you can see one (normally leftmost) background overlayed on the other (note the 100px difference).
- I cannot left click or right click the leftmost background.
- The panel/task manager on the otherwise blank screen can be interacted with.
- Adjusting the display positions does not resolve the issue (attempting this cut off the recording, but trust me it does not work).

EXPECTED RESULT
Both desktops are contained within the proper displays and are interactable

SOFTWARE/OS VERSIONS
Arch Linux w/ KDE Plasma
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
Kernel: 6.2.8-arch1-1
AMD Radeon RX 6600 XT
Mesa: 23.0.0 (this has previously occurred on Mesa v22.x w/ plasma 5.27 as well)
No /etc/X11/xorg.conf file

Attached you will find:
- A video showcasing the problem
- journalctl output from when logging into the session (hostname and username scrubbed)
  - I'd continued with it like that for a few hours, in case you're wondering about the time difference
Comment 1 miranda 2023-03-26 23:38:01 UTC
Created attachment 157608 [details]
journal log during login
Comment 2 Nate Graham 2023-04-05 00:04:26 UTC
OMG! Is this by any chance an upgrade install from Plasma 5.26 or earlier? Or was the 5.27 install a clean install?

When this happens, do both screens show up properly in System Settings > Display and Monitor?
Comment 3 miranda 2023-04-05 04:01:46 UTC
This is an install upgraded from pre-5.26. After the recent overhaul I'd faced this *much* less frequently, but it still happens on occasion.

They both showed under system settings, yes.
Comment 4 miranda 2023-04-05 04:02:13 UTC
In fact, you can see that in the video I had attached.
Comment 5 Nate Graham 2023-04-05 16:14:24 UTC
Ok, so Plasma got confused and put the containment for the left screen on the right screen, along with another one. Weird. By any chance does this also happen on Wayland, or only X11?

Also, can you paste the text in the [ScreenConnectors] section of your ~/.config/plasmashellrc file?
Comment 6 miranda 2023-04-06 05:23:03 UTC
I've had similar issues occur on wayland, but I haven't looked through the kscreen output or anything for a true comparison.

And for the config:

[ScreenConnectors]                                                                                                                                                                                                                          
0=DP-2                                                                                                                                                                                                                                      
1=HDMI-A-1                                                                                                                                                                                                                                  
2=HDMI-0                                                                                                                                                                                                                                    
3=DP-3                                                                                                                                                                                                                                      
4=HDMI-1
Comment 7 Nate Graham 2023-04-06 15:28:54 UTC
Thanks for the info.
Comment 8 Nate Graham 2023-04-11 14:59:33 UTC
if you run `kscreen-doctor -o` in a terminal window, does it report that the screens are overlapping--even by one pixel? You'll need to compare their "geometry" values.
Comment 9 miranda 2023-04-12 20:45:36 UTC
This would be the output:

Output: 1 DP-2 enabled connected priority 1 DisplayPort Modes: 0:1920x1080@60*! 1:1680x1050@60 2:1280x1024@75 3:1280x1024@60 4:1440x900@60 5:1280x960@60 6:1280x800@60 7:1152x864@75 8:1280x720@60 9:1024x768@75 10:1024x768@70 11:1024x768@60 12:832x624@75 13:800x600@75 14:800x600@72 15:800x600@60 16:800x600@56 17:640x480@75 18:640x480@73 19:640x480@67 20:640x480@60 21:720x400@70 22:1280x1024@60 23:1024x768@60 24:1280x800@60 25:1920x1080@60 26:1600x900@60 27:1368x768@60 28:1280x720@60 Geometry: 1920,84 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown
Output: 2 DP-3 enabled connected priority 2 DisplayPort Modes: 0:1920x1080@60*! 1:1680x1050@60 2:1280x1024@75 3:1280x1024@60 4:1440x900@60 5:1280x800@60 6:1152x864@75 7:1280x720@60 8:1024x768@75 9:1024x768@60 10:800x600@75 11:800x600@60 12:640x480@75 13:640x480@60 14:720x400@70 15:1280x1024@60 16:1024x768@60 17:1280x800@60 18:1920x1080@60 19:1600x900@60 20:1368x768@60 21:1280x720@60 Geometry: 0,0 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown


For easier reading the Geometry is:

DP-3 Geometry: 0,0 1920x1080
DP-2 Geometry: 1920,84 1920x1080

DP-3 being the leftward screen. From my understanding that isn't an overlap, but touching on their edges like normal.
Comment 10 Nate Graham 2023-04-14 15:43:16 UTC
Ok, looks like there's no overlap. Thanks for the info.
Comment 11 aeneid 2023-05-04 11:40:47 UTC
Created attachment 158686 [details]
screenshot of the bug

I am seeing something similar, usually happens after login - mostly after resume from suspend i think.
Half of my primary screen (display port) becomes black and non-interactable.

Operating System: EndeavourOS 
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Kernel Version: 6.3.1-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 6700 XT
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: X470 AORUS ULTRA GAMING

kscreen output:

Output: 1 HDMI-A-1 enabled connected priority 2 HDMI Modes: 0:1920x1080@60*! 1:1920x1080@60 2:1920x1080@60 3:1920x1080@50 4:1920x1080@30 5:1920x1080@30 6:1920x1080@25 7:1920x1080@24 8:1920x1080@24 9:1680x1050@60 10:1600x900@60 11:1280x1024@75 12:1280x1024@60 13:1440x900@60 14:1366x768@60 15:1280x800@60 16:1152x864@75 17:1280x720@60 18:1280x720@60 19:1280x720@60 20:1280x720@50 21:1280x720@50 22:1024x768@75 23:1024x768@70 24:1024x768@60 25:832x624@75 26:800x600@75 27:800x600@72 28:800x600@60 29:720x576@50 30:720x480@60 31:720x480@60 32:640x480@75 33:640x480@73 34:640x480@67 35:640x480@60 36:640x480@60 37:720x400@70 38:1280x1024@60 39:1024x768@60 40:1280x800@60 41:1920x1080@60 42:1600x900@60 43:1368x768@60 44:1280x720@60 Geometry: 2560,0 1080x1920 Scale: 1 Rotation: 8 Overscan: 0 Vrr: incapable RgbRange: unknown
Output: 2 DP-2 enabled connected priority 1 DisplayPort Modes: 0:2560x1440@60! 1:2560x1440@75* 2:1920x1200@60 3:1920x1080@60 4:1920x1080@60 5:1920x1080@60 6:1920x1080@50 7:1600x1200@60 8:1280x1440@60 9:1680x1050@60 10:1280x1024@75 11:1280x1024@60 12:1440x900@60 13:1280x960@60 14:1280x800@60 15:1280x720@60 16:1280x720@60 17:1280x720@60 18:1280x720@50 19:1024x768@75 20:1024x768@70 21:1024x768@60 22:832x624@75 23:800x600@75 24:800x600@72 25:800x600@60 26:800x600@56 27:720x576@50 28:720x576@50 29:720x576@50 30:720x480@60 31:720x480@60 32:720x480@60 33:720x480@60 34:720x480@60 35:640x480@75 36:640x480@73 37:640x480@67 38:640x480@60 39:640x480@60 40:640x480@60 41:720x400@70 42:1600x1200@60 43:1280x1024@60 44:1024x768@60 45:1920x1200@60 46:1280x800@60 47:2560x1440@60 48:1920x1080@60 49:1600x900@60 50:1368x768@60 51:1280x720@60 Geometry: 0,0 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: Automatic RgbRange: unknown
Comment 12 Samuel Suther 2023-05-09 07:28:21 UTC
plasmashell 5.27.4

Same here since some weeks. 
After startup left screen is black. Right-Mouseclick on it, don't show any context... seems plasmashell is fully broken for it. 

I've made a little script to reload it... after running it, it work. But that is only an unsatisfying workaround. Hope it will be fixed soon.

```
#!/bin/bash

killall plasmashell
plasmashell > /dev/null 2>&1 & disown

```
Comment 13 aeneid 2023-05-20 16:31:49 UTC
Today it happened again, but during regular use. I was dragging a file from Dolphin and pressed Meta + D.

Possibly relevant logs:

May 20 18:24:46 PC-X470-EOS plasmashell[1251]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:325:17: QML Label: Binding loop detected for property "width"
May 20 18:24:46 PC-X470-EOS plasmashell[1251]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:325:17: QML Label: Binding loop detected for property "width"
May 20 18:24:46 PC-X470-EOS plasmashell[1251]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:325:17: QML Label: Binding loop detected for property "width"
May 20 18:24:46 PC-X470-EOS plasmashell[1251]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:325:17: QML Label: Binding loop detected for property "width"
May 20 18:24:46 PC-X470-EOS plasmashell[1251]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:325:17: QML Label: Binding loop detected for property "width"
May 20 18:24:46 PC-X470-EOS plasmashell[1251]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:325:17: QML Label: Binding loop detected for property "width"
May 20 18:24:46 PC-X470-EOS plasmashell[1251]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:325:17: QML Label: Binding loop detected for property "width"
May 20 18:24:46 PC-X470-EOS plasmashell[1251]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:325:17: QML Label: Binding loop detected for property "width"
May 20 18:24:46 PC-X470-EOS plasmashell[1251]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:325:17: QML Label: Binding loop detected for property "width"
May 20 18:24:46 PC-X470-EOS plasmashell[1251]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:325:17: QML Label: Binding loop detected for property "width"
May 20 18:24:46 PC-X470-EOS plasmashell[1251]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:325:17: QML Label: Binding loop detected for property "width"
May 20 18:24:49 PC-X470-EOS kioslave5[74435]: QObject::connect: No such slot DesktopProtocol::_k_slotRedirection(KIO::Job *, QUrl)
May 20 18:24:49 PC-X470-EOS plasmashell[1251]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x559b26678d50) QQmlContext(0x559b22d39360) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
May 20 18:24:49 PC-X470-EOS plasmashell[1251]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x559b26678d50) QQmlContext(0x559b22d39360) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Comment 14 d0048 2023-07-29 17:25:14 UTC
(In reply to Samuel Suther from comment #12)
> plasmashell 5.27.4
> 
> Same here since some weeks. 
> After startup left screen is black. Right-Mouseclick on it, don't show any
> context... seems plasmashell is fully broken for it. 
> 
> I've made a little script to reload it... after running it, it work. But
> that is only an unsatisfying workaround. Hope it will be fixed soon.
> 
> ```
> #!/bin/bash
> 
> killall plasmashell
> plasmashell > /dev/null 2>&1 & disown
> 
> ```

Also observing this problem. Another potential workaround is to power cycle the left most screen a few times until it gets back.
Comment 15 Nate Graham 2023-08-25 13:48:08 UTC
We think this issue may be fixed in Plasma 6 due to recent multi-screen work that's current master-only. Can I ask you to test in a Plasma 6 session? For example, with a Neon Unstable live session.

Thanks a lot!
Comment 16 Bug Janitor Service 2023-09-09 03:45:16 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 17 Bug Janitor Service 2023-09-24 03:46:08 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!