Thanks for taking the time to report this.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for more information on how to do so. When pasting a stack trace in this bug report, please reset the status of this bug report from NEEDINFO to its previous status. Thanks in advance!

here is the gdb stack trace

$> gdb gnome-control-center
GNU gdb (GDB) 7.12
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from gnome-control-center...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/gnome-control-center 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffcc7c5700 (LWP 28326)]
[New Thread 0x7fffcb78f700 (LWP 28327)]
[New Thread 0x7fffcaf8e700 (LWP 28328)]
libva info: VA-API version 0.39.4
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_39
libva info: va_openDriver() returns 0
[New Thread 0x7fffc3fff700 (LWP 28334)]

^C
Thread 1 "gnome-control-c" received signal SIGINT, Interrupt.
0x00007ffff009348d in poll () from /usr/lib/libc.so.6
(gdb) thread apply all bt

+ Trace 237061

the only other status i could select is RESOLVED, so I am leaving it at NEEDINFO

Crash in Webkit. Reassigning to the only panel that uses webkit. Do you have more details on how to reproduce this bug?

for me, it happens whenever i click on one of the shortcuts to change it, and sometimes at other points

(In reply to charlesaymard from comment #5)
> for me, it happens whenever i click on one of the shortcuts to change it,
> and sometimes at other points

That's a bit short on details. Could you explain exactly the steps to reproduce this bug? How do you start the Settings, and what you click on to reproduce the crash?

well, I am not entirely sure what more details would consist in: I launch the settings panel, select the keyboard section, and as soon as i click on any of the shortcuts to edit them the app freezes and has to be quit forceably.

absent a solution, is there a workaround to set keyboard shortcuts for this issue?

(In reply to charlesaymard from comment #7)
> well, I am not entirely sure what more details would consist in: I launch
> the settings panel, select the keyboard section, and as soon as i click on
> any of the shortcuts to edit them the app freezes and has to be quit
> forceably.

Then it's not a crash, but a hang?! I'm sorry, but I can't reproduce the problem, and unless you find a way for us to reproduce it, we can't fix it.

again, could you in the meantime point me to a way to change shortcuts without using the settings ui that doesn't work for me?

(In reply to charlesaymard from comment #10)
> again, could you in the meantime point me to a way to change shortcuts
> without using the settings ui that doesn't work for me?

never mind, i found the dconf menu to do that. though it shows some weird behaviour when trying to copy a value from one field to paste and edit it in another one.

I'm editing the title of this bug to reflect that it's not a crash, but a hang. Can I mark it as NEEDINFO? From the backtrace and the comments, I still couldn't figure out what's going on.

*** Bug 778929 has been marked as a duplicate of this bug. ***

From bug 778929, it looks like the problem is fixed in 3.26. I'm not certain which changes fixed it, but there were a number of fixes in GTK+, in mutter as well as in gnome-control-center to make it hard to pinpoint the fix.

Could you please test with a 3.26 version of GNOME?

No further input was added, so assuming it's just fixed, closing this bug.

This still happens. I'll open a new case for this on Gitlab.

(In reply to krinkodot22 from comment #16)
> This still happens. I'll open a new case for this on Gitlab.

Thanks!