Comment 38 for bug 280997

The more I think on this, the more it aggravates me. I was scrolling through
the posts earlier to see if any of the dev's have even spoken up about it,
and I came across something to the effect of "not having time to fix it".
This isn't some obscure mouse that for some reason doesn't work, it's an
entire system and along with it, an array of devices. Mice, Keyboards,
modems, wireless/wired cards, headsets, etc. It's not even a single brand of
blue-tooth, but all of them. So far as I have read, it's not working in
Jaunty either... which is due in 3 months. How many distro's are we going to
go through before Bluetooth becomes important. Alot of people rely on it, I
for one have an external logitech BT keyboard I've missed using. And despite
what other people think, I don't believe borrowing Gnome packages for a
purely KDE distro is a "fix". If I had a porche and the engine broke, I'd
fix it, I wouldn't replace it with one from a VW Beetle. Not trying to start
a "flame war" over gnome vs kde, but if I wanted to fill my hard-drive with
gnome packages, don't you think I would have installed ubuntu instead of
kubuntu?

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

> I agree this is a very bad "publicity" for kde to just leave things broken.
> I sent an email to Tom Patzig (he mentioned in one answer from 2008-12-19
> that he welcome any help on fixing this) offering my help and didn't get any
> response at all, so dunno exactly wat's going on.
>
> --
> 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"
>