3.4.0 : nautilus assert failure: nautilus: ../../src/xcb_io.c :528 : _XAllocID: L'assertion « ret != inval_id » failed.

Bug #969824 reported by dino99 on 2012-03-31
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Undecided
Unassigned

Bug Description

new crash on Precise i386 beta2 logged as gnome-classic

similar older crashes are reported as bug #507062

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.4.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-21.34pre201203300400-generic-pae 3.2.13
Uname: Linux 3.2.0-21-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 2.0-0ubuntu1
Architecture: i386
AssertionMessage: nautilus: ../../src/xcb_io.c :528 : _XAllocID: L'assertion « ret != inval_id » a échoué.
Date: Fri Mar 30 20:14:54 2012
ExecutablePath: /usr/bin/nautilus
ProcCmdline: nautilus -n
ProcCwd: /home/oem
Signal: 6
SourcePackage: nautilus
Title: nautilus assert failure: nautilus: ../../src/xcb_io.c :528 : _XAllocID: L'assertion « ret != inval_id » a échoué.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio avahi avahi-autoipd boinc cdrom couchdb crontab daemon debian-tor dialout disk fuse haldaemon klog kmem libuuid lpadmin mail messagebus mlocate mysql mythtv netdev ntp operator plugdev polkituser powerdev pulse root sambashare saned scanner shadow ssh ssl-cert sudo syslog tty users utmp vboxusers video voice whoopsie www-data

dino99 (9d9) wrote :
visibility: private → public

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #955907, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-i386-retrace
dino99 (9d9) wrote :

Still the same problem : as the master report is "private", how to know if this one is really a dupe or not ? and how to follow its activity ?
 This "private" status is a madness, only the "private" data inside the bug report should be hidden because of the "private" data, but not the whole report.

Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 507062, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers