notify-osd crashed with SIGSEGV in g_signal_emit_valist()
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 g_signal_
ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sat Sep 12 11:27:19 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/
GtkTheme: Human
IconTheme: Human
MachineType: ASUSTeK Computer Inc. K50IJ
Package: notify-osd 0.9.21-0ubuntu2
PccardctlIdent:
PccardctlStatus:
ProcCmdLine: root=UUID=
ProcCmdline: /usr/lib/
ProcEnviron:
LANG=uk_UA.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: 0x247776: mov (%eax),%eax
PC (0x00247776) 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:
?? () from /usr/lib/
g_signal_
g_signal_emit () from /usr/lib/
?? ()
g_cclosure_
Title: notify-osd crashed with SIGSEGV in g_signal_
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
WindowManager: gnome-wm
dmi.bios.date: 05/08/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 207
dmi.board.
dmi.board.name: K50IJ
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: K50IJ
dmi.product.
dmi.sys.vendor: ASUSTeK Computer 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 #428302, 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.