Comment 41 for bug 280997

Revision history for this message
SRElysian (srelysian) wrote : Re: [Bug 280997] Re: solid-bluetooth needs update for bluez 4.x

I am actually using KDE 4.2rc1 right now. Unless it sneaks in under the
radar at the last minute official release (which should be due by the end of
this month), it's doubtful it will make it in. I do understand that they are
all working hard, and I was a bit rude about it so I appologize. Just seems
to me that while using kde 4.2 (b1->b2->rc1), I've noticed alot of little
not-so-important things get fixed, while something as important as an entire
hardware system is overlooked :/ I'd gladly trade my spinning cube desktop
switcher for fully functional bluetooth :(

On Fri, Jan 16, 2009 at 8:00 AM, Niels Ganser <email address hidden> wrote:

> frapell: It's great that you want to assist in fixing this! You will
> probably have more success offering your help in
> https://bugs.kde.org/show_bug.cgi?id=172267 though, as this essentially
> is a KDE bug. In https://bugs.kde.org/show_bug.cgi?id=172267#c8 Tom
> references the repository experimental code can be found in that has
> already partially been ported.
>
> It would also help if every one of us voted an the KDE bug so that it
> gets fixed in the 4.2 release.
>
> SRELysian: I guess this bug doesn't really move forward simply because
> no (K)Ubuntu developer is personally affected. Don't get me wrong, I am
> as frustrated about this as you are but after all, all our days only
> have 24 hours so I'm not sure it makes sense to be angry at the
> developers (be it (K)Ubuntu or KDE).
>
> Clearly, this issue sneaked in shortly before the final move to KDE 4
> and once it came up, the transition was already too far progressed to
> stop it with the release coming too soon to fix it in time. So now we're
> just stuck with it. Hopefully only until KDE 4.2 though :)
>
> --
> 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"
>