Ubuntu
notify-osd package

notify-osd crashed with SIGSEGV in gdk_cairo_set_source_pixbuf()

Bug #331378 reported by Taylor "Ripps" LeMasurier-Wren on 2009-02-19

This bug report is a duplicate of: Bug #332042: notify-osd crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED(). Edit Remove

14

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	notify-osd (Ubuntu)	Triaged	Medium	Mirco Müller

Bug Description

Binary package hint: notify-osd

Crashed after I recieved an email with evolution.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/notify-osd/notify-osd
Package: notify-osd 0.8-0ubuntu3
ProcCmdline: /usr/lib/notify-osd/notify-osd
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: notify-osd
StacktraceTop:
gdk_cairo_set_source_pixbuf ()
?? ()
?? ()
?? () from /usr/lib/libgtk-x11-2.0.so.0
g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
Title: notify-osd crashed with SIGSEGV in gdk_cairo_set_source_pixbuf()
Uname: Linux 2.6.28-8-generic i686
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare scanner tape video

Tags:

Revision history for this message

Taylor "Ripps" LeMasurier-Wren (ripps818) wrote on 2009-02-19:

#1

Dependencies.txt Edit (2.6 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.0 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (24.5 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (799 bytes, text/plain; charset="utf-8")
Registers.txt Edit (500 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (1.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-02-19: Symbolic stack trace

#2

Stacktrace.txt (retraced) Edit (3.6 KiB, text/plain)

StacktraceTop:gdk_cairo_set_source_pixbuf ()
?? ()
?? ()
?? () from /usr/lib/libgtk-x11-2.0.so.0
IA__g_closure_invoke (closure=0x8c07850,

Revision history for this message

Apport retracing service (apport) wrote on 2009-02-19: Symbolic threaded stack trace

#3

ThreadStacktrace.txt (retraced) Edit (3.6 KiB, text/plain)

Revision history for this message

Daniel Holbach (dholbach) wrote on 2009-02-19:

#4

Happened to me too, no evolution notification - no idea what happened.

Revision history for this message

Alexander Sack (asac) wrote on 2009-02-19:

#5

opening up bug. stacktrace looks usable -> triaged.

Changed in notify-osd:
assignee:	nobody → macslow
importance:	Undecided → Medium
status:	New → Triaged

Revision history for this message

Alexander Sack (asac) wrote on 2009-02-19:

#6

I looked at the code and notify-osd seems not to disconnect any signal handlers anywhere ...

Revision history for this message

Alexander Sack (asac) wrote on 2009-02-22:

#7

this is a duplicate of bug 332042 which as a better backtrace. Lets continue there.

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #332042 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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