I have a password set on linuxswap.
The password has the symbol «‘». If I press it on the keyboard, it is not displayed in the input field.
Only if I press first «’», and then any other symbol (once), then the symbol «‘» is displayed together with what I just entered. That is, at first it is not visible, and then two symbols are visible at once. At the moment, I first enter the symbol «’», then any other, delete this other and then enter the password.
Naturally, the symbols are hidden and only round symbols are displayed instead (hiding the password «•»). Is it possible to somehow fix this in the future?
This happened after the update on 05-03-2025
There is several chars which looks similiar but are not the same.
One of them is a single quote
The other two are accents.
The accents are usually deadkeys - meaning they will only be echoed when the accented character is entered.
From your description you are entering the wrong char - could be caused by not having a FONT_MAP=<fontmap> in /etc/vconsole.conf which then causes the LUKS passphrase input to fall back to us keymap.
1 Like
It would be strange or impossible to have worked before, but not anymore after the update. 
I can’t type that character on my keyboard (nodeadkeys)
It looks like it’s a backtick or a fancy apostrophe? I don’t even know how to type the latter.
However, if it’s a deadkey, the key (hehe) to type that is to press space after the button in question.
The best option, however, would be to only use the common alphabet A-Z, a-z, 0-9, and maybe the special keys .,- or the ones which you can remember and type it in any* keyboard layout.
(*: Mainly your locale, en_US, and with/without dead keys).
3 Likes
According to mate’s character map it’s a “left single quotation mark” aka U2018
Or press the deadkey twice.
1 Like
His problem is not how to type it.
His problem appears to be that he could type it without “special effort” or “distortions” prior to the update.
output of:
localectl
would help
and output of:
grep ^HOOKS /etc/mkinitcpio.conf
The update alone should not have changed anything - perhaps (improper) merging of some .pacnew files was also involved?
1 Like
I am speculating how you have achieved tthe graphical prompt for passphrase.
I am also speculating why you have swap encrypted with a different passphrase.
Plymouth has not been updated since May 7. 2024 and to my knowledge that plymouth version 22.02.122 does not provide the graphical prompt on Manjaro.
To have a graphical input - you wil lhave to use Plymouth 24.004.60 which is only available from unstable branch (and Arch).
$ mbn info plymouth -q | grep -e Branch -e 'Version' -e 'Build Date'
Branch : archlinux
Version : 24.004.60-10
Build Date : Thu 19 Dec 2024 01:39:37
Branch : unstable
Version : 24.004.60-12
Build Date : Mon 30 Dec 2024 01:06:01
Branch : testing
Version : 22.02.122-18
Build Date : Tue 07 May 2024 16:47:12
Branch : stable
Version : 22.02.122-18
Build Date : Tue 07 May 2024 16:47:12
Yes, you are right. Before the update I could type this symbol without any effort. On my keyboard it is accessible without any effort. Moreover, this same symbol is present in my password for the main luks section. And it is entered normally. It would be very painful if it stopped working there too.
The char is a single quote not a backtick or diacritiic (which is tilted the left or the right).
You should check your /etc/vconsole.conf and ensure the correct values are present.
Then rebuild init
sudo mkinitcpio -P
Well - to diagnose this, how about:
?
It should not have happened - but it apparently did.
And now the cause needs to be found or the issue otherwise diagnosed and sorted.
Operating System: Manjaro Linux
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.14.0-rc4-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i3-9100F CPU @ 3.60GHz
Memory: 15.6 GiB of RAM
Graphics Processor: AMD Radeon RX 470 Graphics
How I got a graphical interface for entering a password is a separate story.
I installed a regular Manjaro Linux build. Then, I did something wrong with the swap file or did not password protect it. Although, I still do not understand whether a password is set on it if I use luks encryption for the main partition. I have: the main partition, swap file and 8 MB just in case of empty space.
Due to the question that arose: whether a password is set on linuxswap, I decided to set a password separately. Using some utility, I deleted the linuxswap partition and created it again, with the same password as the main partition. Since then, when booting the system, I enter two passwords: one for the main luks partition, and the second for linuxswap.
Before the recent update, the password was entered without any difficulties. But after, I could not enter «'» normally.
localectl
System Locale: LANG=en_US.UTF-8
VC Keymap: us-acentos
X11 Layout: us
X11 Model: pc105
grep ^HOOKS /etc/mkinitcpio.conf ✔
grep: Desktop: Is a directory
grep: Documents: Is a directory
grep: Downloads: Is a directory
grep: Music: Is a directory
grep: Pictures: Is a directory
grep: Soft: Is a directory
grep: Videos: Is a directory
grep: _W: Is a directory
that can’t be right
None of that is in /etc/mkinitcpio.conf
less /etc/mkinitcpio.conf
and scroll down and have a look at the HOOKS line
HOOKS=(base udev autodetect kms modconf block keyboard keymap consolefont plymouth resume filesystems)
… that (above) actually looks as it should
This keymap allows you to type that character - with only one key stroke - when you are in a TTY?
right now - when you change to a TTY and log in there?
CTRL+F4 (for example)
Does it?
I have never seen this keymap - and, perhaps obviously, do not have such a keyboard, so I can’t even try to test …
ps:
as @linux-aarhus said:
look at /etc/vconsole.conf
1 Like
It’s my life
This symbol appears in this phrase.
apostrophe
# Written by systemd-localed(8) or systemd-firstboot(1), read by systemd-localed
# and systemd-vconsole-setup(8). Use localectl(1) to update this file.
KEYMAP=us-acentos
XKBLAYOUT=us
XKBMODEL=pc105
No.
you said the character is this:
´
When I type:
It's my life
that character is a different one than in your example:
It’s my life
… it’s a different glyph - it just looks similar …
and one does not use an apostrophe to write that …
an apostrope is not a character that is written on it’s own - only in conjunction with other characters
I’d simply change the password on the encrypted swap partition - to ease the pain 
3 Likes
For reference - this is how my vconsole.conf is populated
$ cat /etc/vconsole.conf
# Written by systemd-localed(8) or systemd-firstboot(1), read by systemd-localed
# and systemd-vconsole-setup(8). Use localectl(1) to update this file.
KEYMAP=dk
FONT=lat2-16
FONT_MAP=8859-1
XKBLAYOUT=dk
XKBMODEL=pc105
XKBOPTIONS=terminate:ctrl_alt_bksp
This is a good example - the first on is a single quote char - the second is a diacritic when it tilts to the right - and that char is an accent - which is usually a deadkey - it can stand alone as the exampel shows but you have to type a space after the diacritic for a standalone to happen.
2 Likes
Thank you guys for your help.