Gnome settings freezes every time I try to configure keyboard shortcut

Ask Fedora
, , , ,
1

It’s just me having the issue cause it looks like no one’s talking about it but every time I try to configure keyboard shortcut, the settings app freezes and all I can do is to kill the app by prompt.
I’m new to fedora and I don’t have so much experience on gnome so not sure if it’s fedora’s issue or gnome’s.
I’m on fedora 36 wayland session with btrfs.
Thanks in advance.

sudo journalctl -p 3 -xb

4月 18 22:15:44 fedora systemd[927]: Failed to load BPF object: Operation not permitted
 4月 18 22:15:44 fedora systemd[927]: Failed to create BPF map: Operation not permitted
 4月 18 22:15:45 fedora gnome-session-binary[951]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
 4月 18 22:15:45 fedora gnome-session-binary[951]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
 4月 18 22:15:46 fedora pipewire-pulse[1025]: pw.conf: execvp error 'pactl': no such file or directory
 4月 18 22:15:50 fedora gdm-password][1366]: gkr-pam: unable to locate daemon control file
 4月 18 22:15:51 fedora systemd[1387]: Failed to load BPF object: Operation not permitted
 4月 18 22:15:51 fedora systemd[1387]: Failed to create BPF map: Operation not permitted
 4月 18 22:15:52 fedora systemd[1387]: Failed to start app-glib-liveinst\x2dsetup-1550.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 174 and the job result is failed.
 4月 18 22:15:52 fedora systemd[1387]: Failed to start app-gnome-liveinst\x2dsetup-1550.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 182 and the job result is failed.
 4月 18 22:15:52 fedora systemd[1387]: Failed to start app-gnome-xdg\x2duser\x2ddirs-1551.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 186 and the job result is failed.
 4月 18 22:15:53 fedora pipewire-pulse[1666]: pw.conf: execvp error 'pactl': そのようなファイルやディレクトリはありません
 4月 18 22:15:54 fedora systemd[1387]: Failed to start app-gnome-gnome\x2dshell\x2doverrides\x2dmigration-1883.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 601 and the job result is failed.
 4月 18 22:15:54 fedora systemd[1387]: Failed to start app-gnome-vmware\x2duser-1887.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit UNIT has finished with a failure.
2

Have you tried logging in with xorg to see if you still have the issue.

3

I’m Japanese, but no one else seems to be experiencing the same problem, so I changed the locale to English, which I thought might be a good idea since most of the people on this forum are English speakers, and the problem did not occur. This seems to be a locale-related bug, and it seems to happen in Xorg as well.I hope this will be fixed in the final release.

4

I would suggest that you report this as a bug against fedora 36. The beta is (or may be) in final freeze before release and they need to know this is an issue. It potentially could be a release blocker.

2 Likes
5

Thank you for your advice. I already reported it in the Report app, is there anything else I should do to contribute to the community? There is a mention of Bugzila in the report app, should I report it there as well?

6

I would, and mark it as urgent

1 Like
7

Alright I’ve just reported to bugzilla. And also I quickly checked if it’s possible to reproduce in VM and found it possible. Hope it will be fixed. Thank you for your advice anyway.