starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 12 Packages Projects Releases 10 Wiki Activity

Font error when running scripts if TOilet is installed and not figlet #234

New Issue
Closed
opened 2026-02-04 17:16:21 +03:00 by OVERLORD · 19 comments
OVERLORD commented 2026-02-04 17:16:21 +03:00
Owner
Copy Link

Originally created by @bigrichwood on GitHub (Dec 29, 2024).

✅ Have you read and understood the above guidelines?

Yes

📜 What is the name of the script you are using?

Proxmox Datacenter Manager LXC

📂 What was the exact command used to execute the script?

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/proxmox-datacenter-manager.sh)"

📝 Provide a clear and concise description of the issue.

After selecting Yes as the first dialog box to create the LXC, the script fails with a missing font error for Slant.

In my environment at least this is because I have TOilet installed as a dependecy of Neofetch, this provides a binary for figlet which means the script believes figlet is installed, but it's not compatible with the font Slant.

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

Run the script, select Yes at the first dialog box.

❌ Paste the full error output (if available).

error: could not load font slant

[ERROR] in line 227: exit code 0: while executing command ascii_art=$(figlet -f slant -w "$term_width" "$APP")

🖼️ Additional context (optional).

Kernel Version - Linux 6.8.12-5-pve (2024-12-03T10:26Z)
Manager Version - pve-manager/8.3.1/fb48e850ef9dde2

with TOilet installed:

rich@organa:~$ file /usr/bin/figlet
/usr/bin/figlet: symbolic link to /etc/alternatives/figlet

rich@organa:~$ file /etc/alternatives/figlet
/etc/alternatives/figlet: symbolic link to /usr/bin/figlet-toilet

rich@organa:~$ figlet -v
TOIlet Copyright 2006 Sam Hocevar
Internet: sam@hocevar.net Version: 0.3, date:

apt install figlet fixes the problem

rich@organa:~$ file /usr/bin/figlet
/usr/bin/figlet: symbolic link to /etc/alternatives/figlet

rich@organa:~$ file /etc/alternatives/figlet
/etc/alternatives/figlet: symbolic link to /usr/bin/figlet-figlet

rich@organa:~$ figlet -v
FIGlet Copyright (C) 1991-2012 Glenn Chappell, Ian Chai, John Cowan, Christiaan Keet and Claudio Matsuoka
Internet: info@figlet.org Version: 2.2.5, date: 31 May 2012

making the test in build.func "command -v figlet-figlet" may be a way forward, but I'm not sure if that'll work in every environment.

Originally created by @bigrichwood on GitHub (Dec 29, 2024). ### ✅ Have you read and understood the above guidelines? Yes ### 📜 What is the name of the script you are using? Proxmox Datacenter Manager LXC ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/proxmox-datacenter-manager.sh)" ### 📝 Provide a clear and concise description of the issue. After selecting Yes as the first dialog box to create the LXC, the script fails with a missing font error for Slant. In my environment at least this is because I have TOilet installed as a dependecy of Neofetch, this provides a binary for figlet which means the script believes figlet is installed, but it's not compatible with the font Slant. ### ⚙️ What settings are you using? - [X] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. Run the script, select Yes at the first dialog box. ### ❌ Paste the full error output (if available). error: could not load font slant [ERROR] in line 227: exit code 0: while executing command ascii_art=$(figlet -f slant -w "$term_width" "$APP") ### 🖼️ Additional context (optional). Kernel Version - Linux 6.8.12-5-pve (2024-12-03T10:26Z) Manager Version - pve-manager/8.3.1/fb48e850ef9dde2 with TOilet installed: rich@organa:~$ file /usr/bin/figlet /usr/bin/figlet: symbolic link to /etc/alternatives/figlet rich@organa:~$ file /etc/alternatives/figlet /etc/alternatives/figlet: symbolic link to /usr/bin/figlet-toilet rich@organa:~$ figlet -v TOIlet Copyright 2006 Sam Hocevar Internet: [sam@hocevar.net](mailto:sam@hocevar.net) Version: 0.3, date: apt install figlet fixes the problem rich@organa:~$ file /usr/bin/figlet /usr/bin/figlet: symbolic link to /etc/alternatives/figlet rich@organa:~$ file /etc/alternatives/figlet /etc/alternatives/figlet: symbolic link to /usr/bin/figlet-figlet rich@organa:~$ figlet -v FIGlet Copyright (C) 1991-2012 Glenn Chappell, Ian Chai, John Cowan, Christiaan Keet and Claudio Matsuoka Internet: [info@figlet.org](mailto:info@figlet.org) Version: 2.2.5, date: 31 May 2012 making the test in build.func "command -v figlet-figlet" may be a way forward, but I'm not sure if that'll work in every environment.
OVERLORD added the question label 2026-02-04 17:16:21 +03:00
OVERLORD commented 2026-02-04 17:16:25 +03:00
Author
Owner
Copy Link

@oOStroudyOo commented on GitHub (Dec 29, 2024):

I was unable to replicate the issue, even with uninstalling figlet and allowing the helper-script to reinstall it:
image

I am running a slightly newer version of pve-manager/8.3.2/3e76eec21c4a14a7 but there isn't anything in the Proxmox change log relating to Figlet.

@oOStroudyOo commented on GitHub (Dec 29, 2024): I was unable to replicate the issue, even with uninstalling figlet and allowing the helper-script to reinstall it: ![image](https://github.com/user-attachments/assets/a2b3d37f-2af6-476f-9973-68bd551eade4) I am running a slightly newer version of pve-manager/8.3.2/3e76eec21c4a14a7 but there isn't anything in the Proxmox change log relating to Figlet.
OVERLORD commented 2026-02-04 17:16:34 +03:00
Author
Owner
Copy Link

@bigrichwood commented on GitHub (Dec 29, 2024):

Having done a bit more digging, my Proxmox nodes have an old version of TOilet which includes a figlet binary. This version does not support the font slant, and I think was installed as a dependecy of neofetch.

rich@organa:~$ figlet -v
TOIlet Copyright 2006 Sam Hocevar
Internet: sam@hocevar.net Version: 0.3, date:

If I install with an apt install figlet, you get a version which does support the appropriate fonts.

rich@organa:~$ figlet -v
FIGlet Copyright (C) 1991-2012 Glenn Chappell, Ian Chai, John Cowan, Christiaan Keet and Claudio Matsuoka
Internet: info@figlet.org Version: 2.2.5, date: 31 May 2012

So it looks like simply checking for the existance of figlet in the script isn't enough, it needs to check if it's a suitable version.

@bigrichwood commented on GitHub (Dec 29, 2024): Having done a bit more digging, my Proxmox nodes have an old version of TOilet which includes a figlet binary. This version does not support the font slant, and I think was installed as a dependecy of neofetch. rich@organa:~$ figlet -v TOIlet Copyright 2006 Sam Hocevar Internet: <sam@hocevar.net> Version: 0.3, date: If I install with an apt install figlet, you get a version which does support the appropriate fonts. rich@organa:~$ figlet -v FIGlet Copyright (C) 1991-2012 Glenn Chappell, Ian Chai, John Cowan, Christiaan Keet and Claudio Matsuoka Internet: <info@figlet.org> Version: 2.2.5, date: 31 May 2012 So it looks like simply checking for the existance of figlet in the script isn't enough, it needs to check if it's a suitable version.
OVERLORD commented 2026-02-04 17:16:42 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 29, 2024):

Can you Update your issue description & title with your latest Message? Then i can check it in a few days

@MickLesk commented on GitHub (Dec 29, 2024): Can you Update your issue description & title with your latest Message? Then i can check it in a few days
OVERLORD commented 2026-02-04 17:16:50 +03:00
Author
Owner
Copy Link

@bigrichwood commented on GitHub (Dec 30, 2024):

Can you Update your issue description & title with your latest Message? Then i can check it in a few days

Hopefully my updates make sense. https://github.com/community-scripts/ProxmoxVE/issues/1083 is probably the same issue.

@bigrichwood commented on GitHub (Dec 30, 2024): > Can you Update your issue description & title with your latest Message? Then i can check it in a few days Hopefully my updates make sense. https://github.com/community-scripts/ProxmoxVE/issues/1083 is probably the same issue.
OVERLORD commented 2026-02-04 17:16:55 +03:00
Author
Owner
Copy Link

@onethree7 commented on GitHub (Dec 30, 2024):

Having done a bit more digging, my Proxmox nodes have an old version of TOilet which includes a figlet binary. This version does not support the font slant, and I think was installed as a dependecy of neofetch.

rich@organa:~$ figlet -v TOIlet Copyright 2006 Sam Hocevar Internet: sam@hocevar.net Version: 0.3, date:

If I install with an apt install figlet, you get a version which does support the appropriate fonts.

rich@organa:~$ figlet -v FIGlet Copyright (C) 1991-2012 Glenn Chappell, Ian Chai, John Cowan, Christiaan Keet and Claudio Matsuoka Internet: info@figlet.org Version: 2.2.5, date: 31 May 2012

So it looks like simply checking for the existance of figlet in the script isn't enough, it needs to check if it's a suitable version.

you are 100% correct and its reproducable as such. Not creating another issue for #jellyfin . This is everywhere, neofetch is basic to all my LXC.

EDIT: Via SSH its erroring before whiptail can load the promptwindow, via Console it allows to do a Whiptail decision, and then error out.

And i tested the old tteck script which still worked in comparison.

@onethree7 commented on GitHub (Dec 30, 2024): > Having done a bit more digging, my Proxmox nodes have an old version of TOilet which includes a figlet binary. This version does not support the font slant, and I think was installed as a dependecy of neofetch. > > rich@organa:~$ figlet -v TOIlet Copyright 2006 Sam Hocevar Internet: [sam@hocevar.net](mailto:sam@hocevar.net) Version: 0.3, date: > > If I install with an apt install figlet, you get a version which does support the appropriate fonts. > > rich@organa:~$ figlet -v FIGlet Copyright (C) 1991-2012 Glenn Chappell, Ian Chai, John Cowan, Christiaan Keet and Claudio Matsuoka Internet: [info@figlet.org](mailto:info@figlet.org) Version: 2.2.5, date: 31 May 2012 > > So it looks like simply checking for the existance of figlet in the script isn't enough, it needs to check if it's a suitable version. you are 100% correct and its reproducable as such. Not creating another issue for #jellyfin . This is everywhere, neofetch is basic to all my LXC. EDIT: Via SSH its erroring before whiptail can load the promptwindow, via Console it allows to do a Whiptail decision, and then error out. And i tested the old tteck script which still worked in comparison.
OVERLORD commented 2026-02-04 17:16:57 +03:00
Author
Owner
Copy Link

@vsisl commented on GitHub (Dec 30, 2024):

I seemingly have the same problem when installing Adguard LXC.

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/adguard.sh)"

error: could not load font slant

[ERROR] in line 227: exit code 0: while executing command ascii_art=$(figlet -f slant -w "$term_width" "$APP")
@vsisl commented on GitHub (Dec 30, 2024): I seemingly have the same problem when installing [Adguard LXC](https://community-scripts.github.io/ProxmoxVE/scripts?id=adguard). ```bash bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/adguard.sh)" error: could not load font slant [ERROR] in line 227: exit code 0: while executing command ascii_art=$(figlet -f slant -w "$term_width" "$APP") ```
OVERLORD commented 2026-02-04 17:17:10 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 31, 2024):

I wonder why you have Toilet or figlet in such ancient versions on the systems? What is the reason?

@MickLesk commented on GitHub (Dec 31, 2024): I wonder why you have Toilet or figlet in such ancient versions on the systems? What is the reason?
OVERLORD commented 2026-02-04 17:17:18 +03:00
Author
Owner
Copy Link

@bigrichwood commented on GitHub (Dec 31, 2024):

I wonder why you have Toilet or figlet in such ancient versions on the systems? What is the reason?

It’s the version currently available in Debian stable packages (https://packages.debian.org/stable/text/toilet), and installed as a dependency of a dependency of another package I use, neofetch.

@bigrichwood commented on GitHub (Dec 31, 2024): > I wonder why you have Toilet or figlet in such ancient versions on the systems? What is the reason? It’s the version currently available in Debian stable packages (https://packages.debian.org/stable/text/toilet), and installed as a dependency of a dependency of another package I use, neofetch.
OVERLORD commented 2026-02-04 17:17:22 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 31, 2024):

Does neofetch running with the .tar.xz in our misc Project folder? Thats the latest figlet

@MickLesk commented on GitHub (Dec 31, 2024): Does neofetch running with the .tar.xz in our misc Project folder? Thats the latest figlet
OVERLORD commented 2026-02-04 17:17:29 +03:00
Author
Owner
Copy Link

@vsisl commented on GitHub (Dec 31, 2024):

I wonder why you have Toilet or figlet in such ancient versions on the systems? What is the reason?

I'm running Proxmox VE 8.3.2

I also have neofetch installed. So maybe it's indeed caused by neofetch? How could I update or install those fonts?

@vsisl commented on GitHub (Dec 31, 2024): > I wonder why you have Toilet or figlet in such ancient versions on the systems? What is the reason? I'm running Proxmox VE 8.3.2 I also have neofetch installed. So maybe it's indeed caused by neofetch? How could I update or install those fonts?
OVERLORD commented 2026-02-04 17:17:43 +03:00
Author
Owner
Copy Link

@onethree7 commented on GitHub (Dec 31, 2024):

problem:

root@jellyfin Dec 31 13:43 ~ > figlet -f slant "Tteck forever"
error: could not load font slant

wo:
sudo wget -qO /usr/share/figlet/slant.flf http://www.figlet.org/fonts/slant.flf
works:

root@jellyfin Dec 31 13:42 ~ > figlet -f slant "Tteck forever"
  ________            __      ____                              
 /_  __/ /____  _____/ /__   / __/___  ________ _   _____  _____
  / / / __/ _ \/ ___/ //_/  / /_/ __ \/ ___/ _ \ | / / _ \/ ___/
 / / / /_/  __/ /__/ ,<    / __/ /_/ / /  /  __/ |/ /  __/ /    
/_/  \__/\___/\___/_/|_|  /_/  \____/_/   \___/|___/\___/_/

the fonts are expected in "/usr/share/figlet/"

Can add a check in the build.func header function (although i really would prefer NOT using any fonts , graphics, pictures and icons at all). I (personally!) dont need fancy texts. All i need is a CLI and text in and out. The fancier, the more it breaks.

The header function is already a lot of lines about figlet its getting bigger by fixing the relocating font topic, or it gets bigger by extra lines added to check if figlet -f slant goes 0 or 1 and thus downloading the files. So much lines just for a redundant "ascii"

@onethree7 commented on GitHub (Dec 31, 2024): problem: ``` root@jellyfin Dec 31 13:43 ~ > figlet -f slant "Tteck forever" error: could not load font slant ``` wo: `sudo wget -qO /usr/share/figlet/slant.flf http://www.figlet.org/fonts/slant.flf ` works: ``` root@jellyfin Dec 31 13:42 ~ > figlet -f slant "Tteck forever" ________ __ ____ /_ __/ /____ _____/ /__ / __/___ ________ _ _____ _____ / / / __/ _ \/ ___/ //_/ / /_/ __ \/ ___/ _ \ | / / _ \/ ___/ / / / /_/ __/ /__/ ,< / __/ /_/ / / / __/ |/ / __/ / /_/ \__/\___/\___/_/|_| /_/ \____/_/ \___/|___/\___/_/ ``` the fonts are expected in "**/usr/share/figlet/**" Can add a check in the build.func header function (although i really would prefer NOT using any fonts , graphics, pictures and icons at all). I (personally!) dont need fancy texts. All i need is a CLI and text in and out. The fancier, the more it breaks. The header function is already a lot of lines about figlet its getting bigger by fixing the relocating font topic, or it gets bigger by extra lines added to check if figlet -f slant goes 0 or 1 and thus downloading the files. So much lines just for a redundant "ascii"
OVERLORD commented 2026-02-04 17:17:50 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 31, 2024):

yes, ive time for 30min. I Prepare an Update, after merge, can you check it?

@MickLesk commented on GitHub (Dec 31, 2024): yes, ive time for 30min. I Prepare an Update, after merge, can you check it?
OVERLORD commented 2026-02-04 17:17:56 +03:00
Author
Owner
Copy Link

@onethree7 commented on GitHub (Dec 31, 2024):

im available.

@onethree7 commented on GitHub (Dec 31, 2024): im available.
OVERLORD commented 2026-02-04 17:17:59 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 31, 2024):

can you check it? ive tested with an clean proxmox vm, should be work. But i dont use toilet or neofetch

@MickLesk commented on GitHub (Dec 31, 2024): can you check it? ive tested with an clean proxmox vm, should be work. But i dont use toilet or neofetch
OVERLORD commented 2026-02-04 17:18:01 +03:00
Author
Owner
Copy Link

@onethree7 commented on GitHub (Dec 31, 2024):

this fixed it for me.

  • i was using the "update" method inside a LXC
  • i had the dependency Toilet/Figlet version as shown above by others.
  • my font was not included or placed correctly,
  • the updated build.func worked around this.

I think the assumption that "if run as INSTALL on the PVE" is fixed, can only be true as well.

@onethree7 commented on GitHub (Dec 31, 2024): this fixed it for me. - i was using the "update" method inside a LXC - i had the dependency Toilet/Figlet version as shown above by others. - my font was not included or placed correctly, - the updated build.func worked around this. I think the assumption that "if run as INSTALL on the PVE" is fixed, can only be true as well.
OVERLORD commented 2026-02-04 17:18:08 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 31, 2024):

I'll leave the issue open, maybe 1-2 others can still test it. But I think that every current use-case should be handled this way.

So now it's PC rest, have a nice New Year's Eve ;)

@MickLesk commented on GitHub (Dec 31, 2024): I'll leave the issue open, maybe 1-2 others can still test it. But I think that every current use-case should be handled this way. So now it's PC rest, have a nice New Year's Eve ;)
OVERLORD commented 2026-02-04 17:18:14 +03:00
Author
Owner
Copy Link

@onethree7 commented on GitHub (Dec 31, 2024):

Happy new year , frohes neues :)

@onethree7 commented on GitHub (Dec 31, 2024): Happy new year , frohes neues :)
OVERLORD commented 2026-02-04 17:18:18 +03:00
Author
Owner
Copy Link

@vsisl commented on GitHub (Jan 3, 2025):

For what it's worth, I fixed this bug by simply

apt install figlet
@vsisl commented on GitHub (Jan 3, 2025): For what it's worth, I fixed this bug by simply ```bash apt install figlet ```
OVERLORD commented 2026-02-04 17:18:21 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 3, 2025):

For what it's worth, I fixed this bug by simply

apt install figlet

Its only possible with the correct repository

@MickLesk commented on GitHub (Jan 3, 2025): > For what it's worth, I fixed this bug by simply > > ```bash > apt install figlet > ``` Its only possible with the correct repository
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#234
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?