vinagre assert failure: vinagre: ../../src/xcb_io.c :385 : _XAllocID: L'assertion « ret != inval_id » a échoué.

Bug #750774 reported by yamo on 2011-04-04
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
vinagre (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: vinagre

Launchpad has not found the duplicates???

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: vinagre 2.30.2-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-28.49-generic 2.6.35.11
Uname: Linux 2.6.35-28-generic i686
Architecture: i386
AssertionMessage: vinagre: ../../src/xcb_io.c :385 : _XAllocID: L'assertion « ret != inval_id » a échoué.
CrashCounter: 1
Date: Mon Apr 4 22:02:42 2011
ExecutablePath: /usr/bin/vinagre
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4)
ProcCmdline: vinagre
ProcEnviron:
 PATH=(custom, user)
 LANG=fr_FR.utf8
 SHELL=/bin/bash
Signal: 6
SourcePackage: vinagre
StacktraceTop:
 __kernel_vsyscall ()
 raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:92
 __assert_fail (assertion=0x39b4e5 "ret != inval_id", file=0x39b4a9 "../../src/xcb_io.c", line=385, function=0x39b664 "_XAllocID") at assert.c:81
 _XAllocID () from /usr/lib/libX11.so.6
Title: vinagre assert failure: vinagre: ../../src/xcb_io.c :385 : _XAllocID: L'assertion « ret != inval_id » a échoué.
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

yamo (stephane-gregoire) wrote :

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #748867, 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.

visibility: private → public
tags: removed: need-i386-retrace
yamo (stephane-gregoire) wrote :

It may be a duplicate of bug #748867.

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

Other bug subscribers