| 4 May 2024 |
 Sandro 🐧 | In reply to @k900:0upti.me
Do we ever need one? yes | 17:07:19 |
| Sandro 🐧 | In reply to @k900:0upti.me
If yes, when? eg diffing booted vs. running system | 17:07:28 |
| Sandro 🐧 | https://github.com/NixOS/nixpkgs/commit/7b8511b5e551f2b1f4a63b32ff2122ded7d9fdbc | 17:07:53 |
| Sandro 🐧 | PR was declined | 17:07:55 |
| Sandro 🐧 | In reply to @k900:0upti.me
I think there might be PAM fuckery So what are we doing about that? revert the wrapper? | 17:08:15 |
 K900 | Enable lingering by default somehow maybe? | 17:26:51 |
|  SomeoneSerge (utc+3) changed their display name from SomeoneSerge (is taking time off and doesn't want to hear about it) to SomeoneSerge (Way down Hadestown). | 21:03:45 |
| Sandro 🐧 | would that prevent windows from shutting down WSL if it is inactive? | 23:06:28 |
| 5 May 2024 |
| K900 | Shouldn't | 04:58:52 |
 nzbr (they/it) | At least for me, there's not user systemd on ubuntu right now either. I know that it was broken when WSL systemd support was released, but I'm pretty sure Microsoft had fixed that at some point, so maybe they broke it again with some recent WSL update? | 08:22:58 |
| nzbr (they/it) | The shell wrapper broke that the default shell gets started as a login shell. I already have a fix for that, just need to make a PR | 08:23:43 |
| nzbr (they/it) | In reply to@nzbr:nzbr.de
The shell wrapper broke that the default shell gets started as a login shell. I already have a fix for that, just need to make a PR https://github.com/nix-community/NixOS-WSL/pull/464 | 08:32:29 |
 Marie | my logind somehow doesn't think i'm logged in, so my ssh agent user unit doesn't start. any ideas what could cause this? | 10:42:24 |
| K900 | In reply to @nzbr:nzbr.de
https://github.com/nix-community/NixOS-WSL/pull/464 This possibly | 10:45:42 |
| Marie | cause or fix? it still doesn't work for me with that branch | 11:21:35 |
| nzbr (they/it) | it doesn't seem to fix user systemd, but that seems to be broken on Ubuntu as well | 11:23:00 |
|  @man2dev:fedora.im left the room. | 15:45:45 |
| 6 May 2024 |
 gleydar | Weird, cause I have the emacs-server running via home-manger as a user-systemd service flawlessly | 11:19:34 |
| gleydar | (in ubuntu) | 11:19:52 |
| gleydar | * (in ubuntu)
I'm on wsl version 2.2.3.0 | 11:20:31 |
| Marie | i'm on 2.2.2.0 and it tells me there's no update :( | 13:01:27 |
| nzbr (they/it) | In reply to@gleydar:beeper.com
Weird, cause I have the emacs-server running via home-manger as a user-systemd service flawlessly Just noticed that I get Failed to connect to bus: No such file or directory when running systemctl status without --user as well, so there's probably something broken with my Ubuntu install
(ps shows systemd as pid 1, so it is enabled) | 14:18:06 |
| K900 | That sounds like your main dbus is dead | 14:18:55 |
| nzbr (they/it) | In reply to@marie:marie.cologne
i'm on 2.2.2.0 and it tells me there's no update :( Anything later than 2.1.5.0 is marked a pre-release on github. You can download and install them manually: https://github.com/microsoft/WSL/releases
I don't know what mechanism decides when they are availale through --update for you | 14:20:54 |
| nzbr (they/it) | In reply to@k900:0upti.me
That sounds like your main dbus is dead I tried restarting it, but that didn't help. I'll try with a fresh debian install I have lying around | 14:21:39 |
| nzbr (they/it) | Same problem | 14:33:35 |
| nzbr (they/it) | I'll try a full reboot then | 14:33:45 |
| gleydar | Damn, that sounds like a 💩 problem to debug | 14:35:23 |
| nzbr (they/it) | Ok now sudo systemctl works, but sudo systemctl --user doesn't. Same thing on Ubuntu | 14:39:12 |
| Marie | In reply to @nzbr:nzbr.de
Just noticed that I get Failed to connect to bus: No such file or directory when running systemctl status without --user as well, so there's probably something broken with my Ubuntu install
(ps shows systemd as pid 1, so it is enabled) is there any session running when you run loginctl | 15:02:21 |
