| Summary: | plasmashell segfaults in BluezQt::PendingCall::finished() when Bluez hangs | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-bluez-qt | Reporter: | mydarkstar <mds_foss> |
| Component: | general | Assignee: | kdelibs bugs <kdelibs-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | Keywords: | drkonqi |
| Priority: | NOR | ||
| Version First Reported In: | 6.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
mydarkstar
2024-04-16 02:54:42 UTC
Created attachment 168575 [details]
New crash information added by DrKonqi
DrKonqi auto-attaching complete backtrace.
The following bug report for Plasma 5.27.7 seems relevant, with *disconnecting* a Bluetooth device: https://bugs.kde.org/show_bug.cgi?id=474893 This bug report for Plasma 5.26.5 also *disconnects* a Bluetooth device: https://bugs.kde.org/show_bug.cgi?id=465031 Lastly, this bug report for Plasma 6.0.1 seems similar, but with *connecting* a Bluetooth device: https://bugs.kde.org/show_bug.cgi?id=482565 Thread 1 (Thread 0x76d8b35d01c0 (LWP 1695)): [KCrash Handler] #5 0x000076d8b95b1629 in QV4::QObjectWrapper::setQmlProperty(QV4::ExecutionEngine*, QQmlRefPointer<QQmlContextData> const&, QObject*, QV4::String*, QFlags<QV4::QObjectWrapper::Flag>, QV4::Value const&) () at /usr/lib/libQt6Qml.so.6 #6 0x000076d8b95a713a in QV4::QQmlContextWrapper::virtualPut(QV4::Managed*, QV4::PropertyKey, QV4::Value const&, QV4::Value*) () at /usr/lib/libQt6Qml.so.6 #7 0x000076d8b95332a3 in QV4::ExecutionContext::setProperty(QV4::String*, QV4::Value const&) () at /usr/lib/libQt6Qml.so.6 #8 0x000076d8b95cbdc5 in QV4::Runtime::StoreNameSloppy::call(QV4::ExecutionEngine*, int, QV4::Value const&) () at /usr/lib/libQt6Qml.so.6 #9 0x000076d8b95ff081 in ??? () at /usr/lib/libQt6Qml.so.6 #10 0x000076d8b960da95 in ??? () at /usr/lib/libQt6Qml.so.6 #11 0x000076d8b9579af8 in ??? () at /usr/lib/libQt6Qml.so.6 #12 0x000076d8b95b1df7 in ??? () at /usr/lib/libQt6Qml.so.6 #13 0x000076d8b8591599 in ??? () at /usr/lib/libQt6Core.so.6 #14 0x000076d853e60d84 in BluezQt::PendingCall::finished(BluezQt::PendingCall*) () at /usr/lib/libKF6BluezQt.so.6 #15 0x000076d853e67488 in ??? () at /usr/lib/libKF6BluezQt.so.6 #16 0x000076d8b8591599 in ??? () at /usr/lib/libQt6Core.so.6 #17 0x000076d8b93bee90 in ??? () at /usr/lib/libQt6DBus.so.6 #18 0x000076d8b857cbb7 in QObject::event(QEvent*) () at /usr/lib/libQt6Core.so.6 #19 0x000076d8ba2f437b in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt6Widgets.so.6 #20 0x000076d8b853a198 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt6Core.so.6 #21 0x000076d8b853a51b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt6Core.so.6 #22 0x000076d8b8775ba4 in ??? () at /usr/lib/libQt6Core.so.6 #23 0x000076d8b7184199 in g_main_dispatch (context=0x76d8ac000f00) at ../glib/glib/gmain.c:3344 #24 0x000076d8b71e33bf in g_main_context_dispatch_unlocked (context=0x76d8ac000f00) at ../glib/glib/gmain.c:4152 #25 g_main_context_iterate_unlocked.isra.0 (context=context@entry=0x76d8ac000f00, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/glib/gmain.c:4217 #26 0x000076d8b7183712 in g_main_context_iteration (context=0x76d8ac000f00, may_block=1) at ../glib/glib/gmain.c:4282 #27 0x000076d8b8773cd4 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt6Core.so.6 #28 0x000076d8b85446ee in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt6Core.so.6 #29 0x000076d8b853cc38 in QCoreApplication::exec() () at /usr/lib/libQt6Core.so.6 #30 0x000055fa14a58476 in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/plasma-workspace/plasma-workspace-6.0.3/shell/main.cpp:214 I haven't had this issue anymore on newer package versions. Closing this as a duplicate. *** This bug has been marked as a duplicate of bug 474893 *** |