Ubuntu
notify-osd package

notify-osd crashed with SIGSEGV in g_signal_emit_valist()

Bug #429577 reported by darkenergy on 2009-09-14

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

happened while i was using amsn and firefox

ProblemType: Crash
Architecture: i386
Date: Mon Sep 14 20:53:53 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/notify-osd/notify-osd
GtkTheme: Dust
IconTheme: Human
Lsusb:
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: MICRO-STAR INT'L CO.,LTD MS-1012
Package: notify-osd 0.9.21-0ubuntu2
PccardctlIdent:
Socket 0:
   no product info available
Socket 1:
   no product info available
PccardctlStatus:
Socket 0:
   no card
Socket 1:
   no card
ProcCmdLine: root=/dev/mapper/secubuntu-system ro quiet splash
ProcCmdline: /usr/lib/notify-osd/notify-osd
ProcEnviron:
PATH=(custom, user)
LANG=de_CH.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:
Segfault happened at: 0xf48776: mov (%eax),%eax
PC (0x00f48776) 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 audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare tape video
WindowManager: gnome-wm
dmi.bios.date: 06/24/2005
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A1012IMS VB.80
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 11
dmi.chassis.vendor: MICRO-STAR INT'L CO.,LTD
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA1012IMSVB.80:bd06/24/2005:svnMICRO-STARINT'LCO.,LTD:pnMS-1012:pvr0121:cvnMICRO-STARINT'LCO.,LTD:ct11:cvrN/A:
dmi.product.name: MS-1012
dmi.product.version: 0121
dmi.sys.vendor: MICRO-STAR INT'L CO.,LTD

Tags:

Revision history for this message

darkenergy (darkenergy) wrote on 2009-09-14:

BootDmesg.txt Edit (40.7 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (3.6 KiB, text/plain; charset="utf-8")
Lsmod.txt Edit (2.6 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (11.0 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (469 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.0 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.7 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (81.7 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (179.1 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (227 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (69.0 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (69.3 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (5.3 KiB, text/plain; charset="utf-8")
glxinfo.txt Edit (16.1 KiB, text/plain; charset="utf-8")
monitors.xml.txt Edit (1.4 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (56.6 KiB, text/plain; charset="utf-8")
xdpyinfo.txt Edit (19.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-09-14: 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.