[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 Nate Graham changed: What|Removed |Added Summary|Containment for the second |Containment for the second |monitor is lost on boot or |monitor is lost and reset |when it is connected|to its default settings on ||boot or when it is ||connected Priority|VHI |HI -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #34 from Nate Graham --- *** Bug 440995 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 Nate Graham changed: What|Removed |Added CC||zheka.lesnov1...@gmail.com --- Comment #35 from Nate Graham --- *** Bug 446316 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 Nate Graham changed: What|Removed |Added CC||mz...@o2.pl --- Comment #36 from Nate Graham --- *** Bug 447388 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=353975 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 Nate Graham changed: What|Removed |Added Priority|HI |VHI -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #44 from Michal Ziabkowski --- A little update: the situation seems to have changed in that now I reliably get a black background which fixes itself in about 30 seconds. Which begs the question - is there some kind of preset timeout somewhere in plasma-shell or kscreen code, after which the outputs are re-probed or the containment is updated? Unlike what I reported earlier, now the behavior is totally reproducible. My educated guess is that there is a race condition between plasma-shell and kscreen. The latter is probably reconfiguring my other screen to be 1080p AFTER Plasma is already running and the containment has been created. I haven't mentioned it, since it didn't seem relevant at the time, but I'm using systemdBoot=true. It's probably worth seeing if forcing plasma-kscreen.service to start before plasma-plasmashell.service (but after plasma-kwin_x11.service, I assume?) changes anything. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #45 from Nate Graham --- What Plasma version are you using, Michal? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #46 from Michal Ziabkowski --- I'm currently on Plasma 5.24.5. And I'm fairly positive that I've been getting the black background consistently ever since upgrading to the 5.24 series. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #47 from Nate Graham --- Yeah unfortunately it seems like something in 5.24 regressed this to be even worse than it was in 5.23 and earlier. The good news is that we think we've fixed it in 5.25, which will be released tomorrow. So I would encourage everyone to upgrade and give it a try. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 Jaap Geurts changed: What|Removed |Added CC||jaap.geu...@fontys.nl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #48 from Jaap Geurts --- I just had it happen to me again on 5.25. I also use a multi-monitor(usually 2 external monitors) and multi activities setup. I'm a laptop users and I connect to many different monitors during the day(I'm a hot desking user). For me it always happens upon switching to another desk with a different set of monitors. It seems that kde doesn't recognize the new monitor(s) or recognizes them too late or relabels the monitor. Then it thinks the new setup has no activity(containment) and decides to create a new activity(containment) for each monitor which makes me lose my old activities(containments). It won't switch back either since the new one is working fine and now the default. Only very occasionally does it revert back) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #49 from Jaap Geurts --- Forgot to mention. I'm on Xorg. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #50 from Michal Ziabkowski --- Yes, unfortunately Plasma 5.25 didn't fix anything for me. Still getting a black background for the first 30 or so seconds. It doesn't even have to be a full reboot. Logging out and in again also causes the issue to happen. Tried to make sure plasma-plasmashell and plasma-kwin_x11 start after plasma-kscreen by adding this systemd config override for each (what I alluded to in comment #44): [Unit] After=plasma-kscreen.service Wants=plasma-kscreen.service While it didn't break anything, it didn't fix the bug either. Looking at the timestamps, all three services seem to be starting concurrently still, so I guess the override didn't work. Can anyone familiar with the code weigh in on where the 30 second timeout before the containment fixes itself comes from? I see a TimeoutSec=40sec in plasma-plasmashell.service, but that can't be it, right? The shell does start and the panel is present, it's just the wallpaper that's missing, so it's not as though the entire service is timing out. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #51 from Michal Ziabkowski --- I've added a 5-second delay before plasma-plasmashell.service is run with this override: [Service] ExecStartPre=sleep 5 While not ideal, this seems to have worked around my missing wallpaper bug. This confirms my theory that plasmashell is starting too early, before screens are properly configured. I have no clue how one would properly resolve this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #52 from Nate Graham --- That seems like a useful data point, thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #53 from David Edmundson --- Plasmashell always was racey against initial screen configuration. In theory it should be no different to a runtime change which should always "just work" correctly. Adding the sleep is a good data point as you say, but it's masking the symptoms of something else. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=456800 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 Nate Graham changed: What|Removed |Added Assignee|aleix...@kde.org|plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 Joel changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=353975| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #37 from Michal Ziabkowski --- Cross-posting from bug 447388, as advised by Nate Graham: Okay, I've finally found some time for some more extensive testing. To remove some variables out of the equation, I purged my appletsrc, changed the wallpapers for both my activities (I have two with different wallpapers) and rebooted a few times. I can attach the config file, but I believe the changes between runs are more interesting: After the first reboot, the path to the wallpaper changes and a new containment is added: @@ -22,7 +22,7 @@ DialogWidth=800 [Containments][1][Wallpaper][org.kde.image][General] -Image=/usr/share/wallpapers/SafeLanding/ +Image=file:///usr/share/wallpapers/SafeLanding/contents/images/5120x2880.jpg SlidePaths=/home/mziab/.local/share/wallpapers,/usr/share/wallpapers [Containments][2] @@ -92,6 +92,20 @@ Image=/usr/share/wallpapers/OneStandsOut/ SlidePaths=/home/mziab/.local/share/wallpapers,/usr/share/wallpapers +[Containments][25] +ItemGeometries-1920x1080= +ItemGeometriesHorizontal= +activityId=c850a35c-21b5-4a3d-a501-e439889d7d98 +formfactor=0 +immutability=1 +lastScreen=2 +location=0 +plugin=org.kde.plasma.folder +wallpaperplugin=org.kde.image + +[Containments][25][Wallpaper][org.kde.image][General] +Image=file:///usr/share/wallpapers/Next/contents/images/1920x1080.png + [Containments][8] activityId= formfactor=2 On the next reboot, the wallpaper path changes again, for the other activity, it seems: @@ -89,7 +89,7 @@ DialogWidth=800 [Containments][24][Wallpaper][org.kde.image][General] -Image=/usr/share/wallpapers/OneStandsOut/ +Image=file:///usr/share/wallpapers/OneStandsOut/contents/images/1920x1080.jpg SlidePaths=/home/mziab/.local/share/wallpapers,/usr/share/wallpapers [Containments][25] Then it changes again on the next reboot: @@ -89,7 +89,7 @@ DialogWidth=800 [Containments][24][Wallpaper][org.kde.image][General] -Image=file:///usr/share/wallpapers/OneStandsOut/contents/images/1920x1080.jpg +Image=file:///usr/share/wallpapers/OneStandsOut/contents/images/2560x1600.jpg SlidePaths=/home/mziab/.local/share/wallpapers,/usr/share/wallpapers [Containments][25] As a reminder, this is an X11 install with two screens, a 1080p one and a 4k one. The latter is set to clone the first one (without scaling) for convenience. It's possible that there are TWO bugs at play here. The changing wallpaper paths might also warrant some scrutiny, but the bug happens with my own wallpapers with no multiple versions for different resolutions, so it's likely not the main culprit. I have conclusive evidence that disconnecting the TV works around the bug. After doing that I couldn't reproduce it, the proper wallpaper appeared instantly. With the TV plugged in, the wallpaper would change to the proper one after 40 or so seconds. Sorry if this is hard to read. I can post more info, just tell me what you need. Please note that this is still on Plasma 5.23, but I got the exact same bug on Plasma 5.23.90, so whatever causes it isn't yet fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #38 from Michal Ziabkowski --- I've found something that might also be related. My systemd journal (I'm using the systemd session) has a dozen or so instances of this just a few seconds after boot: plasmashell[584]: requesting unexisting screen 2 Moreover, I'm getting the same message with screen -1 every 15 minutes or so, which seems worrying. I'll try to remove one of my activities and see if it still happens with a single one. For the record, I have tried removing and recreating both activities and it didn't fix the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #39 from Michal Ziabkowski --- Created attachment 146124 --> https://bugs.kde.org/attachment.cgi?id=146124&action=edit appletsrc after a few reboots I'm attaching my appletsrc after a few reboots with the other screen turned on, just in case. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #40 from Michal Ziabkowski --- Created attachment 146126 --> https://bugs.kde.org/attachment.cgi?id=146126&action=edit kactivitymanagerdrc Also attaching my kactivitymanagerdrc (before removing the second activity) for reference. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #41 from Michal Ziabkowski --- After testing for a few days, I can say pretty conclusively that removing the second activity seems to have resolved the issue. So whatever it is, it seems to be triggered by the combination of multi-screen (different native resolutions might also be at play) AND multiple activities. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #42 from Michal Ziabkowski --- It seems I've spoken too soon. The bug still appears, but seems much harder to trigger without multiple activities. I've gone through several reboots not being able to replicate it until it suddenly happened. So while multiple activities seem to exacerbate the issue, the only real constant is having multiple screens. Is there anything else I could to help debug this? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #43 from Nate Graham --- Thanks, you've already provided a lot of information. Now I think we just need to wait for a developer with relevant knowledge to see if it can be used to pinpoint the bug and fix it. -- You are receiving this mail because: You are watching all bug changes.
