libxcb

notify-osd crashed with SIGSEGV in malloc() while getting a message in empathy

Bug #346257 reported by Justin C
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libxcb
New
Undecided
Unassigned
notify-osd (Ubuntu)
Invalid
Low
Mirco Müller

Bug Description

Binary package hint: notify-osd

Crash while getting a empathy message.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/notify-osd/notify-osd
Package: notify-osd 0.9.6-0ubuntu2
ProcCmdline: /usr/lib/notify-osd/notify-osd
ProcEnviron:
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: notify-osd
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 malloc () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /usr/lib/libxcb.so.1
 xcb_poll_for_event () from /usr/lib/libxcb.so.1
 ?? () from /usr/lib/libX11.so.6
Title: notify-osd crashed with SIGSEGV in malloc()
Uname: Linux 2.6.28-8-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Justin C (jlathian-deactivatedaccount) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:_int_malloc (av=0xb77eb140, bytes=8) at malloc.c:4202
*__GI___libc_malloc (bytes=8) at malloc.c:3551
_xcb_in_read (c=0x9a2d0a0)
xcb_poll_for_event (c=0x9a2d0a0)
wait_or_poll_for_event (dpy=0x9a2cb60, wait=176177072)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in notify-osd:
importance: Undecided → Medium
Sebastien Bacher (seb128)
visibility: private → public
Rick Spencer (rick-rickspencer3)
Changed in notify-osd (Ubuntu):
assignee: nobody → macslow
David Barth (dbarth)
Changed in notify-osd:
importance: Medium → High
Revision history for this message
Mirco Müller (macslow) wrote :

Greetings Justin! Can you please try the latest notify-osd release 0.9.9 and see if you still get this crash?

Revision history for this message
Mirco Müller (macslow) wrote :

Right now I'm using empathy with notify-osd 0.9.9 running and have not been able to get a crash yet. Looking at the stacktrace it's gtk->glib->xlib->xcb->libc (some memory allocation in xcb failing) and it does not seem to be happening in notify-osd itself.

Revision history for this message
Mirco Müller (macslow) wrote :

After a day of running empathy with notify-osd 0.9.9 I've not experienced a single crash. Futhertmore the StackTrace attached to this bug-report clearly shows that the segfault is not happening in notify-osd's code, but rather triggered from xlib/xcb. We linked that as an affected project.

David Barth (dbarth)
Changed in notify-osd (Ubuntu):
importance: High → Low
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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