Red Hat Bugzilla – Bug 118783
(USB SCSI)Remove USB device - while looking at it in Control Center - Crash
Last modified: 2007-11-30 17:10:38 EST
I was exploring - went to Control Center, scrolled to USB, saw
display, plugged in D-Link USB Bluetooth dongle, exited CC, restarted
CC, saw D-Link dongle parameters in CC USB display.
Then I pulled out the USB dongle (why not..) The display did not
update, the mouse froze - could not log in from another computer over
Did a power cycle to regain control..
System is 'up2date -u' up to date (with 2.6.3.. kernel - highest
number in up2date system).
Dual 2.4ghz Xeon w 1GB memory.
I did a bit more testing.
The crash does not have anything to do with Control Center.
I inserted the Bluetooth Dongle in a USB hole, the power LED on the
dongle lit up (as before).
I looked at the dongle using Control Center, but then totally (?)
exited from Control Center.
System was running fine.
Pulled Dongle out of USB hole.
System hung hard. Mouse froze, no blinking lights anywhere.
Power cycle to restart.
Let me know what further tests I can do.
I also have a Keyspan USB Serial Adapter.
I plugged this in and pulled it out and thre were no problems.
I checked for the appearance of the device in the Control Center USB
devices display and everything looked good. Plug it in, device
description appears. Unplug it and description goes away (but I have
to select another screen in Control Center and then go back to USB to
refresh the information.
No crash with the Keyspan USB Serial Adapter plug/unplug.[user1@hoho2
Looks like the previous crash might be more related to Bluetooth.
This is my kernel version:
user1]$ cat /proc/version
Linux version 2.6.3-22.214.171.124.1smp (email@example.com)
(gcc version 3.3.3 20040216 (Red Hat Linux 3.3.3-2.1)) #1 SMP Fri Mar
12 14:23:36 EST 2004
Similar here, only that I don't have an external dongle but an
internal one in the laptop (Dell D800). Enabling/disabling it with
Fn+F2 also hangs the machine.
*** This bug has been marked as a duplicate of 121896 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.