| 29 Dec 2024 |
 K900 | Just adding it to systemPackages is not enough | 12:17:04 |
 mwoodpatrickmx | That worked, thank you | 13:08:41 |
| mwoodpatrickmx | In the vscode settings any suggestions on how to set the setting "vscode-neovim.neovimExecutablePaths.linux" | 14:03:23 |
 Arson Copperflame | By the way, if any of you are currently at 38C3 and want NixOS-WSL Stickers, let me know | 22:10:38 |
| Arson Copperflame | Left a bunch of them at the NixOS assembly just now | 22:22:20 |
| 30 Dec 2024 |
|  trudwin joined the room. | 10:11:53 |
| 1 Jan 2025 |
|  NixOS Moderation Botchanged room power levels. | 14:26:19 |
| 2 Jan 2025 |
|  error_pro joined the room. | 10:11:36 |
|  Oluwapelumi Adeosun joined the room. | 10:14:26 |
| 5 Jan 2025 |
| K900 | So this is fun | 16:31:14 |
| K900 | WSL never updates the systemd activation environment | 16:31:32 |
| Arson Copperflame | The base-distro you get to with --debug-shell or do the env vars? | 21:13:02 |
| 6 Jan 2025 |
| K900 | Uhh what | 03:35:18 |
| Arson Copperflame | i didn't understand what you meant with "systemd activation environment" | 20:35:29 |
| K900 | It's the environment units run in | 21:17:46 |
| K900 | As seen with systemctl --user show-environment | 21:17:58 |
| K900 | Basically right now you can't run graphical stuff from a systemd unit at all | 21:18:11 |
| 7 Jan 2025 |
| Arson Copperflame | I see. Hadn't tried to do that yet | 00:11:09 |
| K900 | Me neither really | 05:41:20 |
| K900 | At least not voluntarily | 05:41:24 |
| 15 Jan 2025 |
|  SomeoneSerge (matrix works sometimes) changed their display name from SomeoneSerge (utc+3) to SomeoneSerge. | 19:02:57 |
| 17 Jan 2025 |
|  loudgolem joined the room. | 04:05:59 |
| 18 Jan 2025 |
|  @mmfallacy:matrix.org joined the room. | 08:08:50 |
| 21 Jan 2025 |
|  Marco joined the room. | 19:17:35 |
| 23 Jan 2025 |
|  shaver joined the room. | 21:45:55 |
| 24 Jan 2025 |
|  jgeofil joined the room. | 06:25:04 |
| 27 Jan 2025 |
| K900 | Did someone touch something | 09:44:18 |
| K900 | My user daemon is not starting | 09:44:30 |
| K900 | * My user systemd is not starting | 09:44:35 |
| Arson Copperflame | Not to my knowledge
I think it might fail if activation/systemd startup takes longer than some hardcoded timeout (I think it was 10 seconds) because WSL just doesn't start your user session in that case. I had hoped that would be fixed by making the shell wrapper wait for activation to finish, so that WSL init never gets the error code that activation hasn't finished, but it probably doesn't work like that. (The waiting also prevents the shell failing when it is started after the timeout has triggered, so it did something, just not as much as I had hoped) | 11:20:09 |
