Description of problem: X started acting strang and blinking the screen, the cursor wouldn't move, etc. Version-Release number of selected component: xorg-x11-server-Xorg-1.17.1-7.fc22 Additional info: reporter: libreport-2.5.0 backtrace_rating: 4 cmdline: /usr/libexec/Xorg vt2 -displayfd 3 -auth /run/user/1975/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -verbose 3 crash_function: switch_to executable: /usr/libexec/Xorg global_pid: 1956 kernel: 4.0.0-0.rc5.git4.1.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1975 Truncated backtrace: Thread no. 1 (7 frames) #4 switch_to at lnx_init.c:72 #5 xf86CloseConsole at lnx_init.c:324 #10 switch_to at lnx_init.c:72 #11 xf86OpenConsole at lnx_init.c:272 #12 InitOutput at xf86Init.c:795 #13 dix_main at main.c:202 #15 _start Potential duplicate: bug 1177409
Created attachment 1011469 [details] File: backtrace
Created attachment 1011470 [details] File: cgroup
Created attachment 1011471 [details] File: core_backtrace
Created attachment 1011472 [details] File: dso_list
Created attachment 1011473 [details] File: environ
Created attachment 1011474 [details] File: limits
Created attachment 1011475 [details] File: maps
Created attachment 1011476 [details] File: mountinfo
Created attachment 1011477 [details] File: namespaces
Created attachment 1011478 [details] File: open_fds
Created attachment 1011479 [details] File: proc_pid_status
Created attachment 1011480 [details] File: var_log_messages
Another user experienced a similar problem: I came back to my machine after only a minute or so away, woke the screen and entered my password in the gnome-shell lock screen. My system entered a tight loop jumping between a virtual terminal and my lock screen until I eventually powered off the machine. reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: /usr/libexec/Xorg vt1 -displayfd 3 -auth /run/user/42/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -verbose 3 crash_function: switch_to executable: /usr/libexec/Xorg global_pid: 20135 kernel: 4.0.0-1.fc22.x86_64 package: xorg-x11-server-Xorg-1.17.1-9.fc22 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 42
Another user experienced a similar problem: In Wayland (no problem in xorg), in this page on firefox " https://bugzilla.redhat.com/show_bug.cgi?id=1214318) " , when I highlights " 1214318 " in the black text on red background and I move this highlights numbers with my mouse, Gnome-shell crashes a second later! That is reproducible. reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: /usr/libexec/Xorg vt1 -displayfd 3 -auth /run/user/42/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -verbose 3 crash_function: switch_to executable: /usr/libexec/Xorg global_pid: 3288 kernel: 4.0.1-300.fc22.x86_64 package: xorg-x11-server-Xorg-1.17.1-10.fc22 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 42
Another user experienced a similar problem: Booted the machine, and logged in by swiping my finger on the fingerprint reader built into this laptop (Lenovo X1 Carbon 2nd Generation). After the crash, I rebooted the box, and logged in by typing in my password -- not sure if the fingerprint reader is a red herring, or if it's actually relevant. reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: /usr/libexec/Xorg vt2 -displayfd 3 -auth /run/user/1975/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -verbose 3 crash_function: switch_to executable: /usr/libexec/Xorg global_pid: 1983 kernel: 4.0.1-300.fc22.x86_64 package: xorg-x11-server-Xorg-1.17.1-10.fc22 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 1975
Another user experienced a similar problem: It is not possible to login from GDM to Gnome or Gnome Classic: as soon as I login I get a message that something crashed and pressing the button returns me to GDM. Login to Gnome Wayland, MATE, Cinnamon, Cinnamon (Software Rendering), LXQT all works (although Wayland shows a "ghost cursor" and its not very usable yet). reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: /usr/libexec/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -verbose 3 crash_function: switch_to executable: /usr/libexec/Xorg global_pid: 6153 kernel: 4.0.3-300.fc22.x86_64 package: xorg-x11-server-Xorg-1.17.1-11.fc22 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Occurred after attemping to log in to gnome wayland session on f22 reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: /usr/libexec/Xorg vt1 -displayfd 3 -auth /run/user/42/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -verbose 3 crash_function: switch_to executable: /usr/libexec/Xorg global_pid: 4418 kernel: 4.0.4-300.fc22.x86_64 package: xorg-x11-server-Xorg-1.17.1-12.fc22 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 42
Another user experienced a similar problem: Currently I don't have time to confirm whether this is a hardware issue or software bug, from dmesg I see nouveau "failed to idle channel...". For this SIGABRT signal I think Xorg is killed when I the display hangs and I issue "systemctl restart gdm", as I find that characters appear slowly and choppily, and also the cursor when I enter the desktop. I guess if I wait for sometime when it hangs completely then these is no chance for me to switch to TTY because it doesn't reponse to key press. This actually happens. reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: /usr/libexec/Xorg vt3 -displayfd 3 -auth /run/user/1002/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -verbose 3 crash_function: switch_to executable: /usr/libexec/Xorg global_pid: 2628 kernel: 4.0.2-300.fc22.x86_64 package: xorg-x11-server-Xorg-1.17.1-12.fc22 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 1002
Some information of my hardware I think might be useful: Lenovo Y400, Nvidia GT650, intel i7 3632. This laptop has SLI and supports dual independent video cards, but it mutes this integrated video card at hardware level. Currently I have only one video card. The issue that X hangs I encountered before and it was resolved by replacing the main board. But this time it's a bit unusual about the softwares: if I use gnome-shell 3.16.2, it becomes likely to happen much more often than gnome-shell 3.16.1, e.g. the screen looks torn apart and scattered, and it freezes completely shortly, doesn't even respond to ALT+CTRL+F*. I can only log in through LAN and try to restart X, however, it's generally unsuccessful and eventually results in me pressing power button because Xorg doesn't even respond to SIGKILL.
Another user experienced a similar problem: I'm not sure that this was the cause, but it happened after: 1) run rhythmbox 2) enable visualisation 3) right-click inside visualisation reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: /usr/libexec/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -verbose 3 crash_function: switch_to executable: /usr/libexec/Xorg global_pid: 2102 kernel: 4.0.4-303.fc22.x86_64 package: xorg-x11-server-Xorg-1.17.1-14.fc22 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Occurred after logging in from GDM to Gnome Wayland session. Gnome shell crashed first. This happens every time the gnome on Wayland session is selected. reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: /usr/libexec/Xorg vt1 -displayfd 3 -auth /run/user/42/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -verbose 3 crash_function: switch_to executable: /usr/libexec/Xorg global_pid: 2816 kernel: 4.0.4-303.fc22.x86_64 package: xorg-x11-server-Xorg-1.17.1-14.fc22 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 42
Another user experienced a similar problem: Hi all, I had to manually kill GDM as after the upgrade to the newer Xorg stack and new kernel 4.1.3 my desktop won't restore after unlocking the screen and log in back. Regards. reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/libexec/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -verbose 3 crash_function: switch_to executable: /usr/libexec/Xorg global_pid: 21530 kernel: 4.0.8-300.fc22.x86_64 package: xorg-x11-server-Xorg-1.17.2-1.fc22 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
In my case this issue happens under the following conditions: You need to have libva-intel-driver installed, it won't crash otherwise. You need to use the Gtk+ 3 build of firefox (or a Gstreamer build with firefox) to reproduce. Tor browser bundle (built for Gtk+ 2 and withoug GStreamer support) doesn't crash. Steps to reproduce: 1. open firefox 2. open any page with a html5 video, e.g. youtube.com 3. play the video What happens: Greenscreen instead of video, sound works fine. Gnome-shell crashes multiple times, tries to kill the session What should happen: No crash anywhere. Additional info: I think this issue is fixed in mesa 10.6.6, see https://bugs.freedesktop.org/show_bug.cgi?id=91254
Another user experienced a similar problem: when system is ON the fedora log is coming and then blank screen is coming. i can't able to find the user name and password in the blank screen but mouse is moving.so kindly do needful help. reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/libexec/Xorg vt7 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -verbose 3 crash_function: switch_to executable: /usr/libexec/Xorg global_pid: 2868 kernel: 4.1.8-200.fc22.x86_64 package: xorg-x11-server-Xorg-1.17.2-2.fc22.2 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.