| Summary: | Containment on second monitor lost after energy saver turns it off until plasmashell is restarted | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | przem.formela |
| Component: | Desktop Containment | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED DOWNSTREAM | ||
| Severity: | normal | CC: | aleixpol, nate, notmart |
| Priority: | NOR | Keywords: | multiscreen |
| Version: | 5.27.3 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| See Also: |
https://bugs.kde.org/show_bug.cgi?id=462316 https://bugs.kde.org/show_bug.cgi?id=469192 |
||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
przem.formela
2023-03-15 21:15:05 UTC
If something crashed, we need a backtrace of it so we can figure out what's going on. Can you please attach a backtrace of the crash using the `coredumpctl` command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl? Thanks! Hi Nate, I'm sorry, I may have used the word "crash" too liberately here. What's actually happening is, the second monitor loses all its containments – what's left is black screen with all the previously opened windows, no panels, wallpaper, nor widgets, but plasmashell is still working and all the containments on main monitor works without issue. I can't provide crash report since there's no crash. I may try to attach to plasmashell with gdb and log results into file, would taht help at all? Ah, if there's no crash then what you described makes sense. You said restarting plasmashell brings it back... any chance you can upgrade to Plasma 5.27.4? We think we fixed a few variants of the issue in that release. Thanks! After upgrading to 5.27.4 it still happens, but not every time. What happens always, though, is the monitors waking up immediately after going to sleep. One of my monitors has a built-in KVM and I'm wondering if that causes the issue. I'll dust up an old monitor and try different configs, then report. A built-in KVM, whoa. That could definitely be a part of it. It would definitely be nice if you can see whether the issue reproduces with other monitors that don't have that fancy hardware, if it's possible for you to test that. 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! Ping; can you reply? Hello Nate, Sorry for the long silence; I've been overtaken by house renovation. Your ping mobilized me to make out some spare time and check the configurations. Turns out, the culprit was second monitor's DP->HDMI Cable. Switching it to a HDMI->HDMI (same with HDMI->DVI) fixed the issue (which never happened on Windows, weirdly; hence I didn't assume t could be a cable issue). Sorry for bothering; this ticket can be closed. I'll stay with this config until I'll get a new DP->HDMI cable. Amazing! Sometimes it can just be the weirdest things. |