Bug 670218 - [abrt] xorg-x11-server-Xorg-1.9.3-3.fc14: OsAbort: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT)
Summary: [abrt] xorg-x11-server-Xorg-1.9.3-3.fc14: OsAbort: Process /usr/bin/Xorg was ...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 14
Hardware: x86_64
OS: Unspecified
low
high
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:f992072c26097709010d82df3c5...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-17 15:28 UTC by Drew
Modified: 2018-04-11 12:05 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-20 16:16:46 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (8.22 KB, text/plain)
2011-01-17 15:28 UTC, Drew
no flags Details
Xorg Config (2.60 KB, text/plain)
2011-01-17 15:30 UTC, Drew
no flags Details
Log file from before Crash (14.41 KB, text/plain)
2011-01-17 15:31 UTC, Drew
no flags Details

Description Drew 2011-01-17 15:28:45 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/Xorg :0 -br -verbose -auth /var/run/gdm/auth-for-gdm-1IvR6K/database -nolisten tcp
comment: This has been happening since late 2010. Originally thought to be related to 649526, but with that patch applied and no configuration settings changed it still occurs. Backtrace shows issue in doListFontsAndAliases() at dixfonts.c:614.
component: xorg-x11-server
crash_function: OsAbort
executable: /usr/bin/Xorg
kernel: 2.6.35.10-74.fc14.x86_64
package: xorg-x11-server-Xorg-1.9.3-3.fc14
rating: 4
reason: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1295277432
uid: 0

How to reproduce
-----
1. Start VLC, or other QT program.
2. If it does not crash instantly, open a window with a text box
3. Place pointer inside text box in order to type

Comment 1 Drew 2011-01-17 15:28:47 UTC
Created attachment 473863 [details]
File: backtrace

Comment 2 Drew 2011-01-17 15:30:32 UTC
Created attachment 473864 [details]
Xorg Config

Comment 3 Drew 2011-01-17 15:31:19 UTC
Created attachment 473865 [details]
Log file from before Crash

Comment 4 Drew 2011-01-17 15:33:09 UTC
Using nvidia drives from Nvidia.com and RPMFusion repo.

Problem persisted when I disabled TwinView and Xinerama and had only one screen operating.

Comment 5 Matěj Cepl 2011-07-20 16:16:46 UTC
Thanks for the report. We are 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).

The open source 'nouveau' driver (in package xorg-x11-drv-nouveau) is the recommended alternative for users of Nvidia graphic chips.  It is used by default in Fedora 11 and later if you remove any customizations that explicitly set the video driver.  The older "nv" driver may be needed in some cases.  It is also available in older Fedora releases.  Install the packages xorg-x11-drv-nouveau or xorg-x11-drv-nv and override the X server's default choice if necessary.  See https://fedoraproject.org/wiki/Features/NouveauAsDefault for more information.

If you used a non-packaged version of the driver from the Nvidia website please clean your system from additional libraries and software it installed. 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:

	http://www.nvnews.net/vbulletin/forumdisplay.php?s=&forumid=14

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 we does not support the proprietary nvidia driver, users requiring technical support may also find the various X.Org, XFree86, and Red Hat/Fedora mailing lists helpful in finding assistance:

X.Org mailing lists:
	http://www.freedesktop.org/XOrg/XorgMailingLists

XFree86 mailing lists:
	http://www.xfree86.org/sos/lists.html

Red Hat/Fedora mailing lists:
	https://listman.redhat.com/mailman/listinfo


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