nautilus crashed with signal 5 in _XError()

[Artur Rona]

Binary package hint: nautilus

Nautilus has been crashed by extract file from file-roller. Bug is related to bug #389888.

ProblemType: Crash
Architecture: i386
Date: Mon Jul 27 12:09:29 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: nvidia
Package: nautilus 1:2.27.4-0ubuntu2
ProcCmdline: nautilus
ProcEnviron:
 PATH=(custom, user)
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.30-10.12-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
 _XEventsQueued () from /usr/lib/libX11.so.6
 _XFlush () from /usr/lib/libX11.so.6
Title: nautilus crashed with signal 5 in _XError()
Uname: Linux 2.6.30-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:gdk_x_error (display=0x9869290, error=0xbfaa4a3c)
_XError (dpy=0x9869290, rep=0x9fd07d8)
process_responses (dpy=0x9869290,
_XEventsQueued (dpy=0x9869290, mode=1)
_XFlush (dpy=0x9869290) at ../../src/xcb_io.c:351

[Artur Rona (ari-tczew)]

(gnome-settings-daemon:3212): Gdk-CRITICAL **: gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(nautilus:3300): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed

(nautilus:3300): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed

Gdk-ERROR **: The program 'nautilus' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAtom (invalid Atom parameter)'.
  (Details: serial 85809 error_code 5 request_code 24 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
aborting...
Initializing nautilus-open-terminal extension
Nautilus-Share-Message: Called "net usershare info" but it failed: "net usershare" zwrócił błąd 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error No such file or directory
Please ask your system administrator to enable user sharing.

[Artur Rona (ari-tczew)]

** (nautilus:3317): CRITICAL **: nautilus_file_get_uri: assertion `NAUTILUS_IS_FILE (file)' failed
Initializing nautilus-open-terminal extension
Nautilus-Share-Message: Called "net usershare info" but it failed: "net usershare" zwrócił błąd 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error No such file or directory
Please ask your system administrator to enable user sharing.

[Artur Rona (ari-tczew)]

$ dmesg: [ 2125.962423] nautilus[3317]: segfault at c ip 08119b71 sp bff6e5e0 error 4 in nautilus[8048000+1be000]

[Tormod Volden (tormodvolden)]

There is a debug backtrace in bug #417836.

[Artur Rona (ari-tczew)]

Tormod, please paste here link to your backtrace.

[James Dearing (dearingj)]

I just ran into this bug too. Marking as confirmed.
I'm running Ubuntu Karmic amd64.

[Pedro Villavicencio (pedro)]

could you get a backtrace? just run gdb as:
gdb nautilus 2>&1 | tee nautilus.log
break gdk_x_error
run --sync
thread apply all bt full

[Tormod Volden (tormodvolden)]

I am not able to reproduce in Lucid.

[Artur Rona (ari-tczew)]

As bug #389888 was fixed in karmic, I'm closing this bug because I guess that this bug also has been fixed.

[Saul (creative-balm)]

Using Maverick 10.10 Alpha 3 - crash appeared after using firefox?? Not sure of exact conditions.

[Saul (creative-balm)]

Recurring bug - crash - happen on booting up into desktop after initial switch on.