Created attachment 697431 [details] portion of system log Description of problem: System lock-up and Xorg crash when plugging in USB Plantronics phone headset Version-Release number of selected component (if applicable): How reproducible: Happens every time the headset is plugged in, and also when booting with the headset already plugged in Steps to Reproduce: 1. Plug Plantronics W02 base into USB port Actual results: Screen goes black. Then there are a few flashes. Then black again. No response to any inputs. dmesg indicates a crash in Xorg. Expected results: No crash, hopefully a working audio device Additional info: The machine is a Thinkpad T60p running Fedora 17 3.7.3-101.fc17.i686 I find it very strange that X11 is involved, but that is what crashed, and the crash is repeatable. I have attached the relevant portion of the system log. There are multiple Xorg logs, all looking quite the same. I will atttach one of them next.
Created attachment 697432 [details] Xorg log from crash, others all look very similar
that log hasn't anything in it about a crash, maybe check /var/log/gdm/:0.log.old or some of those, see if there is some sort of symbol missing error or anything like that.
Created attachment 698301 [details] :0.log from time of crash
Created attachment 698302 [details] :0-greeter.log from time of crash
Created attachment 698303 [details] :0-slave.log from time of crash
Yes, there is no crash stuff in that log, but also nothing in /var/log/gdm looks like a crash either. I'm attaching the gdm logs from the time of the crash. There is a (very big) crash file listed in the console messages. Would that be helpful? How should it be processed?
There was a crash, or at least the console messages (attachment 697431 [details]) indicate that there was one.
okay so I've no idea what abrt has done, it may be one of the abrt reported bugs, but need to see the backtrace.
I was going to use this device for phone calls as well as playing music, but I found out that it is monophonic, but binaural, so I'm not going to. I thus didn't bring it along with me to my apartment and I won't be going back to where it is for over a month, and I've purged the abrt backtraces, due to some other bugs that I'm seeing. Can we leave this in NEEDINFO until I'm back where the device it? Even though I'm not planning on using the device, I've seen quite a number of other reports on problems with it, so it might be a good idea to have the problem cleared up.
please run evemu-describe against the kernel device file and attach the output here.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. 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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.