Pulse Update generates a warning - unbound variable #1221

Open
opened 2025-11-20 05:06:32 -05:00 by saavagebueno · 0 comments
Owner

Originally created by @Jefe2 on GitHub (Jun 3, 2025).

Have you read and understood the above guidelines?

yes

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

Pulse

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

update

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📝 Provide a clear and concise description of the issue.

When updating Pulse, the following is output:
✔️ Stopped Pulse
✔️ Updated Pulse to 3.20.0
✔️ Set permissions.
✔️ Started Pulse
/dev/fd/63: line 1072: CT_TYPE: unbound variable
root@pulse:~#

🔄 Steps to reproduce the issue.

Run "update" in the console.

Paste the full error output (if available).

/dev/fd/63: line 1072: CT_TYPE: unbound variable

🖼️ Additional context (optional).

No response

Originally created by @Jefe2 on GitHub (Jun 3, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Pulse ### 📂 What was the exact command used to execute the script? update ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. When updating Pulse, the following is output: ✔️ Stopped Pulse ✔️ Updated Pulse to 3.20.0 ✔️ Set permissions. ✔️ Started Pulse /dev/fd/63: line 1072: CT_TYPE: unbound variable root@pulse:~# ### 🔄 Steps to reproduce the issue. Run "update" in the console. ### ❌ Paste the full error output (if available). /dev/fd/63: line 1072: CT_TYPE: unbound variable ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 05:06:32 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#1221