bluetooth mouse and keyboard do not work with kde

[ikesterhaney]

Binary package hint: kde-hal-device-manager

My Logitech Mouse and Keyboard do not work with KDE. The bt connection thing says device at (hardware address) is connected, but wants to access files and such on it. Having no files or such on my mouse and keyboard, I find this to be ridiculous. The mouse and keyboard work fine for grub and the bios menus. Only KDE seems to think that they are storage devices.
They work fine under other distributions, although I have not actually loaded KDE in the other distributions yet.

[pittipatti (pittipatti)]

ikesterhaney ,

thank you for your bug-report.
Which keyboard/mouse from logitech are you using?
If you're using the bluetooth-dongle shipped with the keyboard/mouse, can you please try to unplug and replug the dongle and check if the keyoard is working then?

Can you further please attach the output of "lsusb" as an attachment.

[ikesterhaney (ikesterhaney)]

It is a Logitech DiNovo Laser Bluetooth Combo kit.
The Logitech Bluetooth hub came with the set.
Unfortunately, I have installed open Suse in place of Kubuntu right now.
I am under the impression that this bug is in the KDE side of things. I guess this got fixed upstream since the versionof KDE 4 I have installed right now works fine.
I will run lusb tommorow under Open Suse and post the results.

[pittipatti (pittipatti)]

Thank you for your answer.

As far as I can see this seems to be a duplicate of bug 123920 anyway, and I'll mark it as one.
Do you remeber if you had to peer your keyboard on the first boot with opensuse, e.g. enter a numeric key which was shown while booting?

It would still be fine if you could append your output of lsusb.
Thank you!

[bubbalouie (ryan-gossink)]

This bug did not exist on ubuntu 7.04 it has been present since Ubuntu
7.10, open suse has not been tested with these devices. They all
connect fine at boot, there is no problem there (a pairing key was
only required the very first time they connected to the machine). They
disconnect when the computer has been left alone for a little while.
They will not reconnect until after the bluetooth service has been
restarted. The Logitech dongle is not connected at all with this
system. As per you request (the laptop model is Vaio VGN-FE35GP):

Output of lsusb:

Bus 005 Device 003: ID 0ac8:c002 Z-Star Microelectronics Corp.
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 002: ID 044e:300c Alps Electric Co., Ltd
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

Ouput of hidd:

00:07:61:4B:C7:30 Logitech Bluetooth Keyboard [046d:b307] connected
00:07:61:63:F7:96 Logitech Bluetooth Mouse [046d:b003] connected

It is important to note here that everything works perfectly for an
arbitrarily large amount of time so long as the computer is not left
alone for a several minutes. At which point the bluetooth connection
is 'lost', the only solution is a reboot (or more practically to
restart the bluetooth service). At no point is a logitech dongle used,
this all happens using the laptops internal bluetooth adapter.

The other computer with a different dinvo keyboard & mouse set does
not use bluetooth to communicate with they peripherals, it relies on
the dongles HIDD mode which has been locked as per my previous
comment, this system experiences no issues.

On 7/30/08, pittipatti <email address hidden> wrote:
> *** This bug is a duplicate of bug 123920 ***
> https://bugs.launchpad.net/bugs/123920
>
> Thank you for your answer.
>
> As far as I can see this seems to be a duplicate of bug 123920 anyway, and I'll mark it as one.
> Do you remeber if you had to peer your keyboard on the first boot with opensuse, e.g. enter a numeric key which was shown while booting?
>
> It would still be fine if you could append your output of lsusb.
> Thank you!
>
> ** This bug has been marked a duplicate of bug 123920
> Bluetooth Logitech Dinovo Keyboard/Mouse don't work
>
>
> --
> bluetooth mouse and keyboard do not work with kde
> https://bugs.launchpad.net/bugs/228204
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (via bug 123920).
>