Summary: | On X11, Plasma crashes in ShellCorona::screenInvariants() when computer starts up without screen or monitor | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | partain.m |
Component: | Desktop Containment | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | akaykaya810, aleixpol, bertram.daniel, ferenosdev, kde, nate, nicolas.fella, notmart, nstoica2008, postix |
Priority: | NOR | Keywords: | drkonqi, multiscreen |
Version: | 5.24.5 | ||
Target Milestone: | 1.0 | ||
Platform: | unspecified | ||
OS: | Linux | ||
URL: | https://crash-reports.kde.org/organizations/kde/issues/5387/?project=9&query=is%3Aunresolved&referrer=issue-stream&sort=freq&statsPeriod=14d&stream_index=5 | ||
See Also: |
https://bugs.kde.org/show_bug.cgi?id=413782 https://bugs.kde.org/show_bug.cgi?id=468430 https://bugs.kde.org/show_bug.cgi?id=484838 |
||
Latest Commit: | https://invent.kde.org/plasma/libplasma/-/commit/b76440b35bb8c067731dfe30e888589ade90551f | Version Fixed In: | 6.0.5 |
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
Description
partain.m
2022-07-20 16:09:59 UTC
*** Bug 457282 has been marked as a duplicate of this bug. *** Created attachment 151512 [details]
New crash information added by DrKonqi
plasmashell (5.25.3) using Qt 5.15.5
masaüstümde yükle ikonunu gördüm ama hali hazırda bilgisayarımda istem vardı ve birkaç saniye sonra çökme uyarısı geldi.
-- Backtrace (Reduced):
#6 0x00007fd55daffbd9 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7 0x00007fd55dafefe5 in qt_assert(char const*, char const*, int) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8 0x0000562eb20e1c28 in ShellCorona::screenInvariants (this=0x7fd554005490) at /tmp/git-sources/plasma-workspace/shell/shellcorona.cpp:830
#9 0x0000562eb21033c0 in QtPrivate::FunctorCall<QtPrivate::IndexesList<>, QtPrivate::List<>, void, void (ShellCorona::*)() const>::call(void (ShellCorona::*)() const, ShellCorona*, void**) (f=(void (ShellCorona::*)(const ShellCorona * const)) 0x562eb20e17c4 <ShellCorona::screenInvariants() const>, o=0x7fd554005490, arg=0x7ffe03de9040) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:158
#10 0x0000562eb210176e in QtPrivate::FunctionPointer<void (ShellCorona::*)() const>::call<QtPrivate::List<>, void>(void (ShellCorona::*)() const, ShellCorona*, void**) (f=(void (ShellCorona::*)(const ShellCorona * const)) 0x562eb20e17c4 <ShellCorona::screenInvariants() const>, o=0x7fd554005490, arg=0x7ffe03de9040) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:197
Created attachment 151731 [details]
New crash information added by DrKonqi
plasmashell (5.25.4) using Qt 5.15.5
changing themes, the default ones, not other themes from the store.
-- Backtrace (Reduced):
#6 0x00007f836a22ebd9 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7 0x00007f836a22dfe5 in qt_assert(char const*, char const*, int) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8 0x000055bcd4540d38 in ShellCorona::screenInvariants (this=0x7f8360005ae0) at /tmp/git-sources/plasma-workspace/shell/shellcorona.cpp:832
#9 0x000055bcd45624d0 in QtPrivate::FunctorCall<QtPrivate::IndexesList<>, QtPrivate::List<>, void, void (ShellCorona::*)() const>::call(void (ShellCorona::*)() const, ShellCorona*, void**) (f=(void (ShellCorona::*)(const ShellCorona * const)) 0x55bcd45408d4 <ShellCorona::screenInvariants() const>, o=0x7f8360005ae0, arg=0x7ffc9ea0e220) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:158
#10 0x000055bcd456087e in QtPrivate::FunctionPointer<void (ShellCorona::*)() const>::call<QtPrivate::List<>, void>(void (ShellCorona::*)() const, ShellCorona*, void**) (f=(void (ShellCorona::*)(const ShellCorona * const)) 0x55bcd45408d4 <ShellCorona::screenInvariants() const>, o=0x7f8360005ae0, arg=0x7ffc9ea0e220) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:197
*** Bug 458548 has been marked as a duplicate of this bug. *** *** Bug 465921 has been marked as a duplicate of this bug. *** Is anyone who was encountering this specific crash able to reproduce it after upgrading to Plasma 5.27? . 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! Still getting duplicates; re-opening. *** Bug 466857 has been marked as a duplicate of this bug. *** A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/4238 https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/4238 *might* fix that, needs to see if it will make sentry reports go down Git commit dfd160bdf6f660c10b712a664c86a2a7339e8e72 by Marco Martin. Committed on 15/04/2024 at 12:36. Pushed by mart into branch 'master'. Fix redundantoutputs when the enabled screens change very quickly on X11, when a single transaction from KScreen disables screenA and enabled screenB, a new output order arrivers before the old output gets removed and in that moment the new screen will be considered redundant to che screen that is about to be removed, causing an invalid internal state Related: bug 484687 M +4 -3 shell/screenpool.cpp https://invent.kde.org/plasma/plasma-workspace/-/commit/dfd160bdf6f660c10b712a664c86a2a7339e8e72 A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/4239 Git commit da35849d5f4913221ba362d3961fd29526f364d5 by Marco Martin. Committed on 15/04/2024 at 12:37. Pushed by mart into branch 'Plasma/6.0'. Fix redundantoutputs when the enabled screens change very quickly on X11, when a single transaction from KScreen disables screenA and enabled screenB, a new output order arrivers before the old output gets removed and in that moment the new screen will be considered redundant to che screen that is about to be removed, causing an invalid internal state Related: bug 484687 (cherry picked from commit dfd160bdf6f660c10b712a664c86a2a7339e8e72) c6ff79fd Fix redundantoutputs when the enabled screens change very quickly M +4 -3 shell/screenpool.cpp https://invent.kde.org/plasma/plasma-workspace/-/commit/da35849d5f4913221ba362d3961fd29526f364d5 A possibly relevant merge request was started @ https://invent.kde.org/plasma/libplasma/-/merge_requests/1102 Git commit ce01af99fc76ef3c3f48e739c12e96f85b4a79e9 by Akseli Lahtinen. Committed on 16/04/2024 at 09:26. Pushed by akselmo into branch 'master'. containmentview: Remove QueuedConnection from setContainment Queued connection here causes a race condition when restarting plasmashell and can cause it to get stuck to crash loop, since plasmashell tries to assert for panel to be visible but this slot is not even called yet, even though the signal is emitted. M +5 -10 src/plasmaquick/containmentview.cpp https://invent.kde.org/plasma/libplasma/-/commit/ce01af99fc76ef3c3f48e739c12e96f85b4a79e9 A possibly relevant merge request was started @ https://invent.kde.org/plasma/libplasma/-/merge_requests/1103 Git commit b76440b35bb8c067731dfe30e888589ade90551f by Akseli Lahtinen. Committed on 16/04/2024 at 09:27. Pushed by akselmo into branch 'Plasma/6.0'. containmentview: Remove QueuedConnection from setContainment Queued connection here causes a race condition when restarting plasmashell and can cause it to get stuck to crash loop, since plasmashell tries to assert for panel to be visible but this slot is not even called yet, even though the signal is emitted. (cherry picked from commit ce01af99fc76ef3c3f48e739c12e96f85b4a79e9) 5ff7251c containmentview: Remove queuedconnection from setContainment M +5 -10 src/plasmaquick/containmentview.cpp https://invent.kde.org/plasma/libplasma/-/commit/b76440b35bb8c067731dfe30e888589ade90551f That commit made it into Plasma 6.0.5, which will be been released in about two weeks. We think this may have resolved the issue fully; closing the bug report. However please do feel free to re-open if if you can still reproduce the crash with 6.0.5 or later. If you do, make sure it's the exact same crash, with the same backtrace. Thanks! |