| Summary: | When displays wake up and one screen has been deactivated previously, screen layout not correctly restored until plasmashell is restarted | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Malte <malted.dev> |
| Component: | Containment | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | aleixpol, kdedev, manrusin, nate, notmart |
| Priority: | NOR | Keywords: | multiscreen |
| Version First Reported In: | master | ||
| Target Milestone: | 1.0 | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Malte
2023-08-09 18:11:24 UTC
See https://bugs.kde.org/show_bug.cgi?id=467422#c8, which was caused by a bad DP->HDMI cable. But in the case you're only using DP->DP and HDMI->HDMI cables, right? Also has echoes of Bug 462316 and Bug 469192. Yeah, 3x DP<->DP cables and 1x HDMI<->HDMI cable. Also, all screens work 100% fine when they are enabled. And it also works fine when all screens are activated in the System Settings. Thanks! can you compare with plasma6? (for instance with a neon unstable live image) to see if the issue still happens there, it would help narrowing the issue . *** Bug 474224 has been marked as a duplicate of this bug. *** (In reply to Marco Martin from comment #4) > can you compare with plasma6? (for instance with a neon unstable live image) > to see if the issue still happens there, it would help narrowing the issue Tested on live image kde neon unstable from 2023-09-07 Partially broken: The desktop icons auto-aligned, but animations works fine After unlocking got 3 plasmashell crashreports and all cannot be generated. Ok, thanks for testing! But it sounds like those are different issues from what was originally reported here, though. We'd like to know if Malte is able to reproduce the issue in Plasma 6. 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! 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! Sorry, didn't have time to come back to this issue until now. I've just tested with the neon-unstable-20231015-1119 build and can confirm that the problem still exists with latest Plasma 6, so reopening. I'm sorry we weren't able to get to this report until now. Are you still seeing this bug with Plasma 6.4.2 or later? 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. |