Today the problem occurred again, so I could test /usr/lib/gnome- settings-daemon/gsd-media-keys. Do I understand correctly that in a terminal running bash inside, I simply give this /usr/lib/gnome- settings-daemon/gsd-media-keys fully qualified path as a command?
The result is that it does not return to bash prompt, and initially gives no kind of messages. However, when I try any of the custom keystrokes, or any of the usual but overridden keystrokes, then I get the followings: $ /usr/lib/gnome-settings-daemon/gsd-media-keys (gsd-media-keys:2459): GLib-GIO-WARNING **: 22:32:43.149: Dropping signal AcceleratorActivated of type (uuu) since the type from the expected interface is (ua{sv}) (gsd-media-keys:2459): GLib-GIO-WARNING **: 22:32:57.476: Dropping signal AcceleratorActivated of type (uuu) since the type from the expected interface is (ua{sv}) (gsd-media-keys:2459): GLib-GIO-WARNING **: 22:33:01.756: Dropping signal AcceleratorActivated of type (uuu) since the type from the expected interface is (ua{sv}) (gsd-media-keys:2459): GLib-GIO-WARNING **: 22:33:02.460: Dropping signal AcceleratorActivated of type (uuu) since the type from the expected interface is (ua{sv}) (gsd-media-keys:2459): GLib-GIO-WARNING **: 22:33:04.076: Dropping signal AcceleratorActivated of type (uuu) since the type from the expected interface is (ua{sv}) (gsd-media-keys:2459): GLib-GIO-WARNING **: 22:33:04.500: Dropping signal AcceleratorActivated of type (uuu) since the type from the expected interface is (ua{sv}) (gsd-media-keys:2459): GLib-GIO-WARNING **: 22:33:04.804: Dropping signal AcceleratorActivated of type (uuu) since the type from the expected interface is (ua{sv}) (gsd-media-keys:2459): GLib-GIO-WARNING **: 22:33:05.675: Dropping signal AcceleratorActivated of type (uuu) since the type from the expected interface is (ua{sv}) (gsd-media-keys:2459): GLib-GIO-WARNING **: 22:37:17.075: Dropping signal AcceleratorActivated of type (uuu) since the type from the expected interface is (ua{sv}) (gsd-media-keys:2459): GLib-GIO-WARNING **: 22:37:26.746: Dropping signal AcceleratorActivated of type (uuu) since the type from the expected interface is (ua{sv}) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: $ dconf dump /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ [custom1] binding='<Primary><Alt>BackSpace' command='gnome-session-quit --power-off' name='gnome-session-quit --power-off' [custom0] binding='<Primary><Alt>g' command='gnome-terminal --geometry=80x99-0+0' name='gnome-terminal --geometry=80x99-0+0' $ In spite of the above, time to time, not always, but since 18.04 much much more frequently this settings fails to become active just after booting, ... my account is logged in automatically just after boot. If I log out and log in again, then these key bindings work. If I go to the system settings, and define again, then these work again. Earlier, before 18.04 this phenomenon was rare, namely once a week at most. But since 18.04 it is almost guaranteed, not deterministic, but highly probable, that after an initial boot or a warm reboot these key bindings will not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1755106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp