Summary: | Screen shows as "disconnected" after switching monitor. Missing desktop background and panel. | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | leonardopsantos |
Component: | Containment | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | aleixpol, nate, notmart, roy-orbitson |
Priority: | NOR | Keywords: | multiscreen |
Version: | 5.27.4 | ||
Target Milestone: | 1.0 | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Panels and Desktop Management screenshot |
Description
leonardopsantos
2023-05-29 20:34:14 UTC
Workaround mention in comment 8 of bug #427278 works for me: https://bugs.kde.org/show_bug.cgi?id=427278#c8 My script is: ``` systemctl --user stop plasma-plasmashell cp -af $HOME/custom/backup/panels/$SRC/* $HOME/.config/ sleep 5 systemctl --user start plasma-plasmashell ``` I regularly encounter the same issue on a similar setup: two external monitors on a notebook and the built-in monitor disabled. Physically unplugging then reconnecting the "disconnected" display usually gets its connection status reset.. After doing this, I sometimes need to use the Panels and Desktop Management dialogue to move thins back to the correct monitors. I don't know if it's a separate issue but, like bug 427278, Plasma will also "forget" the config eventually, and at a fresh login will have incorrect monitors enabled/disabled or has the externals as duplicates of each other, though I've never set it that way. The login screen (sddm?) never seems to respect these arrangement settings, and will re-enable the built-in monitor and/or disable one of the externals. I tried using autorandr, which applies profiles perfectly from manual invocation, but seems to conflict with Plasma's own automatic detection. If anyone knows how to disable Plasma's detection so I can try autorandr properly, please tell me. I reduce the frustration by backing up this config (after I've made any changes and everything's arranged right): cp -a ~/.config/plasma-org.kde.plasma{,-BACKUP}.desktop-appletsrc When things go awry again, I log out of any graphical sessions, open a TTY session, restore it as follows, then log in again: cp -a ~/.config/plasma-org.kde.plasma{-BACKUP,}.desktop-appletsrc Sorry it took us so long to get to this. I can't reproduce it in current git master, which will shortly become Plasma 6.3. Are either of you still able to reproduce the issue in Plasma 6.2.5 or later? Thanks! Not me, sorry. On 6.1.5. At the time, I was using a DisplayLink-based dock. I've since switched to a Thunderbolt one due to many issues with the former. 🐛🧹 ⚠️ 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. |