Bug 55520

Summary:	Segmentation fault in X11 when running gthumb
Product:	xorg	Reporter:	James Peterson <lyle>
Component:	Server/General	Assignee:	Xorg Project Team <xorg-team>
Status:	RESOLVED NOTOURBUG	QA Contact:	Xorg Project Team <xorg-team>
Severity:	normal
Priority:	low	CC:	lyle
Version:	unspecified
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description James Peterson 2012-10-01 23:12:49 UTC

Running Linux Fedora Core 17, just ran a "yum update" which updated my
X11 server to:
Oct 01 16:10:35 Updated: xorg-x11-server-Xorg-1.12.3-2.fc17.x86_64
as well as lots of other xorg packages:
Oct 01 16:05:39 Updated: 1:xorg-x11-drv-nvidia-libs-304.37-2.fc17.x86_64
Oct 01 16:05:42 Updated: 1:xorg-x11-drv-nvidia-304.37-2.fc17.x86_64
Oct 01 16:10:22 Updated: abrt-addon-xorg-2.0.13-1.fc17.x86_64
Oct 01 16:10:33 Updated: xorg-x11-server-common-1.12.3-2.fc17.x86_64
Oct 01 16:10:35 Updated: xorg-x11-server-Xorg-1.12.3-2.fc17.x86_64
Oct 01 16:11:06 Updated: xorg-x11-drv-siliconmotion-1.7.6-1.fc17.x86_64
Oct 01 16:11:08 Updated: xorg-x11-drv-intel-2.20.8-1.fc17.x86_64
Oct 01 16:11:11 Updated: xorg-x11-drv-cirrus-1.4.0-1.fc17.x86_64

Now, when I start up gthumb, my X11 server dies.  In the Xorg.0.log.old
file, I find:

[  1801.783] 
[  1801.783] Backtrace:
[  1801.784] 0: /usr/bin/Xorg (xorg_backtrace+0x36) [0x4652d6]
[  1801.784] 1: /usr/bin/Xorg (0x400000+0x6a2b9) [0x46a2b9]
[  1801.784] 2: /lib64/libpthread.so.0 (0x7ff1566bd000+0xefe0) [0x7ff1566cbfe0]
[  1801.784] 
[  1801.784] Segmentation fault at address (nil)
[  1801.784] 
Fatal server error:
[  1801.784] Caught signal 11 (Segmentation fault). Server aborting


jim

Comment 1 James Peterson 2012-10-02 16:03:48 UTC

Continuing to try to understand this, I saw a comment that suggested un-installing and re-installing the NVIDIA driver would help.  So I did that and the (immediate) problem seems to have gone away.

Oct 02 08:51:47 Erased: 1:kmod-nvidia-3.5.3-1.fc17.x86_64-304.37-1.fc17.3.x86_64
Oct 02 08:51:56 Erased: 1:kmod-nvidia-304.37-1.fc17.5.x86_64
Oct 02 08:51:58 Erased: 1:kmod-nvidia-3.5.2-1.fc17.x86_64-304.37-1.fc17.1.x86_64
Oct 02 08:52:05 Erased: 1:kmod-nvidia-3.5.4-2.fc17.x86_64-304.37-1.fc17.5.x86_64
Oct 02 08:52:14 Erased: 1:xorg-x11-drv-nvidia-libs-304.37-2.fc17.x86_64
Oct 02 08:52:16 Erased: 1:xorg-x11-drv-nvidia-304.37-2.fc17.x86_64
Oct 02 08:53:02 Installed: 1:xorg-x11-drv-nvidia-libs-304.37-2.fc17.x86_64
Oct 02 08:53:04 Installed: 1:xorg-x11-drv-nvidia-304.37-2.fc17.x86_64
Oct 02 08:53:06 Installed: 1:kmod-nvidia-3.5.4-2.fc17.x86_64-304.37-1.fc17.5.x86
_64
Oct 02 08:53:07 Installed: 1:kmod-nvidia-304.37-1.fc17.5.x86_64


So the real problem seems to have been some kind of mismatch in kernel/nvidia/x11 systems, aggravated by the "yum update".

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.