Bug 483272

OOo has never once taken out an XServer for me in 10 years of development for me :-), so this is not something that I've seen much of. So I'm swung towards blaming X, and the specific driver that you have, whichever that is.

Best to attach the information mentioned at
https://fedoraproject.org/wiki/User:Mcepl/Bug_reporting_HOWTO#Xorg_.26_co._bugs
to this bug so as to get the X details

Created attachment 330491 [details]
xorg.conf for HP DV2854ca

Precisions:
 1. I am using KDE (this happened in 3.5, 4.0 and 4.1).
 2. This happened on different hardware and since a few Fedora versions:
	a- Sun Ultra 20 (Nvidia card), KDE 3.5 (Fedora 8)
	b- HP Pavilion A6652f (desktop), both with the native Intel 3100 driver and more recently with a Nvidia 9500GT card. Fedora 8, 9 and 10.
	c- HP Pavilion DV2654ca (laptop) with Intel 3100 driver. Fedora 10
I am attaching the latter xorg.conf (c) since this just happened to me this morning on that machine.

After it crashes for you attach "X server log file (/var/log/Xorg.*.log)", that might include some info as to what made X crash/exit

Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please attach your X server config file (/etc/X11/xorg.conf, if available) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.

Please note, that we don't support nvidia binary-only driver, so any logs you provide should be created only using open source drivers (either -nv or -nouveau).

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Created attachment 332012 [details]
My log after a crash on a Lenovo T61.

Errr sorry to get your hopes up... binary driver... :(

Yup, you got it :( Standard information follows:

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).

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 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:
    http://www.freedesktop.org/XOrg/XorgMailingLists

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

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

You are very prompt to blame X in the first place, and then binary drivers.
I specifically indicated when I reported this bug that this happens with the Intel hardware and its open source driver. I don't think this is a problem of binary drivers. 

I will reopen the bug if I can attach some log on the Intel platform.

I am sorry, I got caught by comment 7 -- I confused hijacker of this bug with you. Please, do attach these logs from your system.

Thanks and sorry again

No problem captain, hijacking thwarted, resume course to bug-free land.

(In reply to comment #11)
> No problem captain, hijacking thwarted, resume course to bug-free land.

Meaning?

Meaning that I hope we'll solve this eventually (sorry, I thought I was being clear _and_ funny, neither was true). Might take a while though, because with a difficult-to-reproduce bug like this.

Backtrace:
0: /usr/bin/Xorg(xorg_backtrace+0x26) [0x4e7a26]
1: /usr/bin/Xorg(xf86SigHandler+0x39) [0x47a679]
2: /lib64/libc.so.6 [0x3c05032f90]
3: /usr/bin/Xorg(XkbStringText+0x1c) [0x56711c]
4: /usr/bin/Xorg(XkbWriteXKBGeometry+0x15a) [0x55879a]
5: /usr/bin/Xorg(XkbWriteXKBKeymapForNames+0x5bb) [0x557d1b]
6: /usr/bin/Xorg(XkbDDXLoadKeymapByNames+0x18a) [0x561cba]
7: /usr/bin/Xorg(ProcXkbGetKbdByName+0x3ab) [0x53fb2b]
8: /usr/bin/Xorg(Dispatch+0x364) [0x4468d4]
9: /usr/bin/Xorg(main+0x45d) [0x42cd1d]
10: /lib64/libc.so.6(__libc_start_main+0xe6) [0x3c0501e576]
11: /usr/bin/Xorg [0x42c0f9]

Fatal server error:
Caught signal 11.  Server aborting

*** This bug has been marked as a duplicate of bug 469572 ***