| 29 Nov 2022 |
 Arson Copperflame | In reply to @sandro:supersandro.de
Did we get any further with wslg other than running sudo rm -rf /tmp/.X11-unix; ln -s /mnt/wslg/.X11-unix /tmp/.X11-unix every start or am I breaking things? I didn't know that was still a problem (I use X410 instead of XWayland, because it just seemed to work better) | 22:13:41 |
| 30 Nov 2022 |
 Sandro 🐧 | I am not paying money for X11 forwarding | 12:20:40 |
| Sandro 🐧 | K900: is the user dbus session still broken? | 12:39:21 |
| Sandro 🐧 | * K900: is the user dbus session still broken with native systemd? | 12:39:29 |
 K900 | No | 12:39:34 |
| Sandro 🐧 | then it is for me broken 🤓 | 12:40:47 |
| Sandro 🐧 | broken as in the socket is missing in /run/user/1000 | 12:41:08 |
| Sandro 🐧 | Nov 30 13:36:00 francium unknown: Copying /usr/share/applications
Nov 30 13:36:00 francium unknown: Copying /usr/share/icons
Nov 30 13:36:00 francium kernel: misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
Nov 30 13:36:00 francium kernel: misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
Nov 30 13:36:00 francium kernel: misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
Nov 30 13:36:00 francium kernel: misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
Nov 30 13:36:00 francium unknown: Can't ignore signal CHLD, forcing to default.
Nov 30 13:36:00 francium sh: line 1: systemctl: command not found
Nov 30 13:36:00 francium sh: line 1: grep: command not found
Nov 30 13:36:00 francium unknown: setting up /etc...
Nov 30 13:36:00 francium sh: line 1: systemctl: command not found
Nov 30 13:36:00 francium sh: line 1: grep: command not found
Nov 30 13:36:00 francium unknown: setting up /bin...
Nov 30 13:36:00 francium unknown: setting up secrets...
Nov 30 13:36:00 francium sops-install-secrets: Imported /etc/ssh/ssh_host_rsa_key as GPG key with fingerprint 5f896e41a035cc21d70ed4b65df655b64ce35e21
Nov 30 13:36:00 francium sops-install-secrets: Imported /etc/ssh/ssh_host_ed25519_key as age key with fingerprint age12v03lzm0kac3rcjt6qmkpsnpxkqv3pgdxjrxggzsrt6r3j4k3ugqms4k0y
Nov 30 13:36:00 francium unknown: setting up /sbin/init shim...
Nov 30 13:36:00 francium nixos_wsl_native_systemd_shim[1]: Spawning real systemd...
Nov 30 13:36:00 francium unknown: Failed to connect to bus: No such file or directory
Nov 30 13:36:00 francium unknown: Failed to connect to bus: No such file or directory
| 12:42:27 |
| Sandro 🐧 | but then further down:
Nov 30 13:36:00 francium systemd[1]: Started Name Service Cache Daemon.
Nov 30 13:36:00 francium systemd[1]: Reached target Host and Network Name Lookups.
Nov 30 13:36:00 francium systemd[1]: Reached target User and Group Name Lookups.
Nov 30 13:36:00 francium systemd[1]: Starting User Login Management...
Nov 30 13:36:00 francium systemd[1]: Starting Permit User Sessions...
Nov 30 13:36:00 francium systemd[1]: Finished Permit User Sessions.
Nov 30 13:36:00 francium sshd[212]: Server listening on 0.0.0.0 port 22.
Nov 30 13:36:00 francium systemd-logind[224]: New seat seat0.
Nov 30 13:36:00 francium systemd[1]: Starting D-Bus System Message Bus...
Nov 30 13:36:00 francium dbus-daemon[226]: dbus[226]: Unknown username "systemd-oom" in message bus configuration file
Nov 30 13:36:00 francium systemd[1]: Started D-Bus System Message Bus.
Nov 30 13:36:00 francium systemd[1]: Started User Login Management.
Nov 30 13:36:00 francium dbus-daemon[226]: [system] Successfully activated service 'org.freedesktop.systemd1'
Nov 30 13:36:00 francium systemd[1]: Reached target Multi-User System.
Nov 30 13:36:00 francium systemd[1]: Startup finished in 877ms.
Nov 30 13:36:00 francium nscd[213]: 213 monitored file `/etc/resolv.conf` was created, adding watch
Nov 30 13:36:00 francium unknown: WSL (2): Creating login session for sandro
Nov 30 13:36:45 francium kernel: hv_balloon: Max. dynamic memory size: 6144 MB
| 12:43:32 |
| Sandro 🐧 | maybe I should also update nixos-wsl.... I need to either automated this or get my two PRs merged. | 12:45:19 |
| Sandro 🐧 | surprise now it works if you are actually using the fixes 🤦 | 12:47:06 |
| Sandro 🐧 | X11 symlinking still not working, sigh | 12:47:59 |
| 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 |
