| 31 Dec 2024 |
|  getchoo changed their profile picture. | 12:38:56 |
| 1 Jan 2025 |
|  amadaluzia[tde] changed their profile picture. | 07:10:46 |
| amadaluzia[tde] changed their display name from amadaluzia() {} to amadaluzia. | 07:11:21 |
|  NixOS Moderation Botchanged room power levels. | 14:26:15 |
| 2 Jan 2025 |
 @mcnesium:exma.de | the user style sheet extension is at v11 but shown as v10 here. installed doing home.packages = with pkgs; [ … gnomeExtensions.user-stylesheet-font … ]; - source points here but it does not look like there is something to update there, right? how can this ext be updated in nixpkgs? | 16:50:10 |
| 3 Jan 2025 |
|  elikoga changed their display name from elikoga (@38c3 📞488{0,1,9}) to elikoga. | 10:28:14 |
 @MartiniMoe:matrix.org | Hi, has anyone succesfully configured sleep when inactive with home-manager and its dconf.settings? Im trying this:
dconf.settings = {
"org/gnome/desktop/session/idle-delay" = lib.hm.gvariant.mkUint32(0);
"org/gnome/settings-daemon/plugins/power/sleep-inactive-ac-type" = "nothing";
};
But it fails with error: A definition for option dconf.settings."org/gnome/settings-daemon/plugins/power/sleep-inactive-ac-type"' is not of type attribute set of (GVariant value)'. Definition values: - In /nix/store/50krr31h6f9x22ihm6xg50swss37kni8-source/home/moe_omnissiah': "nothing"`
| 11:16:13 |
| @MartiniMoe:matrix.org | * Hi, has anyone succesfully configured sleep when inactive with home-manager and its dconf.settings? Im trying this:
dconf.settings = {
"org/gnome/desktop/session/idle-delay" = lib.hm.gvariant.mkUint32(0);
"org/gnome/settings-daemon/plugins/power/sleep-inactive-ac-type" = "nothing";
};
But it fails with
error: A definition for option `dconf.settings."org/gnome/settings-daemon/plugins/power/sleep-inactive-ac-type"' is not of type `attribute set of (GVariant value)'. Definition values: - In `/nix/store/50krr31h6f9x22ihm6xg50swss37kni8-source/home/moe\_omnissiah': "nothing"\
| 11:16:32 |
 p14 | In case anyone comes across this, somehow dconf read /org/gnome/desktop/lockdown/disable-lock-screen had been set to true. Took some figuring out. | 17:09:11 |
| p14 | Not aware of having set this myself, I wonder what might have set it? | 17:09:22 |
| 4 Jan 2025 |
|  Salt joined the room. | 04:37:20 |
| Salt | Hi, I recently went down a rabbit hole while wondering when a particular GNOME extension would update... It has lead me to the question of whether the update-extensions.py script could be setup to have some sort of filter such that an individual extension could be updated? | 04:45:31 |
|  @kranzes:matrix.org left the room. | 15:30:11 |
| 5 Jan 2025 |
 Jan Tojnar | The keys need to be in a second level, see https://github.com/jtojnar/nixfiles/blob/a39624655dba4703fc0162b1412c5c34f04d2997/hosts/theo/configuration.nix#L544-L551 for an example | 19:06:26 |
| Jan Tojnar | It could probably be added. But generally, we will want to update all at the same time anyway. | 19:07:46 |
| Salt | I get that, it just seems like there are super large gaps between updates being run. This is especially impactful when there is a recent update to a higher GNOME version, where we are stuck waiting for the updated extension to be pulled in. | 19:09:39 |
| Salt | I tried to submit a PR to the open PR for a recent update but unsure if it has been noticed yet. | 19:10:24 |
