notify-osd crashed with SIGSEGV in stack_notify_handler()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
notify-osd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: notify-osd
notify-osd crashed with SIGSEGV in stack_notify_
ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Thu Sep 24 16:43:38 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/
GtkTheme: Human
IconTheme: Human
Lsusb:
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
MachineType: System manufacturer System Product Name
NonfreeKernelMo
Package: notify-osd 0.9.21-0ubuntu3
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /usr/lib/
ProcEnviron:
LANG=ru_RU.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: 0x41f169 <stack_
PC (0x0041f169) ok
source "$0x40" ok
destination "(%rax)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: notify-osd
StacktraceTop:
stack_
dbus_glib_
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /lib/libdbus-1.so.3
Title: notify-osd crashed with SIGSEGV in stack_notify_
Uname: Linux 2.6.31-10-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
WindowManager: metacity
dmi.bios.date: 03/07/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS M2N-SLI DELUXE ACPI BIOS Revision 1405
dmi.board.name: M2N-SLI DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
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.