Version-Release number of selected component: xorg-x11-server-Xorg-1.13.0-11.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /var/run/gdm/auth-for-gdm-bZXT6k/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.6.7-5.fc18.x86_64 open_fds: remote_result: 730498 uid: 0 Truncated backtrace: Thread no. 1 (9 frames) #2 OsAbort at utils.c:1266 #3 ddxGiveUp at xf86Init.c:1071 #4 AbortServer at log.c:652 #5 FatalError at log.c:793 #6 OsSigHandler at osinit.c:146 #9 ?? #10 DoMakeCurrent at glxcmds.c:627 #11 __glXDispatch at glxext.c:581 #12 Dispatch at dispatch.c:428 Potential duplicate: bug 883090
Created attachment 658256 [details] File: backtrace
Created attachment 658257 [details] File: cgroup
Created attachment 658258 [details] File: core_backtrace
Created attachment 658259 [details] File: dso_list
Created attachment 658260 [details] File: environ
Created attachment 658261 [details] File: limits
Created attachment 658262 [details] File: maps
Created attachment 658263 [details] File: proc_pid_status
Created attachment 658264 [details] File: var_log_messages
may be nouveau driver for my Nvidia GeForce 6100, that sometimes don't work and system crash backtrace_rating: 4 Package: xorg-x11-server-Xorg-1.13.1-4.fc18 OS Release: Fedora release 18 (Spherical Cow)
Running KDE on F18. Suspend from KDE menu succeeds, but upon resume, the KDE session is gone and the KDE login screen is presented. /var/log/messages indicates a X crash that I expect is related. This suspend/resume cycle was successful prior to the update listed below, so that's my prime suspect at this point. I'd be glad to take any steps to gather more info for you; please advise if needed. # yum history info 31 <SNIP> Updated xorg-x11-drv-ati-7.0.0-0.6.20120910git7c7f27756.fc18.x86_64 @anaconda Update 7.0.0-0.8.20121015gitbd9e2c064.fc18.x86_64 @updates Updated xorg-x11-drv-intel-2.20.14-1.fc18.x86_64 @anaconda Update 2.20.16-1.fc18.x86_64 @updates Updated xorg-x11-drv-synaptics-1.6.2-7.fc18.x86_64 @anaconda Update 1.6.2-8.fc18.x86_64 @updates Updated xorg-x11-font-utils-1:7.5-9.fc18.x86_64 @anaconda Update 1:7.5-10.fc18.x86_64 @updates Updated xorg-x11-server-Xephyr-1.13.0-11.fc18.x86_64 @fedora Update 1.13.1-1.fc18.x86_64 @updates Updated xorg-x11-server-Xorg-1.13.0-11.fc18.x86_64 @anaconda Update 1.13.1-1.fc18.x86_64 @updates Updated xorg-x11-server-common-1.13.0-11.fc18.x86_64 @anaconda Update 1.13.1-1.fc18.x86_64 @updates backtrace_rating: 4 Package: xorg-x11-server-Xorg-1.13.1-4.fc18 OS Release: Fedora release 18 (Spherical Cow)
Problem occurred after regular updating of packages. Gnome3 crashed after problem and no longer works. Problem persitent accross bootings. backtrace_rating: 4 Package: xorg-x11-server-Xorg-1.13.1-4.fc18 OS Release: Fedora release 18 (Spherical Cow)
nvidia_drv -> CANTFIX
Adam, Why cantfix? Is noveau driver not supported? In this case, which driver for which graphic card is supported?
(In reply to comment #13) > nvidia_drv -> CANTFIX Why has this been closed as CANTFIX and with a reference to nvidia_drv? I and several others have experienced it with the nouveau driver, so it's nothing to do with the proprietary nvidia driver.
hi you need to relink libglx.so in /usr/lib64/xorg/modules/extensions to the nvidia one in the same folder, or you can just delet it and reinstall your nvidia driver again.
I have the same issue with the open source AMD driver. The bug reporting tool thinks it is a duplicate of this bug and refuses to post it. How do I do that manually please or reopen this bug? -- Running report_Bugzilla --- Logging into Bugzilla at https://bugzilla.redhat.com Checking for duplicates Bug is already reported: 883919 Logging out Status: CLOSED CANTFIX https://bugzilla.redhat.com/show_bug.cgi?id=883919
I also found this in ABRT from last month, so don't remember the details, but I certainly don't use any nvidia drivers, all AMD/ATI here.
(In reply to comment #17) > I have the same issue with the open source AMD driver. > > The bug reporting tool thinks it is a duplicate of this bug and refuses to > post it. How do I do that manually please or reopen this bug? > > -- Running report_Bugzilla --- > Logging into Bugzilla at https://bugzilla.redhat.com > Checking for duplicates > Bug is already reported: 883919 > Logging out > Status: CLOSED CANTFIX https://bugzilla.redhat.com/show_bug.cgi?id=883919 try to find /tmp/anaconda-tb-* attached to your bug and uploaded manually
This happens with nouveau driver.
Created attachment 739804 [details] Stacktrace when it crashes with xorg-x11-drv-ati It crashes with xorg-x11-drv-ati. Please re-open this bug.
I had this crash with Intel SandyBridge GPU
I reopen this bug because it happens also on open source drivers. I experienced this using radeon and fglrx.
Seems to be related to use my Lenevo T420 in a docking station with an external monitor attached (which does not work anyway). The problem does not appear everytime. The temperature if the computer might increase the chance for crashes, but that might also just be coincedence. backtrace_rating: 4 cmdline: /usr/bin/Xorg :6 -background none -verbose -auth /var/run/gdm/auth-for-gdm-1nA7TI/database -seat seat0 -nolisten tcp crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.8.11-200.fc18.x86_64 open_fds: package: xorg-x11-server-Xorg-1.13.3-3.fc18 reason: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT) uid: 0 ureports_counter: 1
I had this several times if I drag some text around in XFCE. I'm not sure what happens.
1. Install kde-desktop 2. Reboot and when logging in selecting plasma-workspace will fail 3. Trying to log in wiht plasma-workspace(fallback mode) backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /var/run/gdm/auth-for-gdm-qkNzuh/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.8.11-200.fc18.x86_64 open_fds: package: xorg-x11-server-Xorg-1.13.3-3.fc18 reason: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT) uid: 0 ureports_counter: 2
I was just working as normal. I had just clicked on the menubar of an XEmacs process. The window didn't refresh, so I assumed that mean that XEmacs had gone into some kind of infinite loop. But when I grabbed the mouse to move it to a terminal window, it moved very sluggishly, and nothing I clicked on responded. Then the screen cleared to black, and I saw a message about the GPU locking up. backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /var/run/gdm/auth-for-gdm-uXYFSI/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.9.2-200.fc18.x86_64 open_fds: package: xorg-x11-server-Xorg-1.13.3-3.fc18 reason: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT) uid: 0 ureports_counter: 2
Hmmm, I don't think this is my bug, although abrt seems to think so. Judging by the backtrace, the crash I just saw is bug 875407, and bug 896133, and bug 896745, and bug 951262.
Xserver terminates with an error while I was surfing with google-chrome-stable-x64 reporter: libreport-2.1.4 backtrace_rating: 3 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /var/run/gdm/auth-for-gdm-2NLCbt/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.9.4-200.fc18.x86_64 open_fds: package: xorg-x11-server-Xorg-1.13.3-3.fc18 reason: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT) reported_to: uReport: BTHASH=0777e3a749f1262be4bfe63940d54aa9f3bde2c5 runlevel: N 5 uid: 0 xsession_errors:
windows, desktop, wm and x-server all disappeared. Dumped out to the "ctl+alt+f1" virtual terminal. Somehow bits of the windowing system seems still to be running e.g. I can see a cursor "icon" (though it does not respond to mouse movement) and I can via ctl+alt+fx get to what looks like the gdm user login selector. If I select a user and enter the passwd, then I see the wm/desktop attempt to start, then exit, then back to the f1 virtual terminal ... reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: /usr/bin/Xorg :3 -background none -verbose -auth /var/run/gdm/auth-for-gdm-wfN3Fo/database -seat seat0 -nolisten tcp crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.9.2-200.fc18.x86_64 open_fds: package: xorg-x11-server-Xorg-1.13.3-3.fc18 reason: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT) uid: 0
X terminates and I get dropped back to login screen. I can reproduce this 100% by logging into outlook.com account, opening an email, then clicking back on 'Inbox' menu link. Might have something to do with a jquery call for slide animation. This only happens in Chromium though, Firefox and Midori are OK... very rarely I get the same problem on other sites in Chromium. F18 x86_64.
No idea how this happened. Just working along and suddenly the screen blanked and came up with a login screen. reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /var/run/gdm/auth-for-gdm-0MziXu/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.9.4-200.fc18.x86_64 open_fds: package: xorg-x11-server-Xorg-1.13.3-3.fc18 reason: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 0
My display has been freezing on a regular basis. My machine is still accessible via ssh, but the GUI is completely unresponsive. In this case, I was casually browsing the internet with the chromium browser when the crash occurred. reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/bin/Xorg :1 -background none -verbose -auth /var/run/gdm/auth-for-gdm-BlHAZh/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.10.10-100.fc18.x86_64 open_fds: package: xorg-x11-server-Xorg-1.13.3-3.fc18 reason: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 0
The problem appeared after changing display resolution. Since I am unable to properly open my session (in as a normal user) reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /var/run/gdm/auth-for-gdm-1V6Qje/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.10.9-100.fc18.x86_64 open_fds: package: xorg-x11-server-Xorg-1.13.3-3.fc18 reason: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 0
I was playing 0 A.D. when I got a black screen with some error messages mentioning "noveau" (didn't know what that was at the time). I have dual screens, and had switched from fullscreen to windowed a couple of times. But the crash came minutes later.. (entire computer lock down, not even the num-lock indicator on the keyboard worked).
I am not sure, what caused the problem. But I think it was Wine: I was playing Growtopia (it runs only on Windows), and turned the Fullscreen Mode ON. Then the system had restarted reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /var/run/gdm/auth-for-gdm-da8M37/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.10.10-100.fc18.x86_64 open_fds: package: xorg-x11-server-Xorg-1.13.3-3.fc18 reason: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 0
My system was connnected to a UPS. The UPS was beeping (telling me to replace battery, but I didnt care as it was a new UPS). Then the system switched off on its own. I had to remove the UPS. Started Workstation without UPS (direct supply). On restarting the Xserver didnt start with kernel: 3.10.14-101.fc18.x86_64. Then I booted system in to kernel: 3.10.14-100.fc18.x86_64. It started. Then I got the bugzilla report (Automatic Bug Reporting Tool) that xorg-x11-server crashed. Now I also see a power management icon in sysytem try (battery monitor) telling me that: "AC ADAPETER Not plugged in" reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: /usr/bin/X :1 vt2 -auth /root/.serverauth.1572 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.11.4-101.fc18.x86_64 open_fds: package: xorg-x11-server-Xorg-1.13.3-3.fc18 reason: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT) runlevel: N 5 type: CCpp uid: 0
First 2 times it happened while starting a mp3 movie in kaffeine. Last time it happened at night when the screen was off. The problem has started to occur with a new 27" monitor which works on resolution 2560x1440 (before I had a 24" monitor at 1920x1200 on which the problem has never occured) reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: /usr/bin/X :0 vt1 -background none -nolisten tcp -auth /var/run/kdm/A:0-IA9ska crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.11.4-101.fc18.x86_64 open_fds: package: xorg-x11-server-Xorg-1.13.3-3.fc18 reason: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT) runlevel: N 5 type: CCpp uid: 0
Ever since the latest update of the kernel, the X server, and akmod-nvidia-304xx, the X server may crash as a result of a mouse click. I couldn't find a pattern, it often involves actions with the widgets of the KDE workspace, but not in a repeatable way. Happens infrequently (about once a day), usually during heavy use. reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: /usr/bin/X :0 vt1 -background none -nolisten tcp -auth /var/run/kdm/A:0-Po1Hkb crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.10.14-100.fc18.x86_64 open_fds: package: xorg-x11-server-Xorg-1.13.3-3.fc18 reason: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT) runlevel: N 5 type: CCpp uid: 0
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 18'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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.