Description of problem:
I start machine (Lenovo X61) when it was on dock. Then remove from dock and then
readd it to dock. External (USB) mouse & keyboard which was input into dock was
not working after that. Ethernet, power and audio input was working great. I've
attached archive with output from lspci -v, dmesg, lsusb -v and hal-device. If
you need any other information (or you think, that this is not bug in hal),
please let me know. Thanks.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
You have to input USB mouse and/or keyboard into dock.
1. start machine when its on dock
2. remove from dock (dont shutdown it)
3. add to dock again
external (USB) mouse & keyboard is not working
working external (USB) mouse & keyboard same as before you remove machine from dock.
If you need additional info, please let me know.
Created attachment 291142 [details]
output from dmesg, lsusb, lspci, hal-device
Why do you think this is a hal bug? Closing, feel feel to pick a better
component and reopen..
Additional info about kernel im using:
Created attachment 291198 [details]
dmesg from original tarball
Created attachment 291199 [details]
lsusb from original tarball
Created attachment 291200 [details]
Created attachment 291201 [details]
In the future please attach individual files, not tarballs - it makes
developer's lives MUCH easier :)
Stanley: ok, sorry :)
I just gave this a try on my T61, and with a rather recent rawhide kernel, no
problems whatsoever. Haven't tried an earlier kernel yet, but its possible
there's a fix in the newer thinkpad_acpi kernel code, so please give the latest
rawhide kernel a try and report back.
I tried it with kernel-18.104.22.168-115.fc8 with the same results :( Note, that I
have X61. My colleague with T61 doesn't have problem too.
Michal, just to be absolutely certain this isn't already fixed in later kernels,
can you try 22.214.171.124-7.fc8 or a rawhide kernel? If not, I'll see if I can dig up
an X61 here...
Okay, finding an X61 wasn't a problem, but I don't know about a dock yet...
Also, it would be great if dmesg wasn't tampered with (not truncated).
There's not a single message about USB in dmesg in comment #4, but
this is preposterous. If a device gets detached, certainly something
has to happen (unless somehow the whole keyboard was a sham emulated
by the SMM BIOS, in which case you'd need a fixed firmware -- but we
cannot know that without seeing the whole dmesg... ok, I'm thinking
a few steps ahead here, let's just get dmesg first).
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '8'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 8's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 8 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.