Sender | Message | Time |
---|---|---|
6 May 2024 | ||
Marie | because thats not the case for me | 15:02:31 |
nzbr (they/it) | I went away from the laptop and put it on standby and now as I wanted to check loginctl, the session was there and it has magically fixed itself (on Ubuntu) | 17:41:57 |
nzbr (they/it) | On Debian it's still broken, but loginctl doesn't work either | 17:43:30 |
8 May 2024 | ||
nzbr (they/it) | I can confirm that it is in fact the shell wrapper that is breaking user systemd. Interestingly WSL seems to only start login (and thus a session) once, with the first shell that is opened inside the distro. The shell that is connected to the terminal is not a child of that login process
When a second shell is started, it is the child of a completely separate tree started by /init . The login process and the bash that is a child of it remain running(I'm not putting the second ps output here for space reasons) | 01:13:25 |
nzbr (they/it) | Made it write the error message to a file in /tmp on crashes and this is what I get
The easy workaround would be to sleep forever if the parent process is a login whose parent is /init , but I'd rather have it just start the shell correctly | 02:22:11 |
nzbr (they/it) | Turns out the process gets set up to ignore SIGCHLD, which makes the wrapper crash when it tries to wait for the sh it forks off to parse /etc/set-environment . The wrapper now checks if SIGCHLD is ignored and skips setting the environment if that is the case. That makes systemctl --user work again | 03:23:54 |
K900 | Oh dear lord | 04:43:51 |
K900 | So cursed | 04:43:57 |
K900 | nzbr (they/it): nix has a sigaction wrapper btw | 04:46:09 |
K900 | https://docs.rs/nix/latest/nix/sys/signal/fn.sigaction.html | 04:46:10 |
K900 | Oh I see it doesn't do null | 05:15:41 |
balanced_design joined the room. | 13:57:58 | |
balanced_design | Hey, just looking for a bit of help. Which as far as I understand should just be updating the system config. Context:
I am getting the error that the file-system is read only when I try to save an edited version of the configuration.nix file. I have a full explaination of the exact steps ive taken. Aswell as a full explaination of my interaction searching the docs in attempt to find a solution. | 14:04:29 |
K900 | Waydroid is not going to happen on WSL realistically | 14:04:56 |
K900 | It requires a custom kernel and graphics acceleration | 14:05:07 |
K900 | Which is possible but non-trivial | 14:05:20 |
K900 | And will probably break something or other in the WSL stack anyway because it does some pretty arcane magic to make things work at all | 14:05:50 |
K900 | For VSCode, the easiest workaround is probably https://github.com/K900/vscode-remote-workaround/blob/main/vscode.nix | 14:07:35 |
balanced_design | WSA(windows subsystem for android) works though? WSA is just being depricate in a year, so I was finding an alternative which is decently performant. And WSL is a hypervisor that gets harware access and all apps ive checked have x86 apk versions. As for it breaking other things, I have 2 NixOS installations. The intention was for 1 to only be for waydroid. | 14:09:33 |
K900 | WSA works | 14:10:10 |
K900 | But it's not just WSL | 14:10:14 |
K900 | It's Hyper-V + a lot of custom Microsoft proprietary glue | 14:10:23 |
K900 | It's not WSL running Waydroid, or WSL running anything resembling "normal" Android | 14:10:42 |
K900 | (and WSL can't run "normal" Android anyway, because "normal" Android has surprisingly little in common with desktop Linux) | 14:11:13 |
balanced_design | Any info on how to save my changes to the configuration.nix file without getting the "read only file system" error? | 14:12:03 |
K900 | You should edit it as root | 14:12:14 |
balanced_design | sudo nano configuration.nix
| 14:15:30 |
balanced_design | I assume I dont understand something | 14:15:45 |
K900 | That sounds wrong | 14:17:16 |
K900 | What file are you editing? | 14:17:24 |