Opened 9 years ago

Closed 20 months ago

Last modified 4 months ago

#8077 closed bug (invalid)

USB keyboard stops responding after long uptime

Reported by: Disreali Owned by: nobody
Priority: normal Milestone:
Component: - General Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All


On hrev43005-2hn, after an uptime of just over 15 hours, I noticed that the PrtScrn button did not work when I tried to take a screen capture. I was able to use the mouse to launch the Screenshot app, but then the keyboard did not respond at all to what I was typing. Nothing worked, I could not tab through Screenshot, nor did using the NumLock, CapLock, or ScrollLock keys cause the lights to change when the corresponding key was pressed.

I could launch apps via the menu and navigating through Tracker, but when I attempted to shutdown the system via the menu, nothing happened. Holding Ctrl+Alt+Del for 4 seconds did not work either, not that I really expected it to at that point. Finally, I was forced to hold the power button to shutdown the system.

I've never experienced this before even though in the past, I have left Haiku running for days.

I don't know how to test this except to leave my system running to see if it happens again.

Attaching the syslog in the hopes it may help.

Attachments (3)

syslog_r43005-2hn_keyboard_stopped_responding.txt (323.6 KB ) - added by Disreali 9 years ago.
listusb-verbose_acer-am5620.txt (16.0 KB ) - added by Disreali 9 years ago.
syslog_r43192-2hn_usb-keyboard_stopped_after_media-addon-server_crash.txt (730.9 KB ) - added by Disreali 9 years ago.

Download all attachments as: .zip

Change History (8)

by Disreali, 9 years ago

comment:1 by Disreali, 9 years ago

Attaching a listusb -v as per mmlr's request in ticket:7897.

comment:2 by Disreali, 9 years ago

Experienced on a fresh install of hrev43192. Mouse still worked and was ant to shutdown via the menu. There was a crash of the media-addon-server within 5 minutes of boot up, I clicked debug in the resulting error box and keyboard stopped responding to input.

comment:3 by un_spacyar, 4 years ago

This is still an issue in recent nightly Builds?

comment:4 by waddlesplash, 20 months ago

Resolution: invalid
Status: newclosed

No reply in 2 years.

comment:5 by nielx, 4 months ago

Milestone: R1

Remove milestone for tickets with status = closed and resolution != fixed

Note: See TracTickets for help on using tickets.