Ubuntu
notify-osd package

notify-osd crashed with SIGSEGV in g_signal_emit_valist()

Bug #428114 reported by Andres Monroy-Hernandez on 2009-09-11

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

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	notify-osd (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: notify-osd

it happened out of the blue

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Fri Sep 11 17:13:28 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/notify-osd/notify-osd
GtkTheme: Shiki-Human
IconTheme: gnome-human
MachineType: LENOVO 64771ZU
Package: notify-osd 0.9.21-0ubuntu2
PccardctlIdent:

PccardctlStatus:

ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-10-generic root=UUID=e6e8ef1b-5e44-4d5c-b28a-7afbf11f009f ro quiet splash
ProcCmdline: /usr/lib/notify-osd/notify-osd
ProcEnviron:
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.7.0~git20090910.18882f4d-0ubuntu0tormod
libdrm2 2.4.13-1ubuntu1
xserver-xorg-video-intel 2:2.8.99.901~git20090909.efbcf29d-0ubuntu0tormod
xserver-xorg-video-ati 1:6.12.99+git20090910.a88f60e7-0ubuntu0tormod
SegvAnalysis:
Segfault happened at: 0x7cc776: mov (%eax),%eax
PC (0x007cc776) ok
source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: notify-osd
StacktraceTop:
?? () from /usr/lib/libgobject-2.0.so.0
g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
g_signal_emit () from /usr/lib/libgobject-2.0.so.0
?? ()
g_cclosure_marshal_VOID__VOID ()
Title: notify-osd crashed with SIGSEGV in g_signal_emit_valist()
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
WindowManager: compiz
dmi.bios.date: 09/01/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 7TET34WW (1.08 )
dmi.board.name: 64771ZU
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7TET34WW(1.08):bd09/01/2008:svnLENOVO:pn64771ZU:pvrThinkPadX300:rvnLENOVO:rn64771ZU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 64771ZU
dmi.product.version: ThinkPad X300
dmi.sys.vendor: LENOVO

Tags:

Revision history for this message

Andres Monroy-Hernandez (andresmh) wrote on 2009-09-11:

BootDmesg.txt Edit (52.6 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (36.2 KiB, text/plain; charset="utf-8")
Lsmod.txt Edit (3.2 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (12.3 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (666 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.3 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (93.9 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (221.8 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (1.1 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (113.5 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (126.3 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (6.7 KiB, text/plain; charset="utf-8")
glxinfo.txt Edit (16.7 KiB, text/plain; charset="utf-8")
monitors.xml.txt Edit (2.3 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (51.2 KiB, text/plain; charset="utf-8")
xdpyinfo.txt Edit (19.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-09-12: This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #428302, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.