!XQQVyIbcAcHFvzmcTl:nixos.org

NixOS GNOME

399 Members
A room for maintainers of GNOME & GNOME-Related desktop environments (xfce, cinnamon, pantheon...)91 Servers

Load older messages


SenderMessageTime
6 Jan 2025
@salt:sal.tdSaltyeah, looks like my updates were pulled in, but that's fine, would just like to have a system that keeps extensions updated a bit more regularly17:45:20
@salt:sal.tdSaltI don't see anything there about updating a single extension17:46:39
@mcnesium:exma.de@mcnesium:exma.dethanks. so I clone nixpkgs to my local device, then run that python script, check the other file, and then do a regular merge request?17:47:25
@salt:sal.tdSaltyeah that does appear to be the correct steps for updating all of them17:47:54
@jtojnar:matrix.orgJan Tojnar yeah, plus build nixosTests.gnome-extensions to check if they at least load – that should probably be listed in the readme 18:07:22
@jh-devv:matrix.org@jh-devv:matrix.org changed their display name from Sofie 🏳️‍⚧️ to jh-devv.19:00:27
@jh-devv:matrix.org@jh-devv:matrix.org changed their display name from jh-devv to Sofie Halenius 🏳️‍⚧️.19:01:08
@jh-devv:matrix.org@jh-devv:matrix.org changed their display name from Sofie Halenius 🏳️‍⚧️ to Sofie 🏳️‍⚧️.19:03:17
@salt:sal.tdSalt

just ran through the process but as there weren't new collisions, so I'm not exactly sure what those steps will look like. Here's the general steps (I know, I know, oversimplified):

git clone --depth 1 git@github.com:NixOS/nixpkgs.git
cd nixpkgs/pkgs/desktops/gnome/extensions
git switch -c gnome-extensions
./update-extensions.py
git status (to check if there were new collisions)
cd ../../../../
nix-build -A nixosTests.gnome-extensions
git add pkgs/desktops/gnome/extensions/
git commit -m "gnomeExtensions: auto-update"

while these steps use the main repo, generally they should be followed on your own fork which, after the changes are pushed, can be used to open a Pull Request

21:46:25
@salt:sal.tdSalt(can folks tell I have an extension that I'd really like re-included lol)21:57:46
7 Jan 2025
@mcnesium:matrix.org@mcnesium:matrix.org joined the room.18:24:38
@mcnesium:exma.de@mcnesium:exma.de left the room.18:24:52
@mcnesium:matrix.org@mcnesium:matrix.orgslightly OT: shouldn't this room also be in #space:nixos.org ?18:27:03
@salt:sal.tdSaltit is, it's within one of the subspaces18:31:07
@mcnesium:matrix.org@mcnesium:matrix.orgtrue. the search results were too slow I guess.18:32:29
@salt:sal.tdSaltyeah, it takes forever to load, I just tried to figure out which subspace and it timed out18:32:57
@salt:sal.tdSaltanyhoo, that's how I initially found the channel18:33:19
@sigmasquadron:matrix.orgSigmaSquadron changed their display name from SigmaSquadron to SigmaSquadron (Away until 2024-01-12).19:35:32
@renato-trevisan:matrix.orgRenato Trevisan set a profile picture.21:58:31
8 Jan 2025
@p14:matrix.orgp14 I'm guessing there is no good reason that the display manager sends its debug logs to /dev/null. systemctl show display-manager.service shows that StandardInput=null, and StandardError=inherit, and StandardOutput=journal. Inherit, from the systemd manpage means that it inherits from StandardInput, not StandardOutput, so error messages go to /dev/null. That happens to not be where I want them to go, unfortunately. I hope that's an oversight rather than intentional? 21:09:30
@p14:matrix.orgp14https://github.com/NixOS/nixpkgs/blob/238b407862874909d510ff4deb1391cbe23efd16/nixos/modules/services/x11/display-managers/gdm.nix#L25821:09:32
@elvishjerricco:matrix.orgElvishJerricco p14: I think that's not true 21:25:47
@elvishjerricco:matrix.orgElvishJerricco
   StandardError=

       Controls where file descriptor 2 (stderr) of the executed processes is connected to. The available options are identical to those of StandardOutput=, with some exceptions: if set to inherit the file descriptor used for standard output is duplicated for standard error, while fd:name will use a default file descriptor name of "stderr".
21:26:02
@elvishjerricco:matrix.orgElvishJerricco *

StandardError=

   Controls where file descriptor 2 (stderr) of the executed processes is connected to. The available options are identical to those of StandardOutput=, with some exceptions: if set to inherit the file descriptor used for standard output is duplicated for standard error, while fd:name will use a default file descriptor name of "stderr".
21:26:11
@elvishjerricco:matrix.orgElvishJerricco *

StandardError=

Controls where file descriptor 2 (stderr) of the executed processes is connected to. The available options are identical to those of StandardOutput=, with some exceptions: if set to inherit the file descriptor used for standard output is duplicated for standard error, while fd:name will use a default file descriptor name of "stderr".

21:26:24
@p14:matrix.orgp14 Oh, apologies for my mistake; I'm struggling to explain why I'm not getting debug output for bin/gdm in the display manager process. 21:26:55
@p14:matrix.orgp14I think I must have hallucinated this incorrect point from somewhere.21:27:19
@elvishjerricco:matrix.orgElvishJerricco p14: When I set services.xserver.displayManager.gdm.debug and services.xserver.desktopManager.gnome.debug I get debug output 21:27:25
@elvishjerricco:matrix.orgElvishJerriccoI am glad those exist because at one point either they didn't or I didn't know about them and getting debug output was proving impossible :P21:27:49
@p14:matrix.orgp14I have those set. I have less debug output than I am expecting. I am experimenting with multi-seat and trying to determine why the second seat hangs immediately during login21:27:53

Show newer messages


Back to Room ListRoom Version: 6