Summary: | On X11, plasmashell crashes on launch in QWindow::screenChanged() with multiple screens connected | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Billy <bilorge> |
Component: | generic-crash | Assignee: | Aleix Pol <aleixpol> |
Status: | CONFIRMED --- | ||
Severity: | crash | CC: | bearbuilder, jhmont, kdedev, lauriej, nate, notmart, plasma-bugs, pracz, yurii.zinko |
Priority: | NOR | Keywords: | drkonqi, multiscreen |
Version: | 5.23.4 | ||
Target Milestone: | 1.0 | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
q09aI97pCrai72Ul.png
y0t2azCqrV9AS9FZ.png q09aI97pCrai72Ul.png y0t2azCqrV9AS9FZ.png |
Description
Billy
2021-12-14 18:01:08 UTC
*** Bug 448375 has been marked as a duplicate of this bug. *** this is again the qquickitem still having a dangling pointer to its (former) qquickwindow, I've seen various forms of this crash. In plsma-framework master there isa workaround to mitigate this issue, tough there is still an internal upstream issue in QML which isn't really clear yet how it happens in your 3 screens setup, do you always have one missing desktop when plasma finally comes up or only some times? Created attachment 145621 [details] q09aI97pCrai72Ul.png Marco, Honestly its random when it happens. Generally when I do a "zypper dup" I reboot and that is when I am most likely experience the bug. My solution are one of the following or a combination of both: 1) Go to the display properties and disable the compositor, this generally gets the screen layout the way its supposed to be. I then enable the compositor again 2) Go to the display properties and disable / enable the affected monitor. Once again this gets the display back to normal. Also, the issue generally affects DisplayPort-0 Thank you, Billy On 1/18/22 09:13, Marco Martin wrote: https://bugs.kde.org/show_bug.cgi?id=446987 --- Comment #3 from Marco Martin <notmart@gmail.com> [1] --- in your 3 screens setup, do you always have one missing desktop when plasma finally comes up or only some times? 1. mailto:notmart@gmail.com Created attachment 145622 [details]
y0t2azCqrV9AS9FZ.png
*** Bug 448747 has been marked as a duplicate of this bug. *** Created attachment 145882 [details] q09aI97pCrai72Ul.png Not sure if this will help or not, however, this morning after restarting my computer after a zypper dup all the screens were crashing, only the pointer was available and my usual fixes were not working. The keyboard shortcuts were working and I was able to launch quick setting and changed my sessions from save session to start with a new session and that fixed the issue... Billy On 1/18/22 10:51, Billy Draper wrote: Marco, Honestly its random when it happens. Generally when I do a "zypper dup" I reboot and that is when I am most likely experience the bug. My solution are one of the following or a combination of both: 1) Go to the display properties and disable the compositor, this generally gets the screen layout the way its supposed to be. I then enable the compositor again 2) Go to the display properties and disable / enable the affected monitor. Once again this gets the display back to normal. Also, the issue generally affects DisplayPort-0 Thank you, Billy On 1/18/22 09:13, Marco Martin wrote: https://bugs.kde.org/show_bug.cgi?id=446987 --- Comment #3 from Marco Martin <notmart@gmail.com> [1] --- in your 3 screens setup, do you always have one missing desktop when plasma finally comes up or only some times? 1. mailto:notmart@gmail.com Created attachment 145883 [details]
y0t2azCqrV9AS9FZ.png
Mose of the code here has changed to improve multimonitor use-cases in Plasma 5.27, so the original crash is likely no longer possible. If you experience more crashes with Plasma 5.27.4 or newer, please submit additional bug reports for them. Thanks! *** Bug 466730 has been marked as a duplicate of this bug. *** *** Bug 472642 has been marked as a duplicate of this bug. *** Got a new report from someone using Plasma 5.27.5; re-opening. Looks like it could be a Qt issue. Plasma version 5.27.7, the bug still persists. Any chance this will be fixed in Plasma 6? *** Bug 450594 has been marked as a duplicate of this bug. *** Marking as confirmed |