*** This bug is a duplicate of bug 123920 ***
https://bugs.launchpad.net/bugs/123920
** This bug is no longer a duplicate of bug 318465
Logitech MX5000 doesn't connect via bluetooth under ubuntu
** This bug has been marked a duplicate of bug 123920
Bluetooth Logitech Dinovo
*** This bug is a duplicate of bug 318465 ***
https://bugs.launchpad.net/bugs/318465
** This bug is no longer a duplicate of bug 123920
Bluetooth Logitech Dinovo Keyboard/Mouse don't work
** This bug has been marked a duplicate of bug 318465
Logitech MX5000 doesn't connect via bluetooth
*** This bug is a duplicate of bug 123920 ***
https://bugs.launchpad.net/bugs/123920
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
@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.
--
[Gutsy] Logitec diNovo (USB BT) doesn't work at gdm
** Changed in: bluez-utils (Ubuntu)
Sourcepackagename: None = bluez-utils
--
[Gutsy] Logitec diNovo (USB BT) doesn't work at gdm level after boot any more
https://bugs.launchpad.net/bugs/148290
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
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.
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
After a reboot with dongle pluged in all the whle, again no diNovo at (gdm)
login prompt. Output now:
~$ hcitool dev
Devices:
hci000: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
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
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.
--
[Gutsy] Logitec diNovo (USB BT) doesn't work at gdm level after boot any more
https://bugs.launchpad.net/bugs/148290
You
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
--
[Gutsy] Logitec diNovo (USB BT) doesn't work at gdm level after boot any more
https://bugs.launchpad.net/bugs/148290
You received this bug notification because you are a
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
12 matches
Mail list logo
