johnaman, are you sure that's the same bug?
Debug backtrace from your crash file:
131 if (value->type == GCONF_VALUE_INT)
(gdb) bt
#0 def_group_in_gconf_changed (client=0x8067360, cnxn_id=4294967295,
entry=0x81e8a98, dialog=0x806a380)
at
/build/buildd/control-center-2.16.1/./capplets/keyboard/gnome-keyboard-properties-xkblt.c:131
#1 0x080526c1 in xkb_layouts_fill_selected_tree (dialog=0x806a380)
at
/build/buildd/control-center-2.16.1/./capplets/keyboard/gnome-keyboard-properties-xkblt.c:386
#2 0x080508b9 in setup_xkb_tabs (dialog=0x806a380, changeset=0x0)
at
/build/buildd/control-center-2.16.1/./capplets/keyboard/gnome-keyboard-properties-xkb.c:183
#3 0x0805012e in main (argc=Cannot access memory at address 0x0
) at
/build/buildd/control-center-2.16.1/./capplets/keyboard/gnome-keyboard-properties.c:172
#4 0xb77e68cc in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
It matches upstream http://bugzilla.gnome.org/show_bug.cgi?id=370038
which is a libxklavier bug according to upstream
--
Keyboard Properties launch bug
https://launchpad.net/bugs/64516
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
