Bug 670285

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 add drm.debug=0x04 to the kernel command line, restart computer, and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* output of the dmesg command, and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

Also, what is the attachment 473917 [details] about? File says it is " DOS executable (device driver)" ???

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

Thanks in advance.

Created attachment 474054 [details]
messages

Created attachment 474055 [details]
dmesg

Created attachment 474056 [details]
Xorg.0.log

Created attachment 474057 [details]
Xorg.2.log

Created attachment 474058 [details]
xorg.conf

(In reply to comment #1)
> 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 add drm.debug=0x04 to the kernel command line, restart computer, and
> attach
drm.debug=0x04 gave a a crazy graphics mode, so I use drm.debug=14

> * your X server config file (/etc/X11/xorg.conf, if available),
> * X server log file (/var/log/Xorg.*.log)
> * output of the dmesg command, and
> * system log (/var/log/messages)
> 
> to the bug report as individual uncompressed file attachments using the
> bugzilla file attachment link above.
> 
> Also, what is the attachment 473917 [details] about? File says it is " DOS executable
> (device driver)" ???

What do you mean ?
Where is it ?

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

(In reply to comment #7)
> > Also, what is the attachment 473917 [details] about? File says it is " DOS executable
> > (device driver)" ???
> 
> What do you mean ?
> Where is it ?

Attached to the original description of this bug (and see "The name are as recommeneded" attachment in the above table "Attachments").

(In reply to comment #8)
> (In reply to comment #7)
> > > Also, what is the attachment 473917 [details] about? File says it is " DOS executable
> > > (device driver)" ???
> > 
> > What do you mean ?
> > Where is it ?
> 
> Attached to the original description of this bug (and see "The name are as
> recommeneded" attachment in the above table "Attachments").

I probably did not attached the files right.
I guess that the new attachments are OK.

Here 2 outputs due to the crash

(npviewer.bin:16636): Gdk-WARNING **: XID collision, trouble ahead

(npviewer.bin:16636): Gdk-WARNING **: XID collision, trouble ahead

(npviewer.bin:16636): Gdk-WARNING **: XID collision, trouble ahead

(npviewer.bin:16636): Gdk-WARNING **: XID collision, trouble ahead

(gnome-screensaver:14072): GdkPixbuf-CRITICAL **: gdk_pixbuf_format_get_name: assertion `format != NULL' failed

(gnome-screensaver:14072): GdkPixbuf-CRITICAL **: gdk_pixbuf_format_get_name: assertion `format != NULL' failed

(gnome-screensaver:14072): GdkPixbuf-CRITICAL **: gdk_pixbuf_format_get_name: assertion `format != NULL' failed

Backtrace:
0: /usr/bin/X (xorg_backtrace+0x28) [0x460d18]
1: /usr/bin/X (0x400000+0x63509) [0x463509]
2: /lib64/libc.so.6 (0x3cd3a00000+0x32970) [0x3cd3a32970]
3: /usr/lib64/libpixman-1.so.0 (pixman_region_intersect+0xa1) [0x3cdf213711]
4: /usr/bin/X (miDoCopy+0x21a) [0x535bda]
5: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7f58074c0000+0x39fe0) [0x7f58074f9fe0]
6: /usr/bin/X (0x400000+0xd3008) [0x4d3008]
7: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7f58074c0000+0x35bc2) [0x7f58074f5bc2]
8: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7f58074c0000+0x36879) [0x7f58074f6879]
9: /usr/lib64/libdrm.so.2 (drmHandleEvent+0x103) [0x3ce7a067c3]
10: /usr/bin/X (WakeupHandler+0x4b) [0x443ffb]
11: /usr/bin/X (WaitForSomething+0x1d7) [0x460457]
12: /usr/bin/X (0x400000+0x2d8f2) [0x42d8f2]
13: /usr/bin/X (0x400000+0x2189a) [0x42189a]
14: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x3cd3a1ec5d]
15: /usr/bin/X (0x400000+0x21449) [0x421449]
Segmentation fault at address 0x319

Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting


Please consult the Fedora Project support
         at http://bodhi.fedoraproject.org/
 for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.

gnome-session: Fatal IO error 104 (Connection reset by peer) on X server :0.0.
xinit:  connection to X server lost.
gnome-screensaver: Fatal IO error 104 (Connection reset by peer) on X server :0.0.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
*** NSPlugin Wrapper *** ERROR: NPP_Destroy() wait for reply: Connection reset by peer
*** NSPlugin Wrapper *** WARNING:(../src/npw-wrapper.c:1858):invoke_NPP_Destroy: assertion failed: (rpc_method_invoke_possible(plugin->connection))

Backtrace:
0: /usr/bin/X (xorg_backtrace+0x28) [0x460d18]
1: /usr/bin/X (0x400000+0x63509) [0x463509]
2: /lib64/libc.so.6 (0x3cd3a00000+0x32970) [0x3cd3a32970]
3: /usr/lib64/libpixman-1.so.0 (pixman_region_intersect+0xa1) [0x3cdf213711]
4: /usr/bin/X (miDoCopy+0x21a) [0x535bda]
5: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7f4589857000+0x39fe0) [0x7f4589890fe0]
6: /usr/bin/X (0x400000+0xd3008) [0x4d3008]
7: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7f4589857000+0x35bc2) [0x7f458988cbc2]
8: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7f4589857000+0x36879) [0x7f458988d879]
9: /usr/lib64/libdrm.so.2 (drmHandleEvent+0x103) [0x3ce7a067c3]
10: /usr/bin/X (WakeupHandler+0x4b) [0x443ffb]
11: /usr/bin/X (WaitForSomething+0x1d7) [0x460457]
12: /usr/bin/X (0x400000+0x2d8f2) [0x42d8f2]
13: /usr/bin/X (0x400000+0x2189a) [0x42189a]
14: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x3cd3a1ec5d]
15: /usr/bin/X (0x400000+0x21449) [0x421449]
Segmentation fault at address 0xa9

Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting


Please consult the Fedora Project support
         at http://bodhi.fedoraproject.org/
 for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.

gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
Window manager warning: Fatal IO error 11 (Resource temporarily unavailable) on display ':0.0'.
gnome-settings-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
gpk-update-icon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
nautilus: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
seapplet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
evolution-alarm-notify: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
xinit:  connection to X server lost.
gnome-panel: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
gnome-screensaver: Fatal IO error 104 (Connection reset by peer) on X server :0.0.
polkit-gnome-authentication-agent-1: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
abrt-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
      after 33 requests (33 known processed) with 0 events remaining.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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

Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.