KDE4 Bluetooth

View: New views
6 Messages — Rating Filter:   Alert me  

KDE4 Bluetooth

by Bugzilla from elyk53@gmail.com :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

As the KDE3 version of kbluetooth has almost completely ceased to function on kde 4.3 in testing, I decided to test out the version of kbluetooth4 that's in experimental. It appears to launch without trouble, but is unable to see any bluetooth devices. If I launch it from the console, I see the following diagnostic output:
QDBusObjectPath: invalid path ""
QDBusObjectPath: invalid path ""
process 28753: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file dbus-message.c line 1074.                                                                                                                              
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 "GetProperties"  
process 28753: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file dbus-message.c line 1074.                                                                                                                              
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 "RegisterAgent"  
QDBusObjectPath: invalid path ""                                                                                                    
AGENT registered !                                                                                                                  
process 28753: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file dbus-message.c line 1074.                                                                                                                              
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 "GetProperties"  
process 28753: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file dbus-message.c line 1074.                                                                                                                              
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 "GetProperties"  
kyle@Fireman53:~$ process 28753: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file dbus-message.c line 1074.                                                                                                            
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 "UnregisterAgent"

Setting my computer to be discoverable gives me the following messages:
Object::connect: No such signal Solid::Control::BluetoothInterface::discoverableTimeoutChanged(int)
Object::connect:  (receiver name: 'AdapterWidget')
Object::connect: No such signal Solid::Control::BluetoothInterface::nameChanged(const QString&)
Object::connect:  (receiver name: 'AdapterWidget')
Object::connect: No such signal Solid::Control::BluetoothInterface::discoverableTimeoutChanged(int)
Object::connect:  (receiver name: 'AdapterWidget')
Object::connect: No such signal Solid::Control::BluetoothInterface::nameChanged(const QString&)
Object::connect:  (receiver name: 'AdapterWidget')
Agent Release
Object::connect: No such signal Solid::Control::BluetoothInterface::discoverableTimeoutChanged(int)
Object::connect:  (receiver name: 'AdapterWidget')
Object::connect: No such signal Solid::Control::BluetoothInterface::nameChanged(const QString&)
Object::connect:  (receiver name: 'AdapterWidget')
Object::connect: No such signal Solid::Control::BluetoothInterface::discoverableTimeoutChanged(int)
Object::connect:  (receiver name: 'AdapterWidget')
Object::connect: No such signal Solid::Control::BluetoothInterface::nameChanged(const QString&)
Object::connect:  (receiver name: 'AdapterWidget')
AGENT registered !
KCrash: Application 'kbluetooth4' crashing...

As you can see, it crashed shortly after.
Any ideas on what might be going wrong? Is there DBUS permission that I need to change? I'm already a part of both the bluetooth and netdev groups.
Thanks


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...


Re: KDE4 Bluetooth

by Vincent Frison-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

Is the KDE bluetooth framework still broken in KDE4?

The kdebluetooth package from unstable seems to be for KDE3 only.

In fact I think I managed to have kdebluetooth working on my KDE4 a few months
ago. But now there's nothing I can do, no action are "clickable" from the
kbluetooth systray! It's like I have no BT device on my laptop. But I can see
that a BT device is detected by the kernel and I have all bluetooth and bluez*
packages installed.

Thanks for your help,

Vincent.


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...


Parent Message unknown Re: KDE4 Bluetooth

by Bugzilla from debianx11@gmail.com :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello,  http://packages.debian.org/experimental/kdebluetooth

2009/10/25 Vincent Frison <vincent.frison@...>

Hi,

Is the KDE bluetooth framework still broken in KDE4?

The kdebluetooth package from unstable seems to be for KDE3 only.

In fact I think I managed to have kdebluetooth working on my KDE4 a few months
ago. But now there's nothing I can do, no action are "clickable" from the
kbluetooth systray! It's like I have no BT device on my laptop. But I can see
that a BT device is detected by the kernel and I have all bluetooth and bluez*
packages installed.

Thanks for your help,

Vincent.


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...




--
GNU/Linux user #388803
Debian Squeeze/Sid
Kernel 2.6.29-phenomx4
NVIDIA Kernel Module 185.18.31
Kde 4.3.2

Only two things are infinite, the universe and human stupidity, and I'm not
sure about the former.
Albert Einstein

"there really is no patch for human stupidity"
Mike Danseglio

Re: KDE4 Bluetooth

by Vincent Frison-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Sunday 25 October 2009 at 19:04:48, zakary Flores wrote:
> Hello,  http://packages.debian.org/experimental/kdebluetooth

Thanks for the info!

Any idea why it's not yet in the testing repository?
 


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...


Re: KDE4 Bluetooth

by Bugzilla from modestas@vainius.eu :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello,

On pirmadienis 26 Spalis 2009 20:05:08 Vincent Frison wrote:
> On Sunday 25 October 2009 at 19:04:48, zakary Flores wrote:
> > Hello,  http://packages.debian.org/experimental/kdebluetooth
>
> Thanks for the info!
>
> Any idea why it's not yet in the testing repository?

Because maintainer thinks it is not ready for general consumption yet.

--
Modestas Vainius <modestas@...>


signature.asc (205 bytes) Download Attachment

Re: KDE4 Bluetooth

by Achim Schaefer :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Am Montag 26 Oktober 2009 20:12:45 schrieb Modestas Vainius:

> > Any idea why it's not yet in the testing repository?
>
> Because maintainer thinks it is not ready for general consumption yet.

I think I've got to agree here.
I tried it today but got got some crashes. Was only on a virtualbox guest
system, so not always the easiest part,

Achim


signature.asc (205 bytes) Download Attachment