| 21 Mar 2023 |
 Arson Copperflame | Sandro 🐧: I don't know if that helps you, but I run Tailscale on Windows and have NixOS use 100.100.100.100 as the DNS so I'm not affected by that | 16:21:15 |
 Sandro 🐧 | I could tinker with something like that but it probably falls apart again. I had so much trouble with DNS already. | 16:22:16 |
| Arson Copperflame | Or just set it to something like 8.8.8.8 if you can live without local host names | 16:26:23 |
| Sandro 🐧 | thats the problem, I cannot | 16:44:05 |
| Arson Copperflame | Is the machine portable? If no, you could set it to your router's IP | 16:44:32 |
| Sandro 🐧 | yes and I always forget to change settings when VPN is used... | 16:48:01 |
| 22 Mar 2023 |
|  valconius joined the room. | 00:00:06 |
| 23 Mar 2023 |
| Sandro 🐧 | Just got that when opening a new WSL tab under load. Not sure how actionable it is. Can't reproduce either.
<3>WSL (31727) ERROR: CreateProcessEntryCommon:563: chdir(/wsl.localhost/NixOS/home/sandro/) failed 2
| 14:19:34 |
| Arson Copperflame | Probably not our bug. It's the same thing you get when you try to open it in a path it can't access it I'm not mistaken | 14:21:03 |
 K900 | I've seen this once or twice | 14:21:31 |
| K900 | But never consistently | 14:21:38 |
| K900 | I think there's an upstream issue about this somewhere? | 14:21:47 |
| Arson Copperflame | In reply to @nzbr:nzbr.de
Probably not our bug. It's the same thing you get when you try to open it in a path it can't access it I'm not mistaken nvm, that one's different now:
PS T:\> wsl
<3>WSL (2919) ERROR: CreateProcessParseCommon:786: Failed to translate T:\
| 14:22:50 |
| 24 Mar 2023 |
|  justinkb joined the room. | 15:26:59 |
| 25 Mar 2023 |
|  Maëlys Bras de fer joined the room. | 18:27:45 |
|  rbutani joined the room. | 23:53:32 |
| 26 Mar 2023 |
 henrik-ch | Hi NixOS WSL, what do you think is the best way to recover if my nixos wsl hangs like this when booting?
(I have given it more than 5 minutes)
setting up /usr/share/applications...
setting up /usr/share/icons...
setting up /etc...
setting up /bin...
my launch command from powershell is:
C:\WINDOWS\system32\wsl.exe -d NixOS
| 08:31:29 |
| K900 | Are you using native systemd? | 08:32:44 |
| K900 | If yes, run wsl.exe --system and check dmesg | 08:33:28 |
| henrik-ch | No, I turned it off to get vscode going (against your advice I think! 🥴) | 08:34:08 |
| henrik-ch | Trying in any case. | 08:34:34 |
| K900 | That will not help as the systemd wrapper in non-native mode does not log to dmesg | 08:35:20 |
| henrik-ch | I can run the wsl.exe command, but the dmesg I see there probably relates to my other wsl instances (I also run a couple of ubuntu instances with nix) | 08:36:38 |
| K900 | It's all one kernel | 08:36:59 |
| K900 | So it is all one dmesg | 08:37:02 |
| henrik-ch | It's a wall of text, do you think it's helpful to share, or shall I search for anything in particular? | 08:37:25 |
| K900 | As I said, if you're not using native systemd, it doesn't matter | 08:40:26 |
| K900 | Because no relevant information will be written to dmesg | 08:40:35 |
| henrik-ch | OK, understood. Better start over I guess? At least I kept my config safe. | 08:42:54 |
| K900 | You can try opening a second shell | 08:43:05 |
