You are not logged in.

#1 2018-12-27 08:31:06

herbstschweigen
Member
Registered: 2018-11-04
Posts: 5

[SOLVED] csd-keyboard dumped core

Occasionally I get this message after reboot, like this morning after updating. However, the keyboard works fine, so I can't quite figure out what the problem is. On the next reboot I don't get the message any more. It bothers me however that it appears and I don't know why. I run arch with Cinnamon desktop.

Dez 27 09:18:05 slarti06 systemd-coredump[761]: Process 655 (csd-keyboard) of user 1000 dumped core.
                                                
                                                Stack trace of thread 655:
                                                #0  0x00007fa66e593c36 n/a (libglib-2.0.so.0)
                                                #1  0x00007fa66e59b01c g_log_writer_default (libglib-2.0.so.0)
                                                #2  0x00007fa66e593d29 g_log_structured_array (libglib-2.0.so.0)
                                                #3  0x00007fa66e593fdd g_log_structured_standard (libglib-2.0.so.0)
                                                #4  0x00007fa66ead12ae n/a (libgdk-3.so.0)
                                                #5  0x00007fa66eade445 n/a (libgdk-3.so.0)
                                                #6  0x00007fa66efca52a _XError (libX11.so.6)
                                                #7  0x00007fa66efc73f8 n/a (libX11.so.6)
                                                #8  0x00007fa66efc74a5 n/a (libX11.so.6)
                                                #9  0x00007fa66efc8410 _XReply (libX11.so.6)
                                                #10 0x00007fa66efadfa7 XGetWindowProperty (libX11.so.6)
                                                #11 0x00007fa66eaef049 n/a (libgdk-3.so.0)
                                                #12 0x00007fa66eaefd95 n/a (libgdk-3.so.0)
                                                #13 0x00007fa66ead876f n/a (libgdk-3.so.0)
                                                #14 0x00007fa66ead8a70 n/a (libgdk-3.so.0)
                                                #15 0x00007fa66eaa1ce2 gdk_display_get_event (libgdk-3.so.0)
                                                #16 0x00007fa66ead8804 n/a (libgdk-3.so.0)
                                                #17 0x00007fa66e5a3a2f g_main_context_dispatch (libglib-2.0.so.0)
                                                #18 0x00007fa66e5a55e9 n/a (libglib-2.0.so.0)
                                                #19 0x00007fa66e5a65c2 g_main_loop_run (libglib-2.0.so.0)
                                                #20 0x00007fa66f3042bf gtk_main (libgtk-3.so.0)
                                                #21 0x000055cd47c8d22d main (csd-keyboard)
                                                #22 0x00007fa66e377223 __libc_start_main (libc.so.6)
                                                #23 0x000055cd47c8d39e _start (csd-keyboard)
                                                
                                                Stack trace of thread 679:
                                                #0  0x00007fa66e443c21 __poll (libc.so.6)
                                                #1  0x00007fa66e5a5540 n/a (libglib-2.0.so.0)
                                                #2  0x00007fa66e5a562e g_main_context_iteration (libglib-2.0.so.0)
                                                #3  0x00007fa66e5a5682 n/a (libglib-2.0.so.0)
                                                #4  0x00007fa66e58067b n/a (libglib-2.0.so.0)
                                                #5  0x00007fa66e51ea9d start_thread (libpthread.so.0)
                                                #6  0x00007fa66e44eb23 __clone (libc.so.6)
                                                
                                                Stack trace of thread 720:
                                                #0  0x00007fa66e443c21 __poll (libc.so.6)
                                                #1  0x00007fa66e5a5540 n/a (libglib-2.0.so.0)
                                                #2  0x00007fa66e5a562e g_main_context_iteration (libglib-2.0.so.0)
                                                #3  0x00007fa66794abde n/a (libdconfsettings.so)
                                                #4  0x00007fa66e58067b n/a (libglib-2.0.so.0)
                                                #5  0x00007fa66e51ea9d start_thread (libpthread.so.0)
                                                #6  0x00007fa66e44eb23 __clone (libc.so.6)
                                                
                                                Stack trace of thread 683:
                                                #0  0x00007fa66e443c21 __poll (libc.so.6)
                                                #1  0x00007fa66e5a5540 n/a (libglib-2.0.so.0)
                                                #2  0x00007fa66e5a65c2 g_main_loop_run (libglib-2.0.so.0)
                                                #3  0x00007fa66e70bcb8 n/a (libgio-2.0.so.0)
                                                #4  0x00007fa66e58067b n/a (libglib-2.0.so.0)
                                                #5  0x00007fa66e51ea9d start_thread (libpthread.so.0)
                                                #6  0x00007fa66e44eb23 __clone (libc.so.6)

Last edited by herbstschweigen (2018-12-27 13:57:58)

Offline

#2 2018-12-27 13:52:56

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,120

Re: [SOLVED] csd-keyboard dumped core

That's the keyboard part of the cinnamon settings daemon, ie. sth. to configure your keyboard.
It crashes all the time, see
https://bugzilla.redhat.com/show_bug.cgi?id=1543331
https://bugzilla.redhat.com/show_bug.cgi?id=1452054
https://bugzilla.redhat.com/show_bug.cgi?id=1500485
(and the MAAAAAAAANY duplicates)

It looks like it's trying to obtain a property of a withdrawn or destroyed window, that will generate a (harmless) X11 error, but gdk sh… wets itself for any X11 error (what means the protocol cannot be used async or the process needs exclusive and perfect control over its X11 resources)

If the process gets restarted, this is probably nothing but a nuisance.

Offline

#3 2018-12-27 13:58:44

herbstschweigen
Member
Registered: 2018-11-04
Posts: 5

Re: [SOLVED] csd-keyboard dumped core

Thanks, good to know it's nothing serious.

Offline

Board footer

Powered by FluxBB