notify-osd crashed after suspend/resume, with SIGSEGV in signal_emit_unlocked_R()
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/
GtkTheme: Human
IconTheme: Human
MachineType: Dell Inc. Studio 1537
Package: notify-osd 0.9.21-0ubuntu2
PccardctlIdent:
PccardctlStatus:
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /usr/lib/
ProcEnviron:
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcVersionSign
RelatedPackageV
xserver-xorg 1:7.4+3ubuntu5
libgl1-mesa-glx 7.6.0~git200908
libdrm2 2.4.13-1ubuntu1
xserver-
xserver-
SegvAnalysis:
Segfault happened at: 0x7ff64163f50d <signal_
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_
IA__g_
IA__g_signal_emit (instance=
IA__g_
signal_
Title: notify-osd crashed with SIGSEGV in signal_
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.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Studio 1537
dmi.product.
dmi.sys.vendor: Dell Inc.
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.