Summary: | Panel pop-ups sometimes open on the wrong screen after set of connected screens changes | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Henrik Hudson <rhavenn> |
Component: | generic-multiscreen | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | aleixpol, chniucg, koloved, nate, niccolo.venerandi, notmart, unzippedtarball |
Priority: | NOR | Keywords: | regression |
Version: | 5.27.0 | ||
Target Milestone: | 1.0 | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | https://codereview.qt-project.org/c/qt/qtwayland/+/462780 | Version Fixed In: | latest release of the KDE Qt patch collection |
Sentry Crash Report: |
Description
Henrik Hudson
2023-02-17 22:24:01 UTC
I should add this did not happen the first few times the monitors went to sleep, but the system did somehow get to this state. ...and now after going to sleep again and waking up everything is back to normal. So, some little niggle of a bug in how the panel is keeping track of monitors. *** Bug 466099 has been marked as a duplicate of this bug. *** *** Bug 466079 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 466079 *** Can you paste the output of `kscreen-doctor -o` when this happens? Ultimately this was traced to a Qt bug that we're now hitting in Plasma 5.27 due to changes on our side in how screen stuff works. It's now fixed in Qt with https://codereview.qt-project.org/c/qt/qtwayland/+/462780, which has been packported to our Qt 5 patch collection. You should get the fix as soon as your distro ships an update to the KDE Qt patch collection. I believe I got the patch already, as it hasn't happened for a week now. Probably I have also rushed with this bug report, as I got really frustrated when docking my laptop and, as stated in the report, needing a shell restart or complete system restart. Also want to thank the KDE team for this amazing release, it's the most stable yet! So happy to hear it! *** Bug 467165 has been marked as a duplicate of this bug. *** |