starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-26 01:36:05 +03:00

[PR #12161] [MERGED] fix: Apache Guacamole - bump to Temurin JDK 17 to resolve Debian 13 (Trixie) install failure #10009

New issue

Closed

opened 2026-02-26 17:32:39 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 17:32:39 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE/pull/12161
Author: @Copilot
Created: 2/21/2026
Status: ✅ Merged
Merged: 2/22/2026
Merged by: @michelroegl-brunner

Base: main ← Head: copilot/fix-apache-guacamole-update

📝 Commits (4)

22d75d9 Initial plan
67afa28 Fix get_fallback_suite to apply distro mappings before HTTP availability check
7026aeb Bump Apache Guacamole from Temurin JDK 11 to JDK 17
a4ab494 Revert tools.func changes, keep only Guacamole JDK 11→17 bump

📊 Changes

2 files changed (+2 additions, -2 deletions)

View changed files

📝 ct/apache-guacamole.sh (+1 -1)
📝 install/apache-guacamole-install.sh (+1 -1)

📄 Description

On Debian 13 (Trixie), the Apache Guacamole install and update scripts fail because temurin-11-jdk from the Adoptium repository carries a broken dependency: adoptium-ca-certificates requires p11-kit, which is not available in Debian 13. Bumping to Temurin JDK 17 resolves this issue, as JDK 17 packages do not have this broken dependency.

✍️ Description

install/apache-guacamole-install.sh: Bumped JAVA_VERSION from "11" to "17" so fresh installs use Temurin JDK 17.
ct/apache-guacamole.sh (update script): Bumped JAVA_VERSION from "11" to "17" so existing containers are upgraded to Temurin JDK 17 on the next update run.

Temurin JDK 17 is a supported LTS release, widely compatible with Apache Guacamole, and installs cleanly on both Debian 12 (Bookworm) and Debian 13 (Trixie) without unresolvable dependency conflicts.

✅ Prerequisites (X in brackets)

Self-review completed – Code follows project standards.
Tested thoroughly – Changes work as expected.
No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

🛠️ Type of Change (X in brackets)

🐞 Bug fix – Resolves an issue without breaking functionality.
✨ New feature – Adds new, non-breaking functionality.
💥 Breaking change – Alters existing functionality in a way that may require updates.
🆕 New script – A fully functional and tested script or script set.
🌍 Website update – Changes to website-related JSON files or metadata.
🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.

Original prompt

This section details on the original issue you should resolve

<issue_title>[Bug]: Apache Guacamole Update fails on Debian 13 (Trixie) due to Temurin JDK 11 dependency (p11-kit)</issue_title>
<issue_description>### ✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

No response

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

Apache Guacamole

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

update in ssh console

⚙️ What settings are you using?

Default Settings
Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

pve-manager/9.1.4/5ac30304265fbd8e (running kernel: 6.17.4-2-pve)

📝 Provide a clear and concise description of the issue.

The update script fails during the Java (Temurin JDK 11) installation phase on Debian 13. The Adoptium repository for "trixie" seems to have a dependency conflict where adoptium-ca-certificates requires p11-kit, but p11-kit is not available as an installation candidate in Debian 13 (it has been replaced/restructured).

Since the script forces the installation of Temurin JDK 11, it exits with code 100/1 when APT cannot satisfy the dependencies.

🔄 Steps to reproduce the issue.

Have an Apache Guacamole LXC running on Debian 13.
Run the update script/command.
The script attempts to verify/install temurin-11-jdk.
Installation fails with: Unsatisfied dependencies: adoptium-ca-certificates : Depends: p11-kit but it is not installable.

❌ Paste the full error output (if available).

    ___                     __               ______                                       __
   /   |  ____  ____ ______/ /_  ___        / ____/_  ______ __________ _____ ___  ____  / /__
  / /| | / __ \/ __ `/ ___/ __ \/ _ \______/ / __/ / / / __ `/ ___/ __ `/ __ `__ \/ __ \/ / _ \
 / ___ |/ /_/ / /_/ / /__/ / / /  __/_____/ /_/ / /_/ / /_/ / /__/ /_/ / / / / / / /_/ / /  __/
/_/  |_/ .___/\__,_/\___/_/ /_/\___/      \____/\__,_/\__,_/\___/\__,_/_/ /_/ /_/\____/_/\___/
      /_/

All packages are up to date.
Get:1 https://packages.adoptium.net/artifactory/deb trixie InRelease [7,503 B]
Get:2 https://packages.adoptium.net/artifactory/deb trixie/main amd64 Packages [10.9 kB]
Fetched 18.4 kB in 1s (33.4 kB/s)
All packages are up to date.
Get:1 https://packages.adoptium.net/artifactory/deb trixie InRelease [7,503 B]
Fetched 7,503 B in 0s (22.6 kB/s)
All packages are up to date.
Solving dependencies... Error!
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

Unsatisfied dependencies:
 adoptium-ca-certificates : Depends: p11-kit but it is not installable
  💡   Package installation failed, retrying (1/2)...
Hit:1 https://packages.adoptium.net/artifactory/deb trixie InRelease
All packages are up to date.
Solving dependencies... Error!
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

Unsatisfied dependencies:
 adoptium-ca-certificates : Depends: p11-kit but it is not installable
  💡   Package installation failed, retrying (2/2)...
Get:1 https://packages.adoptium.net/artifactory/deb trixie InRelease [7,503 B]
Fetched 7,503 B in 0s (24.0 kB/s)
All packages are up to date.
Solving dependencies... Error!
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

Unsatisfied dependencies:
 adoptium-ca-certificates : Depends: p11-kit but it is not installable
  ✖️   Failed to install Temurin JDK 11
  ✖️   in line 54: exit code 1 (General error / Operation not permitted): while executing command return 1

  --- Last 20 lines of log ---
[2026-02-21 22:29:12] [INFO] Setup Temurin JDK 11
[2026-02-21 22:29:13] [WARN] Package installation failed, retrying (1/2)...
[2026-02-21 22:29:16] [WARN] Package installation failed, retrying (2/2)...
[2026-02-21 22:29:18] [ERROR] Failed to install Temurin JDK 11
[2026-02-21 22:29:18] [ERROR] in line 54: exit code 1 (General error / Operation not permitted): while executing command return 1
  -----------------------------------

 📋 Full log: /tmp/create-lxc-5d2e59bd.log
root@apache-guacamole-lxc:/opt/apache-guacamole/tomcat9/webapps# ^C
root@apache-guacamole-lxc:/opt/apache-guacamole/tomcat9/webapps# cat /tmp/create-lxc-5d2e59bd.log
[2026-02-21 22:29:12] [INFO] Setu...

</details>



<!-- START COPILOT CODING AGENT SUFFIX -->

- Fixes community-scripts/ProxmoxVE#12160

<!-- START COPILOT CODING AGENT TIPS -->
---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more [Copilot coding agent tips](https://gh.io/copilot-coding-agent-tips) in the docs.

---

<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

## 📋 Pull Request Information **Original PR:** https://github.com/community-scripts/ProxmoxVE/pull/12161 **Author:** [@Copilot](https://github.com/apps/copilot-swe-agent) **Created:** 2/21/2026 **Status:** ✅ Merged **Merged:** 2/22/2026 **Merged by:** [@michelroegl-brunner](https://github.com/michelroegl-brunner) **Base:** `main` ← **Head:** `copilot/fix-apache-guacamole-update` --- ### 📝 Commits (4) - [`22d75d9`](https://github.com/community-scripts/ProxmoxVE/commit/22d75d95887b3bdf5558fc89655c173898351d4d) Initial plan - [`67afa28`](https://github.com/community-scripts/ProxmoxVE/commit/67afa282780cd9eb8b1624438724a66b72d74772) Fix get_fallback_suite to apply distro mappings before HTTP availability check - [`7026aeb`](https://github.com/community-scripts/ProxmoxVE/commit/7026aeb5c8c6190dfe24e61fcd3bd6196a70ab99) Bump Apache Guacamole from Temurin JDK 11 to JDK 17 - [`a4ab494`](https://github.com/community-scripts/ProxmoxVE/commit/a4ab494fc588255ef412d93dafc8dceeb306a0c0) Revert tools.func changes, keep only Guacamole JDK 11→17 bump ### 📊 Changes **2 files changed** (+2 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `ct/apache-guacamole.sh` (+1 -1) 📝 `install/apache-guacamole-install.sh` (+1 -1) </details> ### 📄 Description On Debian 13 (Trixie), the Apache Guacamole install and update scripts fail because `temurin-11-jdk` from the Adoptium repository carries a broken dependency: `adoptium-ca-certificates` requires `p11-kit`, which is not available in Debian 13. Bumping to Temurin JDK 17 resolves this issue, as JDK 17 packages do not have this broken dependency. ## ✍️ Description - **`install/apache-guacamole-install.sh`**: Bumped `JAVA_VERSION` from `"11"` to `"17"` so fresh installs use Temurin JDK 17. - **`ct/apache-guacamole.sh`** (update script): Bumped `JAVA_VERSION` from `"11"` to `"17"` so existing containers are upgraded to Temurin JDK 17 on the next update run. Temurin JDK 17 is a supported LTS release, widely compatible with Apache Guacamole, and installs cleanly on both Debian 12 (Bookworm) and Debian 13 (Trixie) without unresolvable dependency conflicts. ## ✅ Prerequisites (**X** in brackets) - [X] **Self-review completed** – Code follows project standards. - [X] **Tested thoroughly** – Changes work as expected. - [X] **No security risks** – No hardcoded secrets, unnecessary privilege escalations, or permission issues. --- ## 🛠️ Type of Change (**X** in brackets) - [X] 🐞 **Bug fix** – Resolves an issue without breaking functionality. - [ ] ✨ **New feature** – Adds new, non-breaking functionality. - [ ] 💥 **Breaking change** – Alters existing functionality in a way that may require updates. - [ ] 🆕 **New script** – A fully functional and tested script or script set. - [ ] 🌍 **Website update** – Changes to website-related JSON files or metadata. - [ ] 🔧 **Refactoring / Code Cleanup** – Improves readability or maintainability without changing functionality. - [ ] 📝 **Documentation update** – Changes to `README`, `AppName.md`, `CONTRIBUTING.md`, or other docs.  <details> <summary>Original prompt</summary> ---- *This section details on the original issue you should resolve* <issue_title>[Bug]: Apache Guacamole Update fails on Debian 13 (Trixie) due to Temurin JDK 11 dependency (p11-kit)</issue_title> <issue_description>### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? _No response_ ### 📜 What is the name of the script you are using? Apache Guacamole ### 📂 What was the exact command used to execute the script? update in ssh console ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? pve-manager/9.1.4/5ac30304265fbd8e (running kernel: 6.17.4-2-pve) ### 📝 Provide a clear and concise description of the issue. The update script fails during the Java (Temurin JDK 11) installation phase on Debian 13. The Adoptium repository for "trixie" seems to have a dependency conflict where `adoptium-ca-certificates` requires `p11-kit`, but `p11-kit` is not available as an installation candidate in Debian 13 (it has been replaced/restructured). Since the script forces the installation of Temurin JDK 11, it exits with code 100/1 when APT cannot satisfy the dependencies. ### 🔄 Steps to reproduce the issue. 1. Have an Apache Guacamole LXC running on Debian 13. 2. Run the update script/command. 3. The script attempts to verify/install `temurin-11-jdk`. 4. Installation fails with: `Unsatisfied dependencies: adoptium-ca-certificates : Depends: p11-kit but it is not installable`. ### ❌ Paste the full error output (if available). ``` ___ __ ______ __ / | ____ ____ ______/ /_ ___ / ____/_ ______ __________ _____ ___ ____ / /__ / /| | / __ \/ __ `/ ___/ __ \/ _ \______/ / __/ / / / __ `/ ___/ __ `/ __ `__ \/ __ \/ / _ \ / ___ |/ /_/ / /_/ / /__/ / / / __/_____/ /_/ / /_/ / /_/ / /__/ /_/ / / / / / / /_/ / / __/ /_/ |_/ .___/\__,_/\___/_/ /_/\___/ \____/\__,_/\__,_/\___/\__,_/_/ /_/ /_/\____/_/\___/ /_/ All packages are up to date. Get:1 https://packages.adoptium.net/artifactory/deb trixie InRelease [7,503 B] Get:2 https://packages.adoptium.net/artifactory/deb trixie/main amd64 Packages [10.9 kB] Fetched 18.4 kB in 1s (33.4 kB/s) All packages are up to date. Get:1 https://packages.adoptium.net/artifactory/deb trixie InRelease [7,503 B] Fetched 7,503 B in 0s (22.6 kB/s) All packages are up to date. Solving dependencies... Error! Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: Unsatisfied dependencies: adoptium-ca-certificates : Depends: p11-kit but it is not installable 💡 Package installation failed, retrying (1/2)... Hit:1 https://packages.adoptium.net/artifactory/deb trixie InRelease All packages are up to date. Solving dependencies... Error! Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: Unsatisfied dependencies: adoptium-ca-certificates : Depends: p11-kit but it is not installable 💡 Package installation failed, retrying (2/2)... Get:1 https://packages.adoptium.net/artifactory/deb trixie InRelease [7,503 B] Fetched 7,503 B in 0s (24.0 kB/s) All packages are up to date. Solving dependencies... Error! Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: Unsatisfied dependencies: adoptium-ca-certificates : Depends: p11-kit but it is not installable ✖️ Failed to install Temurin JDK 11 ✖️ in line 54: exit code 1 (General error / Operation not permitted): while executing command return 1 --- Last 20 lines of log --- [2026-02-21 22:29:12] [INFO] Setup Temurin JDK 11 [2026-02-21 22:29:13] [WARN] Package installation failed, retrying (1/2)... [2026-02-21 22:29:16] [WARN] Package installation failed, retrying (2/2)... [2026-02-21 22:29:18] [ERROR] Failed to install Temurin JDK 11 [2026-02-21 22:29:18] [ERROR] in line 54: exit code 1 (General error / Operation not permitted): while executing command return 1 ----------------------------------- 📋 Full log: /tmp/create-lxc-5d2e59bd.log root@apache-guacamole-lxc:/opt/apache-guacamole/tomcat9/webapps# ^C root@apache-guacamole-lxc:/opt/apache-guacamole/tomcat9/webapps# cat /tmp/create-lxc-5d2e59bd.log [2026-02-21 22:29:12] [INFO] Setu... </details>  - Fixes community-scripts/ProxmoxVE#12160  --- 💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more [Copilot coding agent tips](https://gh.io/copilot-coding-agent-tips) in the docs. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

kerem

2026-02-26 17:32:39 +03:00

closed this issue
added the
pull-request
label

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#10009

No description provided.

Rows
Columns