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 11 Packages Projects Releases 10 Wiki Activity

Keyboard Layout Issue in Nextcloud VM Script Installation (Turnkey Linux) #75

New Issue
Closed
opened 2026-02-04 16:27:54 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-04 16:27:54 +03:00
Owner
Copy Link

Originally created by @Levtos on GitHub (Nov 19, 2024).

Please verify that you have read and understood the guidelines.

yes

A clear and concise description of the issue.

During the installation of the Proxmox VE Nextcloud VM using the provided script, I encountered an issue related to the keyboard layout. The script seems to default to a US keyboard layout during the setup process. However, after the installation is complete and the keyboard layout is switched to another layout (e.g., German), passwords that include special characters no longer work due to the change in symbol mapping.

This makes it impossible to log in with the originally configured password if special characters (e.g., @, =, ) are used, as they are interpreted differently after the layout switch.

What settings are you currently utilizing?

Default Settings

Which Linux distribution are you employing?

Debian 12

If relevant, including screenshots or a code block can be helpful in clarifying the issue.

No response

Please provide detailed steps to reproduce the issue.

No response

Originally created by @Levtos on GitHub (Nov 19, 2024). ### Please verify that you have read and understood the guidelines. yes ### A clear and concise description of the issue. During the installation of the Proxmox VE Nextcloud VM using the provided script, I encountered an issue related to the keyboard layout. The script seems to default to a US keyboard layout during the setup process. However, after the installation is complete and the keyboard layout is switched to another layout (e.g., German), passwords that include special characters no longer work due to the change in symbol mapping. This makes it impossible to log in with the originally configured password if special characters (e.g., @, =, \) are used, as they are interpreted differently after the layout switch. ### What settings are you currently utilizing? Default Settings ### Which Linux distribution are you employing? Debian 12 ### If relevant, including screenshots or a code block can be helpful in clarifying the issue. _No response_ ### Please provide detailed steps to reproduce the issue. _No response_
OVERLORD added the not a script issue label 2026-02-04 16:27:54 +03:00
OVERLORD commented 2026-02-04 16:28:03 +03:00
Author
Owner
Copy Link

@havardthom commented on GitHub (Nov 20, 2024):

Are you talking about the passwords during Turnkey Linux setup? I don't think we can do anything about that. Our script just creates the VM with the bootdisk which contains the Turnkey ISO image. Turnkey linux forums might be able to help https://www.turnkeylinux.org/forum

@havardthom commented on GitHub (Nov 20, 2024): Are you talking about the passwords during Turnkey Linux setup? I don't think we can do anything about that. Our script just creates the VM with the bootdisk which contains the Turnkey ISO image. Turnkey linux forums might be able to help https://www.turnkeylinux.org/forum
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
question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label not a script issue
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#75
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?