Page 25 of 27
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 6:28 pm
by fehlix
komer wrote: Mon Oct 21, 2019 5:57 pm
fehlix wrote: Mon Oct 21, 2019 5:52 pm
Can you try to adjust the console keyboard layout with
that worked ... I will reboot and see if it is sticky :-)
EDIT: NOPE, it's not. Back to US keyboard after reboot.
can you show /etc/default/keyboard :
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 6:46 pm
by komer
fehlix wrote: Mon Oct 21, 2019 6:28 pm
can you show /etc/default/keyboard :
Code: Select all
┌─[demo@mx1]─[00:32:47]──────────────────────────────────────────[/etc/default]
└─> cat /etc/default/keyboard
# KEYBOARD CONFIGURATION FILE
# Consult the keyboard(5) manual page.
XKBMODEL="pc105"
XKBLAYOUT="hr"
XKBVARIANT=""
XKBOPTIONS="terminate:ctrl_alt_bksp"
BACKSPACE="guess"
┌─[demo@mx1]─[00:45:31]──────────────────────────────────────────[/etc/default]
└─>
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 6:50 pm
by BitJam
komer wrote: Mon Oct 21, 2019 5:57 pmEDIT: NOPE, it's not. Back to US keyboard after reboot.
What is in the file /proc/cmdline? These are the boot parameters and one of them may be over-riding your "manual"
keyboard layout selection. For example, if lang= is used then we automatically set the language, timezone, keyboard layout, and maybe other things. If you have lang= and you don't like the keyboard layout then use the following cheats
kbd= kbopt= kbvar= to specify your keyboard layout, options, and variant.
I believe this works by us writing the file /etc/default/keyboard. This is used by X and the setupcon program magically uses this information to set the console keyboard layouts as well.
So I think there are two approaches. One is to specify the language and the keyboard information in live boot parameters that you save to the live bootloader. The other is to rely on persistence and not use any of these parameters because by so doing you will end up over-writing your persistent settings.
This has been tripping a lot of people up. Maybe there could be a better way. For example we could have a
lang_only= cheat that only sets the language. Or only sets the language for the early boot process. And if we see that persistence is enabled then we can automatically convert lang= to lang_only=.
I'm sorry this has been difficult for you. You're not the only one. We try very hard to make the live system as easy to configure as possible but it looks like the way we are handling the keyboard is not optimal.
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 6:59 pm
by fehlix
komer wrote: Mon Oct 21, 2019 6:46 pm
fehlix wrote: Mon Oct 21, 2019 6:28 pm
can you show /etc/default/keyboard :
Code: Select all
┌─[demo@mx1]─[00:32:47]──────────────────────────────────────────[/etc/default]
└─> cat /etc/default/keyboard
# KEYBOARD CONFIGURATION FILE
# Consult the keyboard(5) manual page.
XKBMODEL="pc105"
XKBLAYOUT="hr"
XKBVARIANT=""
XKBOPTIONS="terminate:ctrl_alt_bksp"
BACKSPACE="guess"
┌─[demo@mx1]─[00:45:31]──────────────────────────────────────────[/etc/default]
└─>
Right, so it show exact just one (and not two or more) keyboard layout, and this one shall default to the console keyboard.
Hmme not sure what's wrong ..
And when you run with Xfce Terminal
dooes it show somwthing like :
Code: Select all
model: pc105
layout: hr
variant:
options: terminate:ctrl_alt_bksp
Perhaps open console again Ctrl-Alt-F1
and
Code: Select all
sudo service keyboard-setup restart
The last line is actually what is done when you reboot, so it should set the console keyboard to the default defined within /etc/default/keyboard.
Actually I changed just now, the system-default console and run "service keyboard-setup restart"
a couple of times, and it always changed the console keyboard.
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 7:04 pm
by fehlix
BitJam wrote: Mon Oct 21, 2019 6:50 pm
What is in the file /proc/cmdline? These are the boot parameters and one of them may be over-riding your "manual"
keyboard layout selection.
yes, of course, I forgot the boot parameter ...
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 7:07 pm
by komer
BitJam wrote: Mon Oct 21, 2019 6:50 pm
komer wrote: Mon Oct 21, 2019 5:57 pmEDIT: NOPE, it's not. Back to US keyboard after reboot.
What is in the file /proc/cmdline? These are the boot parameters and one of them may be over-riding your "manual"
keyboard layout selection.
Code: Select all
┌─[demo@mx1]─[00:54:57]─────────────────────────────────────────────────────[~]
└─> cat /proc/cmdline
persist_static tz=Europe/Berlin quiet splasht
┌─[demo@mx1]─[00:55:04]─────────────────────────────────────────────────────[~]
└─>
I don't think time zone should conflict with anything. Should I remove that option in live persistence settings?
So I think there are two approaches. One is to specify the language and the keyboard information in live boot parameters that you save to the live bootloader.
How would one do that? I didn't mess up a lot with those options. I just like to set basic stuff.
The other is to rely on persistence and not use any of these parameters because by so doing you will end up over-writing your persistent settings.
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 7:38 pm
by fehlix
komer wrote: Mon Oct 21, 2019 7:07 pm
How would one do that?
With the BIOS-boot menu you add kbd=hr to the boot option line and select F8 "save", so the the next boot shall be have the kbd-boot option already.
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 7:40 pm
by BitJam
komer wrote: Mon Oct 21, 2019 7:07 pm
Code: Select all
$ cat /proc/cmdline
persist_static tz=Europe/Berlin quiet splasht
Thanks!
Quick tip: If you want to copy and paste with fancy-prompts enabled, first run "prompt-tiny". This will create a tiny prompt. When you are done go back to your usual prompt with "prompt-fancy" or whatever variant you're using. This is a very useful and powerful feature of fancy-prompts.
I don't think time zone should conflict with anything.
I agree. It only controls the timezone and the automatic repo selection based on the timezone.
Should I remove that option in live persistence settings?
I don't think that will help.
Let me think about this. ISTM your settings are either not getting saved or they are getting clobbered during the live boot. H'mm. It's also possible that we are not running /etc/init.d/console-setup on your live boots. Yes, this may be the problem.
Even though I may be covering old ground, after you boot try runnig:
and see if that fixes things.
The problem is that I'm only running that during the live boot if one of the variables like lang= or kbd= are set. This is because setupcon can take a lot of time to run and if someone has a default system we waste a second or so of boot time for no good reason. But this doesn't work for people like you who have used persistence to change these settings and have not used a boot parameter.
Perhaps the mistake we made was ASSuming the results of setupcon were saved in files that were saved with persistence. But if it is only running programs like loadkeys then it needs to be run on every boot in order to work.
One quick fix would be to add a "setupcon" boot parameter that will cause setupcon to always run. We could also always run setupcon but that seems like a bad solution for all the people who don't need it.
PS: I think the "kbd=hr" fix fehlix proposed will also work.
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 7:56 pm
by BitJam
komer wrote: Mon Oct 21, 2019 7:07 pmI just like to set basic stuff.
If running "sudo /bin/setupcon -k" fixes things then I have a solution that does not require you to change your boot parameters. If you are comfortable with the command line, I can give you simple instructions on how to implement it. but first we must see if the command above fixes the problem.
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 8:43 pm
by komer
BitJam wrote: Mon Oct 21, 2019 7:56 pm
komer wrote: Mon Oct 21, 2019 7:07 pmI just like to set basic stuff.
If running "sudo /bin/setupcon -k" fixes things then I have a solution that does not require you to change your boot parameters. If you are comfortable with the command line, I can give you simple instructions on how to implement it. but first we must see if the command above fixes the problem.
Tnx for the tip.
"sudo /bin/setupcon -k" worked.