This seems to be a consequence of code change made in
gnome-control-center/gnome-settings-daemon/gnome-settings-keyboard-xkb.c
on November 22nd.

This is what happens on a Solaris 9 x86 system (with XFree 4.3.0 :) ...
bash-2.05$ /opt/gnome-2.6/libexec/gnome-settings-daemon
--disable-crash-dialog

(gnome-settings-daemon:637): GLib-GObject-WARNING **:
g_object_set_valist: construct property "show-crash-dialog" for object 
e set after construction
[1076712180,160,xklavier.c:XklInit/]    xkbEvenType: 5E, xkbError: AC,
display: 807c8f0, root: 40
bash-2.05$ gdb /opt/gnome-2.6/libexec/gnome-settings-daemon          
            
GNU gdb 5.3
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and
you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for
details.
This GDB was configured as "i386-pc-solaris2.9"...
(gdb) run
Starting program: /opt/gnome-2.6/libexec/gnome-settings-daemon 
[1076712225,160,xklavier.c:XklInit/]    xkbEvenType: 5E, xkbError: AC,
display: 807c050, root: 40

Program received signal SIGSEGV, Segmentation fault.
0xdcd6ef90 in memcpy () from /usr/lib/libc.so.1
(gdb) where

+ Trace 44164

GARNOME-0.29.1
gcc-3.3.2
GNU ld version 2.14 20030612
XFree86 4.3.0

When loggin in (to start a "Gnome-2.6" session), this little daemon
crash all the time ......

I'm seeing this on sparc Solaris 8, with the Sun Xserver.

setting OS to 'All' since the reports above cover multiple Xserver/OS
combinations.

Is this still happenning?

Yes, it's still happening.  I just tested control-center-2.5.4.

Here's my backtrace:

bugs{poshea}75: gdb ~/usr/libexec/gnome-settings-daemon
GDB is free software and you are welcome to distribute copies of it
 under certain conditions; type "show copying" to see the conditions.
There is absolutely no warranty for GDB; type "show warranty" for details.
GDB 4.16 (sparc-sun-solaris2.5.1), Copyright 1996 Free Software
Foundation, Inc...
(gdb) run
Starting program: /home/poshea/usr/libexec/gnome-settings-daemon
warning: Unable to find dynamic linker breakpoint function.
warning: GDB will be unable to debug shared library initializers
warning: and track explicitly loaded dynamic code.
 
Program received signal SIGSEGV, Segmentation fault.
0xff374af4 in XklInit ()
(gdb) bt

+ Trace 45034

Checking out Padraig's comment above - 
if I start with control-center-2.5.4, but replace
gnome-settings-daemon/gnome-settings-keyboard-xkb.c with version 1.1
from cvs (which seems to be dated Nov. 12) and recompile, I get the
same crash with the same backtrace.  Don't know if this is a valid
test or not.

Is OS really "All"?  It seems to just be Solaris users, on sparc and
x86.  If this sort of crasher were happening in Linux, it'd be fixed
by now.  <woe to us poor Gnome-on-Solaris users/testers>

Looks like a crash in libxklavier.

Can you get a debuggable version installed so that we can get better
backtraces ?  The first trace clearly has nothing to do with the more
recent report.

marking OS 'Solaris', though I bet the real dependency is on the
xserver not the OS.

Please re-test this with libxklavier-1.0.0

I had the gnome-settings-daemon crash-on-login problem on Solaris 9/SPARC on
GNOME 2.6RC1. Today I've upgraded to libxklavier-1.0.0 and recompiled
control-center + gnome-applets. The results:
- the gnome-settings-daemon won't crash as before
- some error window is displayed, regarding XKB or keyboard something (I'm not
on Solaris now, cannot test).
- system runs fine

Also various other problems seem to be solved by this update.

So, again.
I've mate some tests. libxklavier was compiled
--with-xkb-base=/usr/openwin/lib/X11/xkb. I've also tried --without-xkb-base,
which off-course does not work.
The XKB extension CAN be enabled on Sun's Xserver, but it CAN NOT be enabled on
Sun Rays. As I'm trying this on Sun Rays, can't continue test :(

Is there any way to bypass libxklavier (do not compile it) or is it a "must" for
GNOME to work? (in the Gnome 2.4.x there was no such library). Any other advices
to get it start correctly?

Using libxklavier-1.00 and control-center-2.5.4, I get the same results as Ivan
in comment 10.  No crash, but a bunch of error windows about XKB.  

I'm on a SunBlade100 with Solaris 8, if anyone can make suggestions on how to
check whether the Xserver can have the XKB extension enabled, I'll do what I
can.  I don't have root access on my machine, but I do control the startup of
the Xserver.

Peter,

all I know is contained in this document:
http://docs.sun.com/db/doc/816-7282/6mda3k04h?q=XKB&a=view

The document describes Sun's GNOME, I've found no associations with solaris of
specific version (I have Sol9).

It states, that:

Before you can use the AccessX preference tool, you must enable XKB on your
Solaris system.
Note –

XKB is not currently supported on Sun Ray™ systems.

Edit /etc/dt/config/Xservers. If it does not exist, the Document shows you what
to do.

Append the following to the command line (which starts the X itself) at the end
of the file:
+kb

Enter the following command at a command line:

pkill -HUP dtlogin

Log out of your GNOME session and log in again.

To verify if XKB is running, enter xdpyinfo and search for XKEYBOARD in the
extensions list.

End of citation.

I have tried this two times, didn't work for me. But I have no workstation, only
Sun Rays. Bad thing, because I need to run Gnome on thin clients and seems the
libxklavier is tested only for XFree :( The best would be to ignore libxklavier
and compile control-center and gnome-applets without it, but I checked both
"configure" scripts and they NEED libxklavier.

Does anybody know how to get thgrough this on Solaris + Sun Rays?
Does anybody know how to bypass libxklavier? (Is it even possible?)

Well, after a few weeks this bug still seems to be alive. I have bypassed it by
not-calling the function, which shows window with warning. This is ugly, but
actually it works on Solaris + Sun Ray, where no XKB functionality cannot be
expected yet. All keyboard-related things work as they should.

One thing to know (maybe totally unrelated): I had to set Input method to "X
Input Method (XIM)" instead of "Default", or the national characters don't work
(I'm using Slovak keyboard, switching via GKB applet). There is also env.
variable controlling this, so I've added it to my start-session script.

If anyone is interested, I can post a patch here (I'm not on that Solaris
machine right now), or the XIM problem, respectively. These are things which
never occur on Linux, I think...

Ivan : what version of libxklavier ?

doesn't sound as though this bug *is* alive, since the bug is "crash on
startup"; if I read you and comment #10 correctly, there's no crash, only a
warning.  The warning is perfectly appropriate I think.

Sorry for not responding for a long time!

I'm now in GNOME 2.6.2, and no crash during logon! It works.

But I'm forced to use an patch for Solaris, which removes that warning, because
my Sun's X server on Sun Rays does not support XKB, and I can't allow popup
about this each time customer/user logs in.

But this is not something which corresponds to the but title, so I'm leaving.
Thank you.

Thanks for the feedback. Closing this then.