nautilus crashed in background

Bug #468530 reported by Paul Meigniez
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Incomplete
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: nautilus

Nautilus crashed when it was inactive in the background...

ProblemType: Crash
Architecture: i386
AssertionMessage: nautilus: ../../src/xcb_io.c :378 : _XAllocID: L'assertion « ret != inval_id » a échoué.
Date: Sun Nov 1 13:51:46 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.28.1-0ubuntu1
ProcCmdline: nautilus --no-desktop --browser
ProcEnviron:
 PATH=(custom, user)
 LANG=fr_CH.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
Signal: 6
SourcePackage: nautilus
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 __assert_fail () from /lib/tls/i686/cmov/libc.so.6
 _XAllocID () from /usr/lib/libX11.so.6
Title: nautilus assert failure: nautilus: ../../src/xcb_io.c :378 : _XAllocID: L'assertion « ret != inval_id » a échoué.
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare video

Revision history for this message
Paul Meigniez (meigniez) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

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

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
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.

Changed in nautilus (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
status: New → Incomplete
Revision history for this message
Paul Meigniez (meigniez) wrote :

No, it has not been reproduced. The automatic bug report has proposed me to send this bug and I accept it. That's all. What was very strange is that I'm not sure what I was doing but I'm sure I didn't use Nautilus explicitely.

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.