| Summary: | kded4 crashes any time it is launched on login or manually started | ||
|---|---|---|---|
| Product: | [Unmaintained] solid | Reporter: | Shawn Starr <shawn.starr> |
| Component: | libsolid-upnp | Assignee: | Paulo Romulo <paulo.romulo> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | crash | CC: | afiestas, cfeck, cingulingu1, kossebau, phirestalker, rasasi78, rdieter, sloevenh1 |
| Priority: | HI | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| 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 kded4 star console log. kded4 crashes at every login attempt, backtrace |
||
|
Description
Shawn Starr
2011-07-15 18:32:12 UTC
Removing cagibi-0.2.0 stops kded from crashing. There is no "cagibi" product in bugzilla, assigning to solid, since cagibi is about device recovery. Hm, can't reproduce here, has always worked fine :( Can't see anythings suspicious from the backtrace so far. > Just start kded4. Hm, the networkwatcher kded module which has the code from kde-runtime/kioslave/network/network/builder/upnp/cagibidbuscodec.cpp inside should be only loaded on demand, not already on start of kded, see kde-runtime/kioslave/network/kded/networkwatcher.desktop: X-KDE-Kded-autoload=false X-KDE-Kded-load-on-demand=true And currently the only one triggering the loading of the networkwatcher kded module is the network:/ kio-slave AFAIK, solid turned away from it to use HUPnP to do UPnP device discovery decentralized (no comment on that, here). Shawn, could you please share the log of the kded commandline output, until it crashes? Anything else you do? In what environment do you start kded? > cagibi is about device recovery well, device _discovery_ ;) Created attachment 63840 [details]
New crash information added by DrKonqi
kded4 ($Id$) on KDE Platform 4.7.1 (4.7.1) using Qt 4.7.4
- What I was doing when the application crashed:
Happens after logging in to KDE. kded4 cannot be started without restarting the dbus service. Using Qt 4.8.0 beta1 or 4.7.4 doesn't make any difference.
kded4 console output:
"urn:dslforum-org:device:InternetGatewayDevice:1"
KCrash: Attempting to start /usr/bin/kded4 from kdeinit
sock_file=/home/squall38/.kde/socket-Altair/kdeinit4__0
QSocketNotifier: Invalid socket 30 and type 'Read', disabling...
KCrash: Application 'kded4' crashing...
KCrash: Attempting to start /usr/libexec/kde4/drkonqi from kdeinit
sock_file=/home/squall38/.kde/socket-Altair/kdeinit4__0
--
-- Backtrace (Reduced):
#6 QDBusArgumentPrivate::checkReadAndDetach (d=@0x7fff00000000) at qdbusargument.cpp:154
#7 0x00007fa757982549 in QDBusArgument::endMapEntry (this=0x7fff00000000) at qdbusargument.cpp:1036
#8 0x00007fa721c62558 in operator>> (argument=..., device=<optimized out>) at /usr/src/debug/kde-runtime-4.7.1/kioslave/network/network/builder/upnp/cagibidbuscodec.cpp:110
#9 0x00007fa75798756c in QDBusMetaType::demarshall (arg=..., id=<optimized out>, data=0xff9d80) at qdbusmetatype.cpp:285
#10 0x00007fa7579544d3 in QDBusConnectionPrivate::deliverCall (this=0xeb7060, object=0xf38100, msg=..., metaTypes=..., slotIdx=8) at qdbusintegrator.cpp:896
Created attachment 63841 [details]
New crash information added by DrKonqi
kded4 ($Id$) on KDE Platform 4.7.1 (4.7.1) using Qt 4.7.4
- What I was doing when the application crashed:
Happens after logging in to KDE. kded4 cannot be started without restarting the dbus service. Using Qt 4.8.0 beta1 or 4.7.4 doesn't make any difference.
kded4 console output:
"urn:dslforum-org:device:InternetGatewayDevice:1"
KCrash: Attempting to start /usr/bin/kded4 from kdeinit
sock_file=/home/squall38/.kde/socket-Altair/kdeinit4__0
QSocketNotifier: Invalid socket 30 and type 'Read', disabling...
KCrash: Application 'kded4' crashing...
KCrash: Attempting to start /usr/libexec/kde4/drkonqi from kdeinit
sock_file=/home/squall38/.kde/socket-Altair/kdeinit4__0
--
-- Backtrace (Reduced):
#6 QDBusArgumentPrivate::checkReadAndDetach (d=@0x7fff00000000) at qdbusargument.cpp:154
#7 0x00007fa757982549 in QDBusArgument::endMapEntry (this=0x7fff00000000) at qdbusargument.cpp:1036
#8 0x00007fa721c62558 in operator>> (argument=..., device=<optimized out>) at /usr/src/debug/kde-runtime-4.7.1/kioslave/network/network/builder/upnp/cagibidbuscodec.cpp:110
#9 0x00007fa75798756c in QDBusMetaType::demarshall (arg=..., id=<optimized out>, data=0xff9d80) at qdbusmetatype.cpp:285
#10 0x00007fa7579544d3 in QDBusConnectionPrivate::deliverCall (this=0xeb7060, object=0xf38100, msg=..., metaTypes=..., slotIdx=8) at qdbusintegrator.cpp:896
Julian, did you read comment #1? Your crash might be unrelated. To find out which module is crashing, you should also follow http://kdepepo.wordpress.com/2011/05/11/troubleshooting-kded4-bugs/ (In reply to comment #6) > Julian, did you read comment #1? Your crash might be unrelated. I have. Removing cagibi works around the problem but that's really ugly on Fedora because some kdebase packages depend on it. I've now put "ShutDownTimeout = 10" in /etc/cagibi.conf and kded4 no longer crashes now too. Created attachment 66362 [details]
New crash information added by DrKonqi
kded4 ($Id$) on KDE Platform 4.7.2 (4.7.2) "release 5" using Qt 4.7.4
- What I was doing when the application crashed:
it shows when I try to acess Network in dolphin
-- Backtrace (Reduced):
#6 QDBusArgumentPrivate::checkReadAndDetach (d=@0x7fff00000000) at qdbusargument.cpp:154
#7 0x00007f318033be09 in QDBusArgument::endMapEntry (this=0x7fff00000000) at qdbusargument.cpp:1036
[...]
#9 0x00007f318033f55c in QDBusMetaType::demarshall (arg=..., id=<optimized out>, data=0xab3c80) at qdbusmetatype.cpp:285
#10 0x00007f318030b725 in QDBusConnectionPrivate::deliverCall (this=0x8cf620, object=0xa114f0, msg=..., metaTypes=..., slotIdx=8) at qdbusintegrator.cpp:896
#11 0x00007f3180314d5f in QDBusCallDeliveryEvent::placeMetaCall (this=<optimized out>, object=<optimized out>) at qdbusintegrator_p.h:103
*** Bug 289637 has been marked as a duplicate of this bug. *** Created attachment 68255 [details]
New crash information added by DrKonqi
kded4 ($Id$) on KDE Platform 4.7.4 (4.7.4) using Qt 4.7.4
- What I was doing when the application crashed:
I had DrKonqui reporting a kded4 crash on KDE startup. Then every time I retried to start kded4 it crashed. I uninstalled cagibi 2.0 and now kded4 starts properly. Find attached a console log fot the kded4 start.
-- Backtrace (Reduced):
#6 0x00007f0c55150986 in QDBusArgumentPrivate::checkReadAndDetach(QDBusArgumentPrivate*&) () from /usr/lib/libQtDBus.so.4
#7 0x00007f0c55154a19 in QDBusArgument::endMapEntry() const () from /usr/lib/libQtDBus.so.4
#8 0x00007f0c2f3e1cc8 in operator>> (argument=..., device=<optimized out>) at ../../../../kioslave/network/network/builder/upnp/cagibidbuscodec.cpp:110
#9 0x00007f0c5515816c in QDBusMetaType::demarshall(QDBusArgument const&, int, void*) () from /usr/lib/libQtDBus.so.4
#10 0x00007f0c55124652 in QDBusConnectionPrivate::deliverCall(QObject*, int, QDBusMessage const&, QList<int> const&, int) () from /usr/lib/libQtDBus.so.4
Created attachment 68256 [details]
kded4 star console log.
Created attachment 68696 [details]
kded4 crashes at every login attempt, backtrace
Hello: I'm still on KDE 4.7.4 but now on Qt 4.8.1. I'm not experiencing the freeze. Could anyone confirm this? Thanks. HUPNP backend has been disabled, and set as unmaintained |