NixOS GNOME | 399 Members | |
| A room for maintainers of GNOME & GNOME-Related desktop environments (xfce, cinnamon, pantheon...) | 91 Servers |
| Sender | Message | Time |
|---|---|---|
| 6 Jan 2025 | ||
| yeah, 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 regularly | 17:45:20 | |
| I don't see anything there about updating a single extension | 17:46:39 | |
| thanks. 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 | |
| yeah that does appear to be the correct steps for updating all of them | 17:47:54 | |
yeah, plus build nixosTests.gnome-extensions to check if they at least load – that should probably be listed in the readme | 18:07:22 | |
| 19:00:27 | ||
| 19:01:08 | ||
| 19:03:17 | ||
| 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):
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 | |
| (can folks tell I have an extension that I'd really like re-included lol) | 21:57:46 | |
| 7 Jan 2025 | ||
| 18:24:38 | ||
| 18:24:52 | ||
| slightly OT: shouldn't this room also be in #space:nixos.org ? | 18:27:03 | |
| it is, it's within one of the subspaces | 18:31:07 | |
| true. the search results were too slow I guess. | 18:32:29 | |
| yeah, it takes forever to load, I just tried to figure out which subspace and it timed out | 18:32:57 | |
| anyhoo, that's how I initially found the channel | 18:33:19 | |
| 19:35:32 | ||
| 21:58:31 | ||
| 8 Jan 2025 | ||
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 | |
| https://github.com/NixOS/nixpkgs/blob/238b407862874909d510ff4deb1391cbe23efd16/nixos/modules/services/x11/display-managers/gdm.nix#L258 | 21:09:32 | |
| p14: I think that's not true | 21:25:47 | |
| 21:26:02 | |
*
| 21:26:11 | |
*
| 21:26:24 | |
| 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 | |
| I think I must have hallucinated this incorrect point from somewhere. | 21:27:19 | |
p14: When I set services.xserver.displayManager.gdm.debug and services.xserver.desktopManager.gnome.debug I get debug output | 21:27:25 | |
| I 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 :P | 21:27:49 | |
| I 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 login | 21:27:53 | |