Summary: | Crash when dbus exits (crash in QDBusAbstractInterfacePrivate dtor) | ||
---|---|---|---|
Product: | [Unmaintained] kdelibs | Reporter: | Chris K. Jester-Young <cky> |
Component: | kdecore | Assignee: | kdelibs bugs <kdelibs-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | bruno, cky, gdr, halla, nicws9, rasasi78, sebsauer, stasnel |
Priority: | HI | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
Description
Chris K. Jester-Young
2011-06-21 21:41:14 UTC
Created attachment 61220 [details]
New crash information added by DrKonqi
python2 (1.6) on KDE Platform 4.6.2 (4.6.2) using Qt 4.7.2
- Unusual behavior I noticed:
After terminating dbus, the printer-applet crashes too. Included here is the backtrace for printer-applet.
-- Backtrace (Reduced):
#6 QSocketNotifier::setEnabled (this=0x2136ae0, enable=true) at kernel/qsocketnotifier.cpp:293
#7 0x00007f4f658e0489 in pyqtDBusHelper::readSocket (this=0x2148e60, fd=11) at /build/buildd/python-qt4-4.8.3/dbus/dbus.cpp:274
#8 0x00007f4f658e0cd0 in pyqtDBusHelper::qt_metacall (this=0x2148e60, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fff0befbda0) at moc_helper.cpp:75
[...]
#10 0x00007f4f70edeb7e in QSocketNotifier::activated (this=<value optimized out>, _t1=11) at .moc/release-shared/moc_qsocketnotifier.cpp:89
#11 0x00007f4f70e9cf4b in QSocketNotifier::event (this=0x2136ae0, e=0x7fff0befc460) at kernel/qsocketnotifier.cpp:317
Created attachment 62835 [details]
New crash information added by DrKonqi
kded4 ($Id$) on KDE Platform 4.6.2 (4.6.2) using Qt 4.7.2
- What I was doing when the application crashed:
This has happened about 5 minutes after restarting dbus. I have provided printer-applet stack trace in a different bug report, here's kded's one.
-- Backtrace (Reduced):
#7 0x00007f1d0f30e213 in QObject::~QObject (this=0x1b25b90, __in_chrg=<value optimized out>) at kernel/qobject.cpp:861
#8 0x00007f1d0f30e7f9 in QObject::~QObject (this=0x1b25b90, __in_chrg=<value optimized out>) at kernel/qobject.cpp:964
#9 0x00007f1d0c94adf0 in ~QDBusAbstractInterfacePrivate (this=0x1b2b660, __in_chrg=<value optimized out>) at qdbusabstractinterface_p.h:87
#10 QDBusAbstractInterfacePrivate::~QDBusAbstractInterfacePrivate (this=0x1b2b660, __in_chrg=<value optimized out>) at qdbusabstractinterface_p.h:87
#11 0x00007f1d0f30e645 in cleanup (this=0x1b2b590, __in_chrg=<value optimized out>) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:62
bug #276214 (kded4 crashes when dbus exits) and bug #280311 (calligra apps crash when closing & saving changes) report exact the same problem including the same backtrace. Marking confirmed cause now we have different users/developers with different applications having the same crash. *** Bug 280311 has been marked as a duplicate of this bug. *** I btw cannot reproduce myself even after intensive testing. So, probably a timing issue where something is destroyed in an unexpected order... Created attachment 63632 [details]
New crash information added by DrKonqi
kded4 ($Id$) on KDE Platform 4.6.2 (4.6.2) using Qt 4.7.2
- What I was doing when the application crashed:
Saw high CPU usage for dbus-daemon in system monitor. Ran "----@----:/etc/init.d$ sudo ./dbus restart"
- Unusual behavior I noticed: Noticed KDE Launcher was not responding, other applications running very slowly.
-- Backtrace (Reduced):
#7 0x00007fdbbf7ef213 in QObject::~QObject (this=0x1ea20c0, __in_chrg=<value optimized out>) at kernel/qobject.cpp:861
#8 0x00007fdbbf7ef7f9 in QObject::~QObject (this=0x1ea20c0, __in_chrg=<value optimized out>) at kernel/qobject.cpp:964
#9 0x00007fdbbce2bdf0 in ~QDBusAbstractInterfacePrivate (this=0x1eb5060, __in_chrg=<value optimized out>) at qdbusabstractinterface_p.h:87
#10 QDBusAbstractInterfacePrivate::~QDBusAbstractInterfacePrivate (this=0x1eb5060, __in_chrg=<value optimized out>) at qdbusabstractinterface_p.h:87
#11 0x00007fdbbf7ef645 in cleanup (this=0x1ea8050, __in_chrg=<value optimized out>) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:62
Created attachment 66807 [details]
New crash information added by DrKonqi
calligraplan (2.4 Beta 4) on KDE Platform 4.7.4 (4.7.4) "release 20" using Qt 4.8.0
- What I was doing when the application crashed:
I've worked on a Plan document. Closing Plan ask me if I want to save changes, hit the save button, then the crask appear.
-- Backtrace (Reduced):
#7 0x00007f347ed3b19a in QObject::~QObject (this=0x7df130, __in_chrg=<optimized out>) at kernel/qobject.cpp:853
#8 0x00007f347ed3b959 in QObject::~QObject (this=0x7df130, __in_chrg=<optimized out>) at kernel/qobject.cpp:939
#9 0x00007f347ba60d20 in ~QDBusAbstractInterfacePrivate (this=0x7ca260, __in_chrg=<optimized out>) at qdbusabstractinterface_p.h:88
#10 QDBusAbstractInterfacePrivate::~QDBusAbstractInterfacePrivate (this=0x7ca260, __in_chrg=<optimized out>) at qdbusabstractinterface_p.h:88
#11 0x00007f347ed3b6c0 in cleanup (pointer=<optimized out>) at ../../src/corelib/tools/qscopedpointer.h:62
Thank you for the crash report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you. Works with openSUSE Tumbleweed Linux 5.9.12-1-default x86_64 GNU/Linux nvidia: 450.80.02 Qt: 5.15.2 KDE Frameworks: 5.76.0 Plasma: 5.20.4 kmail2 5.15.3 (20.08.3) |