Ubuntu
notify-osd package

notify-osd crashed with SIGSEGV in stack_notify_handler()

Bug #435941 reported by cos_porcos on 2009-09-24

This bug report is a duplicate of: Bug #435848: notify-osd crashed with SIGSEGV in stack_notify_handler(). 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

while trying to turn the volume up app crashed

ProblemType: Crash
Architecture: i386
Date: Thu Sep 24 15:31:35 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/notify-osd/notify-osd
GtkTheme: DarkRoom
IconTheme: Human
Lsusb:
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 03f0:0901 Hewlett-Packard ScanJet 2300c
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VIA Technologies, Inc. P4M266-8235
NonfreeKernelModules: nvidia
Package: notify-osd 0.9.21-0ubuntu3
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-10-generic root=UUID=43d1b464-d10a-44c8-a1ed-c486b4adf1c6 ro quiet splash
ProcCmdline: /usr/lib/notify-osd/notify-osd
ProcEnviron:
LANGUAGE=pt_PT.UTF-8
LANG=pt_PT.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.35-generic
RelatedPackageVersions:
xserver-xorg 1:7.4+3ubuntu5
libgl1-mesa-glx 7.6.0~git20090817.7c422387-0ubuntu5
libdrm2 2.4.13-1ubuntu1
xserver-xorg-video-intel 2:2.8.1-1ubuntu1
xserver-xorg-video-ati 1:6.12.99+git20090825.fc74e119-0ubuntu2
SegvAnalysis:
Segfault happened at: 0x8065164 <stack_notify_handler+3060>: cmpl $0x40,(%esi)
PC (0x08065164) ok
source "$0x40" ok
destination "(%esi)" (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 i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
WindowManager: metacity
dmi.bios.date: 09/01/2004
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: P4M266-8235
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/01/2004:svnVIATechnologies,Inc.:pnP4M266-8235:pvr:rvn:rnP4M266-8235:rvr:cvn:ct3:cvr:
dmi.product.name: P4M266-8235
dmi.sys.vendor: VIA Technologies, Inc.

Tags:

Revision history for this message

cos_porcos (bruno-guerreiro2) wrote on 2009-09-24:

BootDmesg.txt Edit (31.7 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (653 bytes, text/plain; charset="utf-8")
Lsmod.txt Edit (1.9 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (7.2 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (466 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1018 bytes, text/plain; charset="utf-8")
ProcModules.txt Edit (1.9 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (71.6 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (157.9 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (251 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (12.3 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (12.7 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (6.2 KiB, text/plain; charset="utf-8")
glxinfo.txt Edit (10.6 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (46.8 KiB, text/plain; charset="utf-8")
xdpyinfo.txt Edit (13.4 KiB, text/plain; charset="utf-8")

Revision history for this message

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