Version-Release number of selected component (if applicable): > info xorg-x11-server-Xorg.i386 Installed Packages Name : xorg-x11-server-Xorg Arch : i386 Version : 1.5.3 Release : 5.fc10 > info xorg-x11-drv-fpit.i386 Installed Packages Name : xorg-x11-drv-fpit Arch : i386 Version : 1.2.0 Release : 1.fc9 > info kernel.i686 Installed Packages Name : kernel Arch : i686 Version : 2.6.27.5 Release : 117.fc10 How reproducible: Always Steps to Reproduce: 1. Waste some money on a Gateway M285E, CX210, or similar. 2. Install Fedora and confirm that you can exit an X server. 3. Configure the FinePoint digitizer in xorg.conf like this: http://pastebin.mozilla.org/580199 (highlighted lines are the ones I added). 4. Restart X server. 5. Attempt to exit it, using either a "logoff" command or Ctrl Alt Backspace. Actual results: Weird screen with different-coloured lined on the sides and black in the middle shows; caps-lock light starts flashing at regular intervals. Machine is inaccessible from network. Expected results: X server closes and you are returned to either a console or display manager. Additional info: I have a Gateway M285E. I reused the home directory from a previous installation of Ubuntu.
If I wasn't clear enough about this, there is no kernel panic if you happen to be using a different vt at the moment that the X server is closed.
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach your X server config file (/etc/X11/xorg.conf), X server log file (/var/log/Xorg.*.log), and /var/log/dmesg to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Created attachment 324982 [details] Xorg.0.log
Created attachment 324983 [details] dmesg optput
xorg.conf in comment #0 (the pastebin link)
Created attachment 325161 [details] xorg.conf from pastebin
Is this the log file/dmesg from a crash? Or from the working setup? Also, there's a lot of noise in the log file, suggesting that you suspended/resumed the server (or VT switched) a few times before obtaining the log. Please try to obtain a crash log from a "fresh" server to keep the log brief.
Both of these were from a session using the failing configuration but which had not yet crashed. I have no way of obtaining a dmesg from a crash. I will attach the Xorg log file as it exists immediately after a crash next time I restart.
Created attachment 325165 [details] Xorg log after crash This is the log of an X server running GDM which I closed immediately after it loaded. I made a copy of the log in single user mode after restarting due to the kernel panic.
How about this one: http://koji.fedoraproject.org/scratch/whot/task_965148/
Should I also install the debuginfo package?
that'd be a good idea, but may not be necessary. if it still crashes like above, we don't see a backtrace anyway so the debuginfo probably won't help.
It still crashes and panics after installing the package.
Next try: http://koji.fedoraproject.org/scratch/whot/task_968768/ Note that the panic is most likely a kernel fault, but maybe we can figure out what triggers the panic.
The package doesn't help on Fedora 10. I just installed Rawhide and the panic is gone, probably due to the Linux upgrade. The weird line pattern is still there and you can't change vts using CtrlAltF[1-6]. However, new X servers can be started by logging in using SSH to bring the machine back to a mostly usable state. Should this bug be morphed?
Created attachment 325942 [details] Xorg.1.log This is the Xorg.1.log after a crash under Rawhide.
Created attachment 325943 [details] dmesg dmesg from after a crash under Rawhide.
I just discovered that running "chvt 1" via SSH also works.
(In reply to comment #15) > The package doesn't help on Fedora 10. weird. I removed all the code from the driver during unloading so anything after the UnloadModule message is a noop. And the unload is the last message we see in the log. Just to make sure - if you remove the fpit driver from the xorg.conf, you don't see any of these issues?
I don't see these issues if I remove the fpit driver from xorg.conf.
Filed upstream as bug 19124. http://bugs.freedesktop.org/show_bug.cgi?id=19124 However, I have to warn you that fpit is unmaintained and your best chances are to look at the source and try to narrow down the cause of the crash yourself. The git source directory is available from git://anongit.freedesktop.org/git/xorg/driver/xf86-input-fpit.
xorg-x11-drv-fpit-1.3.0-3.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/xorg-x11-drv-fpit-1.3.0-3.fc11
xorg-x11-drv-fpit-1.2.0-2.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/xorg-x11-drv-fpit-1.2.0-2.fc10
Victor: please try either of the packages above (depending on which release you're on) and let me know if that's fixed for you now. You're the only fpit user I know of, so I do rely on you for testing.
xorg-x11-drv-fpit-1.3.0-3.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update xorg-x11-drv-fpit'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-9097
xorg-x11-drv-fpit-1.2.0-2.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update xorg-x11-drv-fpit'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-9106
xorg-x11-drv-fpit-1.2.0-2.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.
xorg-x11-drv-fpit-1.3.0-3.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.