empathy assert failure: empathy: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed.

Bug #649935 reported by P-ruck
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
empathy (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: empathy

empathy was launched at start-up of metacity

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: empathy 2.31.92-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
AssertionMessage: empathy: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed.
Date: Mon Sep 27 00:19:49 2010
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Beta i386 (20100902.1)
ProcCmdline: empathy
ProcEnviron:
 LANG=de_DE.utf8
 SHELL=/bin/bash
Signal: 6
SourcePackage: empathy
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: empathy assert failure: empathy: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed.
UserGroups: adm admin audio cdrom dialout lpadmin netdev plugdev sambashare video www-data
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1326): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-settings-daemon:1236): GdkPixbuf-CRITICAL **: gdk_pixbuf_format_get_name: assertion `format != NULL' failed
 (gnome-settings-daemon:1236): GdkPixbuf-CRITICAL **: gdk_pixbuf_format_get_name: assertion `format != NULL' failed
 (nautilus:1335): GdkPixbuf-CRITICAL **: gdk_pixbuf_format_get_name: assertion `format != NULL' failed
 (empathy:1323): Core-WARNING **: individual-aggregator.vala:159: Error preparing Backend 'telepathy': Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Revision history for this message
P-ruck (p-ruck) wrote :
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.