kbluetooth4 - no icon in tray, if launched in konsole, exit with errors

Bug #281967 reported by lod on 2008-10-11
22
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdebluetooth (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: kdebluetooth

if launched in konsole
kbluetooth4(12634): KUniqueApplication: Cannot find the D-Bus session server

kbluetooth4(12633): KUniqueApplication: Pipe closed unexpectedly.

dbus is working

root 7354 1 0 01:48 ? 00:00:00 dbus-launch --autolaunch fd2a145bd559b2b96058a6f64821f81f --binary-syntax --close-stderr
root 7355 1 0 01:48 ? 00:00:00 //bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
lod 7375 7239 0 01:48 ? 00:00:00 /usr/bin/ck-launch-session /usr/bin/dbus-launch --exit-with-session /usr/bin/startkde
lod 7423 7375 0 01:48 ? 00:00:00 /usr/bin/ssh-agent /usr/bin/ck-launch-session /usr/bin/dbus-launch --exit-with-session /usr/bin/startkde
lod 7437 7375 0 01:48 ? 00:00:00 /bin/sh /usr/bin/startkde
lod 7440 1 0 01:48 ? 00:00:00 /usr/bin/dbus-launch --exit-with-session /usr/bin/startkde

kbluetooth4 was working fine until now.

katoda (katoda-jabster) wrote :
Download full text (3.5 KiB)

The same for me.
kbluetooth4-devicemanager can't connect with kbluetooth4:
kbluetooth4-devicemanager(7101) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: "BlueZ"
process 7101: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file dbus-message.c line 1070.
This is normally a bug in some application using the D-Bus library.
QDBusConnection: error: could not send message to service "org.bluez" path "" interface "org.freedesktop.DBus.Introspectable" member "Introspect"
kbluetooth4-devicemanager(7101) DeviceMan::DeviceMan: Device Manager - Welcome
kbluetooth4-devicemanager(7101) DeviceMan::getConfiguredDevices: Device List Size: 0
kbluetooth4-devicemanager(7101) DeviceMan::slotStartWizard: Starting Wizard
kbluetooth4-wizard(7106) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: "BlueZ"
process 7106: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file dbus-message.c line 1070.
This is normally a bug in some application using the D-Bus library.
QDBusConnection: error: could not send message to service "org.bluez" path "" interface "org.freedesktop.DBus.Introspectable" member "Introspect"
Object::connect: No such slot BTWizard::slotValidatePage()
kbluetooth4-wizard(7106) BTWizard::slotNext: Page ID: 1
kbluetooth4-wizard(7106) BTWizard::slotNext: Page ID: 2
kbluetooth4-wizard(7106) BTWizard::slotNext: page 2 reached!
kbluetooth4-wizard(7106) BTWizard::slotSearch: searching...
process 7106: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file dbus-message.c line 1070.
This is normally a bug in some application using the D-Bus library.
QDBusConnection: error: could not send message to service "org.bluez" path "" interface "org.bluez.Adapter" member "DiscoverDevices"
kbluetooth4-wizard(7106) BTWizard::~BTWizard: Deleting Wizard
kbluetooth4-devicemanager(7101) DeviceMan::~DeviceMan: inputDeviceMap deleted
kbluetooth4-devicemanager(7101) DeviceMan::~DeviceMan: remoteDeviceMap deleted
kbluetooth4-devicemanager(7101) DeviceMan::~DeviceMan: Device Manager closed

DBus is working:
katoda@compal ~ $ ps aux | grep dbus
105 4974 0.0 0.0 3040 1360 ? Ss 07:42 0:00 /bin/dbus-daemon --system
root 5689 0.0 0.0 3124 680 ? S 07:43 0:00 dbus-launch --autolaunch 19452e83451b572343b675ec48f6e5fe --binary-syntax --close-stderr
root 5692 0.0 0.0 2640 728 ? Ss 07:43 0:00 //bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
katoda 5750 0.0 0.0 3532 960 ? Ss 07:43 0:00 /usr/bin/ck-launch-session /usr/bin/dbus-launch --exit-with-session x-session-manager
katoda 5791 0.0 0.0 4740 636 ? Ss 07:43 0:00 /usr/bin/ssh-agent /usr/bin/ck-launch-session /usr/bin/dbus-launch --exit-with-session x-session-manager
katoda 5808 0.0 0.0 3124 672 ? S 07:43 0:00 /usr/bin/dbus-launch --exit-with-session x-session-ma...

Read more...

Jithin Emmanuel (jithin1987) wrote :

I have a problem something similar to this. I have no tray icon, but when I run from konsole it says

~$ kbluetooth4
kbluetooth4
KBluetooth4 is already running!

Marc Bres Gil (marc-bres) wrote :

The same it's happening to me, I have no bluetooth icon in the tray, but when trying to start kbluetooth4 from konsole, says it's already running.
Then I start kbluetooth4-devicemanager from konsole, but when I click at the Add device button, throws me the error:

arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file dbus-message.c line 1070.
This is normally a bug in some application using the D-Bus library.
QDBusConnection: error: could not send message to service "org.bluez" path "" interface "org.freedesktop.DBus.Introspectable" member "Introspect"

I can get any traces you need to solve this bug.

Thanks!

Jimmy (jimmygirardet) wrote :

same thing.
Was working fine before today but I did an upgrade and since it fails.

Mato Konecny (konecm) wrote :

same for me

lod (altoas) wrote :

I've found this info at Kubuntu 8.10 RC release info:
"Bluetooth is currently broken for Kubuntu Intrepid due to a last minute upgrade of the bluez stack. We hope to have a fix for this but only as an update after release, 2008. https://launchpad.net/bugs/280997"

thefuzz4 (jason-hamilton) wrote :

I can confirm that I also am unable to add devices when attempting to search I get this in the konsole.

kbluetooth4-wizard(28930) BTWizard::slotNext: Page ID: 2
kbluetooth4-wizard(28930) BTWizard::slotNext: page 2 reached!
kbluetooth4-wizard(28930) BTWizard::slotSearch: searching...
process 28930: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file dbus-message.c line 1070.
This is normally a bug in some application using the D-Bus library.
QDBusConnection: error: could not send message to service "org.bluez" path "" interface "org.bluez.Adapter" member "DiscoverDevices"

Reading the bug report linked by lod I think this bug report should be closed as a duplicate. To me it seems quite clear that this bug is a direct result of 280997. What do you think?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers