notify-osd crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()

Bug #427924 reported by wavded
924
This bug affects 178 people
Affects Status Importance Assigned to Milestone
notify-osd (Ubuntu)
Fix Released
Medium
Mirco Müller

Bug Description

Binary package hint: notify-osd

after updates from today

ProblemType: Crash
Architecture: i386
Date: Fri Sep 11 10:00:31 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/notify-osd/notify-osd
GtkTheme: chrome-like
IconTheme: Breathe
MachineType: Dell Inc. MXG061
NonfreeKernelModules: nvidia
Package: notify-osd 0.9.21-0ubuntu2
PccardctlIdent:

PccardctlStatus:

ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-10-generic root=UUID=ff93bc52-ac41-4c9c-86ea-2601bf01065d ro quiet splash
ProcCmdline: /usr/lib/notify-osd/notify-osd
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.32-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu5
 libgl1-mesa-glx 7.6.0~git20090817.7c422387-0ubuntu3
 libdrm2 2.4.13-1ubuntu1
 xserver-xorg-video-intel 2:2.8.1-1ubuntu1
 xserver-xorg-video-ati 1:6.12.99+git20090825.fc74e119-0ubuntu1
SegvAnalysis: Failure: Unknown offset literal: *%esi
Signal: 11
SourcePackage: notify-osd
StacktraceTop:
 g_cclosure_marshal_VOID__VOID ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
Title: notify-osd crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
WindowManager: metacity
dmi.bios.date: 04/02/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0CF456
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/02/2007:svnDellInc.:pnMXG061:pvr:rvnDellInc.:rn0CF456:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: MXG061
dmi.sys.vendor: Dell Inc.

Revision history for this message
wavded (wavded) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:IA__g_cclosure_marshal_VOID__VOID (closure=0x8db1098,
g_type_class_meta_marshal (closure=0x8db1098,
IA__g_closure_invoke (closure=0x8db1098, return_value=0x0,
signal_emit_unlocked_R (node=<value optimized out>,
IA__g_signal_emit_valist (instance=0x8dc9528,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in notify-osd (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Simon Déziel (sdeziel)
Changed in notify-osd (Ubuntu):
status: New → Confirmed
Changed in notify-osd (Ubuntu):
importance: Medium → High
assignee: nobody → Mirco Müller (macslow)
importance: High → Medium
Changed in notify-osd:
assignee: nobody → Mirco Müller (macslow)
David Barth (dbarth)
Changed in notify-osd:
importance: Undecided → Critical
milestone: none → ubuntu-9.10-beta-freeze
David Barth (dbarth)
Changed in notify-osd:
status: New → In Progress
Revision history for this message
DougEdey (doug-edey) wrote :

No idea what caused this I'm afraid, I went down the pub and came back to find apport calling my attention

Revision history for this message
Abdiel (abdiel) wrote :

same problem, with me it happened when my wireless stopped working for a second, then the 'connected' OSD notice came up, then apport came up and asked me to file a bug

Revision history for this message
James Lewis (james-fsck) wrote :

<AOL>me too</AOL>

This has happened for me since Alpha5 with a bunch of updates, but I've just seen it happen in a completely fresh, patched install of Alpha6

There doesn't seem to be a cause as such, the only things I had open at the time was 3 gnome-terminals and gtkevemon, none of which send any notifications.

Mirco Müller (macslow)
Changed in notify-osd:
status: In Progress → Fix Committed
Changed in notify-osd (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package notify-osd - 0.9.22-0ubuntu1

---------------
notify-osd (0.9.22-0ubuntu1) karmic; urgency=low

  * New upstream version: notify-osd has been scrutinized thoroughly
    under valgrind to identify all mem-leaks and invalid reads.
    (LP: #427924, #375408, #405364, #378193, #428302)

 -- Sebastien Bacher <email address hidden> Thu, 24 Sep 2009 16:14:59 +0200

Changed in notify-osd (Ubuntu):
status: Fix Committed → Fix Released
David Barth (dbarth)
Changed in notify-osd:
status: Fix Committed → Fix Released
no longer affects: notify-osd
To post a comment you must log in.