Now I am just reading the referred similar bug: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1435020 I have the very similar problems.
In addition to that, when I applied the suggested "unity-settings-daemon --replace" command, then not only my custon settings, but the usual Ctrl-Alt-T terminal short cut also went away. But interestingly not everything went away, for example the Alt-` is still working (switch between the windows of the same binary), this is not in the custom section, and formerly it was a default setting. prohlep@pc56:~$ ps ax | grep settings-daemon 1934 ? Sl 0:00 /usr/lib/unity-settings-daemon/unity-fallback-mount-helper 3287 pts/0 Sl+ 0:00 unity-settings-daemon --replace 3296 pts/0 Sl+ 0:00 /usr/lib/unity-settings-daemon/usd-locate-pointer 3340 pts/1 S+ 0:00 grep settings-daemon prohlep@pc56:~$ unity-settings-daemon --replace ** (unity-settings-daemon:3287): WARNING **: 09:12:51.381: Failed to load PNP ids: Failed to open file “/usr/share/hwdata/pnp.ids”: No such file or directory (unity-settings-daemon:3287): Gtk-WARNING **: 09:12:51.462: Theme parsing error: gtk-main.css:73:38: Failed to import: Error opening file /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or directory ** (unity-settings-daemon:3287): WARNING **: 09:12:51.539: Failed to load PNP ids: Failed to open file “/usr/share/hwdata/pnp.ids”: No such file or directory ** (unity-settings-daemon:3287): WARNING **: 09:12:51.539: Failed to load PNP ids: Failed to open file “/usr/share/hwdata/pnp.ids”: No such file or directory (unity-settings-daemon:3287): media-keys-plugin-WARNING **: 09:12:51.552: Grab failed for some keys, another application may already have access the them. (usd-locate-pointer:3296): Gtk-WARNING **: 09:12:51.559: Theme parsing error: gtk-main.css:73:38: Failed to import: Error opening file /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or directory (unity-settings-daemon:3287): Gtk-WARNING **: 09:12:51.566: Theme parsing error: gtk-main.css:73:38: Failed to import: Error opening file /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or directory ** (unity-settings-daemon:3287): WARNING **: 09:12:51.582: Failed to load PNP ids: Failed to open file “/usr/share/hwdata/pnp.ids”: No such file or directory (unity-settings-daemon:3287): GLib-GIO-CRITICAL **: 09:13:15.145: g_dbus_proxy_call_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed ^^^^^^^^ here the last log item shows what happens, when I wist to refresh the key binding in the custom section. Everytime I try to set a keybinding this gets printed. Also the line "(unity-settings-daemon:3287): media-keys-plugin-WARNING **: 09:12:51.552: Grab failed for some keys, another application may already have access the them." is interesting, ... is this because I started "unity-settings-daemon --replace" manually, and therfore now the original is running and my new command is also running? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-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 unity-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/unity-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
