| 6 Jul 2023 |
Jan Tojnar | Silas Davis: do you have anything from .gsd-media-keys in the journal after reboot? | 14:00:48 |
Jan Tojnar | gnome-settings-daemon is the component responsible for managing keybindings. For example, I get Failed to grab accelerator for keybinding when I switch to a home-manager config with conflicts. | 14:02:35 |
Jan Tojnar | I could imagine gsd resetting the conflicting settings | 14:02:50 |
Jan Tojnar | I tried restarting that with pkill gsd-media-keys; systemctl start --user org.gnome.SettingsDaemon.MediaKeys.target but it did not reset the conflicting dconf key 🤷♀️ | 14:07:02 |
@silasdavis:one.ems.host | so...
I've taken a look at this file: /nix/store/22dzv5x7q98c890f67ilia4vwmhgxjzq-hm-dconf.ini
Which is referenced by /nix/store/rqyhp24x4cha7qx70i71rq0s32sd7hs1-home-manager-generation/activate:
$DRY_RUN_CMD $DCONF_DBUS_RUN_SESSION /nix/store/d9zam93fa4mj43fz3h09cajh81vgpqvn-dconf-0.40.0/bin/dconf load / < /nix/store/22dzv5x7q98c890f67ilia4vwmhgxjzq-hm-dconf.ini
It contains most of my custom settings, but where I have:
"org/gnome/shell/keybindings" = {
open-application-menu = [];
toggle-overview = [];
# Gnome tries to grab Super+m for this, the bastard
toggle-message-tray = [ "<Super>v" ];
};
It has:
$DRY_RUN_CMD $DCONF_DBUS_RUN_SESSION /nix/store/d9zam93fa4mj43fz3h09cajh81vgpqvn-dconf-0.40.0/bin/dconf load / < /nix/store/22dzv5x7q98c890f67ilia4vwmhgxjzq-hm-dconf.ini
| 14:13:35 |
@silasdavis:one.ems.host | * so...
I've taken a look at this file: /nix/store/22dzv5x7q98c890f67ilia4vwmhgxjzq-hm-dconf.ini
Which is referenced by /nix/store/rqyhp24x4cha7qx70i71rq0s32sd7hs1-home-manager-generation/activate:
$DRY_RUN_CMD $DCONF_DBUS_RUN_SESSION /nix/store/d9zam93fa4mj43fz3h09cajh81vgpqvn-dconf-0.40.0/bin/dconf load / < /nix/store/22dzv5x7q98c890f67ilia4vwmhgxjzq-hm-dconf.ini
It contains most of my custom settings, but where I have:
"org/gnome/shell/keybindings" = {
open-application-menu = [];
toggle-overview = [];
# Gnome tries to grab Super+m for this, the bastard
toggle-message-tray = [ "<Super>v" ];
};
It has (in the generated INI file):
[org/gnome/shell/keybindings]
open-application-menu=@as []
| 14:14:04 |
@silasdavis:one.ems.host | So that would explain why my settings are missing | 14:14:13 |
@silasdavis:one.ems.host | However it doesn't explain why they come back after an nixos-rebuild, let's see! | 14:14:28 |
@silasdavis:one.ems.host | In reply to @jtojnar:matrix.org gnome-settings-daemon is the component responsible for managing keybindings. For example, I get Failed to grab accelerator for keybinding when I switch to a home-manager config with conflicts. ❯ journalctl -b | grep .gsd-media-keys
Jul 06 15:54:14 mifla .gsd-media-keys[1457]: Failed to grab accelerator for keybinding settings:playback-repeat
Jul 06 15:54:14 mifla .gsd-media-keys[1457]: Failed to grab accelerator for keybinding settings:hibernate
Jul 06 15:54:21 mifla .gsd-media-keys[1457]: Unable to get default sink
Jul 06 15:54:21 mifla .gsd-media-keys[1457]: Unable to get default source
Jul 06 15:54:23 mifla .gsd-media-keys[2483]: Failed to grab accelerator for keybinding settings:hibernate
Jul 06 15:54:23 mifla .gsd-media-keys[2483]: Failed to grab accelerator for keybinding settings:playback-repeat
Jul 06 15:54:23 mifla .gsd-media-keys[2483]: Failed to grab accelerator for keybinding settings:screensaver
Jul 06 15:54:23 mifla .gsd-media-keys[2483]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
Jul 06 15:54:34 mifla systemd[2065]: Started Application launched by gsd-media-keys.
Jul 06 15:59:33 mifla systemd[2065]: Started Application launched by gsd-media-keys.
Jul 06 15:59:43 mifla systemd[2065]: Started Application launched by gsd-media-keys.
Jul 06 16:01:45 mifla systemd[2065]: Started Application launched by gsd-media-keys.
Jul 06 16:08:36 mifla systemd[2065]: Started Application launched by gsd-media-keys.
Jul 06 16:15:02 mifla systemd[2065]: Started Application launched by gsd-media-keys.
| 14:16:13 |
@silasdavis:one.ems.host |
Okay so nixos-rebuild --switch as ever restores my keys. Finding activate script:
systemctl show home-manager-silas.service | grep Exec
❯ cat activate | grep dconf
_iNote "Activating %s" "dconfSettings"
/nix/store/83mizl0zb58zzyby47rk7iafa1mrrrmr-dconf-cleanup \
"$oldGenPath/state/dconf-keys.json" \
"$newGenPath/state/dconf-keys.json"
$DRY_RUN_CMD $DCONF_DBUS_RUN_SESSION /nix/store/bll3yc6g3fc6bgxrs97idjxx27qkn9n2-dconf-0.40.0/bin/dconf load / < /nix/store/6676vj0l7kawrqkblqqicyjl3gc99im6-hm-dconf.ini
Now my settings are back:
[org/gnome/shell/keybindings]
open-application-menu=@as []
toggle-message-tray=@as ['<Super>v']
toggle-overview=@as []
| 14:18:20 |
@silasdavis:one.ems.host | will reboot | 14:18:30 |
@silasdavis:one.ems.host | so now the unit has changed | 14:21:30 |
@silasdavis:one.ems.host | After restart, broken:
❯ systemctl show home-manager-silas.service | grep ExecStart=
ExecStart={ path=/nix/store/fqhlc4pka1a9yx5dfy392abxlkibf9hv-hm-setup-env ; argv[]=/nix/store/fqhlc4pka1a9yx5dfy392abxlkibf9hv-hm-setup-env /nix/store/rqyhp24x4cha7qx70i71rq0s32sd7hs1-home-manager-generation ; ignore_errors=no ; start_time=[Thu 2023-07-06 16:18:51 CEST] ; stop_time=[Thu 2023-07-06 16:18:52 CEST] ; pid=941 ; code=exited ; status=0 }
After nixos-rebuild --switch (working):
❯ systemctl show home-manager-silas.service | grep ExecStart=
ExecStart={ path=/nix/store/dpalk76wpvnyfhnr2byxmhnpxrimbal7-hm-setup-env ; argv[]=/nix/store/dpalk76wpvnyfhnr2byxmhnpxrimbal7-hm-setup-env /nix/store/b4pclvgfkw8q6rvpir9zh28dms149br4-home-manager-generation ; ignore_errors=no ; start_time=[Thu 2023-07-06 16:22:06 CEST] ; stop_time=[Thu 2023-07-06 16:22:07 CEST] ; pid=5368 ; code=exited ; status=0 }
| 14:22:46 |
Jan Tojnar | Silas Davis: sounds like home-manager bug then | 14:26:19 |
@silasdavis:one.ems.host | looks like it | 14:26:55 |
@silasdavis:one.ems.host | hm actually thinking about it this feels like exactly what I'd expect loading into a slightly earlier generation! | 14:34:21 |
@silasdavis:one.ems.host | which I'm not intending to | 14:34:33 |
| @dchoi:matrix.org joined the room. | 19:55:40 |
@dchoi:matrix.org | Hello, quick question, how could I change gdm font and display config declaratively? | 20:00:17 |
| Hayley joined the room. | 20:18:53 |
Jan Tojnar | Danche Choi: display config with home-manager (home.file.".config/monitors.xml" for gdm user) | 20:58:36 |
Jan Tojnar | font perhaps with dconf home-manager module? | 20:59:12 |
| 7 Jul 2023 |
| @neul:matrix.org changed their display name from neul to neul (they/any). | 00:29:41 |
| @lotte:chir.rs changed their profile picture. | 05:37:48 |
| Miles Dyson joined the room. | 14:05:41 |
Miles Dyson | Hello, I am just getting started with NixOS and have it installed on QEMU/KVM inside of an Arch build. I am wondering what I need to install and configure to copy&paste, and dynamically resize the Nix guest to match window size. Is there a guide in the tutorials or documentation about this topic? | 14:15:07 |
Miles Dyson | Also, is this the right channel/room for this question? | 14:15:47 |
| Miles Dyson changed their display name from technicus to Miles Dyson. | 15:27:17 |
Jan Tojnar | Miles Dyson: https://matrix.to/#/#nix:nixos.org is probably a better place, this is mostly for GNOME and related environments-specific discussions | 19:30:35 |
Miles Dyson | Thanks. | 19:31:53 |