Created attachment 394922 [details] gdb full backtrace Description of problem: I have a setup with two nvidia quadro fx 1700 and four displays. When moving the cursor from the primary display to the one left to it the cursor flickers and skips back and forth and there's no way of getting control of it back. Pressing a any key after a few seconds crashes the xorg server. There's no problem moving the cursor to the ones right of the primary display and no issues are present when I disable the leftmost display. Backtrace: 0: /usr/bin/X (xorg_backtrace+0x28) [0x49ec18] 1: /usr/bin/X (0x400000+0x61c29) [0x461c29] 2: /lib64/libpthread.so.0 (0x7f09d672f000+0xf0f0) [0x7f09d673e0f0] 3: /usr/bin/X (0x400000+0x146d4a) [0x546d4a] 4: /usr/bin/X (0x400000+0x1532b7) [0x5532b7] 5: /usr/bin/X (0x400000+0x153600) [0x553600] 6: /usr/bin/X (miPointerUpdateSprite+0x157) [0x458847] 7: /usr/bin/X (0x400000+0x589a9) [0x4589a9] 8: /usr/bin/X (0x400000+0x160770) [0x560770] 9: /usr/bin/X (mieqProcessDeviceEvent+0x19a) [0x49e17a] 10: /usr/bin/X (mieqProcessInputEvents+0xda) [0x49e2ba] 11: /usr/bin/X (ProcessInputEvents+0x9) [0x46c259] 12: /usr/bin/X (0x400000+0x2c463) [0x42c463] 13: /usr/bin/X (0x400000+0x21d9a) [0x421d9a] 14: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x7f09d557ab1d] 15: /usr/bin/X (0x400000+0x21949) [0x421949] Segmentation fault at address 0x38 Version-Release number of selected component (if applicable): xorg-x11-server-Xorg-1.7.4-6.fc12.x86_64 How reproducible: Always Steps to Reproduce: 1. Move the cursor to the display left of the primary display. 2. Wait a few seconds. 3. Press a key on the keyboard. Actual results: Xorg server segfaults. Expected results: Normal mouse movements and no segfault. Additional info: This is a yum upgraded system from F10->F11->F12 with all packages updated as of today running KDE and NVidia drivers.
Created attachment 394923 [details] Xorg log
Created attachment 394924 [details] xorg configuration
I tried a few more different configurations and it looks like any display on the left side of screen 0 will cause this crash.
I upgraded from F11 but ended up doing a fresh install of F12. I have two nVidia 8800 and the latest driver via akmods, and using KDE. The exact same phenomena on my four screens. If I move mouse over to screen 2 (the third monitor) which is to the left of screen 0, the mouse becomes erratic and ignores any attempts to move it. Once I press a key it restarts X. The same xorg.conf worked fine under a few previous Fedora versions going back from F11. Running four screens appears to be too uncommon to get much debugging done. Too bad. Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" 1280 0 Screen 1 "Screen1" RightOf "Screen0" Screen 2 "Screen2" LeftOf "Screen0" Screen 3 "Screen3" RightOf "Screen1" InputDevice "Keyboard0" "CoreKeyboard" InputDevice "Mouse0" "CorePointer" EndSection Section "Files" FontPath "/usr/share/fonts/default/Type1" ModulePath "/usr/lib64/xorg/modules/extensions/nvidia" ModulePath "/usr/lib64/xorg/modules/drivers" ModulePath "/usr/lib64/xorg/modules" EndSection Section "Module" Load "dbe" Load "extmod" Load "type1" Load "freetype" Load "glx" EndSection Section "ServerFlags" Option "Xinerama" "1" EndSection Section "InputDevice" # generated from default Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/input/mice" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" # generated from data in "/etc/sysconfig/keyboard" Identifier "Keyboard0" Driver "kbd" Option "XkbLayout" "us" Option "XkbModel" "pc105" EndSection Section "Monitor" # HorizSync source: edid, VertRefresh source: edid Identifier "Monitor0" VendorName "Unknown" ModelName "Samsung SyncMaster" HorizSync 30.0 - 81.0 VertRefresh 56.0 - 75.0 Option "DPMS" EndSection Section "Monitor" # HorizSync source: edid, VertRefresh source: edid Identifier "Monitor1" VendorName "Unknown" ModelName "Samsung SyncMaster" HorizSync 30.0 - 81.0 VertRefresh 56.0 - 75.0 Option "DPMS" EndSection Section "Monitor" Identifier "Monitor2" VendorName "Unknown" ModelName "Samsung SyncMaster" HorizSync 30.0 - 81.0 VertRefresh 56.0 - 75.0 EndSection Section "Monitor" Identifier "Monitor3" VendorName "Unknown" ModelName "Samsung SyncMaster" HorizSync 30.0 - 81.0 VertRefresh 56.0 - 75.0 EndSection Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "GeForce 8800 GT" BusID "PCI:3:0:0" Screen 0 EndSection Section "Device" Identifier "Device1" Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "GeForce 8800 GT" BusID "PCI:3:0:0" Screen 1 EndSection Section "Device" Identifier "Device2" Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "GeForce 8800 GT" BusID "PCI:4:0:0" Screen 0 EndSection Section "Device" Identifier "Device3" Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "GeForce 8800 GT" BusID "PCI:4:0:0" Screen 1 EndSection Section "Screen" Identifier "Screen0" Device "Device0" Monitor "Monitor0" DefaultDepth 24 Option "TwinView" "0" Option "metamodes" "DFP-0: nvidia-auto-select +0+0" SubSection "Display" Depth 24 EndSubSection EndSection Section "Screen" Identifier "Screen1" Device "Device1" Monitor "Monitor1" DefaultDepth 24 Option "TwinView" "0" Option "metamodes" "DFP-1: nvidia-auto-select +0+0" SubSection "Display" Depth 24 EndSubSection EndSection Section "Screen" Identifier "Screen2" Device "Device2" Monitor "Monitor2" DefaultDepth 24 Option "TwinView" "0" Option "metamodes" "CRT-0: nvidia-auto-select +0+0" SubSection "Display" Depth 24 EndSubSection EndSection Section "Screen" Identifier "Screen3" Device "Device3" Monitor "Monitor3" DefaultDepth 24 Option "TwinView" "0" Option "metamodes" "CRT-1: nvidia-auto-select +0+300 SubSection "Display" Depth 24 EndSubSection EndSection Section "Extensions" Option "Composite" "Enable" EndSection
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
As this bug is about to be closed: Shortly after filing the bug I "downgraded" to a dual display TwinView configuration and haven't experienced this bug since (as the setup is totally different). Currently I don't have time to replicate the bug in F13. For future reference: The bug was not solved for me although it might be fixed/working in current versions.
(In reply to comment #6) > For future reference: The bug was not solved for me although it might be > fixed/working in current versions. yeah, but for even possibility of fixing this (and I am sorry, that we haven't had enough time to take appropriate care for this one) we need active collaboration from reporter. Closing as INSUFFICIENT_DATA