notify-osd crashed with SIGSEGV in stack_notify_handler()

[Steffen Röcker]

Binary package hint: notify-osd

crashed a few minutes after boot.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Thu Sep 24 14:18:52 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/notify-osd/notify-osd
GtkTheme: Shiki-Wise
IconTheme: gnome-wise
Package: notify-osd 0.9.21-0ubuntu3
ProcCmdLine: root=UUID=7cfdd4fc-6aab-4bd1-8bb5-5e1e2827aa45 ro quiet splash
ProcCmdline: /usr/lib/notify-osd/notify-osd
ProcEnviron:
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.35-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu5
 libgl1-mesa-glx 7.7.0~git20090923.20e77382-0ubuntu0tormod
 libdrm2 2.4.14-0ubuntu0tormod
 xserver-xorg-video-intel 2:2.8.99.902~git20090923.a92bbcc9-0ubuntu0tormod
 xserver-xorg-video-ati 1:6.12.99+git20090920.97a4e747-0ubuntu0tormod
SegvAnalysis:
 Segfault happened at: 0x41f169 <stack_notify_handler+2761>: cmpq $0x40,(%rax)
 PC (0x0041f169) ok
 source "$0x40" ok
 destination "(%rax)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: notify-osd
StacktraceTop:
 stack_notify_handler ()
 dbus_glib_marshal_stack_VOID__STRING_UINT_STRING_STRING_STRING_BOXED_BOXED_INT_POINTER ()
 ?? () from /usr/lib/libdbus-glib-1.so.2
 ?? () from /usr/lib/libdbus-glib-1.so.2
 ?? () from /lib/libdbus-1.so.3
Title: notify-osd crashed with SIGSEGV in stack_notify_handler()
Uname: Linux 2.6.31-10-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare video
WindowManager: metacity
dmi.bios.date: 09/25/2006
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.30
dmi.board.asset.tag: 00000000
dmi.board.name: 939Dual-SATA2
dmi.board.version: 1.00
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.30:bd09/25/2006:svn:pn939Dual-SATA2:pvr1.00:rvn:rn939Dual-SATA2:rvr1.00:
dmi.product.name: 939Dual-SATA2
dmi.product.version: 1.00

[Apport retracing service (apport)]

StacktraceTop:stack_notify_handler ()
dbus_glib_marshal_stack_VOID__STRING_UINT_STRING_STRING_STRING_BOXED_BOXED_INT_POINTER ()
invoke_object_method (object=0x7edd40,
gobject_message_function (
_dbus_object_tree_dispatch_and_unlock (

[Mirco Müller (macslow)]

The upcoming 0.9.22 release of notify-osd fixes those.

[Glauco (glauco-hass)]

The fix already is in the repositories? The update I had early today caused the bug, but the updates released some minutes ago didn't fixed it.
Related packages version in my pc:
notify-osd 0.9.21-0ubuntu3
notify-osd-icons 0.1

[Glauco (glauco-hass)]

Sorry, I opened the page and didn't noted the comment #4.

[Ramiro Queso (rqueso)]

Posterior al arranque de ubuntu. No es posible configurar red wireless

[Noel J. Bergman (noeljb)]

Good to know that the code is fixed in source control, but isn't it supposed to be Fix Committed until the Fix is actually Released?

[Noel J. Bergman (noeljb)]

Nevermind ... it just hit the repos. I expect that the Janitor will post something soon.

[Mirco Müller (macslow)]

Ramiro, please stick to English here on the comments and bug-reports on launchpad. It's the best common denominator for communicating with people all over the globe. Use Google translate... saves other people some time using it, when they try to read what you wrote :)

Noel, "Fix released" means it's in a released tarball, thus the hands of the desktop people. From my normal point of view, wearing my notify-osd upstream hat, that means released to me. That's why I marked it as such. But it's also true, form a distro-integration point of view, that when the desktop-team uploaded stuff to the build-farm means "Fix released". This fine line I sometimes forget to keep in the back of my head.