Application: plasmashell (6.1.0) Qt Version: 6.7.2 Frameworks Version: 6.3.0 Operating System: Linux 6.9.6-zen1-1-zen x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 6.1.0 [CoredumpBackend] -- Information about the crash: I was changing settings in Telegram-Desktop (Version 5.1.7), specifically the Speakers and Camera where Telegram grabs the Camera signal as well as audio. Plasma crashed as soon as I exited this menu. Can't seem to replicate at all. The crash does not seem to be reproducible. -- Backtrace (Reduced): #5 0x00007041c2c813d1 in QQmlContextData::contextObject (this=<optimized out>, this=<optimized out>) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/qml/qqmlcontextdata_p.h:128 #6 QQmlContextData::ContextGuard::objectDestroyedImpl (impl=0x5916ea6e4768) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/qml/qqmlcontextdata_p.h:455 #7 0x00007041c2c8f2d2 in QQmlData::destroyed (this=0x5916ec97a280, object=0x5916ec97a260) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/qml/qqmlengine.cpp:1415 #8 0x00007041c1b9071e in QObject::~QObject (this=<optimized out>, this=<optimized out>) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobject.cpp:1078 #9 0x00007041c33d88f3 in QQuickImplicitSizeItem::~QQuickImplicitSizeItem (this=<optimized out>, this=<optimized out>) at /usr/src/debug/qt6-declarative/qtdeclarative/src/quick/items/qquickimplicitsizeitem_p.h:24 Reported using DrKonqi
Created attachment 171043 [details] New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace.
I don't see any obvious KDE related code in coredump, possibly Qt bug?
Thread 1 (Thread 0x7041bb93e200 (LWP 918)): [KCrash Handler] #5 0x00007041c2c813d1 in QQmlContextData::contextObject (this=<optimized out>, this=<optimized out>) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/qml/qqmlcontextdata_p.h:128 #6 QQmlContextData::ContextGuard::objectDestroyedImpl (impl=0x5916ea6e4768) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/qml/qqmlcontextdata_p.h:455 #7 0x00007041c2c8f2d2 in QQmlData::destroyed (this=0x5916ec97a280, object=0x5916ec97a260) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/qml/qqmlengine.cpp:1415 #8 0x00007041c1b9071e in QObject::~QObject (this=<optimized out>, this=<optimized out>) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobject.cpp:1078 #9 0x00007041c33d88f3 in QQuickImplicitSizeItem::~QQuickImplicitSizeItem (this=<optimized out>, this=<optimized out>) at /usr/src/debug/qt6-declarative/qtdeclarative/src/quick/items/qquickimplicitsizeitem_p.h:24 #10 QQuickLoader::~QQuickLoader (this=<optimized out>, this=<optimized out>) at /usr/src/debug/qt6-declarative/qtdeclarative/src/quick/items/qquickloader.cpp:281 #11 QQmlPrivate::QQmlElement<QQuickLoader>::~QQmlElement (this=<optimized out>, this=<optimized out>) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/qml/qqmlprivate.h:100 #12 QQmlPrivate::QQmlElement<QQuickLoader>::~QQmlElement (this=<optimized out>, this=<optimized out>) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/qml/qqmlprivate.h:100 #13 0x00007041c1b8be0a in qDeleteInEventHandler (o=0x5916ec97a260) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobject.cpp:5002 #14 QObject::event (this=0x5916ec97a260, e=0x5916eb75b9f0) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobject.cpp:1437 #15 0x00007041c3afc51c in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x5916ec97a260, e=0x5916eb75b9f0) at /usr/src/debug/qt6-base/qtbase/src/widgets/kernel/qapplication.cpp:3287 #16 0x00007041c1b44d28 in QCoreApplication::notifyInternal2 (receiver=0x5916ec97a260, event=event@entry=0x5916eb75b9f0) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qcoreapplication.cpp:1142 #17 0x00007041c1b450eb in QCoreApplication::sendEvent (receiver=<optimized out>, event=0x5916eb75b9f0) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qcoreapplication.cpp:1583 #18 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x5916e8a79ba0) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qcoreapplication.cpp:1940 #19 0x00007041c1da49ec in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qcoreapplication.cpp:1797 #20 postEventSourceDispatch (s=0x5916e8aa7b20) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:244 #21 0x00007041c07c9a89 in g_main_dispatch (context=0x7041b4000f00) at ../glib/glib/gmain.c:3344 #22 0x00007041c082b9b7 in g_main_context_dispatch_unlocked (context=0x7041b4000f00) at ../glib/glib/gmain.c:4152 #23 g_main_context_iterate_unlocked.isra.0 (context=context@entry=0x7041b4000f00, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/glib/gmain.c:4217 #24 0x00007041c07c8f95 in g_main_context_iteration (context=0x7041b4000f00, may_block=1) at ../glib/glib/gmain.c:4282 #25 0x00007041c1da2cbd in QEventDispatcherGlib::processEvents (this=0x5916e8abc780, flags=...) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:394 #26 0x00007041c1b4f01e in QEventLoop::processEvents (this=0x7fffb2675ba0, flags=...) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qeventloop.cpp:100 #27 QEventLoop::exec (this=0x7fffb2675ba0, flags=...) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qeventloop.cpp:182 #28 0x00007041c1b4934d in QCoreApplication::exec () at /usr/src/debug/qt6-base/qtbase/src/corelib/global/qflags.h:74 #29 0x00007041c3af83ba in QApplication::exec () at /usr/src/debug/qt6-base/qtbase/src/widgets/kernel/qapplication.cpp:2555 #30 0x00005916bf87ed66 in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/plasma-workspace/plasma-workspace-6.1.0/shell/main.cpp:188
Yeah. Without any KDE code to implicate or a way to reproduce it, I'm not sure there's anything we can do here. I can't reproduce it by playing with that page in Telegram.
The backtrace looks very similar to bug 492356, which has been resolved since this bug was opened. Are you still able to reproduce this on an up to date system? I'm still not able to reproduce with Telegram on Plasma git-master
(In reply to TraceyC from comment #5) > The backtrace looks very similar to bug 492356, which has been resolved > since this bug was opened. Are you still able to reproduce this on an up to > date system? I'm still not able to reproduce with Telegram on Plasma > git-master Bug has seemingly been fixed on updates. Should I report this as fixed?
Sounds good!