[Gutsy] Logitec diNovo (USB BT) doesn't work at gdm level after boot any more

[schnollk]

after upgrade on Sept. 30th (to Gutsy beta?) I noticed the diNovo set not working. I only found out after unplugging the dongle and plugging it back in again and diNovo worked again. I gave no further notice. But today as I booted my computer diNovo didn't work at gdm level for login again (it did work at grub level though). Again a work around was to unplug the dongle and plug it back in again. The desktop set (keyboard, mouse and keypad) worked well all the while untill Sunday.

Unfortunatelly I don't have a lsusb output of when diNovo doesn't work. I hopefully will not forget it at my next boot.

$ lsusb | grep 'Logitech' #now that it's working
Bus 004 Device 008: ID 046d:c70c Logitech, Inc.
Bus 004 Device 007: ID 046d:c70b Logitech, Inc.
Bus 004 Device 006: ID 046d:0b02 Logitech, Inc.
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu gutsy (development branch)
Release: 7.10
Codename: gutsy

[schnollk (schnollk)]

maybe it's a doublicate of Bug #96036? But if so, why did it work until now? I don't have the time right now to test the suggestions in that bug. Will update if done.

[schnollk (schnollk)]

oh, and this:
~$ uname -a
Linux ubuntu-desktop-i386 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 GNU/Linux

[schnollk (schnollk)]

also these outputs as found in Bug #83484:
$ hcitool dev
Devices:
$ hid2hci
Switching device 046d:c70c to HCI mode failed (No such file or directory)
Switching device 046d:c70b to HCI mode failed (No such file or directory)

and just in case it's bluez-utils:
$ apt-show-versions bluez-utils
bluez-utils/gutsy uptodate 3.19-0ubuntu2

[schnollk (schnollk)]

After a reboot with dongle pluged in all the whle, again no diNovo at (gdm) login prompt. Output now:
~$ hcitool dev
Devices:
        hci0 00:07:61:41:5D:3A
$ hid2hci
Switching device 046d:c70c to HCI mode failed (No such file or directory)
Switching device 046d:c70b to HCI mode failed (No such file or directory)
$ lsusb | grep Logitech
Bus 004 Device 005: ID 046d:c709 Logitech, Inc.
Bus 004 Device 004: ID 046d:c70c Logitech, Inc.
Bus 004 Device 003: ID 046d:c70b Logitech, Inc.
Bus 004 Device 002: ID 046d:0b02 Logitech, Inc.

Then I took out the dongle and plugged it back in. diNovo worked with output now:
$ hcitool dev
Devices:
$ hid2hci
Switching device 046d:c70b to HCI mode failed (No such file or directory)
Switching device 046d:c70c to HCI mode failed (No such file or directory)
$ lsusb | grep Logitech
Bus 004 Device 007: ID 046d:c70b Logitech, Inc.
Bus 004 Device 008: ID 046d:c70c Logitech, Inc.
Bus 004 Device 006: ID 046d:0b02 Logitech, Inc.

Right now it's a minor issue to me but nevertheless I hope it can be fixed. Don't hisitate to ask for more information.

[schnollk (schnollk)]

as suggested here

https://bugs.launchpad.net/ubuntu/+source/bluez-utils/+bug/96036/comments/5

I have now removed bluez-utils (version 3.19-0ubuntu2 by the way) and will see what happens next time I reboot.

PS. After I reinstalled bluez-utils to find out the package version (only after that I noticed an aptitude show | grep Version would have done) I noticed that right after starting bluetooth services the mouse cursor stopped responding (I had been moving it around the whole time):

$ sudo aptitude remove bluez-utils+
[schnipp]
The following NEW packages will be installed:
  bluez-utils
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/471kB of archives. After unpacking 1303kB will be used.
Writing extended state information... Done
Selecting previously deselected package bluez-utils.
(Reading database ... 199796 files and directories currently installed.)
Unpacking bluez-utils (from .../bluez-utils_3.19-0ubuntu2_i386.deb) ...
Setting up bluez-utils (3.19-0ubuntu2) ...
Creating device nodes ...
udev active, devices will be created in /dev/.static/dev/
 * Starting Bluetooth services [ OK ]

^right here the cursor stopped moving.

Is there a way to start the bluetooth services in debug mode, something like /etc/init.d/bluetooth start-debug?

[schnollk (schnollk)]

A workaround so you don't have to remove bluez-utils is to
~$ sudo rm -f /etc/rc2.d/S25bluetooth
This will not run bluetooth services automatically at boot time. Do
~$ sudo /etc/init.d/bluetooth start
if you need bluetooth and then unplug the dongle, wait 2 sec and plug it back in again.

If you wish to start bluetooth at boot time again do
sudo ln -s /etc/init.d/bluetooth /etc/rc2.d/S25bluetooth

[tommy (yobbobandana)]

I'm having this problem too. Running fully updated Gutsy Beta.

My Logitech Dinovo Edge doesn't work after a reboot until I turn the keyboard off and then on again, or remove and plug in the usb dongle.

Disabling bluetooth under System > Administration > Services is the easiest workaround for me.

[Alex Mayorga (alex-mayorga)]

@schnollk, tommy,

This is what worked for me and I still keep Bluetooth capabilities of the dongle http://ubuntuforums.org/showthread.php?p=2334318#post2334318

This is still a hack, hope it'll point the developers on the right direction.

[Pascal De Vuyst (pascal-devuyst)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug is a duplicate of bug #123920, it has the same hardware and more recent information. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.