kblueplugd crashed with DBusException in call_blocking()

Also seeing this problem after upgrading to the new bluetooth package.

Problem happened with an on-line upgrade from 08.04 to 08.10 as well.
Laptop specs.
Intel core 2 duo processor
2gb ram
intel GMA950.
Fujitsu Siemens Amilo series.

same here. got a report-bug-message after upgrade/reboot. I hope, the necessary informations have been uploaded somewhere... at least report-bug told so

greetings
karl

Yes. The problem is a new version of the bluetooth libraries was uploaded
without it being tested against KDE. We are broken until the package can
be changed to work with the newer infrastructure.

The error occured after i upgrade/rebooted as well, but i dont really have bluetooth so it should not be a problem.

Also happened to me. Kubuntu Intrepid 32-bit up-to-date; Inspiron 6000 with Intel Celeron M 1.4 GHz, 2 GB RAM and Intel 915 graphics... And Bluetooth, apparently.

Actually, to parallel the note I just left in bug https://bugs.launchpad.net/ubuntu/+source/dbus-python/+bug/212388 I should probably point out that I also got a very similar crash in Python, and there are apparently other KDE python programs failing the same way (that bug is for /usr/share/python-support/kde-guidance-powermanager/guidance-power-manager.py)

The guidance-power-manager bug produces a similar backtrace, but is a
competely different issue do to it not reacting well if hal goes missing.

This also happens on the 64bit version of Kubuntu, not only the 32bit.

I can also confirm this bug, today it appeared when I started a new kde sessions after last intrepid upgrade.

The same thing is happened after a last intrepid upgrade.

confirm problem

Second confirmation of 64bit Kubuntu 8.10.

I'm also confirming this for kubuntu 64bit (8.10)

I can also confirm this in 8.10 on Kubuntu installed from Beta release.

No need for more 'me too' comments on this bug. It's well confirmed at this point.

This bug was fixed in the package kdebluetooth - 1:0.2-0ubuntu2

---------------
kdebluetooth (1:0.2-0ubuntu2) intrepid; urgency=low

  * debian/kblueplugd:
    - Update to 4.x API (LP: #279983)
  * debian/control:
    - Depend on bluetooth instead of the transitional bluez-utils
      package (LP: #279958)

 -- Mario Limonciello <email address hidden> Thu, 09 Oct 2008 14:18:12 -0500

you are sure version of package is exactly 1:0.2-0ubuntu2 and not 1:0.2-0ubuntu1?
with 1:0.2-0ubuntu1 kdeplugd crash
if new version is 1:0.2-0ubuntu2 a this moment is not in repository

The bug gets marked closed when it's uploaded. It has to be compiled and then
added to the repository before it's available. Some lag in the process is
normal.

yes, i know, my question was only a doubt
tank you

this happens to me as well on 32bit intrepid. after upgrade and restart as mentioned above.

this happens to me

Oct 10 00:01:29 kub-kal bluetoothd[7207]: Bluetooth daemon
Oct 10 00:01:29 kub-kal bluetoothd[7207]: Starting SDP server
Oct 10 00:01:29 kub-kal bluetoothd[7207]: Starting experimental netlink support
Oct 10 00:01:29 kub-kal bluetoothd[7207]: Failed to find Bluetooth netlink family
Oct 10 00:01:29 kub-kal bluetoothd[7207]: Can't init plugin /usr/lib/bluetooth/plugins/netlink.so
Oct 10 00:01:29 kub-kal bluetoothd[7207]: Can't create GN bridge
Oct 10 00:01:29 kub-kal bluetoothd[7207]: HCI dev 0 registered
Oct 10 00:01:29 kub-kal bluetoothd[7207]: HCI dev 0 already up
Oct 10 00:01:29 kub-kal bluetoothd[7207]: Registered interface org.bluez.Service on path /org/bluez/hci0
Oct 10 00:01:29 kub-kal bluetoothd[7207]: Registered interface org.bluez.SerialProxyManager on path /org/bluez/hci0
Oct 10 00:01:29 kub-kal bluetoothd[7207]: Registered interface org.bluez.NetworkPeer on path /org/bluez/hci0
Oct 10 00:01:29 kub-kal bluetoothd[7207]: Registered interface org.bluez.NetworkHub on path /org/bluez/hci0
Oct 10 00:01:29 kub-kal bluetoothd[7207]: Registered interface org.bluez.NetworkRouter on path /org/bluez/hci0
Oct 10 00:01:29 kub-kal bluetoothd[7207]: Adapter /org/bluez/hci0 has been enabled
Oct 10 00:01:29 kub-kal bluetoothd[7207]: Starting security manager 0

kblueplugd
# of devices at startup: 1
kbluetooth4(7219) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: "BlueZ"
kbluetooth4(7219) KBlueTray::offlineMode: offline Mode
waiting for bt device (un)plug events ...

kbluetooth4-devicemanager
QDBusConnection: error: could not send message to service "org.bluez" path "" interface "org.bluez.Adapter" member "DiscoverDevices"

kdebluetooth:
  Installed: 1:0.2-0ubuntu2
  Candidate: 1:0.2-0ubuntu2
  Version table:
 *** 1:0.2-0ubuntu2 0
        500 http://archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

Linux kub-kal 2.6.27-6-generic #1 SMP Tue Oct 7 04:15:04 UTC 2008 i686 GNU/Linux

Yes. More work to be done to get a running bluetooth stack. See Bug #280997
for details. Please add any new information there.