| 23 Apr 2025 |
 rosssmyth | Is run0 supposed to work? I tried it today and it fails with
Failed to execute /run/current-system/sw/bin/pkttyagent: No such file or directory
Failed to start transient service unit: Access denied
| 15:42:10 |
| rosssmyth | I get that just by running run0 without any arguments | 15:42:35 |
| rosssmyth | * I get that just by running run0 without any arguments, or with any arguments. | 15:42:42 |
 K900 | You need polkit for that | 15:48:02 |
| K900 | security.polkit.enable = true | 15:48:15 |
 thou-vow | git push is freezing my WSL entirely... | 18:49:30 |
| K900 | WSL1 or WSL2? | 18:53:39 |
| thou-vow | In reply to @k900:0upti.me
WSL1 or WSL2? It's WSL 2 | 20:20:19 |
| 24 Apr 2025 |
| K900 | Check for disk corruption maybe | 04:41:59 |
|  sorm_cha changed their profile picture. | 21:53:24 |
| 26 Apr 2025 |
 mwoodpatrickmx | I'm trying to get vscode-neovim in NixOS running on WSL-2.
I do have NixOS running in the latest version of WSL-2
I do have neovim version 0.11.0 running on NixOS
I do have vscode server running on my NixOS distro and con connect and launch a terminal using vscode from the windows side and can launch "code ." within the distro and it launches vscode without issue.
My Path to neovim in the NixOS distro is /run/current-system/sw/bin/nvim and did set the
"vscode-neovim.neovimExecutablePaths.linux": "/run/current-system/sw/bin/nvim"
But when I restart vscode I get:
[Failed to start nvim] Unable to find a suitable neovim executable. Please check your neovim installation.
Does anyone have any suggestions about what I'm doing wrong or how best to debug | 14:35:39 |
 Gleydar | How do you set the neovimExecutable path? | 16:16:57 |
|  debabrata pattnayak joined the room. | 18:06:00 |
| 1 May 2025 |
|  Rosuavio changed their display name from Rosario Pulella to Rosuavio. | 20:08:18 |
| 7 May 2025 |
 98765abc | 🤨hmm wired. Podman with Container Device Interface is not usable on my Machine
DEBU[0000] ExitCode msg: "container create failed (no logs from conmon): conmon bytes \"\": readobjectstart: expec
t { or n, but found \x00, error found in #0 byte of ...||..., bigger context ...||..."
Error: container create failed (no logs from conmon): conmon bytes "": readObjectStart: expect { or n, but found ,
error found in #0 byte of ...||..., bigger context ...||...
DEBU[0000] Shutting down engines
| 13:32:12 |
| K900 | I highly doubt CDI will work on WSL | 13:33:03 |
| K900 | Because WSL handles drivers very differently | 13:33:11 |
| K900 | And not at all like a normal Linux system | 13:33:20 |
| K900 | And CDI is a stupid workaround for Nvidia driver handling already being stupid | 13:33:30 |
|  @wimpress:matrix.org changed their profile picture. | 15:12:18 |
| 8 May 2025 |
|  isabel changed their profile picture. | 08:58:02 |
| 98765abc changed their profile picture. | 11:35:18 |
| @wimpress:matrix.org left the room. | 19:20:09 |
| 11 May 2025 |
|  @erzet:beeper.com left the room. | 11:08:15 |
| 12 May 2025 |
 lxsameer | hey folks. I'm not familiar with windows, would it be possible to build windows executable that runs on any windows system using WSL and nix? | 10:15:10 |
| K900 | No | 10:16:29 |
| K900 | WSL is a Linux VM | 10:16:31 |
| K900 | It doesn't do native Windows things | 10:16:44 |
 nzbr (they/it) | WSL lets you run linux executables, so that's not really helping there. You may be able to cross-compile for windows if the compiler supports it, but there isn't really a point in that if you're running windows anyway | 10:17:35 |
| lxsameer | cool, thank you | 10:18:02 |
