nautilus assert failure: nautilus: ../../src/xcb_io.c:385: _XAllocID: Asserzione \"ret != inval_id\" non riuscita.

Bug #633624 reported by CcC
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

Binary package hint: nautilus

error when started the operative system

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: nautilus 1:2.31.90-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Uname: Linux 2.6.35-20-generic i686
Architecture: i386
AssertionMessage: nautilus: ../../src/xcb_io.c:385: _XAllocID: Asserzione \"ret != inval_id\" non riuscita.
CheckboxSubmission: d377122429099894f761365efb5586ea
CheckboxSystem: b8f3ec504801f13fc208edb5c785b099
CrashCounter: 1
Date: Thu Sep 9 01:03:59 2010
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: nautilus
ProcEnviron:
 PATH=(custom, user)
 LANG=it_IT.utf8
 SHELL=/bin/bash
Signal: 6
SourcePackage: nautilus
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/libc.so.6
 abort () from /lib/libc.so.6
 __assert_fail () from /lib/libc.so.6
 _XAllocID () from /usr/lib/libX11.so.6
Title: nautilus assert failure: nautilus: ../../src/xcb_io.c:385: _XAllocID: Asserzione \"ret != inval_id\" non riuscita.
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (bluetooth-applet:1534): Gtk-CRITICAL **: IA__gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed
 (polkit-gnome-authentication-agent-1:1543): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (awn-applet:1594): Gdk-WARNING **: XID collision, trouble ahead
 (dropbox:1557): Gdk-CRITICAL **: IA__gdk_window_thaw_toplevel_updates_libgtk_only: assertion `private->update_and_descendants_freeze_count > 0' failed
 (nautilus:1547): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

Revision history for this message
CcC (canicacurri) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __kernel_vsyscall ()
 *__GI_raise (sig=6)
 *__GI_abort () at abort.c:92
 *__GI___assert_fail (assertion=0xf7c4e5 "ret != inval_id",
 _XAllocID (dpy=0x94621c0) at ../../src/xcb_io.c:385

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.
This will help us to find and resolve the problem.

visibility: private → public
Changed in nautilus (Ubuntu):
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.