[Expired for gnome-settings-daemon (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Incomplete => Expired
--
gconf2 crashes. No way to activate XKB custom settings
https://bugs.launchpad.net/bugs/545689
You received this bug n
layouts = [aa,hu]
** (gnome-settings-daemon:5841): DEBUG: Starting keyboard manager
Error:Can't find file "aa" for symbols include
Exiting
Abandoning symbols file "(null)"
How did the "aa" get in there? Does it still crash if you reset your gconf
The output of "
gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
echo $GDM_KEYBOARD_LAYOUT
grep ^X /etc/default/console-setup
xprop -root|grep XKB
" script is:
layouts = [aa,hu]
options = []
model =
hu
XKBMODEL="pc105"
XKBLAYOUT="hu"
XKBVARIANT=""
XKBOPTIONS=""
_XKB_RULES_NAMES_
After logging in (without the gconftool workaround in your .bashrc),
please copy&paste the output of
gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
echo $GDM_KEYBOARD_LAYOUT
grep ^X /etc/default/console-setup
xprop -root|grep XKB
Then please do
killall gnome-settings-daemon
g
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Incomplete => New
--
gconf2 crashes. No way to activate XKB custom settings
https://bugs.launchpad.net/bugs/545689
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
I'm using Lucid Lynx. The bug appeared yesterday, after I'd upgraded to current
lucid, and restarted the system.
One hour later I reported this bug, here.
--
gconf2 crashes. No way to activate XKB custom settings
https://bugs.launchpad.net/bugs/545689
You received this bug notification because y
the error is rather a gnome-settings-daemon error than a gconf2 bug,
what ubuntu version do you use and when did you start getting the issue?
** Package changed: gconf2 (Ubuntu) => gnome-settings-daemon (Ubuntu)
** Changed in: gnome-settings-daemon (Ubuntu)
Importance: Undecided => Low
** Ch
