[Bug 29506] agreed -- the bug still exists

[Robert Lange]

32-bit Hardy, upgraded from Gutsy (32-bit).  Using a dinovo media
desktop laser keyboard and mouse.  Both devices are paired and trusted.

I have the exact same problem as described by Simone Malacarne.  I can
reconnect the devices using the same workaround he described.  I agree
we need to reopen the bug.

My system has original Hardy bluetooth configuration files -- I have
made no manual changes.

This is a huge problem for me, because I bought my Bluetooth keyboard
and mouse set with the intention of eliminating my wired keyboard and
mouse.  Currently, whenever I leave the computer for a while, I would
need to plug in a wired device for a moment just to resume using the
Bluetooth devices.  If that is the case, I might as well throw away the
Bluetooth devices, because they are useless for me!

I would like to avoid kludgy workarounds if possible, like the
suggestions above to hard-code device-specific connections or disable
ACPI.  Those seem like the sorts of things that will, in the long term,
break more than they fix.

Adam: I am pretty sure that the Bluetooth devices shut down after a
while as power-saving feature.  The question is, once I move the mouse
or hit a key on the keyboard, why does it not successfully re-connect,
until *after* I use a wired device to manually "disconnect" the
Bluetooth device from the Gnome bluetooth-properties applet?

-- 
Bluetooth mouse doesn't work.
https://bugs.launchpad.net/bugs/29506
You received this bug notification because you are a member of
Bluetooth, which is subscribed to bluez-utils in ubuntu.