I confirm this, after a fresh install if you change the gdm theme to:
Theme: Selected Only
and choose a single theme, upon reboot you get:
Theme: Random from Selected
and a few themes selected which usually are the circles gnome ones
If you choose the correct theme then it gets stored
--
At fi
Pete you could still use the legacy tech since it involve the legacy daemons,
but you must do the pairing manually.
Another technique, for gnome users, could be recover the gnome-bluetooth applet
from intrepid since it's based on previous bluez version... still it's a nasty
bug that need to be s
I too confirm that the workaround of loading bluez-compat works...
Microsoft Bluetooth Notebook Mouse 5000
so the problem lies in the hid part of bluez 4.x
--
[Jaunty] Cannot connect to a bluetooth mouse
https://bugs.launchpad.net/bugs/343727
You received this bug notification because you are a
Uhmm from bluez-compat description
This package provides the legacy binaries that were reminiscent of the
BlueZ 3.x pairing methods. These binaries are not supported, and will go
away again in the future. The provided binaries are:
hidd dund pand
So this workaround makes use of old daemons... i
I installed the netbook remix of jaunty on an acer aspire one
with an external dongle which worked fine on hardy
Bus 002 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle
(HCI mode)
The mouse is a Microsoft Bluetooth Notebook Mouse 5000 which worked fine
in hardy too
In sysl
