nautilus crashed with signal 5 in _XError()

[Mark Sobell]

Binary package hint: nautilus

Run on virtual machine (vmw).
Nautilus crashed as the system came up from a reboot.

ProblemType: Crash
Architecture: i386
Date: Fri Feb 26 13:29:37 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100224.1)
Package: nautilus 1:2.29.91-0ubuntu1
ProcCmdline: nautilus
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
Signal: 5
SourcePackage: nautilus
StacktraceTop:
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 _XError () from /usr/lib/libX11.so.6
 ?? () from /usr/lib/libX11.so.6
 _XReadEvents () from /usr/lib/libX11.so.6
 XIfEvent () from /usr/lib/libX11.so.6
Title: nautilus crashed with signal 5 in _XError()
Uname: Linux 2.6.32-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1098): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-power-manager:1105): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed
 (bluetooth-applet:1104): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed

[Apport retracing service (apport)]

StacktraceTop:
 gdk_x_error (display=0x8a85ee0, error=0xbff77c1c)
 _XError (dpy=0x8a85ee0, rep=0x8c0ce40)
 process_responses (dpy=0x8a85ee0,
 _XReadEvents (dpy=0x8a85ee0) at ../../src/xcb_io.c:279
 XIfEvent (dpy=0x8a85ee0, event=0xbff77dbc,

[Pedro Villavicencio (pedro)]

Thanks for the report, could you run nautilus as:

gdb nautilus
break gdk_x_error
run --sync

reproduce the crash and after that
thread apply all bt full

and attach the resulting output as a file to the report, thanks in advance.

[Mark Sobell (mark-sobell)]

I am running an up-to-date A3 and the problem no longer occurs.
I will report back if I see it again.
Thanks!

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.