| 30 Nov 2022 |
 Sandro 🐧 | The tmpfiles rul wsl injects is just being ignored
▶ sudo systemd-tmpfiles --create
/run/tmpfiles.d/wsl.conf:3: Duplicate line for path "/tmp/.X11-unix", ignoring.
| 12:57:16 |
 K900 | Yeah but it's identical to ours as far as I can see | 13:03:17 |
| K900 | And older WSLs don't inject it | 13:03:21 |
| Sandro 🐧 | nope, it is a symlink
# /run/tmpfiles.d/wsl.conf
# Note: This file is generated by WSL to prevent systemd-tmpfiles from removing /tmp/.X11-unix during boot.
L /tmp/.X11-unix - - - - /mnt/wslg/.X11-unix
| 13:07:28 |
| Sandro 🐧 | yeah, got it working when removing our rule. Should I update it instead? | 13:09:26 |
| K900 | Maybe? | 13:12:18 |
| Sandro 🐧 | https://github.com/nix-community/NixOS-WSL/pull/172 | 13:28:06 |
| K900 | I really wanna say remove it and just say we depend on latest WSL from the store | 13:41:35 |
| K900 | Now that it's available on 10 | 13:41:41 |
| Sandro 🐧 | I am not sure what the preconditions are for that on Windows 10 and if you need the latest update | 14:14:55 |
| Sandro 🐧 | but yeah then we could remove quite some other workarounds | 14:15:05 |
 Arson Copperflame | In reply to @sandro:supersandro.de
K900: is the user dbus session still broken with native systemd? Understandable, I bought that when WSLg wasn't a thing yet, so I just kept using it | 14:48:55 |
| Sandro 🐧 | I was custom building things and procrastinated it long enough to be fixed by MS | 15:11:21 |
| Sandro 🐧 | but yeah if you already bought it why not continue using it but I am not going to pay twice 25 € | 15:11:41 |
| 1 Dec 2022 |
| Sandro 🐧 | In reply to @sandro:supersandro.de
Am I the only one that encounters the following:
After building many packages and the system being under load for 15 to 30 minutes I cannot load new wsl processes and they just hang? I just got that again with no high load and I have no idea why and how. | 13:13:32 |
| Arson Copperflame | I had WSL crash on me yesterday when building some packages, but I suspect that was due to RAM being full and some critical process got OOM-Killed | 13:33:38 |
| Sandro 🐧 | I suspect that some process in windows just deadlocks when the CPU usage is to high for to long and then you need to reboot to fix WSL | 13:40:48 |
| Arson Copperflame | For me, restarting WSL fixed it, no reboot required - so it's a different problem | 22:08:13 |
| 2 Dec 2022 |
| Sandro 🐧 | wsl.exe --shutdown hangs forever as well | 00:52:33 |
| Sandro 🐧 | or long enough that I restarted. Usually it is done within a minute. | 00:52:50 |
| K900 | https://github.com/microsoft/WSL/releases | 07:28:05 |
| K900 | They have a second person doing WSL releases! | 07:28:11 |
| K900 | (and also yet another attempt at not clobbering the X socket) | 07:28:18 |
| 6 Dec 2022 |
|  hdhog | 18:43:50 |
| 7 Dec 2022 |
| Sandro 🐧 | Anyone has any advice for https://github.com/microsoft/WSL/issues/5806 ? | 16:08:16 |
| Sandro 🐧 | nzbr (they/it): what do you think about deleting the tmpfiles rule altogether in https://github.com/nix-community/NixOS-WSL/pull/172 ? | 16:18:56 |
| Arson Copperflame | If it's an upstream issue that we're fixing, I'd say yes. Do other distros have the same issue? | 18:11:59 |
| Sandro 🐧 | They probably didn't have the tmpfiles rule in the first place | 19:15:42 |
| 8 Dec 2022 |
|  Daniel Kahlenberg joined the room. | 08:37:49 |
| Daniel Kahlenberg | I am experiencing a weird behaviour since I enabled native-systemd or native-docker or both at the same time - trying to figure out which combo it is:
After a restart of the physical machine and trying to run wsl -d NixOS --user myuser again, the NixOS instance entirely refuses to start or even give me some output at all, only (useless workaround was the -e sh switch that basically gave me nothing to work with either. | 08:42:08 |
