| 2 Oct 2023 |
 uep | I have the following being set by hm
"org/gnome/settings-daemon/plugins/media-keys" = {
"custom-keybindings" = [ "/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0" ];
screensaver = [ "<Super>l" ];
};
"org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0" = {
binding = "<Control><Alt>t";
command = "alacritty";
name = "Terminal";
};
| 00:35:10 |
| uep | those are exactly the things that get set when manually making the same keybinding in the control panel, as per dconf watch | 00:36:04 |
| uep | assuming there's only the one keybinding, so there's no other clash for the custom-keybindings list | 00:36:33 |
| uep | It works. Kind of. Sometimes. | 00:36:55 |
| uep | It might work when I log in, but if I restart the home-manager-dan.service even for unrelated changes, it stops working.. as do actual media keys like volume control, and the control panel to go look at the settings will crash | 00:37:54 |
| uep | or it will be broken at login, even if the hm service hasn't restarted (because I just log out/in as me) | 00:38:53 |
| uep | (also the screensaver one doesn't work, but that's pop-shell's fault) | 00:39:34 |
| uep | If i dconf reset -f /org/gnome/settings-daemon/plugins/media-keys to try and recover when it's in the broken state, I can set a new keybinding again manually via control panel. But it might not actually work, and it might not still be there after logout/in. | 00:42:51 |
| uep | It's very odd | 00:42:55 |
| uep | * If i dconf reset -f /org/gnome/settings-daemon/plugins/media-keys to try and recover when it's in the broken state, I can set a new keybinding again manually via control panel. But it might not actually work, and it might not still be there after logout/in (making sure that hm hasn't re-run). | 00:43:28 |
| 3 Oct 2023 |
 @js:ukvly.org | hi! is anyone here at Oceansprint in two weeks? :) Would be a good opportunity to debug this: https://github.com/NixOS/nixpkgs/issues/234265 | 07:49:55 |
| @js:ukvly.org | Does anyone have a quick pointer how to override derivations in pkgs.gnome? Specifically, I'd like to add a patch to gnome-session. | 14:06:31 |
| @js:ukvly.org | gnome = super.gnome // {
gnome-session = super.gnome.gnome-session.overrideAttrs (old: {
patches = (old.patches or []) ++ [
../patches/gnome-session/0001-gsm-manager-Fix-Inhibit-DBus-method-handler.patch
];
});
};
| 14:07:51 |
| @js:ukvly.org | this seems to have done the trick, but looks a bit intimidating :) | 14:08:03 |
 piegames | Nope, looks good | 14:08:15 |
| piegames | Welcome to Nix :) | 14:08:26 |
| piegames | * Welcome to the Nix experience :) | 14:08:33 |
| @js:ukvly.org | lol | 14:09:16 |
| @js:ukvly.org | https://github.com/NixOS/nixpkgs/pull/258808 <- if someone wants to make gnome-boxes users happy :) | 14:25:02 |
|  Alex S joined the room. | 15:45:34 |
 Colin | how feasible is it, and does it make sense, to update components like gtk and libadwaita independently from the massive GNOME ecosystem updates (like the outstanding 44 -> 45 PR)? | 21:04:24 |
| Colin | i notice a number of non-GNOME package updates are blocked on gtk and libadwaita right now | 21:04:52 |
|  pbsds changed their profile picture. | 21:04:54 |
| Colin | more of a question about workflows/future changes, since this current release cycle update seems nearly ready | 21:05:59 |
| 4 Oct 2023 |
|  jadtl joined the room. | 06:55:35 |
 felschr | Is anyone else getting frequent (seemingly random) core dumps on gnome-shell?
Oct 04 13:26:55 home-pc systemd-coredump[639235]: [🡕] Process 107196 (.gnome-shell-wr) of user 1000 dumped core.
Module libcanberra-pulse.so without build-id.
Module libmp3lame.so.0 without build-id.
Module libmpg123.so.0 without build-id.
[...]
| 11:48:04 |
| felschr | It's started happening for me since a couple of weeks/months ago. Not entirely sure when. But I didn't have these issues running before, and I've been running Gnome on NixOS for years. | 11:49:34 |
