Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Unlocked the screensaver Version-Release number of selected component: xorg-x11-server-Xorg-1.16.0-3.fc21 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/libexec/Xorg.bin :0 -background none -noreset -verbose 3 -logfile /dev/null -auth /run/gdm/auth-for-gdm-bnvu7F/database -seat seat0 -nolisten tcp vt1 crash_function: present_set_tree_pixmap executable: /usr/libexec/Xorg.bin kernel: 3.16.1-301.fc21.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 present_set_tree_pixmap at present.c:378 #1 present_unflip at present.c:415 #2 present_flip_notify at present.c:459 #3 present_event_notify at present.c:484 #4 present_flip_handler at sna_present.c:314 #5 sna_mode_wakeup at sna_display.c:6837 #6 sna_mode_reset at sna_display.c:6108 #7 sna_leave_vt at sna_driver.c:898 #13 present_set_tree_pixmap at present.c:378 #14 present_set_abort_flip at present.c:398
Created attachment 932766 [details] File: backtrace
Created attachment 932767 [details] File: cgroup
Created attachment 932768 [details] File: core_backtrace
Created attachment 932769 [details] File: dso_list
Created attachment 932770 [details] File: environ
Created attachment 932771 [details] File: exploitable
Created attachment 932772 [details] File: limits
Created attachment 932773 [details] File: maps
Created attachment 932774 [details] File: open_fds
Created attachment 932775 [details] File: proc_pid_status
Created attachment 932776 [details] File: var_log_messages
Another user experienced a similar problem: I think crash happened when I wanted to update system. I logged out, changed vt via alt-ctrl-F2, logged in as root in vt, service gdm stop, yum update and this is all. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/libexec/Xorg.bin :0 -background none -noreset -verbose 3 -logfile /dev/null -auth /run/gdm/auth-for-gdm-RIGtLS/database -seat seat0 -nolisten tcp vt1 crash_function: present_set_tree_pixmap executable: /usr/libexec/Xorg.bin kernel: 3.16.3-300.fc21.x86_64 package: xorg-x11-server-Xorg-1.16.0-10.fc21 reason: Xorg.bin killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: I think this is what happened: I locked my screen and went for a walk. When I got back, I pressed a key to remove the lock screen. At this time, it seemed to crash and bring up gdm. I entered my password in gdm - it took me back to a locked gnome-shell. I entered my password - it brought it up - all my GUI apps had been killed. Only byobu had detached and survived. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/libexec/Xorg.bin :0 -background none -noreset -verbose 3 -logfile /dev/null -auth /run/gdm/auth-for-gdm-VauEH9/database -seat seat0 -nolisten tcp vt1 crash_function: present_set_tree_pixmap executable: /usr/libexec/Xorg.bin kernel: 3.17.0-0.rc7.git3.1.fc22.x86_64 package: xorg-x11-server-Xorg-1.16.1-1.fc21 reason: Xorg.bin killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0
Happening quite often here - 3 times today already.
This time I experienced this bug under weston + Xwayland. I opened Firefox in the same terminal that I opened Xwayland and htop.
Another user experienced a similar problem: init3 startx reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/libexec/Xorg.bin :0 -background none -noreset -verbose 3 -logfile /dev/null -auth /run/gdm/auth-for-gdm-bxKGcv/database -seat seat0 -nolisten tcp vt1 crash_function: present_set_tree_pixmap executable: /usr/libexec/Xorg.bin kernel: 3.17.4-301.fc21.x86_64 package: xorg-x11-server-Xorg-1.16.2-1.fc21 reason: Xorg.bin killed by SIGSEGV runlevel: 5 3 type: CCpp uid: 0
Another user experienced a similar problem: The problem is reported by OS. I didn't have much chance to check or reproduce the problem. reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/libexec/Xorg.bin :0 -background none -noreset -verbose 3 -logfile /dev/null -auth /run/gdm/auth-for-gdm-qo103z/database -seat seat0 -nolisten tcp vt1 crash_function: present_set_tree_pixmap executable: /usr/libexec/Xorg.bin kernel: 3.17.4-301.fc21.i686 package: xorg-x11-server-Xorg-1.16.1-1.fc21 reason: Xorg.bin killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: My pc shut down again and again while I am using. reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/libexec/Xorg.bin :0 -background none -noreset -verbose 3 -logfile /dev/null -auth /run/gdm/auth-for-gdm-3PSlhb/database -seat seat0 -nolisten tcp vt1 crash_function: present_set_tree_pixmap executable: /usr/libexec/Xorg.bin kernel: 3.18.3-201.fc21.x86_64 package: xorg-x11-server-Xorg-1.16.3-2.fc21 reason: Xorg.bin killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: Problem occurred when trying to shut down reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/libexec/Xorg.bin :0 -background none -noreset -verbose 3 -logfile /dev/null -auth /run/gdm/auth-for-gdm-szhb5r/database -seat seat0 -nolisten tcp vt1 crash_function: present_set_tree_pixmap executable: /usr/libexec/Xorg.bin kernel: 3.18.7-200.fc21.x86_64 package: xorg-x11-server-Xorg-1.16.3-2.fc21 reason: Xorg.bin killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: Woke the Lenovo x230 laptop from sleep and Xorg crashed and logged me out. reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/libexec/Xorg.bin :0 -background none -noreset -verbose 3 -logfile /dev/null -auth /run/gdm/auth-for-gdm-3FEYCR/database -seat seat0 -nolisten tcp vt1 crash_function: present_set_tree_pixmap executable: /usr/libexec/Xorg.bin kernel: 3.18.6-200.fc21.x86_64 package: xorg-x11-server-Xorg-1.16.3-2.fc21 reason: Xorg.bin killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: i do not remember to be honest.. a lot of things just crashed and a few dependencies were hindering the update procedure.. reporter: libreport-2.3.0 backtrace_rating: 3 cmdline: /usr/libexec/Xorg.bin :0 -background none -noreset -verbose 3 -logfile /dev/null -auth /run/gdm/auth-for-gdm-nLASGa/database -seat seat0 -nolisten tcp vt1 crash_function: present_set_tree_pixmap executable: /usr/libexec/Xorg.bin kernel: 3.17.4-301.fc21.x86_64 package: xorg-x11-server-Xorg-1.16.3-2.fc21 reason: Xorg.bin killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0
Not sure if it is related, but my login screen show many (>10) failed login attempts.
Also not sure it is related, but I seem to encounter this when attaching to a docking station thus changing screen settings.
Seems to have been caused by trying to run VNC+GDM?
I reproduced it consistently this way locally on my laptop (GDM, Gnome 3): 1) Login as one user (will be at Virtual Console #1); 2) Switch user via menu to login concurrently as another Gnome user on VC#2; 3) Ctrl-Alt-F1 to switch back to first user, enter password to unlock; 4) Ctrl-Alt-F2 to switch back to second user (no password needed); 5) Ctrl-Alt-F1 to first user (no password needed now either, fine); 6) Ctrl-Alt-F2 to second user (quite fast, fine, optionally do more switches); 7) Logout second user => black screen, Ctrl-Alt-* useless, all VC's inaccessible; 8) Powerbutton short press fortunately shuts down cleanly and powers off laptop; The latest crash, after installing xorg-x11-{server,drv-intel}-debuginfo (2 packages): kernel: 4.0.4-202.fc21.x86_64 package: xorg-x11-server-Xorg-1.16.3-2.fc21 and using xorg-x11-drv-intel-2.99.916-3.20141117.fc21.x86_64 & default xorg.conf.d/ : ===================================================================================== # cd /var/tmp/abrt/ccpp-2015-06* # gdb /usr/libexec/Xorg.bin coredump [...] Program terminated with signal SIGSEGV, Segmentation fault. #0 present_set_tree_pixmap (window=0x0, pixmap=0x23bb410) at present.c:378 378 visit.old = (*screen->GetWindowPixmap)(window); (gdb) bt ### Backtrace edited, removing less important info #0 present_set_tree_pixmap (window=0x0, pixmap=0x23bb410) at present.c:378 #1 0x... in present_unflip (screen=0x22fea20) at present.c:415 #2 0x... in present_flip_notify (...) at present.c:459 #3 present_event_notify (...) at present.c:484 #4 0x... in present_flip_handler (...) at sna_present.c:319 #5 0x... in sna_mode_wakeup (...) at sna_display.c:7419 #6 0x... in sna_mode_reset (...) at sna_display.c:6549 #7 0x... in sna_leave_vt (...) at sna_driver.c:932 #10 0x... in FatalError (..."Caught signal %d (%s). Server aborting\n") #13 present_set_tree_pixmap (window=0x0, pixmap=0x23bb410) at present.c:378 #14 0x... in present_set_abort_flip (screen=0x22fea20) at present.c:398 (gdb) up 14 #14 0x... in present_set_abort_flip (screen=0x22fea20) at present.c:398 398 present_set_tree_pixmap(screen->root, (*screen->GetScreenPixmap)(screen)); (gdb) print screen->root $1 = (WindowPtr) 0x0 ### As we already knew by "window=0x0" in #13 above (gdb) list 393 394 if (screen_priv->flip_window) 395 present_set_tree_pixmap(screen_priv->flip_window, 396 (*screen->GetScreenPixmap)(screen)); 397 398 present_set_tree_pixmap(screen->root, (*screen->GetScreenPixmap)(screen)); 399 400 screen_priv->flip_pending->abort_flip = TRUE; 401 } 402 ===================================================================================== The crash is avoided by not calling preset_set_tree_pixmap when screen->root is NULL. That fix was in fact committed upstream already on 2014-07-31, only 14 days too late for the 1.16 branch, but included in 1.17 and later (including fc22!??), AFAICS: http://cgit.freedesktop.org/xorg/xserver/commit/present/present.c?id=40dc81154ad38514793f2181447d597b57d39e80 Yesterday I verified that that commit indeed fixes the crash problem on my laptop (by installing xorg-x11-server-1.16.3-2.fc21.src.rpm, adding the patch to SOURCES-dir and .spec file, building updated packages, updating xorg-x11-server-{Xorg,common} to the patched versions). As a side note, before installing debuginfo, ABRT directed me to one of the Intel bugs instead, probably rhbz #1172232. I therefore tested applying the 2 patches there to the Intel driver, but they didn't help. The reason is now obvious. The bugs are similar, but unrelated.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 EOL if it remains open with a Fedora 'version' of '21'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 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 this bug is closed as described in the policy above. 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.