gnome-settings-daemon crashed with SIGSEGV in xkl_engine_ensure_vtable_inited()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-settings-daemon (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gnome-settings-
I've tried to change the Ubuntu theme in the System > Preferences > Appareance menu to "New Wave" theme.
The theme change, but it instantelly turn to a native-like theme (wich look like to a very old theme, like the Windows 95 one).
Before changing this theme, i had open OpenOffice Writer, to see if the problem of the menu dark dark text on dark blackground) were resolved (well, it's not... but i had report for ubuntu 10.04 RC1, see : https:/
Only the windows top bar (with the close button on it) is displayed correctly.
Please fin enclosed a screen shot showing the problem.
ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gnome-settings-
ProcVersionSign
Uname: Linux 2.6.32-21-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Tue Jun 8 23:21:25 2010
ExecutablePath: /usr/lib/
LiveMediaBuild: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: /usr/lib/
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f825fd48ea4 <xkl_engine_
PC (0x7f825fd48ea4) ok
source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-
StacktraceTop:
xkl_engine_
xkl_engine_
?? () from /usr/lib/
gkbd_status_
g_closure_invoke ()
Title: gnome-settings-
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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 #546927, 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.