[GH-ISSUE #21] Failure for binary to launch without config file, even with -w or --config-wizard #5

New issue

Closed

opened 2026-02-26 18:43:09 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 18:43:09 +03:00

Owner

Originally created by @BenRachmiel on GitHub (Aug 4, 2025).
Original GitHub issue: https://github.com/devnullvoid/pvetui/issues/21

Originally assigned to: @devnullvoid on GitHub.

Hey, firstly: amazing project, really something I'd love to daily drive for my homelab.

Info on machine where bug encountered:
 distro │ Arch Linux x86_64
 kernel │ Linux 6.15.8-arch1-1
 term │ alacritty 0.15.1
 shell │ zsh 5.9
󰍛 cpu │ 11th Gen Intel(R) Core(TM) i7-1165G7 (8) @ 4.70 GHz
󰉉 disk │ 92.99 GiB / 952.40 GiB (10%) - xfs
 memory │ 7.17 GiB / 31.00 GiB (23%)

I encountered the following bug after building from source. Steps followed:

git clone
git submodule init && git submodule update
cd in & make build
attempted to run binary ./bin/proxmox-tui
after no response (exited), attempted to run ./bin/proxmox-tui --config-wizard
No response whatsoever, failure to launch.

Found the following after running strace -e trace=openat,read ./bin/proxmox-tui --config-wizard 2>&1 | grep -v SIGURG:

openat(AT_FDCWD, "/home/REDACTED/proxmox-tui/bin/proxmox-tui", O_RDONLY|O_CLOEXEC) = 4
openat(AT_FDCWD, "/etc/sops/audit.yaml", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
+++ exited with 1 +++

I then touched /etc/sops/audit.yaml after installing sops via paru, and reran, which led to again exit-code 1'ing without error output.

Resolved by creating config.yml in .config/proxmox-tui and running.

Resolution steps: seems as if the check for the config isn't appropriately firing, at least on my build. Also, might be worthwhile doing a SOPS check if it is necessary, or including SOPS as a requirement in the build from source instructions.

Originally created by @BenRachmiel on GitHub (Aug 4, 2025). Original GitHub issue: https://github.com/devnullvoid/pvetui/issues/21 Originally assigned to: @devnullvoid on GitHub. Hey, firstly: amazing project, really something I'd love to daily drive for my homelab. Info on machine where bug encountered:  distro │ Arch Linux x86_64  kernel │ Linux 6.15.8-arch1-1  term │ alacritty 0.15.1  shell │ zsh 5.9 󰍛 cpu │ 11th Gen Intel(R) Core(TM) i7-1165G7 (8) @ 4.70 GHz 󰉉 disk │ 92.99 GiB / 952.40 GiB (10%) - xfs  memory │ 7.17 GiB / 31.00 GiB (23%) I encountered the following bug after building from source. Steps followed: 1) git clone 2) git submodule init && git submodule update 3) cd in & make build 4) attempted to run binary ./bin/proxmox-tui 5) after no response (exited), attempted to run ./bin/proxmox-tui --config-wizard No response whatsoever, failure to launch. Found the following after running strace -e trace=openat,read ./bin/proxmox-tui --config-wizard 2>&1 | grep -v SIGURG: openat(AT_FDCWD, "/home/REDACTED/proxmox-tui/bin/proxmox-tui", O_RDONLY|O_CLOEXEC) = 4 openat(AT_FDCWD, "/etc/sops/audit.yaml", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) +++ exited with 1 +++ I then touched /etc/sops/audit.yaml after installing sops via paru, and reran, which led to again exit-code 1'ing without error output. Resolved by creating config.yml in .config/proxmox-tui and running. Resolution steps: seems as if the check for the config isn't appropriately firing, at least on my build. Also, might be worthwhile doing a SOPS check if it is necessary, or including SOPS as a requirement in the build from source instructions.

kerem

2026-02-26 18:43:09 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 18:43:09 +03:00

Author

Owner

@BenRachmiel commented on GitHub (Aug 4, 2025):

Very seriously would be happy to try and tackle the issue. I'm not a golang wizard, but I can take a crack at it. If you'd be down for that, would appreciate contrib guidelines. If you have a recommendaiton where to look, would also appreciate that.

@BenRachmiel commented on GitHub (Aug 4, 2025): Very seriously would be happy to try and tackle the issue. I'm not a golang wizard, but I can take a crack at it. If you'd be down for that, would appreciate contrib guidelines. If you have a recommendaiton where to look, would also appreciate that.

kerem commented

2026-02-26 18:43:09 +03:00

Author

Owner

@devnullvoid commented on GitHub (Aug 6, 2025):

thanks for the report! Testing is not my strongest suit, so I appreciate the feedback! I must have had a regression somewhere. I'll get this fixed.

@devnullvoid commented on GitHub (Aug 6, 2025): thanks for the report! Testing is not my strongest suit, so I appreciate the feedback! I must have had a regression somewhere. I'll get this fixed.

kerem referenced this issue

2026-02-26 18:43:15 +03:00

[PR #5] [MERGED] deps(deps): bump github.com/gdamore/tcell/v2 from 2.7.1 to 2.8.1 #23

kerem referenced this issue

2026-02-27 12:38:22 +03:00

[PR #5] deps(deps): bump github.com/gdamore/tcell/v2 from 2.7.1 to 2.8.1 #97