Comment 44 for bug 280997

You have my (20) vote(s). Hopefully this will change the priority a little.

On Fri, Jan 16, 2009 at 8:40 AM, frapell <email address hidden> wrote:

> @Niels Ganser:
> Yes, that was the answer i was referring to... forgot to add a link there,
> heh...
> The mail i sent him was asking how to start, if i should read something
> first, etc... but i will get the code and see if there's something i can
> contribute...
>
> And yes, is a wonderful idea... everybody that want's this fixed NOW, go
> to https://bugs.kde.org/show_bug.cgi?id=172267 create an account and
> give that bug 20 votes :)
>
> --
> solid-bluetooth needs update for bluez 4.x
> https://bugs.launchpad.net/bugs/280997
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in KDE Base Components: Confirmed
> Status in Ubuntu Release Notes: Fix Released
> Status in "kdebase-workspace" source package in Ubuntu: Triaged
> Status in kdebase-workspace in Ubuntu Intrepid: Confirmed
>
> Bug description:
> Binary package hint: kdebase-workspace
>
> Bluetooth still doesn't work after the kdebluetooth fixes.
>
> :/usr/bin$ kbluetooth4-devicemanager
> kbluetooth4-devicemanager(8525)
> Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: "BlueZ"
> process 8525: 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(8525) DeviceMan::DeviceMan: Device Manager -
> Welcome
> kbluetooth4-devicemanager(8525) DeviceMan::getConfiguredDevices: Device
> List Size: 0
> kbluetooth4-devicemanager(8525) DeviceMan::slotStartWizard: Starting Wizard
> kbluetooth4-wizard(8542) Solid::Control::ManagerBasePrivate::loadBackend:
> Backend loaded: "BlueZ"
> process 8542: 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(8542) BTWizard::slotNext: Page ID: 1
> kbluetooth4-wizard(8542) BTWizard::slotNext: Page ID: 2
> kbluetooth4-wizard(8542) BTWizard::slotNext: page 2 reached!
> kbluetooth4-wizard(8542) BTWizard::slotSearch: searching...
> process 8542: 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"
>