Ubuntu
bluedevil package

kded crashes at login

Bug #641297 reported by Phil Driscoll
256
This bug affects 43 people
Affects Status Importance Assigned to Milestone
bluedevil (Ubuntu)
Fix Released
Critical
Unassigned
Ubuntu ubuntu-10.10
Maverick
Fix Released
Critical
Unassigned
Ubuntu ubuntu-10.10

Bug Description

Binary package hint: kubuntu-docs

Application: kded4 ($Id: kded.cpp 1156841 2010-07-29 19:59:05Z zander $)
KDE Platform Version: 4.5.1 (KDE 4.5.1)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-22-generic i686
Distribution: Ubuntu maverick (development branch)

-- Information about the crash:
- What I was doing when the application crashed:
Immediately on logging in, KDED segfaults.
If i try to run kded manually from a terminal I get the message 'Aborted (core dumped)'
Problem started after installing a set of Maverick updates today.

The crash can be reproduced every time.

-- Backtrace:
Application: KDE Dæmon (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#7 0x0076c714 in QObject::connect (sender=0xb776d710, signal=0x2d4cf68 "2SessionConnected(QDBusObjectPath)", receiver=0x8cf4778, method=0x2d4cf44 "1SessionConnected(QDBusObjectPath)", type=Qt::AutoConnection) at kernel/qobject.cpp:2491
#8 0x02d3f850 in ObexFtpDaemon::ObexFtpDaemon(QObject*, QList<QVariant> const&) () from /usr/lib/kde4/kded_obexftpdaemon.so
#9 0x02d47068 in QObject* KPluginFactory::createInstance<ObexFtpDaemon, QObject>(QWidget*, QObject*, QList<QVariant> const&) () from /usr/lib/kde4/kded_obexftpdaemon.so
#10 0x00e68450 in KPluginFactory::create (this=0x8cf5e98, iface=0x8cf4778 "\b\375\324\002\ba\317\b\310E\317\b\300C\317\b", parentWidget=0x0, parent=0x8baa818, args=..., keyword=...) at ../../kdecore/util/kpluginfactory.cpp:191
#11 0x021a821b in create<KDEDModule> (this=0x8baa818, s=..., onDemand=false) at ../../kdecore/util/kpluginfactory.h:491
#12 Kded::loadModule (this=0x8baa818, s=..., onDemand=false) at ../../kded/kded.cpp:381
#13 0x021aa0c7 in Kded::initModules (this=0x8baa818) at ../../kded/kded.cpp:239
#14 0x021ac531 in KDEDApplication::newInstance (this=0xbf8c4cf0) at ../../kded/kded.cpp:818
#15 0x003a6800 in KUniqueApplicationAdaptor::newInstance (this=0x8cc1c20, asn_id=..., args=...) at ../../kdeui/kernel/kuniqueapplication.cpp:440
#16 0x003a6f62 in KUniqueApplicationAdaptor::qt_metacall (this=0x8cc1c20, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbf8c422c) at ./kuniqueapplication_p.moc:81
#17 0x0012f9dc in QDBusConnectionPrivate::deliverCall (this=0x8bb08b8, object=0x8cc1c20, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:916
#18 0x00130cbf in QDBusConnectionPrivate::activateCall (this=0x8bb08b8, object=0x8cc1c20, flags=337, msg=...) at qdbusintegrator.cpp:819
#19 0x00131770 in QDBusConnectionPrivate::activateObject (this=0x8bb08b8, node=..., msg=..., pathStartPos=16) at qdbusintegrator.cpp:1376
#20 0x00131a2a in QDBusActivateObjectEvent::placeMetaCall (this=0x8ccf968) at qdbusintegrator.cpp:1490
#21 0x007686a2 in QObject::event (this=0xbf8c4cf0, e=0xb776d710) at kernel/qobject.cpp:1219
#22 0x007559db in QCoreApplication::event (this=0xbf8c4cf0, e=0x8ccf968) at kernel/qcoreapplication.cpp:1561
#23 0x00ffb524 in QApplication::event (this=0xbf8c4cf0, e=0x8ccf968) at kernel/qapplication.cpp:2439
#24 0x00ff802c in QApplicationPrivate::notify_helper (this=0x8bab1b0, receiver=0xbf8c4cf0, e=0x8ccf968) at kernel/qapplication.cpp:4396
#25 0x00ffe09e in QApplication::notify (this=0xbf8c4cf0, receiver=0xbf8c4cf0, e=0x8ccf968) at kernel/qapplication.cpp:3798
#26 0x0039e68a in KApplication::notify (this=0xbf8c4cf0, receiver=0xbf8c4cf0, event=0x8ccf968) at ../../kdeui/kernel/kapplication.cpp:310
#27 0x00755b3b in QCoreApplication::notifyInternal (this=0xbf8c4cf0, receiver=0xbf8c4cf0, event=0x8ccf968) at kernel/qcoreapplication.cpp:732
#28 0x00758d8b in sendEvent (receiver=0x0, event_type=0, data=0x8b54f20) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#29 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8b54f20) at kernel/qcoreapplication.cpp:1373
#30 0x00758f4d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1266
#31 0x00784a74 in sendPostedEvents (s=0x8bcc910) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#32 postEventSourceDispatch (s=0x8bcc910) at kernel/qeventdispatcher_glib.cpp:277
#33 0x03930015 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#34 0x03933e28 in ?? () from /lib/libglib-2.0.so.0
#35 0x03934008 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#36 0x00784565 in QEventDispatcherGlib::processEvents (this=0x8b561d0, flags=...) at kernel/qeventdispatcher_glib.cpp:415
#37 0x010b9a35 in QGuiEventDispatcherGlib::processEvents (this=0x8b561d0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#38 0x00754609 in QEventLoop::processEvents (this=0xbf8c4c44, flags=) at kernel/qeventloop.cpp:149
#39 0x00754a8a in QEventLoop::exec (this=0xbf8c4c44, flags=...) at kernel/qeventloop.cpp:201
#40 0x0075900f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#41 0x00ff6e57 in QApplication::exec () at kernel/qapplication.cpp:3672
#42 0x021aacf7 in kdemain (argc=1, argv=0x8b9a070) at ../../kded/kded.cpp:894
#43 0x0804e4d1 in launch (argc=<value optimized out>, _name=<value optimized out>, args=<value optimized out>, cwd=0x0, envc=0, envs=0x0, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x80517f7 "0") at ../../kinit/kinit.cpp:723
#44 0x0805048d in main (argc=4, argv=0xbf8c5474, envp=0xbf8c5488) at ../../kinit/kinit.cpp:1835

Possible duplicates by query: bug 251527.

Report to https://bugs.kde.org

Revision history for this message
Alex Sidorenko (asid) wrote :

I have a similar problem after yesterday's Maverick update - but on login only, I can start kded4 manually fine and it works as expected.

Alex

Revision history for this message
Phil Driscoll (phil-dialsolutions) wrote :
Download full text (5.5 KiB)

Oops - I was trying to run kded not kded4.
However, if I try to run kded4 from konsole, it still crashes:

phil@philsx335:~$ kded4
QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance()
QDBusObjectPath: invalid path ""
KCrash: Attempting to start /usr/bin/kded4 from kdeinit
sock_file=/home/phil/.kde/socket-philsx335/kdeinit4__0
kded(16307): Communication problem with "kded" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" "

phil@philsx335:~$ KCrash: Application 'kded4' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
sock_file=/home/phil/.kde/socket-philsx335/kdeinit4__0

Application: kded4 ($Id: kded.cpp 1156841 2010-07-29 19:59:05Z zander $)
KDE Platform Version: 4.5.1 (KDE 4.5.1)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-22-generic i686
Distribution: Ubuntu maverick (development branch)

-- Information about the crash:
<In detail, tell us what you were doing when the application crashed.>

The crash can be reproduced every time.

-- Backtrace:
Application: KDE Dæmon (kded4), signal: Segmentation fault
[KCrash Handler]
#7 0x02db4714 in QObject::connect (sender=0xb7851710, signal=0x1d9ef68 "2SessionConnected(QDBusObjectPath)", receiver=0x8b0e200, method=0x1d9ef44 "1SessionConnected(QDBusObjectPath)", type=Qt::AutoConnection) at kernel/qobject.cpp:2491
#8 0x01d91850 in ObexFtpDaemon::ObexFtpDaemon(QObject*, QList<QVariant> const&) () from /usr/lib/kde4/kded_obexftpdaemon.so
#9 0x01d99068 in QObject* KPluginFactory::createInstance<ObexFtpDaemon, QObject>(QWidget*, QObject*, QList<QVariant> const&) () from /usr/lib/kde4/kded_obexftpdaemon.so
#10 0x00dbb450 in KPluginFactory::create (this=0x8b11bc0, iface=0x8b0e200 "\b\035\332\001 \026\261\b8\352\260\b\270\346\260\b", parentWidget=0x0, parent=0x8a12fa8, args=..., keyword=...) at ../../kdecore/util/kpluginfactory.cpp:191
#11 0x00a6821b in create<KDEDModule> (this=0x8a12fa8, s=..., onDemand=false) at ../../kdecore/util/kpluginfactory.h:491
#12 Kded::loadModule (this=0x8a12fa8, s=..., onDemand=false) at ../../kded/kded.cpp:381
#13 0x00a6a0c7 in Kded::initModules (this=0x8a12fa8) at ../../kded/kded.cpp:239
#14 0x00a6c531 in KDEDApplication::newInstance (this=0xbf980e90) at ../../kded/kded.cpp:818
#15 0x00564800 in KUniqueApplicationAdaptor::newInstance (this=0x8ad94e8, asn_id=..., args=...) at ../../kdeui/kernel/kuniqueapplication.cpp:440
#16 0x00564f62 in KUniqueApplicationAdaptor::qt_metacall (this=0x8ad94e8, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbf9803cc) at ./kuniqueapplication_p.moc:81
#17 0x0079d9dc in QDBusConnectionPrivate::deliverCall (this=0x8a0dfb0, object=0x8ad94e8, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:916
#18 0x0079ecbf in QDBusConnectionPrivate::activateCall (this=0x8a0dfb0, object=0x8ad94e8, flags=337, msg=...) at qdbusintegrator.cpp:819
#19 0x0079f770 in QDBusConnectionPrivate::activateObject (this=0x8a0dfb0, node=..., msg=..., pathStartPos=16) at qdbusintegrator.cpp:1376
#20 0x0079fa2a in QDBusActivateObjectEvent::placeMetaCall (this=0x8adfe70) at qdbusintegrator.cp...

Read more...

Revision history for this message
erdewit (erdewit) wrote :

I had the same error that Phil has and got rid of it by removing packages obex-data-server and obexd-client (this will also remove KDE bluetooth functionality).

Jonathan Thomas (echidnaman)
affects: kubuntu-docs (Ubuntu) → bluedevil (Ubuntu)
Revision history for this message
Leo Milano (lmilano) wrote :

I had the same crash, Kubuntu 64 bit, after upgrading from 10.04 to 10.10 beta. Removing all the obex related packages did the trick, many thanks to Erdewit.

This is a really problematic bug. It would prevent networkmanagement from working at all (the computer would not connect to the wireless AP). After removing the bluetooth packages everything went back to normal.

Is this a packaging issue?

Revision history for this message
Phil Driscoll (phil-dialsolutions) wrote :

I can confirm that removal of the packages obex-data-server and obexd-client stopped kded crashing for me.

Revision history for this message
Robert Clark (robert-a-clark) wrote :

I have removed all of the obex modules, but KDE still crashes at login. If it matters, I'm running a Win7 64 ultimate VirtualBox 3.2.8 host, with Meerkat. Meerkat is at the latest release as of 2010.09.18

Revision history for this message
Scott Kamp (scottkamp) wrote : Re: [Bug 641297] Re: kded crashes at login

ive removed

apt-get remove bluedevil gnome-bluetooth kbluetooth obex-data-server
obexd-client

rebooted and tried to login to kde on Kubuntu 10.10rc1 64bit and it still
kicks me out back to the login, so no joy, this isnt a fix

On Sat, Sep 18, 2010 at 12:10 PM, Robert Clark <email address hidden>wrote:

> I have removed all of the obex modules, but KDE still crashes at login.
> If it matters, I'm running a Win7 64 ultimate VirtualBox 3.2.8 host,
> with Meerkat. Meerkat is at the latest release as of 2010.09.18
>
> --
> kded crashes at login
> https://bugs.launchpad.net/bugs/641297
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (641539).
>

Revision history for this message
Götz Christ (g-christ) wrote :

Downgrading the bluedevil package from version 1.0~rc4-0ubuntu1 to 1.0~rc3-0ubuntu2 works as a workaroud for me, kded4 starts again.

KDE bug https://bugs.kde.org/show_bug.cgi?id=251359 It is fixed in master. Could you backport the fix?

Revision history for this message
Robert Clark (robert-a-clark) wrote :

Please find attached the .xsession-errors file that was rename to KDE_xsession_errors.

Revision history for this message
wonko (oekj) wrote :

Same problem and solution as Phil. And luckily, to my surprise, removing bluedevil did not stop my logitech dinovo edge (connected by bluetooth dongle) from working :) Thanks a bunch erdewit! Would have liked to try to downgrade bluedevil, but can't figure out how...

Revision history for this message
Esko Kauppinen (e-kauppinen) wrote :

I had the same error, noticed in rekonq having cookie probs (unable to start the cookie handler service). This ment that I could not log on to Gmail or to bank service. After removing all installed obex stuff and rebooting, all but bluetooth is ok.

Jonathan Thomas (echidnaman)
Changed in bluedevil (Ubuntu):
importance: Undecided → Critical
status: New → In Progress
Changed in bluedevil (Ubuntu Maverick):
milestone: none → ubuntu-10.10
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package bluedevil - 1.0~rc4-0ubuntu2

---------------
bluedevil (1.0~rc4-0ubuntu2) maverick; urgency=low

  * Add kubuntu_01_fix_obexdaemon_connect_crash.diff to fix a kded crash on
    startup. (LP: #641297)
 -- Jonathan Thomas <email address hidden> Sun, 19 Sep 2010 09:37:20 -0400

Changed in bluedevil (Ubuntu Maverick):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.