Red Hat Bugzilla – Bug 143792
system fails to maintain kvm's attention
Last modified: 2015-01-04 17:14:25 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Description of problem:
belkin 2 port usb+audio kvm
This device derives its power directly and exclusively through the USB
During the installation process the kvm erroneously believes that the
system is no longer active and switches to the other connected box.
Once the files start to be copied from the CDs the kvm "sticks" to the
system running Fedora.
When rebooting the system the kvm loses focus on the Fedora box every
20-30 seconds and switches back to the other machine: once a user has
logged on the kvm never loses focus.
The kvm does not exhibit this behavior when the machine is running
other flavors of linux.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install current release of fedora from .iso files burned to CD
reboot the system and allow the logon screen to be displayed for 20-30
Actual Results: kvm appears to lose power from the fedora machine and
switches to the "active" system
Expected Results: Fedora machine should maintain focus of kvm
I ran the system utility and updated everything that had an available
update. The system at logon has an even shorter attention span: I am
no longer able to log into the GUI because the kvm loses focus even
This is no usbutils userland problem. It is a kernel driver problem.
Assigning to kernel.
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem. Please update to this new kernel, and
report whether or not it fixes your problem.
If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.
This bug has been automatically closed as part of a mass update.
It had been in NEEDINFO state since July 2005.
If this bug still exists in current errata kernels, please reopen this bug.
There are a large number of inactive bugs in the database, and this is the only
way to purge them.