Summary: | kde daemon crash | ||
---|---|---|---|
Product: | [Unmaintained] solid | Reporter: | Philip <rootadmin> |
Component: | bluetooth-daemon | Assignee: | Alex Fiestas <afiestas> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | bruno, cfeck, emilsedgh, iinm, jreznik, kavol, mail.aroessler, mail, manisandro, mbriza, rdieter, swedishelk, tittiatcoke, xavier, zhaldybin |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/bluedevil/744ff9bb65162db0ed3f07d5dc0166a20c46f136 | 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 New crash information added by DrKonqi valgrind log of kded4 crashlog (not that usefull) |
Description
Philip
2011-10-15 07:40:36 UTC
Are you using Network Manager? If yes, you could try disabling the networking related modules in System Settings, as described in http://kdepepo.wordpress.com/2011/05/11/troubleshooting-kded4-bugs/ Otherwise, a different module might cause the crash. Following the steps from the above link, you can isolate the offending module. This information is required for identifying the problem. *** Bug 291344 has been marked as a duplicate of this bug. *** Created attachment 68189 [details]
New crash information added by DrKonqi
kded4 ($Id$) on KDE Platform 4.8.00 (4.8.0 "release 462" using Qt 4.8.0
- What I was doing when the application crashed:
Logging in after suspend. After the login the crash manager appeared, this happens some times since I've installed KDE 4.8
-- Backtrace (Reduced):
#6 0x00007ff5767b5c90 in QObject::property (this=0x856cf0, name=0x7ff573533510 "_qdbus_slotCache") at kernel/qobject.cpp:3750
#7 0x00007ff5734f3d19 in QDBusConnectionPrivate::activateCall (this=0x858010, object=0x856cf0, flags=273, msg=...) at qdbusintegrator.cpp:807
#8 0x00007ff5734f4a9b in QDBusConnectionPrivate::activateObject (this=0x858010, node=..., msg=..., pathStartPos=<optimized out>) at qdbusintegrator.cpp:1423
#9 0x00007ff5734f4b8b in QDBusActivateObjectEvent::placeMetaCall (this=0x84ac40) at qdbusintegrator.cpp:1537
#10 0x00007ff5767bc926 in QObject::event (this=0x896540, e=<optimized out>) at kernel/qobject.cpp:1204
*** Bug 292420 has been marked as a duplicate of this bug. *** Created attachment 68405 [details]
New crash information added by DrKonqi
kded4 ($Id$) on KDE Platform 4.8.00 (4.8.0 "release 462" using Qt 4.8.0
- What I was doing when the application crashed:
Battery emtpy the system suspend correctly, Then I plug the power, wake up the computer okay.
The screensaver open (I've the analog clock on it) with the login box. But there's not background at that time.
I open the session at get the crash reporting dialog box. But the rest of the session is here, and all plasma related is running too.
-- Backtrace (Reduced):
#6 0x00007f2e1483fc90 in QObject::property (this=0x92f200, name=0x7f2e115bd510 "_qdbus_slotCache") at kernel/qobject.cpp:3750
#7 0x00007f2e1157dd19 in QDBusConnectionPrivate::activateCall (this=0x96a5a0, object=0x92f200, flags=273, msg=...) at qdbusintegrator.cpp:807
#8 0x00007f2e1157ea9b in QDBusConnectionPrivate::activateObject (this=0x96a5a0, node=..., msg=..., pathStartPos=<optimized out>) at qdbusintegrator.cpp:1423
#9 0x00007f2e1157eb8b in QDBusActivateObjectEvent::placeMetaCall (this=0xb721e0) at qdbusintegrator.cpp:1537
#10 0x00007f2e14846926 in QObject::event (this=0x9311c0, e=<optimized out>) at kernel/qobject.cpp:1204
*** Bug 293507 has been marked as a duplicate of this bug. *** This morning I created another bugreport as that the initial backtrace for this bug was different then mine. (I reported it using the drkonqi crash reporter). However reading through this bug report, it seems that the crash I experience is equal to this one. As I indicated in my original bugreport, is that I have noticed that having BlueDevil active as a service seems to cause the crash. Please note that it is not necessary to have active bluetooth connections for the system to crash. If I stop and deactivate the bluedevil service from running, then I can resume my laptop from sleep without any crashes and everything runs normal. If bluedevil is active, I receive a crash every time I resume from a sleep. With me Network Management plasmoid is active, but I am not sure if Network Management is somehow changed by having bluedevil active (just running, no active Bluetooth connections). Thanks for the update. Reassigning to bluetooth developers for further inspection. Created attachment 68768 [details]
New crash information added by DrKonqi
kded4 ($Id$) on KDE Platform 4.8.00 (4.8.0 "release 2" using Qt 4.8.0
- What I was doing when the application crashed: a kde 4.8.0 (opensuse 12.1 KR48 repository) I suspend the computer will wifi + bluetooth on (but no connection)
The only active connection during the suspend was a wired one (mono ipv4)
For the wake up, it was on a wired connection too, ipv4 + ipv6. Immediately after unlocking the screen the crash occurs.
-- Backtrace (Reduced):
#6 0x00007f42d806ac90 in QObject::property (this=0x93d320, name=0x7f42d4de8510 "_qdbus_slotCache") at kernel/qobject.cpp:3750
#7 0x00007f42d4da8d19 in QDBusConnectionPrivate::activateCall (this=0x976e40, object=0x93d320, flags=273, msg=...) at qdbusintegrator.cpp:807
#8 0x00007f42d4da9a9b in QDBusConnectionPrivate::activateObject (this=0x976e40, node=..., msg=..., pathStartPos=<optimized out>) at qdbusintegrator.cpp:1423
#9 0x00007f42d4da9b8b in QDBusActivateObjectEvent::placeMetaCall (this=0xc1c8a0) at qdbusintegrator.cpp:1537
#10 0x00007f42d8071926 in QObject::event (this=0x93fac0, e=<optimized out>) at kernel/qobject.cpp:1204
*** Bug 296575 has been marked as a duplicate of this bug. *** Created attachment 69994 [details]
New crash information added by DrKonqi
kded4 ($Id$) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.1
- What I was doing when the application crashed:
Unsuspended. Happens every time. My Bluedevil kded is stopped, though.
I use NetworkManager.
-- Backtrace (Reduced):
#6 0x00007f5eab2dca2c in QObject::thread (this=0x1b66ce0) at kernel/qobject.cpp:1371
#7 0x00007f5eab6a0476 in QDBusConnectionPrivate::activateCall (this=0x1b5b830, object=0x1b66ce0, flags=273, msg=...) at qdbusintegrator.cpp:802
#8 0x00007f5eab6a4b90 in QDBusConnectionPrivate::activateObject (this=0x1b5b830, node=..., msg=..., pathStartPos=16) at qdbusintegrator.cpp:1423
#9 0x00007f5eab6a5501 in QDBusActivateObjectEvent::placeMetaCall (this=0x7f5e8c012af0) at qdbusintegrator.cpp:1537
#10 0x00007f5eab2dc59d in QObject::event (this=0x1b665e0, e=0x7f5e8c012af0) at kernel/qobject.cpp:1195
Created attachment 70047 [details] New crash information added by DrKonqi kded4 ($Id$) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0 - What I was doing when the application crashed: the same as comment #11 - it crashes on wakeup, seems reproducible (nearly?) always wifi used, no bluetooth -- Backtrace (Reduced): #6 0x00007f7abbcb4cc2 in QObject::property (this=0x9d55c0, name=0x7f7abc05a3d0 "_qdbus_slotCache") at kernel/qobject.cpp:3741 #7 0x00007f7abc01cc8c in QDBusConnectionPrivate::activateCall (this=this@entry=0x9d1d60, object=0x9d55c0, flags=flags@entry=273, msg=...) at qdbusintegrator.cpp:807 #8 0x00007f7abc01d966 in QDBusConnectionPrivate::activateObject (this=0x9d1d60, node=..., msg=..., pathStartPos=<optimized out>) at qdbusintegrator.cpp:1423 #9 0x00007f7abc01da5b in QDBusActivateObjectEvent::placeMetaCall (this=0xb73730) at qdbusintegrator.cpp:1537 #10 0x00007f7abbcb70ee in QObject::event (this=0x9e08d0, e=<optimized out>) at kernel/qobject.cpp:1195 enough dups (and I can easily reproduce), confirmed. *** Bug 297270 has been marked as a duplicate of this bug. *** I can confirm removing or disabling the bluedevil kded module makes crashes go away. $rpm -q bluedevil bluedevil-1.3-0.2.rc1.fc17.x86_64 And some good news, reverting to bluedevil-1.2.2 build ... I can no longer reproduce this crash. So, seems particular to the 1.3 branch. *** Bug 298070 has been marked as a duplicate of this bug. *** *** Bug 296085 has been marked as a duplicate of this bug. *** This bug is also filed in Fedora as https://bugzilla.redhat.com/show_bug.cgi?id=794955 reported during KDE Plasma Workspaces Test Day. Created attachment 70657 [details]
valgrind log of kded4
Log showing where the crash happens for me.
Created attachment 70658 [details]
crashlog (not that usefull)
Here is the crashlog, it does not show where the cause of the crash happens.
Git commit 744ff9bb65162db0ed3f07d5dc0166a20c46f136 by Alex Fiestas. Committed on 26/04/2012 at 04:46. Pushed by afiestas into branch 'master'. Set a new Object as parent of BlueZAgent You can't register a child of a parent exposed with ExportChildObjects, if you do so the app may crash. for not making this patch too big I'm using the parent() reference from the BlueAgent object itself to delete the parent and this will delete the agent. I will improve it in BlueDevil 2.0 Versions minor to 1.3 are not affected by this bug since they use qApp as a parent instead of BlueDevilDAemon. M +2 -2 src/daemon/kded/BlueDevilDaemon.cpp M +1 -1 src/daemon/kded/bluezagent.cpp http://commits.kde.org/bluedevil/744ff9bb65162db0ed3f07d5dc0166a20c46f136 I can confirm that with the current git master, the KDED crash is no longer appearing. Thanks Ryamond ! really glad this is finally fixed |