Bug 243694 - X server crashes when starting f-spot
Summary: X server crashes when starting f-spot
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11   
(Show other bugs)
Version: 7
Hardware: x86_64 Linux
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2007-06-11 13:29 UTC by Samuel Irlapati
Modified: 2018-04-11 11:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-06-12 15:04:58 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Samuel Irlapati 2007-06-11 13:29:51 UTC
Description of problem: X server crashes when starting f-spot.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Log into a gnome desktop session
2. Start f-spot
Actual results:X server crashes. It takes me back to a console prompt and then
the X server restarts.

Expected results:

Additional info:

Comment 1 Samuel Irlapati 2007-06-11 13:31:49 UTC
Here are the last few lines of Xorg log file.

(II) XINPUT: Adding extended input device "<default pointer>" (type: MOUSE)
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(--) <default pointer>: PnP-detected protocol: "ExplorerPS/2"
(II) <default pointer>: ps2EnableDataReporting: succeeded
(II) 3rd Button detected: disabling emulate3Button

0: /usr/bin/Xorg(xf86SigHandler+0x6d) [0x48b20d]
1: /lib64/libc.so.6 [0x3c5fc30620]

Fatal server error:
Caught signal 11.  Server aborting

Comment 2 Samuel Irlapati 2007-06-11 13:33:54 UTC
This happens when starting Beryl too.

I have an nvidia card. Below is my xorg.conf file.

# Xorg configuration created by system-config-display

Section "ServerLayout"
	Identifier     "single head configuration"
	Screen      0  "Screen0" 0 0
	InputDevice    "Keyboard0" "CoreKeyboard"

Section "Files"


Section "Module"
	Load  "fbdevhw"
	Load  "record"
	Load  "freetype"
	Load  "type1"
	Load  "glx"
	Load  "dbe"
	Load  "extmod"

Section "InputDevice"
	Identifier  "Keyboard0"
	Driver      "kbd"
	Option	    "XkbModel" "pc105"
	Option	    "XkbLayout" "us"

Section "Monitor"

	Identifier   "Monitor0"
	ModelName    "LCD Panel 1280x1024"
 ### Comment all HorizSync and VertSync values to use DDC:
	HorizSync    31.5 - 67.0
	VertRefresh  50.0 - 75.0
	Option	    "dpms"
	Option	    "SWCursor"

Section "Device"
	Identifier  "Videocard0"
	Driver      "nvidia"
	Option	    "TripleBuffer" "True"
	Option	    "AllowGLXWithComposite" "True"
	Option	    "RenderAccel" "True"
	Option	    "DisableGLXRootClipping" "True"
	Option	    "AddARGBGLXVisuals" "True"

Section "Screen"
	Identifier "Screen0"
	Device     "Videocard0"
	Monitor    "Monitor0"
	DefaultDepth     16
	SubSection "Display"
		Viewport   0 0
		Depth     24
		Modes    "1280x1024" "1280x960" "1280x800" "1152x864" "1152x768" "1024x768"
"800x600" "640x480"
	SubSection "Display"
		Viewport   0 0
		Depth     16
		Modes    "1280x1024" "1280x960" "1280x800" "1152x864" "1152x768" "1024x768"
"800x600" "640x480"

Section "DRI"
	Group        0
	Mode         0666

Section "Extensions"
	Option	    "Composite" "Enable"
	Option	    "RenderAccel" "Enable"

Comment 3 Matěj Cepl 2007-06-12 15:04:58 UTC
Thanks for the report. I am sorry, that we cannot help you with your problem,
but we are not able to support binary-only drivers. If you would be able to
reproduce this issue using only open source software, please, reopen this bug
with the additional information, but in meantime I have no choice than to close
this bug as CANTFIX (because we really cannot fix it).

For users who are experiencing problems installing, configuring, or using the
unsupported 3rd party proprietary "nvidia" video driver, Nvidia provides
indirect customer support via an online web based support forum.  Nvidia
monitors these web forums for commonly reported problems and passes them on to
Nvidia engineers for investigation.  Once they've isolated a particular problem,
it is often fixed in a future video driver update.

The NVNews Nvidia Linux driver forum is located at:


Once you have reported this issue in the Nvidia web forums, others who may have
experienced the particular problem may be able to assist.  If there is a real
bug occuring, Nvidia will be able to determine this, and will likely resolve the
issue in a future driver update for the operating system releases that they
officially support.

While Red Hat does not support the proprietary nvidia driver, users requiring
technical support may also find the various X.Org, XFree86, and Red Hat mailing
lists helpful in finding assistance:

X.Org mailing lists:

XFree86 mailing lists:

Red Hat mailing lists:

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