notify-osd crashed 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
ProblemType: Crash
Architecture: i386
Date: Thu Sep 17 16:12:53 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/
GtkTheme: UbuntuStudio
IconTheme: UbuntuStudio
MachineType: PACKARD BELL BV EasyNote_SJ51
NonfreeKernelMo
Package: notify-osd 0.9.21-0ubuntu2
ProcCmdLine: root=UUID=
ProcCmdline: /usr/lib/
ProcEnviron:
PATH=(custom, user)
LANG=en_US.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: 0x1e0776 <signal_
PC (0x001e0776) 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:
signal_
IA__g_
IA__g_signal_emit (instance=
bubble_timed_out ()
g_timeout_dispatch (source=0x827a320, callback=0,
Title: notify-osd crashed with SIGSEGV in signal_
UdevDb: Error: [Errno 2] No such file or directory
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare scanner tape video
WindowManager: metacity
dmi.bios.date: 09/13/2007
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 1.0E-3221-0010
dmi.board.name: EasyNote_SJ51
dmi.board.vendor: PACKARD BELL BV
dmi.board.version: REFERENCE
dmi.chassis.type: 3
dmi.chassis.vendor: PACKARD BELL BV
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: EasyNote_SJ51
dmi.product.
dmi.sys.vendor: PACKARD BELL BV
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 #430291, 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.