!XQQVyIbcAcHFvzmcTl:nixos.org

NixOS GNOME

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

Load older messages


SenderMessageTime
8 Jan 2025
@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
@salt:sal.tdSalthmm, is there a good reference for how packages pass through nix generally so I can potentially avoid some of these questions? For instance I notice that when updating extensions the bot automatically opened a backport PR, however there is a large set of updates that was merged a couple weeks ago that doesn't appear to have a PR. And I presume without the backports PR things will only be available in unstable until the next release. So what steps can be taken to open a backports PR if one wasn't automatically generated?23:51:12
9 Jan 2025
@elvishjerricco:matrix.orgElvishJerricco Is there a way to tell gnome to wake the screen from a udev rule? I've got a udev rule that does loginctl lock-sessions when I unplug my yubikey, but I also want it to wake the display when I plug it in. This particular machine would not be expected to be suspended. 07:51:12
@uep:matrix.orguephttps://nixpk.gs/pr-tracker.html is very helpful for such cases21:31:02
10 Jan 2025
@jtojnar:matrix.orgJan Tojnaryes, that is correct. I try to add labels for auto-backports when it makes sense and when someone pings me, merge PRs to stable, but otherwise I avoid stable-related stuff00:38:31
@jtojnar:matrix.orgJan TojnarI also usually ignore extension PRs for the same reason (testing them is time consuming)00:40:43
@jtojnar:matrix.orgJan Tojnar I would expect some D-Bus API to work. There is SimulateUserActivity on org.freedesktop.ScreenSaver but it appears g-s-d does not implement it 00:47:36
@jtojnar:matrix.orgJan Tojnar maybe Inhibit would disable the screensaver even if already active? 00:48:32
@sigmasquadron:matrix.orgSigmaSquadron changed their display name from SigmaSquadron (Away until 2024-01-12) to SigmaSquadron (Away until 2024-01-11).22:15:45
@salt:sal.tdSaltvery cool, thanks22:36:10
@salt:sal.tdSalt okay, well what would the best steps be for getting the changes made in this PR to be backported? 22:38:13
@salt:sal.tdSaltmost importantly, Nautilus 74.1 fixes a fairly major bug that is triggered when resized using keys22:39:31
@jtojnar:matrix.orgJan Tojnaradded a tag, let’s see if auto-backport works22:39:37
@salt:sal.tdSalt* most importantly, Nautilus 47.1 fixes a fairly major bug that is triggered when resized using keys22:39:44

Show newer messages


Back to Room ListRoom Version: 6