| Summary: | On Wayland, containment is black/missing on plasmashell startup | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | spaceforce-temp |
| Component: | Containment | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | grave | CC: | john.kizer, kde, nate, notmart, olib141 |
| Priority: | HI | Keywords: | regression, wayland-only |
| Version First Reported In: | 6.3.5 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| See Also: |
https://bugs.kde.org/show_bug.cgi?id=494262 https://bugs.kde.org/show_bug.cgi?id=490040 |
||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
spaceforce-temp
2025-05-16 07:24:11 UTC
Do you have multiple screens when this happens? (In reply to Nate Graham from comment #1) > Do you have multiple screens when this happens? No. The big TV is my only display. Thanks. I'm not seeing anything terribly suspicious in the changelog for 6.3.5 (https://kde.org/announcements/changelogs/plasma/6/6.3.4-6.3.5) which jumps out to me as explaining what's going on here. Let's focus on the black desktop issue here. It sounds quite a bit like Bug 494262, but that so far has only affected people with more than one screen, but you only have one. And it also sounds like Bug 490040, but so far that has only affected people on X11, but you're on Wayland. (In reply to Nate Graham from comment #3) > Thanks. I'm not seeing anything terribly suspicious in the changelog for > 6.3.5 (https://kde.org/announcements/changelogs/plasma/6/6.3.4-6.3.5) which > jumps out to me as explaining what's going on here. > > Let's focus on the black desktop issue here. It sounds quite a bit like Bug > 494262, but that so far has only affected people with more than one screen, > but you only have one. And it also sounds like Bug 490040, but so far that > has only affected people on X11, but you're on Wayland. I will try an X11 session today and see how that goes. It would be useful to see journal log output when this happens, are you able to collect such data? (In reply to Oliver Beard from comment #5) > It would be useful to see journal log output when this happens, are you able > to collect such data? Here is a journalctl output showing lines between Plasma/Wayland initializing and when a lot of DrKonqi messages start showing up: https://pastebin.com/jVYY6KRN I have also noticed that sometimes the plasmashell system crashes when turning on the display even if it hasn't gone to a lock screen. I know older versions of Arch Linux/KDE would "forget" this TV was plugged in after a while and force you to pull and re-insert the HDMI cable. Maybe there is something weird with how this TV presents itself to the GPU compared to a monitor? It's possible. TVs are very weird these days; they're basically mini-computers, and often try to outsmart the video input sources they're connected to. Hi - possibly related to that point, is the TV connected via HDMI? If so, is it possible to disable HDMI CEC on the TV and see if that happens to change anything? (In reply to John Kizer from comment #8) > Hi - possibly related to that point, is the TV connected via HDMI? If so, is > it possible to disable HDMI CEC on the TV and see if that happens to change > anything? It is connected via HDMI (I prefer DisplayPort but this TV doesn't have an option for that). I looked for HDMI CEC in the settings and it is already disabled. I have logged into an X11 session and I can confirm the desktop blanking bug does not happen under X. Whether the other bugs trigger remains to be seen. P.S. what info do you still need? Thanks - I'll need to defer to folks with more knowledge on this one. Continuing to use the X11 sessions, I have had no problems with it (aside from not having Wayland features like HDR, anyway). This is definitely Wayland specific. Just to check - does this issue occur using a new user account on your device, with no desktop plasmoids or customization settings changed? Thanks! 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. |