Bug 690182 - [JUNIPER] Xorg randomly crashing
Summary: [JUNIPER] Xorg randomly crashing
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 15
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Jérôme Glisse
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-23 14:24 UTC by Jeff Layton
Modified: 2014-06-18 07:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-07 19:15:22 UTC
Type: ---


Attachments (Terms of Use)
Xorg.0.log (74.20 KB, text/plain)
2011-03-23 14:24 UTC, Jeff Layton
no flags Details
yum update log from this morning (11.56 KB, text/plain)
2011-03-23 14:26 UTC, Jeff Layton
no flags Details
Piece of Wallpaper Sundown Dunes (garbled) (85.17 KB, image/png)
2011-03-23 21:58 UTC, Joachim Frieben
no flags Details

Description Jeff Layton 2011-03-23 14:24:02 UTC
Created attachment 487051 [details]
Xorg.0.log

Description of problem:
Did a yum update of my F15 machine this morning, and since then Xorg has been randomly segfaulting crashing all over the place. There are also some other gnome apps segfaulting too, but they may be separate problems.

Attaching Xorg.0.log.old from one of these events. The stack trace in the log is:

Backtrace:
[  1247.475] 0: /usr/bin/Xorg (xorg_backtrace+0x2f) [0x4a105f]
[  1247.475] 1: /usr/bin/Xorg (0x400000+0x620a6) [0x4620a6]
[  1247.475] 2: /lib64/libpthread.so.0 (0x7f30fadaf000+0xf4e0) [0x7f30fadbe4e0]
[  1247.475] 3: /usr/lib64/xorg/modules/extensions/libglx.so (0x7f30f9cde000+0x339cb) [0x7f30f9d119cb]
[  1247.475] 4: /usr/bin/Xorg (FreeClientResources+0xd5) [0x44c495]
[  1247.476] 5: /usr/bin/Xorg (CloseDownClient+0x5e) [0x42df6e]
[  1247.476] 6: /usr/bin/Xorg (0x400000+0x2ea1f) [0x42ea1f]
[  1247.476] 7: /usr/bin/Xorg (0x400000+0x22d3a) [0x422d3a]
[  1247.476] 8: /lib64/libc.so.6 (__libc_start_main+0xed) [0x7f30fa5a731d]
[  1247.476] 9: /usr/bin/Xorg (0x400000+0x23021) [0x423021]
[  1247.476] Segmentation fault at address (nil)
[  1247.476] 
Fatal server error:
[  1247.476] Caught signal 11 (Segmentation fault). Server aborting

Comment 1 Jeff Layton 2011-03-23 14:26:23 UTC
Created attachment 487053 [details]
yum update log from this morning

Here's a list of packages that were updated this morning. No xorg packages were updated, so it seems semi-likely that the problem is in a related library. I'm not sure which one though, so I've opened this as an xorg-x11-server bug until we can determine that.

Comment 2 Jeff Layton 2011-03-23 14:28:35 UTC
FWIW, attempting to change the background wallpaper in gnome-control-center seems to trigger the crash pretty frequently (not always though). It has also crashed doing things unrelated to that as well.

Comment 3 Joachim Frieben 2011-03-23 21:58:30 UTC
Created attachment 487153 [details]
Piece of Wallpaper Sundown Dunes (garbled)

Open "My Settings", then "Background". Before, gnome-control-center would crash at this point. Now, the thumbnails of the various wallpapers get rendered in the left pane. When a particular thumbnail gets a mouse click, then the background is rendered correctly. But a second later, X crashes, and upon logging in, the wallpaper is garbled. The previous Xorg.0.log shows a backtrace near ist tail:

Backtrace:
[   452.990] 0: /usr/bin/Xorg (xorg_backtrace+0x2f) [0x4a105f]
[   452.990] 1: /usr/bin/Xorg (0x400000+0x620a6) [0x4620a6]
[   452.990] 2: /lib64/libpthread.so.0 (0x7f872d86c000+0xf4e0) [0x7f872d87b4e0]
[   452.990] Segmentation fault at address (nil)
[   452.990] 
Fatal server error:
[   452.990] Caught signal 11 (Segmentation fault). Server aborting

Comment 4 Jeff Layton 2011-03-25 14:26:38 UTC
Maybe related problem -- often (50% of the time or so) when I log in I get no wallpaper at all. It'll show up on the desktop briefly as GNOME starts up, and then go black. If I log out and back in a few times, eventually the wallpaper will stick around after gnome has started.

Comment 5 Fedora End Of Life 2012-08-07 19:15:24 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached 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 to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.