!XQQVyIbcAcHFvzmcTl:nixos.org

NixOS GNOME

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

Load older messages


SenderMessageTime
7 Jan 2025
@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
@p14:matrix.orgp14Unfortunately it also produces no log messages. Maybe because it is hanging so early in the process? 21:28:11
@p14:matrix.orgp14I've found a helpful soul who is trying to help me to get it to working but they're claiming I'm missing logs.21:28:33
@p14:matrix.orgp14(Which I'd believe because there are so few of them)21:28:38
@p14:matrix.orgp14I'm sort of beginning to think this second seat's gdm is just not producing logs and I don't understand why21:29:41
@p14:matrix.orgp14Right, there isn't a gdm-per-seat, it's just the one gdm... 🤔21:30:58
@salt:sal.tdSaltokay, new question about extensions... what is the timeline from merge of backport PR to actually being in nixpkgs?22:23:32
@qyliss:fairydust.spaceAlyssa Rosscouple of days22:24:37
@salt:sal.tdSaltkay, will try to be a bit more patient before checking whether a specific extension is breaking22:25:15
@qyliss:fairydust.spaceAlyssa Ross(assuming backport to a release branch, not to staging)22:25:18
@salt:sal.tdSaltyeah, it appears to be a release backport22:25:51
@salt:sal.tdSalt* yeah, it appears to be a release backport, merged 2 days ago22:27:16
@salt:sal.tdSalt

I just saw this comment while trying to track down a different package's backport state and was wondering it is the general consensus?

I don't think any of the GNOME packagers use stable so you are on your own testing the changes :-)

23:45:29

Show newer messages


Back to Room ListRoom Version: 6