*** 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 Keyboard/Mous
*** 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 o
*** This bug is a duplicate of bug 148290 ***
https://bugs.launchpad.net/bugs/148290
** This bug has been marked a duplicate of bug 148290
[Gutsy] Logitec diNovo (USB BT) doesn't work at gdm level after boot any more
--
Blutooth DiNovo does not work after boot
https://bugs.launchpad.net/b
i install from synaptic the logitech-applet and lomoco and work fine.
--
Blutooth DiNovo does not work after boot
https://bugs.launchpad.net/bugs/96036
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ub
** Changed in: bluez-utils (Ubuntu)
Sourcepackagename: xorg-server => bluez-utils
--
Blutooth DiNovo does not work after boot
https://bugs.launchpad.net/bugs/96036
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mai
Thanks...
Will try it tonight. I think this is a bug in the Ubuntu environment though.
This bug should be registered om bluez-utils then.
2007/4/25, johan <[EMAIL PROTECTED]>:
>
> This is a work around:
> "A quick search around the Internet and it turns out that using the
> Synaptic Package Manag
This is a work around:
"A quick search around the Internet and it turns out that using the Synaptic
Package Manager to remove 'bluez-utils' solves the problem."
works great if you do that!
--
Blutooth DiNovo does not work after boot
https://bugs.launchpad.net/bugs/96036
You received this bug
Found something here about it:
http://www.bl0g.co.uk/index.php?dt=070128
--
Blutooth DiNovo does not work after boot
https://bugs.launchpad.net/bugs/96036
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing lis
same problem for me ...
--
Blutooth DiNovo does not work after boot
https://bugs.launchpad.net/bugs/96036
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubunt
** Changed in: xorg-server (Ubuntu)
Sourcepackagename: None => xorg-server
--
Blutooth DiNovo does not work after boot
https://bugs.launchpad.net/bugs/96036
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing li
Even with autologin via gdm the functionality stops.
But when run this way it hangs after gnome splash has been shown.
What is the common denominator for theese two ways of starting X and
gnome? Is it possibly some auto-something-system that restarts or starts
during this step?
Any suggestions?
Tested on several computers now. Same behaviour.
** Changed in: Ubuntu
Status: Needs Info => Confirmed
--
Blutooth DiNovo does not work after boot
https://bugs.launchpad.net/bugs/96036
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
13 matches
Mail list logo
