starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-25 09:15:59 +03:00

[GH-ISSUE #9096] Issue updating Linkwarden #1987

New issue

Closed

opened 2026-02-26 12:50:54 +03:00 by kerem · 8 comments

kerem commented

2026-02-26 12:50:54 +03:00

Owner

Originally created by @Thrilleratplay on GitHub (Nov 12, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/9096

✅ Have you read and understood the above guidelines?

yes

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

Linkwarden

📂 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?

Ubuntu 24.04

📈 Which Proxmox version are you on?

pve-manager/9.0.10/deb1ca707ec72a89 (running kernel: 6.14.11-3-pve)

📝 Provide a clear and concise description of the issue.

When running rustc, the following error is returned:

error: rustup could not choose a version of rustc to run, because one wasn't specified explicitly, and no default is configured.
help: run 'rustup default stable' to download the latest stable release of Rust and set it as your default toolchain.

I ran rustup default stable and reran update which completed successfully.

Could rustup default be set by the installation script?

🔄 Steps to reproduce the issue.

Step 1: Install old version of Linkwarden via proxmox-helper script
Step 2: try to update lxc.

❌ Paste the full error output (if available).

    __    _       __                           __         
   / /   (_)___  / /___      ______ __________/ /__  ____ 
  / /   / / __ \/ //_/ | /| / / __ `/ ___/ __  / _ \/ __ \
 / /___/ / / / / ,<  | |/ |/ / /_/ / /  / /_/ /  __/ / / /
/_____/_/_/ /_/_/|_| |__/|__/\__,_/_/   \__,_/\___/_/ /_/ 
                                                          

  ✔️   Update available: linkwarden 2.13.0 → 2.13.1
Get:1 https://pkgs.tailscale.com/stable/ubuntu noble InRelease
Hit:2 https://apt.postgresql.org/pub/repos/apt noble-pgdg InRelease                       
Hit:3 http://archive.ubuntu.com/ubuntu noble InRelease                                    
Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease
Hit:5 http://archive.ubuntu.com/ubuntu noble-updates InRelease
Hit:6 http://archive.ubuntu.com/ubuntu noble-security InRelease
Fetched 6,581 B in 1s (9,012 B/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
20 packages can be upgraded. Run 'apt list --upgradable' to see them.

changed 13 packages in 2s

28 packages are looking for funding
  run `npm fund` for details
  ✔️   Update Node.js 22
  ⏳   Updating yarn to latest version
changed 1 package in 728ms
  ✔️   Installed Node.js modules: yarn@latest
  ✔️   Stopped Service

[ERROR] in line 4332: exit code 0: while executing command CURRENT_VERSION=$(rustc --version 2> /dev/null | awk '{print $2}')

🖼️ Additional context (optional).

No response

Originally created by @Thrilleratplay on GitHub (Nov 12, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/9096 ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Linkwarden ### 📂 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? Ubuntu 24.04 ### 📈 Which Proxmox version are you on? pve-manager/9.0.10/deb1ca707ec72a89 (running kernel: 6.14.11-3-pve) ### 📝 Provide a clear and concise description of the issue. When running `rustc`, the following error is returned: ``` error: rustup could not choose a version of rustc to run, because one wasn't specified explicitly, and no default is configured. help: run 'rustup default stable' to download the latest stable release of Rust and set it as your default toolchain. ``` I ran `rustup default stable` and reran `update` which completed successfully. Could `rustup default` be set by the installation script? ### 🔄 Steps to reproduce the issue. Step 1: Install old version of Linkwarden via proxmox-helper script Step 2: try to update lxc. ### ❌ Paste the full error output (if available). ``` __ _ __ __ / / (_)___ / /___ ______ __________/ /__ ____ / / / / __ \/ //_/ | /| / / __ `/ ___/ __ / _ \/ __ \ / /___/ / / / / ,< | |/ |/ / /_/ / / / /_/ / __/ / / / /_____/_/_/ /_/_/|_| |__/|__/\__,_/_/ \__,_/\___/_/ /_/ ✔️ Update available: linkwarden 2.13.0 → 2.13.1 Get:1 https://pkgs.tailscale.com/stable/ubuntu noble InRelease Hit:2 https://apt.postgresql.org/pub/repos/apt noble-pgdg InRelease Hit:3 http://archive.ubuntu.com/ubuntu noble InRelease Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease Hit:5 http://archive.ubuntu.com/ubuntu noble-updates InRelease Hit:6 http://archive.ubuntu.com/ubuntu noble-security InRelease Fetched 6,581 B in 1s (9,012 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done 20 packages can be upgraded. Run 'apt list --upgradable' to see them. changed 13 packages in 2s 28 packages are looking for funding run `npm fund` for details ✔️ Update Node.js 22 ⏳ Updating yarn to latest version changed 1 package in 728ms ✔️ Installed Node.js modules: yarn@latest ✔️ Stopped Service [ERROR] in line 4332: exit code 0: while executing command CURRENT_VERSION=$(rustc --version 2> /dev/null | awk '{print $2}') ``` ### 🖼️ Additional context (optional). _No response_

kerem

2026-02-26 12:50:54 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 12:50:55 +03:00

Author

Owner

@MickLesk commented on GitHub (Nov 12, 2025):

How old is the Install? (Which Version before?)

@MickLesk commented on GitHub (Nov 12, 2025): How old is the Install? (Which Version before?)

kerem commented

2026-02-26 12:50:55 +03:00

Author

Owner

@Thrilleratplay commented on GitHub (Nov 12, 2025):

linkwarden 2.13.0 → 2.13.1

@Thrilleratplay commented on GitHub (Nov 12, 2025): linkwarden 2.13.0 → 2.13.1

kerem commented

2026-02-26 12:50:55 +03:00

Author

Owner

@MickLesk commented on GitHub (Nov 12, 2025):

Have you an snapshot? I can test tomorrow something, but i need your execution after this

@MickLesk commented on GitHub (Nov 12, 2025): Have you an snapshot? I can test tomorrow something, but i need your execution after this

kerem commented

2026-02-26 12:50:55 +03:00

Author

Owner

@Thrilleratplay commented on GitHub (Nov 12, 2025):

I don't, sorry.

@Thrilleratplay commented on GitHub (Nov 12, 2025): I don't, sorry.

kerem commented

2026-02-26 12:50:55 +03:00

Author

Owner

@arjen-w commented on GitHub (Nov 16, 2025):

When I try to update linkwarden today, I get the following error:
✖️ Cannot update package lists - APT is critically broken
/dev/fd/63: line 1460: jq: command not found
✔️ Update available: linkwarden 2.10.0 →

[ERROR] in line 159: exit code 0: while executing command "$@" > /dev/null 2>&1

Seems like there is still something wrong in the script.
I tried the rustup default stable command, but that did not change the outcome.

@arjen-w commented on GitHub (Nov 16, 2025): When I try to update linkwarden today, I get the following error: ✖️ Cannot update package lists - APT is critically broken /dev/fd/63: line 1460: jq: command not found ✔️ Update available: linkwarden 2.10.0 → [ERROR] in line 159: exit code 0: while executing command "$@" > /dev/null 2>&1 Seems like there is still something wrong in the script. I tried the rustup default stable command, but that did not change the outcome.

kerem commented

2026-02-26 12:50:55 +03:00

Author

Owner

@MickLesk commented on GitHub (Nov 16, 2025):

No, you have an old Install, jq is missing Like the Text say, Just Install it

@MickLesk commented on GitHub (Nov 16, 2025): No, you have an old Install, jq is missing Like the Text say, Just Install it

kerem commented

2026-02-26 12:50:55 +03:00

Author

Owner

@arjen-w commented on GitHub (Nov 16, 2025):

No, you have an old Install, jq is missing Like the Text say, Just Install it

Hmm. That only solved part of the error, still getting this message:

✔️ Update available: linkwarden 2.10.0 → 2.13.1
✖️ Cannot update package lists - APT is critically broken

[ERROR] in line 30: exit code 0: while executing command return 1

@arjen-w commented on GitHub (Nov 16, 2025): > No, you have an old Install, jq is missing Like the Text say, Just Install it Hmm. That only solved part of the error, still getting this message: ✔️ Update available: linkwarden 2.10.0 → 2.13.1 ✖️ Cannot update package lists - APT is critically broken [ERROR] in line 30: exit code 0: while executing command return 1

kerem commented

2026-02-26 12:50:55 +03:00

Author

Owner

@MickLesk commented on GitHub (Nov 16, 2025):

Then Like the other Text say, Check your apt packages.

@MickLesk commented on GitHub (Nov 16, 2025): Then Like the other Text say, Check your apt packages.

kerem referenced this issue

2026-02-26 13:33:36 +03:00

[PR #1987] [MERGED] Update elementsynapse-install.sh #3462

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ProxmoxVE#1987

No description provided.

Rows
Columns