Bug 427677
Summary: | Bluetooth mouse and keyboard (logitech dinovo) stop working after system is idle | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Brad Smith <bradley.g.smith> | ||||||
Component: | bluez-libs | Assignee: | David Woodhouse <dwmw2> | ||||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 8 | CC: | bnocera, kna | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2008-06-25 09:55:25 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Brad Smith
2008-01-06 16:43:38 UTC
Please show output of 'hcidump -XVt' when it stops working. Created attachment 291085 [details]
hcidump -XVt > hcidump2.txt
hcidump as requested
At what point during that dump does it stop working? Can you show it with only one device at a time? Is there anything in /var/log/messages when this happens? i started the dump at the point after i logged in with the usb keyboard. the pressed the keys on the keyboard a few times and moved the mouse a bit. hcidump captured events but the mouse cursor does not move and key presses do not display. then i opened the gnome bluetooth preferences application and dropped both devices and then added them. the log output only has the device creation: Jan 8 13:28:17 pico input[2350]: Created input device: /org/bluez/input/pointing5 Jan 8 13:28:18 pico input[2350]: New input device 00:07:61:31:A8:B0 (Logitech MX900 Mouse) Jan 8 13:28:18 pico kernel: input: Logitech MX900 Mouse as /class/input/input15 Jan 8 13:28:40 pico input[2350]: Created input device: /org/bluez/input/keyboard6 Jan 8 13:29:36 pico input[2350]: Encryption link key not found Jan 8 13:29:36 pico input[2350]: New input device 00:07:61:31:81:20 (Logitech diNovo Keyboard) Jan 8 13:29:36 pico kernel: input: Logitech diNovo Keyboard as /class/input/input16 Jan 8 13:33:17 pico gnome-keyring-daemon[2880]: couldn't read 4 bytes from client: i will create another dump that i start before the system is idle Created attachment 291106 [details]
as requested
hcidump3.txt is started just as i leave the workstation for about 25 min. Close
to 1600 local time, i test the bluetooth keyboard only for response. Then use
usb keyboard to enter password and disconnect bluetooth keyboard. and then
reconnect keyboard. hcidump then terminated by using the bluetooth keyboard.
Mouse not touched until after hcidump terminated.
I seem to be bitten by the same bug on Fedora 9 on x86_64 architecture. Most of the time my Mouse don't work at all, at connect time I usually get: Couldn't display "obex://[00:07:61:BB:7A:F4]/". Error: DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) Please select another viewer and try again. (In reply to comment #7) > I seem to be bitten by the same bug on Fedora 9 on x86_64 architecture. Most of > the time my Mouse don't work at all, at connect time I usually get: > Couldn't display "obex://[00:07:61:BB:7A:F4]/". Trying to browse files on a mouse will _obviously_ not work. As for the mouse not reconnecting after disconnecting for power saving, it's a kernel bug. Feel free to test the patch in the other bug and report whether it fixes the problem for you. *** This bug has been marked as a duplicate of 449872 *** |