Description of problem: Prior to this problem encountered, I've disabled SELinux. Changing SELinux status to forcing/permissive, boot-up seems no problem. But after 100% initializing, system stopped at blackscreen, and the cursor became a cross. Version-Release number of selected component: xorg-x11-server-Xorg-1.14.0-4.fc20 Additional info: backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-zpSdgj/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.9.0-0.rc7.git3.2.fc20.i686.PAE open_fds: runlevel: unknown uid: 0 ureports_counter: 1 Truncated backtrace: Thread no. 1 (9 frames) #3 OsAbort at utils.c:1299 #4 ddxGiveUp at xf86Init.c:1075 #5 AbortDDX at xf86Init.c:1119 #6 AbortServer at log.c:670 #7 FatalError at log.c:811 #8 OsSigHandler at osinit.c:147 #10 xf86CursorSetCursor at xf86Cursor.c:333 #11 xf86CursorEnableDisableFBAccess at xf86Cursor.c:233 #12 ?? at /usr/lib/xorg/modules/drivers/nvidia_drv.so Potential duplicate: bug 703807
Created attachment 738950 [details] File: backtrace
Created attachment 738951 [details] File: cgroup
Created attachment 738952 [details] File: core_backtrace
Created attachment 738953 [details] File: dso_list
Created attachment 738954 [details] File: environ
Created attachment 738955 [details] File: limits
Created attachment 738956 [details] File: maps
Created attachment 738957 [details] File: proc_pid_status
Created attachment 738958 [details] File: var_log_messages
Normal activity and X server would crash. Downgrading to xorg-x11-drv-intel-2.21.8-1.fc20.x86_64 and things are stable again. reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/bin/X -background none :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch crash_function: OsAbort environ: executable: /usr/bin/Xorg kernel: 3.11.0-0.rc2.git4.1.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.2-7.fc20 reason: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 0
Is it fixed?
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle. Changing version to '20'. More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20
I've triggered this twice in quick succession; I'm not 100% sure of the cause, but I had just opened http://www.theguardian.com/technology/2013/oct/07/nokia-lumia-1020-review-41-megapixel-camera in a tab in firefox.-review-41-megapixel-camera the 1st time, and the 2nd time it died was when I went back to Firefox and started to scroll down in that reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/bin/X :0 vt1 -background none -nolisten tcp -seat seat0 -auth /var/run/kdm/A:0-gT92ua crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.11.7-300.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.3-4.fc20 reason: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT) runlevel: N 5 type: CCpp uid: 0
Hmm that comment was added to this bug by the automatic-bug reporter deciding this was a dupe of my bug - IMHO it's completely different; my backtrace is: [ 26490.499] (EE) [ 26490.499] (EE) Backtrace: [ 26490.503] (EE) 0: /usr/bin/X (OsLookupColor+0x129) [0x4734f9] [ 26490.503] (EE) 1: /lib64/libpthread.so.0 (__restore_rt+0x0) [0x322920f74f] [ 26490.503] (EE) 2: /lib64/libc.so.6 (__memcpy_sse2_unaligned+0x29) [0x3228a93fd9] [ 26490.504] (EE) 3: /usr/lib64/xorg/modules/drivers/radeon_drv.so (_init+0x1f297) [0x7fdeab3dbbb7] [ 26490.504] (EE) 4: /usr/lib64/xorg/modules/libexa.so (exaMoveOutPixmap+0x43e0) [0x7fdeaa75ee90] [ 26490.504] (EE) 5: /usr/bin/X (dixDestroyPixmap+0x1459) [0x437ea9] [ 26490.504] (EE) 6: /usr/bin/X (SendErrorToClient+0x427) [0x43a1b7] [ 26490.505] (EE) 7: /usr/bin/X (_init+0x3b1a) [0x42be0a] [ 26490.505] (EE) 8: /lib64/libc.so.6 (__libc_start_main+0xf5) [0x3228a21d65] [ 26490.505] (EE) 9: /usr/bin/X (_start+0x29) [0x428a25] [ 26490.505] (EE) 10: ? (?+0x29) [0x29] [ 26490.505] (EE) [ 26490.506] (EE) Bus error at address 0x7fde97425000 [ 26490.506] (EE) Fatal server error: [ 26490.506] (EE) Caught signal 7 (Bus error). Server aborting and it's on a Radeon
I've now reported that as bug 1029144
I downloaded those three videos with firefox using the "dwhelper" addon: https://www.youtube.com/watch?v=J2OXVBW8Zso[0D] https://www.youtube.com/watch?v=7tXIO-YjtaY[0D] https://www.youtube.com/watch?v=WD2Dhnu3tP0 and watched them using totem. Then I got logged out. reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-HkFHDu/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.11.9-300.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-5.fc20 reason: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT) runlevel: N 5 type: CCpp uid: 0
This happens on docking or undocking the notebook reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-hHeaEm/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.11.9-300.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-5.fc20 reason: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT) runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: open compiz with gtk decorator reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/X -background none :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch crash_function: OsAbort environ: executable: /usr/bin/Xorg kernel: 3.12.5-301.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-5.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: Nothing special, just switched from X to the shell with Ctrl+Alt+F2. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-dYc3LA/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.11.10-301.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-5.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: Nothing special reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-naiao0/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.11.10-301.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-5.fc20 reason: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT) runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: I was just browsing internet... with some flash videos. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/X :0 vt1 -background none -nolisten tcp -seat seat0 -auth /var/run/kdm/A:0-U6JVqc crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.12.5-302.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-5.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: I was trying to open an image file in Pinta 1.4, when everything crashed back to the login screen. I had Firefox 26.0, Thunderbird 24.2.0, VirtualBox 4.3.6 r91406 (with windows xp), CherryTree 0.30.5, reporter: libreport-2.1.10.10.g12a3c backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-G4Gdud/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.12.5-302.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-5.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: I had this happen four or five times already, while running updates from the KDE PackageKit tray icon. SystemD reloads and I get a crash. ABRT identified this bug as a duplicate of mine.
I can reproduce this bug all the time when uploading a bunch of pictures using the image uploader on photobox.com using Firefox 26, using Chrome doesn't trigger the problem.
If you're hitting what abrt thinks is this bug, please if you can: 1) State the graphics card you're using 2) Provide the backtrace My suspicion is it's over merging bugs.
rh, could you be a little clearer please? I'm not sure I understand your thinking on this. Thanks.
KitchM: I'm suspecting a bunch of unrelated bugs are being merged to this one. (I've filed https://bugzilla.redhat.com/show_bug.cgi?id=1047071 to give detail) but if you look at that original backtrace from the original reporter you'll see the first 8 stack entries were all post-signal and they seem to be pretty consistent; so something bad happens and then whatever that bad thing was the last 8 stack frames look the sameish.
Oh, I see. Well wouldn't these automated bug reports all have backtrace info to compare? Thanks.
KitchM: Well I don't understand Abrt properly yet; but comments 16..24 don't seem to have backtraces; I think something (libreport/abrt?) is thinking these bugs are the same and then not adding the detail.
Ooow, that would be bad. My reporting usually asks for a a backtrace, but I can see where that might not always occur. Mine says that there was a backtrace rating of 4; whatever that means. But I will tell you that it is serious in that it totally crashed all programs running on the computer at that time. I will also add that this happened after "upgrading" to Fedora 20. I know I wish I never had, since the whole thing has been only worse since then. There is program slowdown, and it is even visible when playing a simple game of solitaire. On shutdown that whole system hangs while trying to close some CUPS process, even though there are no print jobs waiting and there is no printer connected at this time. I am pretty sure that Fedora screwed up the environment on this one. I would stongly sugggest looking into that source of the problems. This is not a coinsidence. My system was rock solid before. Thanks, and good luck.
Created attachment 843058 [details] backtrace FF triggered problem on radeon
(In reply to rh from comment #25) > If you're hitting what abrt thinks is this bug, please if you can: > 1) State the graphics card you're using > 2) Provide the backtrace > > My suspicion is it's over merging bugs. Using: Radeon HD 6750M with radeon driver Backtrace: https://bugzilla.redhat.com/attachment.cgi?id=843058 How to reproduce 100% of the time: upload a bunch of pictures using the image uploader on photobox.com using Firefox 26, using Chrome doesn't trigger the problem.
Hi Francois; re your comment 31/32: That backtrace looks very similar to the one I have in bug 1029144; in particular it's failing in the memcpy moving an image about for a very large image; mine is on the older r600 code, but it looks like the same code to me (but I'm no expert on this yet). It's certainly nothing like the backtrace that the original reporter on this bug has - which starts off in xf86CursorSetCursor. Dave
Another user experienced a similar problem: From libreoffice-writer, I pressed the print menu item from the File menu and at that moment, I was kicked out to the gdm login screen. HP Device Manager was running (in the system tray) and would have printed the file I was trying to print. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/X -background none :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch crash_function: OsAbort environ: executable: /usr/bin/Xorg kernel: 3.12.5-302.fc20.i686 open_fds: package: xorg-x11-server-Xorg-1.14.4-5.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: This F20 is updated from F19. When I drag a window, and move it around, the fps will slow down, a crash happen. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-L6BN0d/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.12.6-300.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-5.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
Are you all using GNOME or GTK related DE?
(In reply to Christopher Meng from comment #36) > Are you all using GNOME or GTK related DE? me? yes, it's GNOME 3.
I'm on KDE
I'm on GNOME3
GNOME3 as well
I'm using Xfce 4.10.1.
Another user experienced a similar problem: Screens went black, then I was returned to the log in screen. At the time I was editing a file in inkscape, moving a text object with alt+arrow key. I am running MATE desktop, on a thinkpad x230 (Intel HD Grpahics 4000 (i7-3520M)). I have an external monitor connected via VGA. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/X -background none :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch crash_function: OsAbort environ: executable: /usr/bin/Xorg kernel: 3.12.5-302.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-5.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
My backtrace is [312682.534] (EE) Backtrace: [312682.553] (EE) 0: /usr/bin/X (OsLookupColor+0x129) [0x473899] [312682.554] (EE) 1: /lib64/libpthread.so.0 (__restore_rt+0x0) [0x3b1fa0f74f] [312682.555] (EE) 2: /usr/bin/X (miPointerUpdateSprite+0x242) [0x58dd22] [312682.555] (EE) 3: /usr/bin/X (miPointerUpdateSprite+0x4cd) [0x58e40d] [312682.555] (EE) 4: /usr/bin/X (CompositeRegisterAlternateVisuals+0x2af3) [0x4e10f3] [312682.556] (EE) 5: /usr/bin/X (PanoramiXRenderReset+0x191) [0x527a71] [312682.556] (EE) 6: /usr/bin/X (BlockHandler+0x44) [0x43e554] [312682.556] (EE) 7: /usr/bin/X (WaitForSomething+0x134) [0x46a9a4] [312682.556] (EE) 8: /usr/bin/X (SendErrorToClient+0x111) [0x43a0c1] [312682.557] (EE) 9: /usr/bin/X (_init+0x3b1a) [0x42c02a] [312682.570] (EE) 10: /lib64/libc.so.6 (__libc_start_main+0xf5) [0x3b1f221d65] [312682.570] (EE) 11: /usr/bin/X (_start+0x29) [0x428c45] [312682.616] (EE) 12: ? (?+0x29) [0x29] I'll attach the full backtrace.
Created attachment 847743 [details] backtrace_xorg_samtygier
Another user experienced a similar problem: resumed from forced suspend. (got this crash report as well as ones for gnome-shell and gnome-session) reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-75p6Oa/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.13.0-0.rc6.git0.1.fc21.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-5.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: I was watching a video with VLC reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-AevY2w/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.12.7-300.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-5.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: Crash during restart after hibernation reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: /usr/bin/X :0 vt1 -background none -nolisten tcp -seat seat0 -auth /var/run/kdm/A:0-qpbLRb crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.12.7-300.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-5.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: Opened tweak tool. reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-udwiCq/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.12.8-300.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-5.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: It happened during a "yum update", but i do not know if it was related. I can not reproduce. reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-NekLUw/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.12.7-300.fc20.i686+PAE open_fds: package: xorg-x11-server-Xorg-1.14.4-5.fc20 reason: Xorg killed by SIGABRT runlevel: unknown type: CCpp uid: 0
Another user experienced a similar problem: The problem can be reproduced: - Using IBM Lotus Notes v9.0.1 - if I open a particular mail, the X server dump - I stored the email for further investigation reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-zC7BQz/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.12.8-300.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-5.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
Is this bug a duplicate https://bugzilla.redhat.com/show_bug.cgi?id=1003221 ?
(In reply to Sergio Pascual from comment #51) > Is this bug a duplicate > > https://bugzilla.redhat.com/show_bug.cgi?id=1003221 > > ? They're similar alright, except that they're for different Fedora versions and architectures, so it's ok to leave both of them, unless the maintainer has a better idea.
Another user experienced a similar problem: I was using firefox-26.0-6.fc20.x86_64 in full screen mode, watching some photos on Google+, when the screen got blank. I switched to VT2 before it going into suspend mode as it happened another time. I managed to login as root then I switched to VT3 in order to login as another user. At that time I think X finally crashed. reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-s1aSTb/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.12.8-300.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-5.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
Sergio: It *might* be a dupe - problem is that this bug has loads of different failures all landing in this bug all with very different backtraces except the last few entries (that are irrelevant)
I keep getting this crash during most but not all updates (both PackageKit and yum). Unfortunately that causes updates to fail part way through since the Xsession that yum is running in closes. In addition i can no longer log in (after waiting for X to restart or switching tty) since the system is apparently still booting up (something about pam_nologin?). Since the only safe way for me to update at the moment is outside of X i am doing my updates in multi-user.target rather than graphical.target. Interestingly on some updates in multi-user i am actually being kicked to the initial boot message screen (although i can switch back to my previous tty and carry on). I haven't been tracking what updates i have been running when this happens but i am pretty sure each time there has been an update involving a systemd service (which might explain the "still booting" part). I also don't know if this is relevant but i have been having this problem since around the same time as the SELinux issue but i fixed that, cleaned up and reinstalled all packages installed or updated during that time and did a full relabel just to be sure.
john5342: Do you have the backtrace that you get? This bug is actually a messy mix of 5 or 6 different failures.
This one apparently: https://retrace.fedoraproject.org/faf/reports/300041/ (I hate that abrt has become useless at giving information)
Another user experienced a similar problem: Following the steps at http://www.linux.com/learn/tutorials/542356-weekend-project-zap-your-coworkers-minds-with-multi-pointer-x : $ xinput list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ Microsoft Microsoft Basic Optical Mouse v2.0 id=10 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=16 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Video Bus id=7 [slave keyboard (3)] ↳ Sleep Button id=8 [slave keyboard (3)] ↳ Integrated Camera id=9 [slave keyboard (3)] ↳ Logitech USB Keyboard id=11 [slave keyboard (3)] ↳ Logitech USB Keyboard id=12 [slave keyboard (3)] ↳ HD Webcam C525 id=13 [slave keyboard (3)] ↳ Logitech Inc Logitech USB Headset H540 id=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=15 [slave keyboard (3)] ↳ ThinkPad Extra Buttons id=18 [slave keyboard (3)] $ xinput create-master laptop $ xinput reattach 16 'laptop pointer' reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-8iU0MZ/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.12.8-300.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-5.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
I suspect my report is for a different bug than those earlier in this ticket. Retrace log for my crash is at https://retrace.fedoraproject.org/faf/reports/357938/ .
Another user experienced a similar problem: ran yum update, system rebooted upon completion. [root@matthjac ~]# uname -a Linux tardis 3.12.8-300.fc20.x86_64 #1 SMP Thu Jan 16 01:07:50 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux I ran the update around 12:15AM Feb 15th, 2014. hardware = lenovo thinkpad w520 reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/bin/X -background none :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch crash_function: OsAbort environ: executable: /usr/bin/Xorg kernel: 3.12.8-300.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-5.fc20 reason: Xorg killed by SIGABRT runlevel: unknown type: CCpp uid: 0
Possible way to reproduce: I tried to see some Slideshare slides[1] using firefox-27.0-1.fc20.x86_64. Everything worked fine, until I pressed the fullscreen button from the bottom-right corner of the slides. Firefox displayed the slide on the whole screen and asked me if I allow or deny that. Then after a couple of seconds, X crashed. The video card is an Intel HD4000 (xorg-x11-drv-intel-2.21.15-5.fc20.x86_64). [1]: http://www.slideshare.net/brendangregg/what-linux-can-learn-from-solaris-performance-and-viceversa
Another user experienced a similar problem: Computer was just sitting idle, came back to this error. reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: Xorg :8 -config /etc/bumblebee/xorg.conf.nvidia -configdir /etc/bumblebee/xorg.conf.d -sharevts -nolisten tcp -noreset -verbose 3 -isolateDevice PCI:01:00:0 -modulepath /usr/lib64/nvidia-bumblebee/xorg,/usr/lib64/xorg/modules crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.13.5-200.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-6.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
I don't know if this will help, but I have noticed that what I stated in Comment 30 is most likely the cause. The reason I make this point is because things have begun to settle out now that there have been a couple updates to the OS. To reiterate, my experience is that this sort of thing is most likely to occur because one upgrades. I believe it is like the first model year of a car; never buy the first model year. The bugs need time to be sorted out, and one should never be the guinea pig for these programmers who don't appear to want to do their own testing. My rule of thumb is to wait until there have been at least three (3) upgrades to the new version before upgrading the OS version. It will save a huge amount of problems and personal headaches due to lost productivity. Thanks.
With the latest updates (kernel-3.13.5-200.fc20.x86_64 and xorg-x11-server-Xorg-1.14.4-6.fc20.x86_64) I can't reproduce my problem any more. My particular problem seems to be fixed.
I am using kernel-3.13.5-200.fc20.x86_64 and xorg-x11-server-Xorg-1.14.4-7.fc20.x86_64 and it still crashed yesterday when I switched firefox-27.0.1-1.fc20.x86_64 to full screen mode.
Another user experienced a similar problem: I simply double clicked to open a wine based app and GNOME crashed. I have to say this is the buggiest release of Fedora I have EVER been on ... and I've been on dozens (literally). And it is NOT getting better! reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-BUYOmh/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.13.6-200.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-7.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: $ xrandr --listproviders Providers: number : 3 Provider 0: id: 0x85 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 3 outputs: 4 associated providers: 2 name:Intel Provider 1: id: 0x59 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 6 outputs: 4 associated providers: 2 name:radeon Provider 2: id: 0x59 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 6 outputs: 4 associated providers: 2 name:radeon $ xrandr --setprovideroffloadsink 0x59 0x59 At this point there is a segfault reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/bin/X :0 vt1 -background none -nolisten tcp -seat seat0 -auth /var/run/kdm/A:0-8HUjUb crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.13.6-200.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-7.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
Description of problem: add on new vga nvidia 7950 on fc18, and then upgrade to fc20 using fedup. Version-Release number of selected component: xorg-x11-server-Xorg-1.14.4-7.fc20 Additional info: backtrace_rating: 4 cmdline: /usr/bin/X :0 vt1 -auth /root/.serverauth.4394 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.13.6-200.fc20.x86_64 last_occurrence: 1395192999 open_fds: type: CCpp uid: 0 ureports_counter: 1 Truncated backtrace: Thread no. 1 (10 frames) #2 OsAbort at utils.c:1303 #3 ddxGiveUp at xf86Init.c:1097 #4 AbortDDX at xf86Init.c:1141 #5 AbortServer at log.c:767 #6 FatalError at log.c:908 #7 OsSigHandler at osinit.c:147 #9 nouveau_resource_map_offset at nouveau_buffer.c:506 #10 nv30_emit_vtxattr at nv30/nv30_vbo.c:48 #11 nv30_vbo_validate at nv30/nv30_vbo.c:234 #12 nv30_state_validate at nv30/nv30_state_validate.c:487
Another user experienced a similar problem: uiohjio reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-oOFfmq/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.12.8-300.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-5.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: Started fullscreen LibreOffice presentation which ran video and subsequently gone wild. reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-HClo6W/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.13.7-200.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-7.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
I could perhaps prepare a reproducer, if interested. Radeon 7600M series.
Another user experienced a similar problem: I was trying to troubleshoot/launch the java ice-tea to get into a vpn when it occurred. I had two browsers trying to get to the vpn site, chrome and FF. had just installed 32 bit java SE 7u51 to try and get around the java vpn plugin to work. However, I had been trying to install two Java 32 bit versions and I am not sure if trying to install both version did it or if the last one did. reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-sKlaoL/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.11.10-301.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-5.fc20 reason: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT) runlevel: N 5 type: CCpp uid: 0
Since this is happening randomly is there any way to "prepare" the system to get a full backtrace, which could actually help identifying the problem?
I upgraded Gnome to 3.12 using the instructions here: http://fedoramagazine.org/running-gnome-3-12-on-fedora-20/ last Friday and have had no problems so far this week. Previously, I would get this failure at least a couple of times each day.
This seems to be a very generic bug. I just hit it trying to open a 6251 x 6251 png file with the Gnome image viewer.
I would wager that we can readily agree that this is a bad intereaction between the customized kernel and existing technology. Something has changed to create this incompatibility. And I would further bet that it does not seem to be shared with other distros. We do know that there are many video-related problems with various programs including Mozilla apps. It is hard to believe that well stabilized apps like X11, Mozilla, etc. share a common flaw. I have also witnessed sound and SCSI issues which I have never experienced outside of Fedora. Everything points to underlying OS code incompatibility with existing hardware. Just saying....
Who here is running Haswell or other latest chipset with hybrid video (Intel + ATI or Intel + NVidia)?
I have Haswell with hybrid video (Intel + NVidia). I *think* I have the integrated GPU turned off. Does that still count as hybrid?
Notes to everybody, please do a full update of your Fedora to the latest packages at least. Fresh F20 install can't promise no problem(same case like fedup shipped in F20 iso). Also remember if you want to help developers please provide "coredump" by check the box during ABRT submission.
Created attachment 885365 [details] Image that causes Xorg crash When I try to open this image in Firefox (tried via command line : firefox marketing-comunicacao-digital.jpg ) and Xorg crashes. NOTE: Since I'm a KDE user I can open the image with Gwenview or Konqueror Note: I've taken the image from this site: http://cursos.eduke.me/curso-agregado-marketing-comunicacao-digital/ because it was crashing my Xorg when I try to visit the site. Note 1: Gwenview complains about the image: Gwenview::ImageMetaInfoModelPrivate::fillExivGroup: Failed to read some meta info: No namespace info available for XMP prefix `stMfs' Gwenview::ImageMetaInfoModelPrivate::fillExivGroup: Failed to read some meta info: No namespace info available for XMP prefix `xmpG' I will try to get a second computer to get the Xorg running under gdb, until then I leave here this image for other people to test and see if the same happens.
I am running all the latest FC20 packages. I have 3rd gen I5 cpu. I believe thats Ivy bridge cpu. I am running optimus with 630m nVidia card, using nvidia driver.
I was confusing this one with a different X crash. My graphics cards: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV630 PRO [Radeon HD 2600 PRO] 02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV515 [Radeon X1300/X1550] 02:00.1 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] RV515 [Radeon X1300/X1550 Series] (Secondary) I tried opening the 6251 x 6251 png file in ImageMagick and it worked once yesterday, but it crashed X today.
Samuel: That one is bug 1029144 (which has an upstream fix and so just needs someone to merge it into our packages) - that's specific to Radeon's on large images.
ABRT sent me here. I think what I actually hit was https://bugzilla.redhat.com/show_bug.cgi?id=1029144 Evidence: /var/tmp/abrt/ccpp-2014-04-18-15:03:41-835/core_backtrace shows __memcpy_sse2_unaligned R600UploadToScreenCS exaPutImage
Another user experienced a similar problem: https://ask.fedoraproject.org/en/question/45924/fedora-20-updated-hibernation-and-freezing-issue/ reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/X :0 vt1 -background none -nolisten tcp -seat seat0 -auth /var/run/kdm/A:0-NKBSca crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.14.1-200.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-7.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: May happen when I try to Switch User from root KDE session (session no. 2). This is a qemu/spice VM. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/Xorg :1 -background none -verbose -auth /run/gdm/auth-for-gdm-czfBvi/database -seat seat0 -nolisten tcp crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.14.2-200.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-7.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
If I switch firefox-29.0-5.fc20.x86_64 to fullscreen mode, X goes ballistic. Could someone else verify if this happens to them, too?
Another user experienced a similar problem: Playing Civilization using wine reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -noreset -verbose 3 -logfile /dev/null -auth /run/gdm/auth-for-gdm-mLf1iu/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.14.2-200.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-7.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
(In reply to Cristian Ciupitu from comment #87) > If I switch firefox-29.0-5.fc20.x86_64 to fullscreen mode, X goes ballistic. > Could someone else verify if this happens to them, too? not here on fedora 20 ( with kde )
Another user experienced a similar problem: Attempted to run DRI_PRIME=1 on a optimus laptop with nouveau. No bumble or bbswitch components installed. Here is the log with drm.debug=14. This is me running DRI_PRIME=0 glxspheres first, then the DRI_PRIME=1 second. May 14 11:57:16 maddy. kernel: [drm:drm_mode_addfb], [FB:50] May 14 11:57:17 maddy. kernel: [drm:intel_crtc_cursor_set], cursor off May 14 11:57:18 maddy. kernel: [drm:i915_gem_open], May 14 11:57:18 maddy. kernel: [drm:i915_gem_context_create_ioctl], HW context 1 created May 14 11:57:18 maddy. kernel: [drm:drm_mode_addfb], [FB:51] May 14 11:57:18 maddy. kernel: [drm:drm_mode_addfb], [FB:50] May 14 11:57:22 maddy. kernel: [drm:i915_gem_context_destroy_ioctl], HW context 1 destroyed May 14 11:57:22 maddy. kernel: [drm:drm_mode_addfb], [FB:51] May 14 11:57:27 maddy. kernel: [drm:drm_mode_addfb], [FB:50] May 14 11:57:27 maddy. kernel: [drm:intel_crtc_cursor_set], cursor off May 14 11:57:29 maddy. kernel: [drm:intel_crtc_set_config], [CRTC:3] [FB:49] #connectors=1 (x y) (0 0) May 14 11:57:29 maddy. kernel: [drm:intel_set_config_compute_mode_changes], computed changes for [CRTC:3], mode_changed=0, fb_changed=1 May 14 11:57:29 maddy. kernel: [drm:intel_modeset_stage_output_state], [CONNECTOR:12:eDP-1] to [CRTC:3] May 14 11:57:29 maddy. kernel: [drm:intel_modeset_stage_output_state], [CONNECTOR:9:VGA-1] to [CRTC:5] May 14 11:57:29 maddy. kernel: [drm:ironlake_update_plane], Writing base 000A1000 00000000 0 0 7680 May 14 11:57:29 maddy. kernel: [drm:intel_edp_psr_match_conditions], PSR disable by flag May 14 11:57:29 maddy. kernel: [drm:intel_crtc_set_config], [CRTC:5] [FB:49] #connectors=1 (x y) (0 0) May 14 11:57:29 maddy. kernel: [drm:intel_set_config_compute_mode_changes], computed changes for [CRTC:5], mode_changed=0, fb_changed=1 May 14 11:57:29 maddy. kernel: [drm:intel_modeset_stage_output_state], [CONNECTOR:12:eDP-1] to [CRTC:3] May 14 11:57:29 maddy. kernel: [drm:intel_modeset_stage_output_state], [CONNECTOR:9:VGA-1] to [CRTC:5] May 14 11:57:29 maddy. kernel: [drm:ironlake_update_plane], Writing base 000A1000 00000000 0 0 7680 May 14 11:57:29 maddy. kernel: [drm:intel_edp_psr_match_conditions], PSR disable by flag May 14 11:57:29 maddy. kernel: [drm:intel_crtc_set_config], [CRTC:7] [NOFB] May 14 11:57:29 maddy. kernel: [drm:intel_set_config_compute_mode_changes], computed changes for [CRTC:7], mode_changed=0, fb_changed=0 May 14 11:57:29 maddy. kernel: [drm:intel_modeset_stage_output_state], [CONNECTOR:12:eDP-1] to [CRTC:3] May 14 11:57:29 maddy. kernel: [drm:intel_modeset_stage_output_state], [CONNECTOR:9:VGA-1] to [CRTC:5] May 14 11:57:29 maddy. kernel: [drm:intel_crtc_set_config], [CRTC:3] [FB:49] #connectors=1 (x y) (0 0) May 14 11:57:29 maddy. kernel: [drm:intel_set_config_compute_mode_changes], computed changes for [CRTC:3], mode_changed=0, fb_changed=0 May 14 11:57:29 maddy. kernel: [drm:intel_modeset_stage_output_state], [CONNECTOR:12:eDP-1] to [CRTC:3] May 14 11:57:29 maddy. kernel: [drm:intel_modeset_stage_output_state], [CONNECTOR:9:VGA-1] to [CRTC:5] May 14 11:57:29 maddy. kernel: [drm:intel_crtc_set_config], [CRTC:5] [FB:49] #connectors=1 (x y) (0 0) May 14 11:57:29 maddy. kernel: [drm:intel_set_config_compute_mode_changes], computed changes for [CRTC:5], mode_changed=0, fb_changed=0 May 14 11:57:29 maddy. kernel: [drm:intel_modeset_stage_output_state], [CONNECTOR:12:eDP-1] to [CRTC:3] May 14 11:57:29 maddy. kernel: [drm:intel_modeset_stage_output_state], [CONNECTOR:9:VGA-1] to [CRTC:5] May 14 11:57:29 maddy. kernel: [drm:intel_crtc_set_config], [CRTC:3] [FB:49] #connectors=1 (x y) (0 0) May 14 11:57:29 maddy. kernel: [drm:intel_set_config_compute_mode_changes], computed changes for [CRTC:3], mode_changed=0, fb_changed=0 May 14 11:57:29 maddy. kernel: [drm:intel_modeset_stage_output_state], [CONNECTOR:12:eDP-1] to [CRTC:3] May 14 11:57:29 maddy. kernel: [drm:intel_modeset_stage_output_state], [CONNECTOR:9:VGA-1] to [CRTC:5] May 14 11:57:29 maddy. kernel: [drm:intel_crtc_set_config], [CRTC:5] [FB:49] #connectors=1 (x y) (0 0) May 14 11:57:29 maddy. kernel: [drm:intel_set_config_compute_mode_changes], computed changes for [CRTC:5], mode_changed=0, fb_changed=0 May 14 11:57:29 maddy. kernel: [drm:intel_modeset_stage_output_state], [CONNECTOR:12:eDP-1] to [CRTC:3] May 14 11:57:29 maddy. kernel: [drm:intel_modeset_stage_output_state], [CONNECTOR:9:VGA-1] to [CRTC:5] May 14 11:57:29 maddy. abrt-hook-ccpp[3315]: Saved core dump of pid 1285 (/usr/bin/Xorg) to /var/tmp/abrt/ccpp-2014-05-14-11:57:29-1285 (29487104 bytes) May 14 11:57:29 maddy. kernel: thinkpad_acpi: EC reports that Thermal Table has changed May 14 11:57:30 maddy. abrt-server[3317]: Generating core_backtrace May 14 11:57:30 maddy. abrt-server[3317]: Generating backtrace May 14 11:57:30 maddy. kernel: nouveau E[ PIBUS][0000:02:00.0] GPC0: 0x4188ac 0x00000001 (0x1e70822e) This is the vgaswitching state: cat /sys/kernel/debug/vgaswitcheroo/switch 0:IGD:+:Pwr:0000:00:02.0 1:DIS: :DynOff:0000:02:00.0 Relevant lspci 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device 220f Flags: bus master, fast devsel, latency 0, IRQ 46 Memory at f1000000 (64-bit, non-prefetchable) [size=4M] Memory at e0000000 (64-bit, prefetchable) [size=256M] I/O ports at 4000 [size=64] Expansion ROM at <unassigned> [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 Kernel modules: i915 02:00.0 VGA compatible controller: NVIDIA Corporation GK208M [GeForce GT 730M] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device 220f Flags: bus master, fast devsel, latency 0, IRQ 47 Memory at f0000000 (32-bit, non-prefetchable) [size=16M] Memory at c0000000 (64-bit, prefetchable) [size=256M] Memory at d0000000 (64-bit, prefetchable) [size=32M] I/O ports at 3000 [size=128] Expansion ROM at <ignored> [disabled] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [128] Power Budgeting <?> Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> Capabilities: [900] #19 Kernel driver in use: nouveau Kernel modules: nouveau xrandr --listproviders Providers: number : 2 Provider 0: id: 0x68 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 3 outputs: 6 associated providers: 1 name:Intel Provider 1: id: 0x3f cap: 0x5, Source Output, Source Offload crtcs: 0 outputs: 0 associated providers: 1 name:nouveau reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-U6vHMi/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.14.2-200.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-7.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: Xorg crash randomly after few minutes from login. It's a FC20 KVM Virtual machine, with qxl video reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/X -background none :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch crash_function: OsAbort environ: executable: /usr/bin/Xorg kernel: 3.14.4-200.fc20.i686 open_fds: package: xorg-x11-server-Xorg-1.14.4-9.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: It crashes always when I try to run the game "Braid". reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/Xorg :1 -background none -noreset -verbose 3 -logfile /dev/null -auth /run/gdm/auth-for-gdm-IltFSs/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.14.4-200.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-9.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
In a ssh shell I've attached gdb to a running Xorg and opened an image that crashes with firefox: Program received signal SIGBUS, Bus error. __memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:39 39 movdqu %xmm8, (%rdi) (gdb) bt #0 __memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:39 #1 0x00007f95934b2f07 in memcpy (__len=31924, __src=<optimized out>, __dest=0x7f9582af4000) at /usr/include/bits/string3.h:51 #2 EVERGREENUploadToScreen (pDst=0x21ecc70, x=0, y=0, w=7981, h=8, src=<optimized out>, src_pitch=31924) at evergreen_exa.c:1726 #3 0x00007f9593060e10 in exaDoPutImage (depth=32, src_stride=<optimized out>, bits=0x258bb78 "\320\316\315\377\320\316\315\377\320\316\315\377\320\316\315\377\320\316\315\377\320\316\315\377\320\316\315\377\320\316\315\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377"..., format=2, h=8, w=7981, y=0, x=0, pGC=0x21dc980, pDrawable=0x21ecc70) at exa_accel.c:212 #4 exaPutImage (pDrawable=0x21ecc70, pGC=0x21dc980, depth=32, x=0, y=0, w=7981, h=8, leftPad=0, format=2, bits=0x258bb78 "\320\316\315\377\320\316\315\377\320\316\315\377\320\316\315\377\320\316\315\377\320\316\315\377\320\316\315\377\320\316\315\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377"...) at exa_accel.c:233 #5 0x0000000000436d99 in ProcPutImage (client=0x214bc50) at dispatch.c:1966 #6 0x000000000043a327 in Dispatch () at dispatch.c:432 #7 0x00000000004288da in main (argc=11, argv=0x7fff1605d598, envp=<optimized out>) at main.c:298 (gdb) bt full #0 __memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:39 No locals. #1 0x00007f95934b2f07 in memcpy (__len=31924, __src=<optimized out>, __dest=0x7f9582af4000) at /usr/include/bits/string3.h:51 No locals. #2 EVERGREENUploadToScreen (pDst=0x21ecc70, x=0, y=0, w=7981, h=8, src=<optimized out>, src_pitch=31924) at evergreen_exa.c:1726 pScrn = 0x173d1d0 info = 0x173d750 accel_state = <optimized out> driver_priv = 0x213bd70 scratch = <optimized out> copy_dst = 0x205f220 dst = 0x7f9582af4000 <error: Cannot access memory at address 0x7f9582af4000> size = 31924 dst_domain = 4 bpp = <optimized out> scratch_pitch = <optimized out> copy_pitch = 32000 dst_pitch_hw = <optimized out> ret = <optimized out> flush = <optimized out> r = 1 i = 0 src_obj = {pitch = 7981, width = 31924, height = 32, bpp = 0, domain = 0, bo = 0x850405b80d016b00, tiling_flags = 24433120, surface = 0x7f959349bb69 <RADEONEXAPixmapIsOffscreen+9>} dst_obj = {pitch = 35572848, width = 0, height = 2466643016, bpp = 32661, domain = 2468803456, bo = 0x7f959349bb69 <RADEONEXAPixmapIsOffscreen+9>, tiling_flags = 35572848, surface = 0x7f959305fc48 <exaPixmapHasGpuCopy_mixed+104>} height = <optimized out> base_align = <optimized out> #3 0x00007f9593060e10 in exaDoPutImage (depth=32, src_stride=<optimized out>, bits=0x258bb78 "\320\316\315\377\320\316\315\377\320\316\315\377\320\316\315\377\320\316\315\377\320\316\315\377\320\316\315\377\320\316\315\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377"..., format=2, h=8, w=7981, y=0, x=0, pGC=0x21dc980, pDrawable=0x21ecc70) at exa_accel.c:212 y1 = <optimized out> x2 = <optimized out> ok = <optimized out> x1 = <optimized out> y2 = <optimized out> src = <optimized out> pExaPixmap = <optimized out> nbox = <optimized out> ---Type <return> to continue, or q <return> to quit--- pPix = 0x21ecc70 xoff = 0 ret = 1 pClip = <optimized out> pbox = 0x212ef60 yoff = 0 bpp = <optimized out> #4 exaPutImage (pDrawable=0x21ecc70, pGC=0x21dc980, depth=32, x=0, y=0, w=7981, h=8, leftPad=0, format=2, bits=0x258bb78 "\320\316\315\377\320\316\315\377\320\316\315\377\320\316\315\377\320\316\315\377\320\316\315\377\320\316\315\377\320\316\315\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377"...) at exa_accel.c:233 No locals. #5 0x0000000000436d99 in ProcPutImage (client=0x214bc50) at dispatch.c:1966 pGC = 0x21dc980 pDraw = 0x21ecc70 length = <optimized out> lengthProto = <optimized out> tmpImage = 0x258bb78 "\320\316\315\377\320\316\315\377\320\316\315\377\320\316\315\377\320\316\315\377\320\316\315\377\320\316\315\377\320\316\315\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377\321\317\316\377"... stuff = 0x258bb60 #6 0x000000000043a327 in Dispatch () at dispatch.c:432 clientReady = 0x1a12230 result = <optimized out> client = 0x214bc50 nready = 0 icheck = 0x822670 <checkForInput> start_tick = 200 #7 0x00000000004288da in main (argc=11, argv=0x7fff1605d598, envp=<optimized out>) at main.c:298 i = <optimized out> alwaysCheckForInput = {0, 1} (gdb)
Another user experienced a similar problem: Put laptop to sleep (suspend), disconnect external monitors, close laptop lid. Upon reopening laptop lid the session crashed and I was logged out. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-yOJBGi/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.14.4-200.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-9.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
Paulo: If that was an absolutely huge image then that backtrace looks to me like you're hitting: https://bugzilla.redhat.com/show_bug.cgi?id=1029144
This is the image used: http://cursos.eduke.me/wp-content/uploads/2014/03/marketing-comunicacao-digital.jpg I've downloaded and opened, but if you open it with firefox will crash. I can open it with KDE tools (Konqueror, Gwenview, etc) without problems. Also, I've tested in a KVM virtual machine and found no problem.
Paulo: Just for kicks, try disabling acceleration in the Nouveau driver. In /etc/modprobe.d/nouveau.conf, add the line, "options nouveau noaccel=1", without the " symbols and reboot.
LarryO: I'm using radeon driver not nouveau, my laptop got an ATI/AMD card.
Paulo: Yes, I'm pretty sure that's 1029144 you're hitting; I only ever hit it with large images in Firefox.
Another user experienced a similar problem: Trying to use DRI Prime and gallium HUD instantly segfaults X. Command line is: DRI_PRIME=1 GALLIUM_HUD="cpu0+cpu1+cpu2+cpu3:100,cpu:100,fps;draw-calls,requested-VRAM+requested-GTT,pixels-rendered" pymol GPUs are a radeon hd5750 as gpu0 and radeon 7950 as gpu1 reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/X -background none :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch crash_function: OsAbort environ: executable: /usr/bin/Xorg kernel: 3.13.10-200.gb990fxa40_2.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-9.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: Xorg freeze and restart X when conect another monitor AOC on hp pavilion dm4. I donw know Why it is happening. it was working just fine. now i cant connect another monitor. The same Laptop has windows on dualboot and it works fine. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/X -background none :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch crash_function: OsAbort environ: executable: /usr/bin/Xorg kernel: 3.14.4-200.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-9.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
Working off a tip, I disabled acceleration in the Nouveau driver by creating /etc/modprobe.d/nouveau.conf with the following lines: # The next line was added 6/1/2014 by Larry to disable # acceleration in the Nouveau drive to prevent hangs. options nouveau noaccel=1 The symptom used to occur between 2 and 5 times a week and hasn't occurred since 6/1. If the problem doesn't recur by the end of this month, this will clearly indicate possible causes or, at leats, a work-around.
Today I've tried again loading this image, which has caused trouble in past: http://cursos.eduke.me/wp-content/uploads/2014/03/marketing-comunicacao-digital.jpg and got no problems.
Was that after another update to the OS?
Was a new instalation but also now I have a different graphics card: Intel.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.