Login Password Devuan 4 requires US key for #

swarfendor437 · 2021-12-18 19:32:48

I installed choosing English Language, English UK and English-GB keyboard layout.
However, as # is part of my password I need to press shift and 3 to get the hash key instead of the hash key!
Any way to resolve this? Thanks.

Head_on_a_Stick · 2021-12-18 19:43:27

Can we see the content of /etc/default/keyboard?

Try

# apt install console-setup
# dpkg-reconfigure keyboard-configuration

And make sure the desired options are selected.

swarfendor437 · 2021-12-18 20:33:13

Thanks for responding Head_on_a_Stick.

Here are the contents of /etc/default/keyboard:

# KEYBOARD CONFIGURATION FILE

# Consult the keyboard(5) manual page.

XKBMODEL="pc105"
XKBLAYOUT="gb"
XKBVARIANT=""
XKBOPTIONS=""

BACKSPACE="guess"

Results of those commands you posted:

root@devuanfour:/home/swarfendor437# apt install console-setup
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
console-setup is already the newest version (1.205).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@devuanfour:/home/swarfendor437# dpkg-reconfigure keyboard-configuration
bash: dpkg-reconfigure: command not found
root@devuanfour:/home/swarfendor437# dpkg-reconfigure keyboard-configuration
bash: dpkg-reconfigure: command not found
root@devuanfour:/home/swarfendor437#

Last edited by swarfendor437 (2021-12-18 20:35:31)

Head_on_a_Stick · 2021-12-18 20:38:07

swarfendor437 wrote:

root@devuanfour:/home/swarfendor437# dpkg-reconfigure keyboard-configuration
bash: dpkg-reconfigure: command not found

So you haven't read the release notes then?

Use either sudo -i or su - to obtain a root shell. For the second command the - is important

swarfendor437 · 2021-12-18 21:33:31

Oops! What a lazy boy I am!

OK, changed to what the installer pointed to, 101-pc as I noticed 105-pc had (Intl.) [International] and guessed this was the issue. Made changes, rebooted but still have to use Shift+ 3 to get '#'.

Head_on_a_Stick · 2021-12-18 22:24:06

pc105 should be fine, that's what I have in /etc/default/keyboard.

Are you experiencing this problem in both the console (TTY) and graphical desktops?

EDIT: does this fix things in the graphical environment:

setxkbmap gb

Last edited by Head_on_a_Stick (2021-12-18 22:26:08)

swarfendor437 · 2021-12-19 14:55:40

Head_on_a_Stick wrote:

pc105 should be fine, that's what I have in /etc/default/keyboard.
Are you experiencing this problem in both the console (TTY) and graphical desktops?
EDIT: does this fix things in the graphical environment:
setxkbmap gb

I can use the # key as normal as i have it in Root password in GUI (Synaptic Package Manager authorizaton box) and when using su - just user login.
Tried the last command you gave me, rebooted and still the same.

Head_on_a_Stick · 2021-12-19 15:42:03

The setxkbmap command does not persist between reboots.

swarfendor437 wrote:

I can use the # key as normal as i have it in Root password in GUI (Synaptic Package Manager authorizaton box) and when using su - just user login.

Sorry but I do not understand this sentence.

Please try to explain the exact situation in which you experience the problem more fully. Include as much detail as possible. Thanks.

swarfendor437 · 2021-12-19 20:46:08

OK, I boot into Devuan and arrive at the Login page. I select my user. I enter my user password setup during install which has the hash sign within it. The hash sign is also present in my root user password. Ironically, if I leave the machine for some time and it logs me out, I can enter my password with the hash key - but not at login! If I use the hash key in root user password when using Synaptic Package Manager, no issue, and no issue when using root password that has a hash key when using 'su' in the terminal. It is just at initial login! If I uncheck the hide password, if I press the hash key [#] on the keyboard I get '/' - I have to use Shift plus 3 to get '#'

Last edited by swarfendor437 (2021-12-19 20:47:06)

Head_on_a_Stick · 2021-12-19 20:55:44

Perhaps try https://bbs.archlinux.org/viewtopic.php?id=245451

I think localectl(1) is meant to handle this in Debian but it's part of systemd. For Devuan you may have to create the X.Org configuration file manually (as per the linked thread).

swarfendor437 · 2021-12-19 21:39:42

Tried that - changed 20 to 40 and made the Xkblayout to "gb" - still no joy. Made a mistake in last post, instead of '#' when I press the # key it shows '\' and not '/'

Last edited by swarfendor437 (2021-12-19 21:40:10)

Head_on_a_Stick · 2021-12-20 05:52:56

swarfendor437 wrote:

changed 20 to 40

I have no idea what this means.

Please share the exact, full contents of the configuration file along with it's precise location and also share the full X.Org & display manager (LightDM?) logs. Remember to use code tags when posting terminal output and perhaps consider using a pastebin and sharing a link here if the logs are large. Thanks.

globalgoldfish · 2021-12-20 14:27:47

swarfendor437 wrote:

... if I leave the machine for some time and it logs me out, I can enter my password with the hash key - but not at login!

Before you log in, your user preferences are not known. Try this:

After logging in, change to a console (e.g., Ctrl-Alt-F1) and log in as root – you'll probably have to use Shift-3 for the # symbol. Having logged in, run dpkg-reconfigure keyboard-configuration again. This shouldn't be necessary, but ... just to be sure.

Now run setupcon to have the your default keyboard settings applied to the console. After that, you should get a # on the console when you press that key; Shift-3 should give you £. Now try rebooting and see what you get at the login screen.

Incidentally, I agree with what's been said – pc105 and gb for a standard UK keyboard.

Head_on_a_Stick · 2021-12-20 15:26:56

globalgoldfish wrote:

Now run setupcon to have the your default keyboard settings applied to the console.

The console-setup package is supposed to ensure that the desktop & console keyboard settings are the same.

Reference: https://salsa.debian.org/installer-team … tinst#L133

globalgoldfish · 2021-12-20 15:55:05

Head_on_a_Stick wrote:

globalgoldfish wrote:
Now run setupcon to have the your default keyboard settings applied to the console.
The console-setup package is supposed to ...

Agreed. The console is also supposed to follow /etc/default/keyboard at boot, but it doesn't. At least, it doesn't here. I just suggested the steps that I took to get my keyboard preference everywhere – X session, user and root tty, and login screen.

The standard installer generally sets all this, only asking once. The Devuan desktop live doesn't, which is where I came across a similar situation to the OP.

swarfendor437 · 2021-12-20 22:22:18

globalgoldfish wrote:

swarfendor437 wrote:
... if I leave the machine for some time and it logs me out, I can enter my password with the hash key - but not at login!
Before you log in, your user preferences are not known. Try this:
After logging in, change to a console (e.g., Ctrl-Alt-F1) and log in as root – you'll probably have to use Shift-3 for the # symbol. Having logged in, run dpkg-reconfigure keyboard-configuration again. This shouldn't be necessary, but ... just to be sure.
Now run setupcon to have the your default keyboard settings applied to the console. After that, you should get a # on the console when you press that key; Shift-3 should give you £. Now try rebooting and see what you get at the login screen.
Incidentally, I agree with what's been said – pc105 and gb for a standard UK keyboard.

After logging in and press key combination of Ctrl+ Alt+ F1 I don't get a console but back to login screen after a brief black screen with my login details.
Just also to mention that after a recent login I briefly saw during the scrolling consol on populating devs etc there was reference to a

... dirty bit ...

Is this indication of a hard drive error? I only replaced the last failing drive this March with a WD Gold which is supposed to be built for machines to be on 24/7. it sounds like a Hitachi 'DeathStar' (deskstar) drive at times.

swarfendor437 · 2021-12-20 22:27:20

Head_on_a_Stick wrote:

swarfendor437 wrote:
changed 20 to 40
I have no idea what this means.
Please share the exact, full contents of the configuration file along with it's precise location and also share the full X.Org & display manager (LightDM?) logs. Remember to use code tags when posting terminal output and perhaps consider using a pastebin and sharing a link here if the logs are large. Thanks.

I followed your link to that article - there was no config file - there was just the xorg.conf.d folder with nothing in it.

I copied the entry you gave a link to [https://bbs.archlinux.org/viewtopic.php?id=245451].
In that file there was reference to "20" - when using older versions of GNU/Linux I remembered that en-gb used to be listed as number "40" which is why I changed the number from that original post and replaced "de" in that post with "gb". Should it have been "en-gb"?

Head_on_a_Stick · 2021-12-20 22:40:52

Any reason why you're not sharing the actual file? I would think that would be easier than posting a vague description.

Anyway, here's what systemd created in my Arch box:

archie:~$ cat /etc/X11/xorg.conf.d/00-keyboard.conf  
# Written by systemd-localed(8), read by systemd-localed and Xorg. It's
# probably wise not to edit this file manually. Use localectl(1) to
# instruct systemd-localed to update it.
Section "InputClass"
        Identifier "system-keyboard"
        MatchIsKeyboard "on"
        Option "XkbLayout" "gb"
EndSection
archie:~$

Try that.

EDIT: the name of the file isn't really important. It needs to end in .conf and the files are read in lexicographical order but you shouldn't have any conflicts anyway.

Last edited by Head_on_a_Stick (2021-12-20 22:42:23)

globalgoldfish · 2021-12-21 10:24:12

Adding to xorg.conf is a red herring, imo – there's no issue with the keyboard layout in X, or after X has started, e.g., unlocking the screensaver.

swarfendor437 wrote:

After logging in and press key combination of Ctrl+ Alt+ F1 I don't get a console but back to login screen after a brief black screen with my login details.

That is not normal. What about with the other virtual consoles (Ctrl-Alt-F2 to -F6)? It this a standard desktop keyboard or a laptop with other functions on the Fn keys? Do you have proprietary (i.e., nVidia) graphics?

swarfendor437 wrote:

... there was reference to a
... dirty bit ...

Dirty filesystem, usually caused by abruptly switching off instead of shutting down gracefully. Should be fixable by fsck, but the partition must be unmounted to do that.

Edit: typo.

Last edited by globalgoldfish (2021-12-21 10:25:19)

swarfendor437 · 2021-12-21 10:53:46

Head_on_a_Stick wrote:

Any reason why you're not sharing the actual file? I would think that would be easier than posting a vague description.
Anyway, here's what systemd created in my Arch box:
archie:~$ cat /etc/X11/xorg.conf.d/00-keyboard.conf  
# Written by systemd-localed(8), read by systemd-localed and Xorg. It's
# probably wise not to edit this file manually. Use localectl(1) to
# instruct systemd-localed to update it.
Section "InputClass"
        Identifier "system-keyboard"
        MatchIsKeyboard "on"
        Option "XkbLayout" "gb"
EndSection
archie:~$
Try that.
EDIT: the name of the file isn't really important. It needs to end in .conf and the files are read in lexicographical order but you shouldn't have any conflicts anyway.

Here is the entries from the file:

Section "InputClass"
Identifier "keyboard"
MatchIsKeyboard "yes"
Option "XkbLayout" "gb"
Option "XKbVariant" "nodeadkeys"
EndSection

That's strange, I was sure I put 40 in there somewhere. I named the file 40-keyboard.conf and it is located in /etc/X11/xorg.conf.d

swarfendor437 · 2021-12-21 10:57:55

globalgoldfish wrote:

Adding to xorg.conf is a red herring, imo – there's no issue with the keyboard layout in X, or after X has started, e.g., unlocking the screensaver.
swarfendor437 wrote:
After logging in and press key combination of Ctrl+ Alt+ F1 I don't get a console but back to login screen after a brief black screen with my login details.
That is not normal. What about with the other virtual consoles (Ctrl-Alt-F2 to -F6)? It this a standard desktop keyboard or a laptop with other functions on the Fn keys? Do you have proprietary (i.e., nVidia) graphics?
swarfendor437 wrote:
... there was reference to a
... dirty bit ...
Dirty filesystem, usually caused by abruptly switching off instead of shutting down gracefully. Should be fixable by fsck, but the partition must be unmounted to do that.
Edit: typo.

This is a desktop pc that previously had Devuan 3.0 then I 'upgraded' or rather installed Devuan 3.1.1 after the drive Devuan 3.0 was on started to die. Tried to do an upgrade to 4.0 from 3.1.1 but that went disastrously wrong. On this install I have chosen the following layouts:
1. Devuan default (LXQt)
2. Gnome flashback
3. LXQt
4. KDE (Plasma) - this is the DE I use each day.

The keyboard is a Cherry DW 9000 SLIM keyboard with mouse - both wireless. No keyboard or password issues in Devuan 3.0 or 3.1.1. - will get back to you regarding other Fn keys.

Update - Fn 2 through Fn 6 just displays a flashing underscore on a black screen, no tty login - reinstall?

I've never liked nVidia proprietary drivers as they always gave me a poor experience, especially in Firefox, but now that Firefox no longer supports ALSA I won't be using it in future and will be removing Firefox ESR and replace with epiphany and possibly FlashPeak Slimjet browser as alternatives.

Last edited by swarfendor437 (2021-12-21 11:03:04)

Head_on_a_Stick · 2021-12-21 11:17:38

Off topic but:

swarfendor437 wrote:

now that Firefox no longer supports ALSA

Not sure why you think that but Firefox supports pure ALSA just fine.

EDIT: proof here for the latest ESR version.

On topic: which display manager is this? If it's SLiM then change to either GDM (preferred) or LightDM.

As for your TTY issue does this work:

# chvt 4

If it does test the keyboard layout there and report back.

Last edited by Head_on_a_Stick (2021-12-21 11:20:08)

swarfendor437 · 2021-12-21 11:28:23

I always choose GDM.

# chvt 4

Same result as Fn keys 1 through 6 - flashing line and no tty login. Thanks.

Sorry for the off-topic - will post elsewhere.

Last edited by swarfendor437 (2021-12-21 11:29:15)

Head_on_a_Stick · 2021-12-21 12:03:13

Do you have /etc/inittab? If so then please share it here.

EDIT: right I've set up a VM and installed Devuan 4 from the netinstall ISO with your desktops and GDM3 and I can reproduce this error in a fresh system. The TTYs work though

When I try to add a keyboard via gnome-control-center it gives this error message:

Could not get 'org.freedesktop.locale1.set-locale' permission: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.locale1.set-locale is not registered

That action is supplied by systemd:

https://manpages.debian.org/bullseye/sy … .5.en.html

^ That man page does not exist in Devuan, for obvious reasons.

So it seems that systemd is now required for the correct (ie, non-US) keyboard configuration in GDM3.

Time to take this to the Devuan developers, there's nothing we can do here (IMO). When submitting the bug report be sure to link to this thread for background.

Last edited by Head_on_a_Stick (2021-12-21 12:47:56)

swarfendor437 · 2021-12-21 13:16:58

Hi Head_on_a_Stick, Many thanks for your investigations on this. I don't have inittab in /etc, only init.d and initramfs-tools. Will report bug as suggested.

The officially official Devuan Forum!

#1 2021-12-18 19:32:48

Login Password Devuan 4 requires US key for #

#2 2021-12-18 19:43:27

Re: Login Password Devuan 4 requires US key for #

#3 2021-12-18 20:33:13

Re: Login Password Devuan 4 requires US key for #

#4 2021-12-18 20:38:07

Re: Login Password Devuan 4 requires US key for #

#5 2021-12-18 21:33:31

Re: Login Password Devuan 4 requires US key for #

#6 2021-12-18 22:24:06

Re: Login Password Devuan 4 requires US key for #

#7 2021-12-19 14:55:40

Re: Login Password Devuan 4 requires US key for #

#8 2021-12-19 15:42:03

Re: Login Password Devuan 4 requires US key for #

#9 2021-12-19 20:46:08

Re: Login Password Devuan 4 requires US key for #

#10 2021-12-19 20:55:44

Re: Login Password Devuan 4 requires US key for #

#11 2021-12-19 21:39:42

Re: Login Password Devuan 4 requires US key for #

#12 2021-12-20 05:52:56

Re: Login Password Devuan 4 requires US key for #

#13 2021-12-20 14:27:47

Re: Login Password Devuan 4 requires US key for #

#14 2021-12-20 15:26:56

Re: Login Password Devuan 4 requires US key for #

#15 2021-12-20 15:55:05

Re: Login Password Devuan 4 requires US key for #

#16 2021-12-20 22:22:18

Re: Login Password Devuan 4 requires US key for #

#17 2021-12-20 22:27:20

Re: Login Password Devuan 4 requires US key for #

#18 2021-12-20 22:40:52

Re: Login Password Devuan 4 requires US key for #

#19 2021-12-21 10:24:12

Re: Login Password Devuan 4 requires US key for #

#20 2021-12-21 10:53:46

Re: Login Password Devuan 4 requires US key for #

#21 2021-12-21 10:57:55

Re: Login Password Devuan 4 requires US key for #

#22 2021-12-21 11:17:38

Re: Login Password Devuan 4 requires US key for #

#23 2021-12-21 11:28:23

Re: Login Password Devuan 4 requires US key for #

#24 2021-12-21 12:03:13

Re: Login Password Devuan 4 requires US key for #

#25 2021-12-21 13:16:58

Re: Login Password Devuan 4 requires US key for #

Board footer