Bug 473980 - Plasmashell crashes when closing the "undo deleting this panel" notification
Summary: Plasmashell crashes when closing the "undo deleting this panel" notification
Status: RESOLVED DUPLICATE of bug 468180
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (show other bugs)
Version: 5.27.5
Platform: Debian stable Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2023-08-31 08:12 UTC by Gladox114
Modified: 2023-09-01 01:52 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
New crash information added by DrKonqi (108.76 KB, text/plain)
2023-08-31 08:12 UTC, Gladox114
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gladox114 2023-08-31 08:12:22 UTC
Application: plasmashell (5.27.5)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.26-stb-cbq aarch64
Windowing System: Wayland
Distribution: Debian GNU/Linux 12 (bookworm)
DrKonqi: 5.27.5 [CoredumpBackend]

-- Information about the crash:
I got many messages that I removed a Panel, I pressed on the X to close them and after the second message the Desktop crashed.

Using Debian 12 Stable.

The crash can be reproduced sometimes.

-- Backtrace (Reduced):
#5  0x0000ffffb805af4c in QtQml::qmlExecuteDeferred(QObject*) () from /lib/aarch64-linux-gnu/libQt5Qml.so.5
#6  0x0000ffffb84fd868 in QQuickTransition::prepare(QList<QQuickStateAction>&, QList<QQmlProperty>&, QQuickTransitionManager*, QObject*) () from /lib/aarch64-linux-gnu/libQt5Quick.so.5
#7  0x0000ffffb84f24f8 in QQuickTransitionManager::transition(QList<QQuickStateAction> const&, QQuickTransition*, QObject*) () from /lib/aarch64-linux-gnu/libQt5Quick.so.5
#8  0x0000ffffb688e5c4 in QObject::event(QEvent*) () from /lib/aarch64-linux-gnu/libQt5Core.so.5
#9  0x0000ffffb762c0a0 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/aarch64-linux-gnu/libQt5Widgets.so.5


Reported using DrKonqi
Comment 1 Gladox114 2023-08-31 08:12:23 UTC
Created attachment 161297 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Nate Graham 2023-08-31 16:19:27 UTC
Pasting full backtrace for searchability:

Thread 1 (Thread 0xffffb90d44e0 (LWP 59180)):
[KCrash Handler]
#5  0x0000ffffb805af4c in QtQml::qmlExecuteDeferred(QObject*) () from /lib/aarch64-linux-gnu/libQt5Qml.so.5
#6  0x0000ffffb84fd868 in QQuickTransition::prepare(QList<QQuickStateAction>&, QList<QQmlProperty>&, QQuickTransitionManager*, QObject*) () from /lib/aarch64-linux-gnu/libQt5Quick.so.5
#7  0x0000ffffb84f24f8 in QQuickTransitionManager::transition(QList<QQuickStateAction> const&, QQuickTransition*, QObject*) () from /lib/aarch64-linux-gnu/libQt5Quick.so.5
#8  0x0000ffffb688e5c4 in QObject::event(QEvent*) () from /lib/aarch64-linux-gnu/libQt5Core.so.5
#9  0x0000ffffb762c0a0 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/aarch64-linux-gnu/libQt5Widgets.so.5
#10 0x0000ffffb685cd40 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/aarch64-linux-gnu/libQt5Core.so.5
#11 0x0000ffffb68bdd60 in QTimerInfoList::activateTimers() () from /lib/aarch64-linux-gnu/libQt5Core.so.5
#12 0x0000ffffb68be6cc in ?? () from /lib/aarch64-linux-gnu/libQt5Core.so.5
#13 0x0000ffffb4e1774c in g_main_context_dispatch () from /lib/aarch64-linux-gnu/libglib-2.0.so.0
#14 0x0000ffffb4e179e0 in ?? () from /lib/aarch64-linux-gnu/libglib-2.0.so.0
#15 0x0000ffffb4e17a84 in g_main_context_iteration () from /lib/aarch64-linux-gnu/libglib-2.0.so.0
#16 0x0000ffffb68beaa8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/aarch64-linux-gnu/libQt5Core.so.5
#17 0x0000ffffb685b258 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/aarch64-linux-gnu/libQt5Core.so.5
#18 0x0000ffffb68642dc in QCoreApplication::exec() () from /lib/aarch64-linux-gnu/libQt5Core.so.5
#19 0x0000aaaae2467a64 in ?? ()
#20 0x0000ffffb61f7780 in __libc_start_call_main (main=main@entry=0xaaaae2466d80, argc=argc@entry=2, argv=argv@entry=0xffffd8eeba28) at ../sysdeps/nptl/libc_start_call_main.h:58
#21 0x0000ffffb61f7858 in __libc_start_main_impl (main=0xaaaae2466d80, argc=2, argv=0xffffd8eeba28, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=<optimized out>) at ../csu/libc-start.c:360
#22 0x0000aaaae2467bf0 in ?? ()
Comment 3 Nate Graham 2023-08-31 16:23:11 UTC
Cannot reproduce, no KDE code is implicated in what I can see from the backtrace, and the backtrace has no debug symbols for anything that would help. :(

If this crash is reproducible, could you please install debug symbols, reproduce the crash, and attach a new symbolicated backtrace? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Thanks!
Comment 4 Fushan Wen 2023-09-01 01:52:03 UTC

*** This bug has been marked as a duplicate of bug 468180 ***