[Breezy] gnome-settings-daemon starts crashing after using keyboard properties capplet

Created an attachment (id=3264)
Content of keyboad directory

Thanks for your bug. Can you get a backtrace of the crash (the bug-buddy dialog
to send the bug upstream has it)?
The usual way to send a gconf config is "gconftool-2 -R
/desktop/gnome/peripherals/keyboard".

Bug-buddy didn't appeared. So no, I don't have a bt.

>The usual way to send a gconf config is "gconftool-2 -R
>/desktop/gnome/peripherals/keyboard".

Thanks for the tip.

how do you know it crashes? Could you attach gdb to it when it try to restart or
start an instance with gdb?

>how do you know it crashes?

I've had the crash window, but not report druid.

>Could you attach gdb to it when it try to restart or
start an instance with gdb?

I'll try that. Pleasee note that you ask me to break my system again :)

I'm having similar problems that I think are related to this bug. I don't get a
crash dialog at all though.

When I delete or add the default us international layout, the theme flashes to
the gtk default and then to my regular theme settings. Switching to any other
layout doesn't seem to work. The dialog updates, but when I try to enable
deadkeys using the layout for it for example, it doesn't actually work.

I attached gdb to the gnome-settings-daemon process, and all it said was:
"Program exited with code 01."

I've deleted the entire /desktop gconf directory before, but it doesn't seem to
help.

(In reply to comment #4)
> how do you know it crashes? Could you attach gdb to it when it try to restart or
> start an instance with gdb?

I have the exact same problem: After modifying the system keyboard properties, window decoration starts going crazy until
after a while, I get the message "gnome-setting-daemon couldn't start" (that's the gist of it). When running gnome-
settings-daemon in a terminal, I get the following:

Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
                  Ignoring extra symbols
Warning: No symbols defined for <SYRQ> (keycode 92)
[...]
Warning: No symbols defined for <I7F> (keycode 255)
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 1580 error_code 2 request_code 145 minor_code 9)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
[1129906626,000,xklavier.c:XklStartListen/] The backend does not require manual layout management - but it is provided
by the application

Complete output attached. I guess this is not a segfault so a gdb backtrace won't be available.

Created an attachment (id=4725)
output of "gnome-settings-daemon --sync >debug.txt 2>&1"

Additional information:
 - This occurs in an unmodified breezy release trying (unsuccessfully) to enable the feature to enter french accents on a
German keyboard.
 - "gconftool-2 --recursive-unset /desktop/gnome/peripherals/keyboard" fixes the problem

Could you try with the packages uploaded to -update for bug #21595 and let we
know if that fixes the issue?

Thanks. The provided .debs are definitely an improvement. gnome-settings-daemon doesn't quit any more. However,

 1) there are still warning messages, repeated many times:

![1129912101,000,xklavier_evt_xkb.c:_XklXkbEventHandler/] ATTENTION! Currently cached group 0 is not equal to the
current group from the event: 1
Warning: No symbols defined for <I7F> (keycode 255)

    the latter for a variety of keycodes.

 2) it is still impossible to activate two-key input of accented French letters (é). This is related to the nodeadkeyes
option which may need to be changed in X-Server configuration. The "dead grave accent" option sounds as though it should
handle this. Selecting this option incidently used to trigger gnome-settings-daemon's crash (before the -update debs).

Thanks for the comment. Could describe what is your configuration (gconftool-2
-R /desktop/gnome/peripherals/keyboard/kbd) and what happen exactly with the
current xorg packages?

Okay I tried again. It works indeed without changing xorg.conf:
 0) Keyboard properties / Layout
 1) Add "Germany Dead grave acute"
 2) Remove "Eliminate dead keys"

The UI isn't very logical, though. It shouldn't be possible to enable both options at the same time. There
doesn't appear to be an option for "dead circonflexe" - drôle (cannot be typed without composite key).

I spoke too soon. Sometimes (can't seem to reproduce) the setting gets reset. This is how it is supposed to
look like:

gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = [de deadgraveacute]
 model =
 options = [grp grp:alts_toggle,Compose key compose:caps]
 overrideSettings = true

Note the empty "model" option (maybe that's intentional). Once I saw the deadgraveacute setting displayed twice
in the layouts listbox. There seems to be a bug left in the gnome-keyboard-properties UI.

Daniel, what should the layout be for that configuration?

Does "setxkbmap -layout 'de' -model pc105 -option 'grp:alts_toggle' -option
'compose:caps' -print | xkbcomp - :0.0" works correctly?

Your bug lacks information we would need to investigate further. We
are now going to close the bug - please reopen if you have more
information at hand.