Ubuntu
notify-osd package

notify-osd crashed after suspend/resume, with SIGSEGV in signal_emit_unlocked_R()

Bug #428849 reported by Andy Whitcroft on 2009-09-13

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

OSD reported crashed following a a resume. I was testing suspend resume and I believe I had resuspended very soon after resume while OSD had boxes up for the network reconnect.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Sun Sep 13 12:28:02 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/notify-osd/notify-osd
GtkTheme: Human
IconTheme: Human
MachineType: Dell Inc. Studio 1537
Package: notify-osd 0.9.21-0ubuntu2
PccardctlIdent:

PccardctlStatus:

ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-10-generic root=UUID=cf503727-25f2-4ecd-b0f3-2b894523bcba ro crashkernel=384M-2G:64M,2G-:128M quiet splash
ProcCmdline: /usr/lib/notify-osd/notify-osd
ProcEnviron:
LANG=en_GB.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: 0x7ff64163f50d <signal_emit_unlocked_R+2413>: mov (%rax),%rax
PC (0x7ff64163f50d) ok
source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: notify-osd
StacktraceTop:
signal_emit_unlocked_R (node=0x11bd8e0, detail=<value optimised out>,
IA__g_signal_emit_valist (instance=0x11dd020,
IA__g_signal_emit (instance=0x1340dac,
IA__g_closure_invoke (closure=0x1273330,
signal_emit_unlocked_R (node=0x14292c0,
Title: notify-osd crashed with SIGSEGV in signal_emit_unlocked_R()
Uname: Linux 2.6.31-10-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video voice
WindowManager: compiz
dmi.bios.date: 09/22/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A03
dmi.modalias: dmi:bvnDellInc.:bvrA03:bd09/22/2008:svnDellInc.:pnStudio1537:pvrA03:rvnDellInc.:rn:rvrA03:cvnDellInc.:ct8:cvrA03:
dmi.product.name: Studio 1537
dmi.product.version: A03
dmi.sys.vendor: Dell Inc.

Tags:

Revision history for this message

Andy Whitcroft (apw) wrote on 2009-09-13:

BootDmesg.txt Edit (50.4 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (60.7 KiB, text/plain; charset="utf-8")
Lsmod.txt Edit (2.8 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (15.3 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (800 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.4 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (108.5 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (213.3 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (1.7 KiB, text/plain; charset="utf-8")
XorgLog.gz Edit (8.3 KiB, application/x-gzip)
XorgLogOld.gz Edit (7.0 KiB, application/x-gzip)
Xrandr.txt Edit (11.0 KiB, text/plain; charset="utf-8")
glxinfo.txt Edit (16.6 KiB, text/plain; charset="utf-8")
monitors.xml.txt Edit (1.8 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (46.8 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-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 #428026, 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.