notify-osd crashed with SIGSEGV in g_variant_unref()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
notify-osd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
normal boot
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: notify-osd 0.9.32-0ubuntu2
ProcVersionSign
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
Date: Wed Aug 24 19:46:37 2011
ExecutablePath: /usr/lib/
GtkTheme: Ambiance
IconTheme: ubuntu-mono-dark
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: LENOVO 3626WNQ
ProcCmdline: /usr/lib/
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
xserver-xorg 1:7.6+7ubuntu6
libgl1-mesa-glx 7.11-0ubuntu3
libdrm2 2.4.26-1ubuntu1
xserver-
xserver-
SegvAnalysis:
Segfault happened at: 0x7f5724c934e9 <g_variant_
PC (0x7f5724c934e9) ok
source "%eax" ok
destination "0x24(%rdi)" (0x00000024) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: notify-osd
StacktraceTop:
g_variant_unref () from /lib/x86_
g_settings_
?? ()
?? ()
g_object_newv () from /usr/lib/
Title: notify-osd crashed with SIGSEGV in g_variant_unref()
UdevDb: Error: [Errno 2] No such file or directory
UpgradeStatus: Upgraded to oneiric on 2011-08-23 (5 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
WindowManager: No value set for `/desktop/
dmi.bios.date: 12/17/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6QET62WW (1.32 )
dmi.board.name: 3626WNQ
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 3626WNQ
dmi.product.
dmi.sys.vendor: LENOVO
glxinfo: Error: [Errno 2] No such file or directory
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 #835082, 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.