mirror of
https://github.com/devnullvoid/pvetui.git
synced 2026-04-25 05:15:51 +03:00
[GH-ISSUE #11] Installing OliveTin fails and locks up TUI when custom MOTD runs neofetch #3
Labels
No labels
bug
bug
documentation
enhancement
pull-request
question
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/pvetui#3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @unclesp1d3r on GitHub (Jun 21, 2025).
Original GitHub issue: https://github.com/devnullvoid/pvetui/issues/11
Originally assigned to: @devnullvoid on GitHub.
Describe the bug
When attempting to install OliveTin through the community scripts in the Proxmox TUI tool, the script fails and causes the TUI to become unresponsive if the Proxmox host has a custom
/etc/motd. The failure seems to originate from the OliveTin script prompting for input that isn’t handled properly, resulting in repeated "Please answer yes or no." messages that flood the terminal. The TUI then hangs and requires multiple manual interrupts to regain control.To Reproduce
Steps to reproduce the behavior:
Select a Proxmox server and press
mto open the menu.Choose
Toolsfrom the menu.Select
OliveTinfrom the Script Selection menu.Press the
Installbutton.Terminal output floods with
Please answer yes or no.—likely several thousand lines.The client becomes unresponsive. Press
Ctrl+Cto interrupt.The following error message appears, but the TUI remains unresponsive until a second interrupt:
Expected behavior
While successful installation of OliveTin would be ideal, a failure should not leave the TUI in a locked or unusable state. It should handle unexpected input/output gracefully, return to the main menu, and ideally provide an informative error message. If cleanup of the failed install is feasible, that would also improve the user experience.
Screenshots
N/A
Desktop (please complete the following information):
Server (please complete the following information):
Additional context
The Proxmox host is configured to run
neofetchautomatically via/etc/motdon login shells. This likely injects unexpected terminal output during script execution, which seems to confuse or break the OliveTin install process, resulting in repeated prompts for user input. While this is a non-default configuration, it’s not uncommon for administrators to include visual or diagnostic output in their MOTDs. More defensive handling of unexpected output (or a non-interactive execution environment) could improve the resilience of the TUI tool in these cases.Thanks again for the effort on this tool—this kind of functionality is a welcome addition to Proxmox, and I’m happy to help improve it.
@unclesp1d3r commented on GitHub (Jun 22, 2025):
With further experimentation, it seems that either the community script is not exiting correctly, or more likely, the TUI's SSH session is not recognizing the script's exit and simply hangs. Even when the community script exits properly, the TUI does not close the SSH session and return to the menu, regardless of how many times I press Enter.
For example, installing Apache Tika, returns this prompt after the install, but pressing enter just adds a new line to the terminal and does not return to the TUI.
@devnullvoid commented on GitHub (Jun 22, 2025):
thanks for the detailed bug report, this is very helpful! I'm able to reproduce both issues and I'm working on a fix.
@devnullvoid commented on GitHub (Jun 23, 2025):
@unclesp1d3r this should be fixed in
1e49c16c5dwhich is included in the latest release (v0.6.0)give it a try and let me know if there are any further issues.
@unclesp1d3r commented on GitHub (Aug 3, 2025):
Sorry for the late reply! This fixed the issue and worked like a charm. Thanks!