@ Arnaud

You also chose french keyboard while installing Mageia 2 Alpha 1?

Which install medium did you use?
Did you install all updates?

CC: (none) => marja11
Assignee: bugsquad => thierry.vignaud
Source RPM: (none) => drakx-kbd-mouse-x11

Hmm, I should have read bug 3471 before reading this one!

I understand you installed Mageia-2-alpha1-LiveCD-GNOME-Europe1-Americas-i586-CD
and could only choose English during install.

Have you now installed the French locales?

@ Thierry, I don't know enough about locales. Can you install any keyboard, regardless of which locales you use?

hi,

Yes, i hav install "locale-fr" all my system is now in french

When i select french keyboard it is run okay but when i restart only the keyboard come back in english (but in CCM menu it was still french selected)

Hi,

I have the same thing here. I start mageia, automatic login with KDE. English layout is selected for the keyboard. I select french keyboard ant it is run okay. If I restart the keyboard come back in english...

CC: (none) => thibautf

The problem was solved, but it occurs again for 4 or 5 days with a cauldron up to date.

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

The bug is still valid for Mageia 2.

The problem is seen on a Fujitsu desktop PC with a Logitech wireless USB keyboard. The keyboard layout is Norwegian, which is also selected in the control panel.

After every boot or logout/login the following must be done to reset the keyboard layout:
Mageia Control Center | Hardware | Configure keyboard | ("Norwegian" is already selected) | Click "OK"

The problem does not exist on a Thinkpad T60 laptop with Norwegian keyboard.

CC: (none) => arberg
Version: Cauldron => 2

Also fails on Mageia 3 alpha 3, booted from Mageia-3-alpha3-LiveDVD-KDE4-i586-DVD.iso

Version: 2 => Cauldron
Whiteboard: (none) => mga2 3alpha3

Another observation: If I change the keyboard type in the control centre from "Generic | 105-key (Intl) PC" to "Generic | 102-key (Intl) PC", the language setting is not lost any more. Tested on Mageia 2.

The keyboard has "Menu" and "Microsoft" keys, so I guess it should not be detected as 102key.

This must be a release blocker with major severity. We cannot release a new Mageia with this problem

Priority: Normal => release_blocker
Severity: normal => major

Annoying without any doubts.Still not release_blocker as it can be fixed at any time. Adding it in a list to give it high priority after Mageia 3 is out

Priority: release_blocker => High
CC: (none) => ennael1

This can likely be fixed with a few debus calls to localed in the control centre.

CC: (none) => mageia

NB This bug was filed against gnome live install, so presumably gnome desktop, but are you using mga control centre or gnome control centre to set the keyboard settings. If you use gnome tools it should all work fine. You can even copy the user settings to the system settings there.

(In reply to Anne Nicolas from comment #12)
> Annoying without any doubts.Still not release_blocker as it can be fixed at
> any time. Adding it in a list to give it high priority after Mageia 3 is out

Which means that you have to change keyboard settings each and every time you log in to your system. 

If this problem is not solved before final release Mageia should certainly NOT state in a release announcement that Mga 3 supports e.g. danish language. And for any other language with special characters. How can you say that this is not a release blocker? Have you ever actually used Mga 3 betas with other language than english?

(In reply to Hans Micheelsen from comment #15)
> If this problem is not solved before final release Mageia should certainly
> NOT state in a release announcement that Mga 3 supports e.g. danish
> language. And for any other language with special characters. How can you
> say that this is not a release blocker? Have you ever actually used Mga 3
> betas with other language than english?

Yes, I do that every day :) But I'm using KDE. You didn't answer how did you change your keyboard settings.

And it isn't release blocker as it can be fixed with update after release (if we can figure out what is going on and why it doesn't work).

CC: (none) => sander.lepik

FWIW, I strongly suspect you can use localectl to set things up properly (this is effectively what gnome's system settings effectively uses (it uses the dbus calls directly tho')

e.g. localectl set-x11-keymap fr

will set the x11 keymap to French. It will ask for authorisation via polkit before writing out the file /etc/X11/xorg.conf.d/00-keyboard.conf which makes the change permanent.

Just need to hook up the control centre to write that file.

that said IIRC we should have some udev rules which set the keyboard settings from /etc/sysconfig/keyboard also. Can you confirm the following:
 1. Do you have /etc/sysconfig/keyboard and if so what are it's contents?
 2. Do you have a /etc/X11/xorg.conf.d/00-keyboard.conf and if so what are it's contents.
 3. Does running localectl set-x11-keymap work for you and produce/edit the above file? Does rebooting make things "Just work"?
 4. What interface are you using to configure the keyboard?

(In reply to Sander Lepik from comment #16)
> (In reply to Hans Micheelsen from comment #15)
> > If this problem is not solved before final release Mageia should certainly
> > NOT state in a release announcement that Mga 3 supports e.g. danish
> > language. And for any other language with special characters. How can you
> > say that this is not a release blocker? Have you ever actually used Mga 3
> > betas with other language than english?
> 
> Yes, I do that every day :) But I'm using KDE. You didn't answer how did you
> change your keyboard settings.

Well, nobody asked. Each time I log in to my system I have to go to Controlcenter|Configure Mouse and Keyboard|Setup keyboard layout and press OK. If not I'll not have danish keyboard.

I also use KDE. But the problem is also there in Gnome.

> 
> And it isn't release blocker as it can be fixed with update after release
> (if we can figure out what is going on and why it doesn't work).

Then you have to state in the release notes that Mga doesn't support e.g. danish language unless the user forces it each and every time he logs in to the system. NOT recommendable!

(In reply to Hans Micheelsen from comment #18)
> Well, nobody asked.

I asked in comment 14, although I missed the "?" so it was not clear.

I have also asked additional questions in comment 17. Can you please answer them so I can fix this bug.

> > And it isn't release blocker as it can be fixed with update after release
> > (if we can figure out what is going on and why it doesn't work).
> 
> Then you have to state in the release notes that Mga doesn't support e.g.
> danish language unless the user forces it each and every time he logs in to
> the system. NOT recommendable!

If this isn't fixed, then there will indeed be an errata entry added to cover it. While it's an annoying bug, please don't get so wrapped up in it! Remember you're likely seeing one or two bugs but the rest of us have to deal with 100s and they are the most important bug in the world for the reporter. Please keep things in context and we'll do our best to try and deal with the issues.

But we need your help, so please do answer my questions from comment 17! :)

(perhaps this bug is limited only to some keyboards)
another info request, could you give the output of (as user from a terminal)
  xinput list



could you try to run 'setxkbmap' at the start of the session in a terminal; is it sufficient to have the good keymap?

CC: (none) => lmenut

>  1. Do you have /etc/sysconfig/keyboard and if so what are it's contents?
XkbModel=pc105
XkbLayout=dk
KEYBOARD=dk
XkbOptions=compose:rwin
KEYTABLE=dk-latin1


>  2. Do you have a /etc/X11/xorg.conf.d/00-keyboard.conf and if so what are
> it's contents.
Folder /etc/X11/xorg.conf.d is empty

>  3. Does running localectl set-x11-keymap work for you and produce/edit the
> above file? Does rebooting make things "Just work"?
Worked!! And the content of /etc/X11/xorg.conf.d/00-keyboard.conf is:

# Read and parsed by systemd-localed. It's probably wise not to edit this file
# manually too freely.
Section "InputClass"
        Identifier "system-keyboard"
        MatchIsKeyboard "on"
        Option "XkbLayout" "dk"
EndSection


>  4. What interface are you using to configure the keyboard?
I use Controlcenter|Configure Mouse and Keyboard|Setup keyboard layout

(In reply to Hans Micheelsen from comment #21)

Sorry, but it didn't cure the problem.
I do have /etc/X11/xorg.conf.d/00-keyboard.conf but the keyboard layout is still wrong after reboot

(In reply to Hans Micheelsen from comment #22)
> (In reply to Hans Micheelsen from comment #21)
> 
> Sorry, but it didn't cure the problem.
> I do have /etc/X11/xorg.conf.d/00-keyboard.conf but the keyboard layout is
> still wrong after reboot

A "funny" detail is that with that file present pressing ctrl+alt+del instantly reboots the system instead of giving a logout box. 
I removed the file and got the logout box back

As you said you're using both Gnome and KDE, can I ask in which DE it's wrong. If Gnome, can you:

Go to the Gnome System Settings (click on your name in the top right and select "System Settings"), Click on "Region & Language"

You should be able to use this UI to ensure that all is configured correctly.

I suspect the issue you are having here is that the *system* settings are good now (which use the xorg.conf.d snippet), but when your user session loads the user settings are taking over. As these are stored and activated by gnome-settings-daemon, you have to use the gnome config UIs to adjust them.

Can you play with them and see how you get on?

I am using KDE with a Norwegian keyboard and have now tested on Mageia-3-beta4-LiveDVD-KDE4-i586-DVD.iso. Keyboard settings have been configured in the live boot dialig and in the Magaia control centre.

Symptoms are like Hans have described (except Norwegian instead of Danish settings in the config files).

Running 'setxkbmap' in a terminal corrects the problem for the current session.

I added a line
setxkbmap
at the end of /etc/X11/xinit/fixkeyboard and that solved the problem. Probably not good enough for a permanent solution, though.

Whiteboard: mga2 3alpha3 => mga2 3alpha3 3beta4

Edgar, can you verify the following for me?:
 1. /etc/X11/xorg.conf.d/00-keyboard.conf does not exist.
 2. Run "localectl set-x11-keymap XX" (where XX is the norwegian kb identifier)
 3. Check that the file from 1) now exists.
 4. Remove your hack from /etc/X11/xinit/fixkeyboard
 5. Reboot and double check all is well.

I suspect this should work under KDE. Gnome I think behaves different with it's setup (which is why I specifically asked about KDE vs. Gnome in comment 24 above)

(In reply to Colin Guthrie from comment #24)


In Gnome the keyboard layout is correct at bootup.
In KDE and IceWM the keyboard layout is not correct at bootup.

The configuration is correct for all three systems ConfigureSettings-tools

(In reply to Colin Guthrie from comment #26)
> Edgar, can you verify the following for me?:

I tried with the live iso, but failed to get all the answers.

>  1. /etc/X11/xorg.conf.d/00-keyboard.conf does not exist.
Does not exist.

>  2. Run "localectl set-x11-keymap XX" (where XX is the norwegian kb
> identifier)
localectl set-x11-keymap no

>  3. Check that the file from 1) now exists.
Exists.

>  4. Remove your hack from /etc/X11/xinit/fixkeyboard
Removed.

>  5. Reboot and double check all is well.
> 
> I suspect this should work under KDE. Gnome I think behaves different with
> it's setup (which is why I specifically asked about KDE vs. Gnome in comment
> 24 above)

After logout/login, the keyboard layout is still wrong.

You asked for reboot, but I do not know how to reboot the live iso without losing the 00-keyboard.conf file.

So I installed to virtualbox from the live iso. But in virtualbox there is no such problem. (As I wrote in comment 8, this problem occurs only on some computers. VB apparently is one where is works.)

I also tried to test in on Mageia 2, but there is no localectl command there.

Any suggestion to how I can test this without overwriting the Mageia 2 installation on the hard disk?

(In reply to Colin Guthrie from comment #26)
> Edgar, can you verify the following for me?:

Colin, here are the results:
>  1. /etc/X11/xorg.conf.d/00-keyboard.conf does not exist.
Does not exist.

>  2. Run "localectl set-x11-keymap XX" (where XX is the norwegian kb
> identifier)
localectl set-x11-keymap no

>  3. Check that the file from 1) now exists.
Exists.

>  4. Remove your hack from /etc/X11/xinit/fixkeyboard
Removed.

>  5. Reboot and double check all is well.
Sorry, the keyboard layout is still wrong after reboot.

> 
> I suspect this should work under KDE. Gnome I think behaves different with
> it's setup (which is why I specifically asked about KDE vs. Gnome in comment
> 24 above)

FWIW, I've just done a regular network install.

I picked French as language and keyboard layout. I installed and then booted into KDE. All was as expected.

I then used Mageia Control Centre to change keyboard settings to UK keyboard. This worked immediately and then I rebooted and confirmed my keyboard was still UK - it was.

I then used the KDE settings and configured a Danish layout. This also worked fine and after reboot my login manager was in UK layout for password entry but after login my user was in Danish as expected.

All in all, things are behaving as expected here. Obviously it doesn't help that the DE's implement their own settings per-user, but e also have the concept of a "system" setting that is honoured if the user overrides it.

I'll try doing a live install in VirtualBox, but some are reporting that that's generally OK.

OK, I've now installed from the Beta 4 GNOME Live DVD.

This seemed to correctly set things up and I selected a danish keyboard and things were installed with a Danish keyboard layout (the fonts were a bit messed up initially as I picked some strange locale settings, but after correcting that in MCC it was OK).

I then changed the keyboard to french in MCC. Rebooting lost that setting for my user, /etc/sysconfig/keyboard was OK. The DM is not shown, but I strongly suspect it would have been in French if it were. The reason this happened was that on first boot, GNOME recognised the input format and saved this as a user setting. After changing the keyboard in MCC the GNOME settings remained as they were. On reboot, the system settings were set but when my user logged in the user settings took over. Editing the settings in GNOME allowed for correct behaviour surviving over reboots.

So far this is all as expected. I've yet to try with the KDE Live DVD

I have seen that this problem is system dependent (fails on a Fujitsu desktop, works on a Thinkpad and in Virtualbox). So I tried another keyboard on the desktop to see if that changes anything, and it does.

Fails with a Logitech K340 wireless keyboard (USB dongle).
Works with a Fujitsu wired USB keyboard.

The system is otherwise the same and I changed no configuration.

Well, I use a k750 wireless keyboard with usb dongle.

Any chance to solve this important bug before release?

How about other distributions. How did they solve the problem?

Could it be possible to put a setxkbmap into /etc/bashrc or into some initd-stuff until there is a real solution?

I really don't think Mageia should do a final release with this problem. Apparently the problem is present for Danish, Norwegian and French. Which others?

As I've outlined above, I've done several tests and cannot reproduce the problem you are describing. The install works fine and the user inherits the settings of the installer.

Running the DE provided tools to change my user account and it all works fine. I specifically tried with a Danish layout and it all worked fine for me in both GNOME and KDE.

Without being able to reproduce the actual problem, it's nearly impossible to provide a fix. If the problem is indeed related to some kind of hotplugging as suggested above then any hacks to put setxkbmap in bashrc etc. would be entirely irrelevant anyway.

It's getting very confusion as you've now reported about both GNOME and KDE both of which will override system settings with their own configuration. So the only sensible way for you to test is on a brand new, clean user account.

When you do this and login to a DE of your choice (please state which), try running the following:

In terminal 1: become root and do: tail -f /var/log/Xorg.0.log

In terminal 2: become root and do: udevadm trigger --subsystem-match=input --action=add

This should cause X11 to spew out a whole bunch of stuff to it's log in the first terminal.

Can you attach that output.

Please also report what happens with your fresh user account. Please ensure you also attach the contents of /etc/X11/xorg.conf.d/00-keyboard.conf and /etc/sysconfig/keyboard.

Ultimately I think there are conflicting settings that are all trying to do things differently. Unless all the configs align, then things won't work that well.

My current thought on the matter is this:

1. GNOME and KDE have their own user settings that should allow you to configure things via their own DEs.

2. Mageia has some udev magic that applies a system wide default to all devices on hotplug (via mageia-setup-keyboard and /lib/udev/rules.d/61-x11-input.rules which reads settings from /etc/sysconfig/keyboard), this *might* be overriding the GNOME or KDE settings.

3. GNOME has a mechanism to copy the user settings to the system settings. The system settings are store in /etc/X11/xorg.conf.d/00-keyboard.conf. These could (in theory) get out of sync with the ones in /etc/sysconfig/keyboard.

So, in short, if all of the settings agree (system, mga sysconfig and user) then there should be no problems. If they differ slightly, then there might be some fighting over user settings and mga sysconfig settings.


It's possibly enough to disable the /lib/udev/rules.d/61-x11-input.rules (i.e. just type: "ln -s /dev/null /etc/udev/rules.d/61-x11-input.rules") and then only use the DE settings and the system settings (from /etc/X11/xorg.conf.d/00-keyboard.conf) and basically ignore the ones from mga sysconfig (/etc/sysconfig/keyboard).

But again, I couldn't reproduce the issue, so I suspect that to replicate, the settings would all have to get out of sync. If they all agree I really cannot see how anything could be wrong.

Hopefully the above will give you some insight into what is happening here and allow you to see why your settings are behaving oddly. If you identify where the settings are out of sync, and can confirm that syncing them all allows things to work for you, we can then look at working how to best fix it.

Created attachment 3921 [details]
File /etc/sysconfig/keyboard from Hans Micheelsen

Created attachment 3922 [details]
File /etc/X11/xorg.conf.d/00-keyboard.conf from Hans Micheelsen

Created attachment 3923 [details]
File /var/log/Xorg.0.log from Hans Micheelsen


At 1452.759 I did a "udevadm trigger --subsystem-match=input --action=add"

At 1643.287 I did a "setxkbmap"

At 1662.180 I did a "udevadm trigger --subsystem-match=input --action=add"

Created attachment 3924 [details]
Snippet of /var/log/Xorg.0.log before setxkbmap from Hans Micheelsen

Created attachment 3925 [details]
Snippet of /var/log/Xorg.0.log after setxkbmap from Hans Micheelsen

Blast!!! I forgot to set the log files as plain/text. Sorry 'bout that. But at least they are here now.

I've investigated the two last Xorg-files with kompare to see some obvious differences. There are lots of differences. I hope someone can figure which are the interesting ones.

I hope you can use my files

And I logged KDE

And like I stated in comment 27 the keyboard layout is correct in Gnome but not in KDE

The problem is already present in the login-screen and therefore before the DE has been chosen.
So if I had chosen Jørgen or Ãge as username I would not have been able to log into my system

So all of the log outputs and config files show things working and setup correctly :(

I guess you are using KDM as a login screen?

What is really odd here is that the system settings look fine. The Xorg.log file extracts show it setting the keymap appropriately from the udev command.

This therefore looks like the login screen should be OK.

The fact that KDE settings are incorrect could simply be related to the user settings in KDE.

In systemsettings -> Hardware -> Input Devices: Select Keyboard from the left and then select the "Layouts" tab.

Can you attach a screenshot of this page? Namely I'm interested in if the "Configure Layouts" box is ticked? If it's not ticket it should just inherit whatever the X server is, if it is configured, then is it correct?

These settings should only affect your user, and the login screen *should* inherit the xserver settings, although it's always possible that some settings have been set for e.g. the root user (I think kdm runs as root but I could be wrong) which are overriding the xserver defaults and thus apply for the login page.

Created attachment 3955 [details]
Screenshot of Layout tab in Systemsettings ->HW->Input devices->Keyboard

Once I ticked the Configure Layouts I got Danish layout. And even if I untick it and restart my machine I still have Danish layout.

But new users on the system still have incorrect keyboard layout until I tick Configure Layout.

And both KDM and XDM have incorrect keyboard layout. 
(KDM is my default login screen)


BTW: Why is my keyboard set to Generic 101-key in the HW-tab? It is a Logitech Wireless K750. Is there a connection?

Like I say above, in my tests all my users had the correct layout even without ticking this box. I'll do some further tests, but I'm really struggling to reproduce the problems you're encountering (which could be related to the h/w in some capacity), so it's really hard for me to fix :s

That sounds fair to me. I'll try to look into the problem once I've finished my exams. That's next Tuesday. I'm looking forward to learn some X11 stuff (or whatever the problem is...).
Lets just hope there are not too many end users that have the same keyboard as I do.

This still fails on Mageia 4 beta 1 booted from Mageia-4-beta1-LiveDVD-KDE4-x86_64-DVD.iso. The symptoms are the same:
1. Correct keyboard layout after choosing "norwegian" when booting the live iso.
2. Wrong (USA) keyboard layout after logout/login.
3. Typing 'setxkbmap' with no arguments in a Konsole window corrects the keyboard layout for current session only.

Unless someone with the skill to find the root cause of the problem can test on the problematic hardware (two types of Logitech wireless keyboards known), I suggest considering the fix described in comment 25 for Mageia 4. I have used it successfully all the time with Mageia 3.

Whiteboard: mga2 3alpha3 3beta4 => mga2 3alpha3 3beta4 mga3 4beta1

(In reply to Edgar Johansen from comment #51)
> This still fails on Mageia 4 beta 1 booted from
> Mageia-4-beta1-LiveDVD-KDE4-x86_64-DVD.iso. The symptoms are the same:

<snip>

> Unless someone with the skill to find the root cause of the problem can test
> on the problematic hardware (two types of Logitech wireless keyboards
> known), I suggest considering the fix described in comment 25 for Mageia 4.
> I have used it successfully all the time with Mageia 3.

Thanks for the feedback, Edgar :-)

If it is 100% sure only Logitech keyboards are affected (sorry, I don't have time to read all the comments now), then that should be stated in the summary of this bug

(In reply to Edgar Johansen from comment #25)

> I added a line
> setxkbmap
> at the end of /etc/X11/xinit/fixkeyboard and that solved the problem.
> Probably not good enough for a permanent solution, though.

More Logitech keyboards, even *wired* ones, might be affected. In #mageia and #mageia-fr, a user "cyrano" reported what seems to be the same problem, with a /wired/ logitech keyboard after a live DVD install

If anyone sees cyrano when he returns in an IRC channel, please ask him to try the above fix from comment 25 and report back here.

Is this indeed only a i586 bug? (if not, please change platform to *all*)

Again sorry for not reading all comments: Does this bug only occur with live installs, or also with traditional installs?

Summary: Keyboard loosing language => Keyboard loosing language - only Logitech? - wireless (and wired?)

(In reply to Marja van Waes from comment #52)

Thank you for responding, Marja. Her is some more info.

> If it is 100% sure only Logitech keyboards are affected (sorry, I don't have
> time to read all the comments now), then that should be stated in the
> summary of this bug

I am not 100 % sure which keyboards are affected. Two of the cases reported here are Logitech wireless keyboards, types K340 and K750. The machine with the K340 keyboard works correctly with a Fujitsu wired USB keyboard connected instead. More observations would be valuable.

> Is this indeed only a i586 bug? (if not, please change platform to *all*)

Changing platform to all, as it is also an x86_64 bug.

> Again sorry for not reading all comments: Does this bug only occur with live
> installs, or also with traditional installs?

On Mageia 4, I have only tested with boot from live KDE DVD iso.

On Mageia 3, the bug occurred on all tested installs:
- boot from live media
- install from live media
- install from network.

A modified fixkeyboard file does not survive reboot from live media, but can be tested with logout/login.

Hardware: i586 => All

HI,

I've been searching for a solution to this problem for well over a year (well, off and on ... it only affects our (home) server.  My other PCs work fine.)


Symptoms: Keyboard layout always defaults to English (US) after reboot.  Keyboard is a Logitech wireless, model K400 

Problem:  Keyboard is FI.  This messes with passwords when trying to log in. 

Have had this from Mageia 3 and now with Mageia 4.   I thought that I had messed up the install, but after glancing through this thread, I think not.

Every system file I have checked says that the keyboard layout is Finnish, but once we reboot it's back to the English layout.  I HAVE to reset it as root, and
as I mentioned, it messes with the passwords (includes a lot of cursing!)
(BTW I'm using KDE.)

I'm going to try Edgar's fix, but a permanent solution would be welcome.

CC: (none) => vera.hansper

I am also affected by this keyboard layout issue, using swedish layout. I have a Logitech K400 wireless USB keyboard with integrated mousepad, and it has always been weird regarding the keyboard layout settings. Ever since I got it (years ago) it has been sensitive about wich distros I can use. Ubuntu has always been a sure bet, always worked out of the box. Kubuntu on the other hand always had english layout at login (mixed up passwords), after logging in the swedish layout took over. Can't recall if LinuxMint was affected or not. Been using Ubuntu for many years.

I am currently moving over to Mageia 4 Cinnamon and I can report the same bug as others previusly have done here - I set Svenska as preferred language during the install, but when booting up the new system English layout is default at login. After login it is still English layout even thougt both the Cinnamon control center and Mageia control center states that Svenska is preset keyboard layout. Does not help to re-enable Svenska in Cinnamon control center, must click OK in Mageia control center to enable Svenska as keyboard layout. Svenska is now working during the session, but if I reboot same happens as för the others - Login is back to English layout and also after login. Have to click OK in Mageia control center to enable Svenska keyboard layout every time I want to use this computer!

My tip to you developers is to investigate what Ubuntu has done to make these Logitech wireless USB keyboards work as intented. Hope this will be resolved cause I really like this handy little K400 keyboard. And I would very much like to use it with Mageia! :)

ps. when I've connected a wired keyboard these problems has always dissapeared for all distros with this problem, both the login and the following sessions has had the default Svenska keyboard layout working as intended. But wired isn't an option for me on this PC because it is connected to my plasma-TV and I am sitting laid back in a leather armchair 4 meters away...

CC: (none) => per.engstrom
Hardware: All => x86_64
Target Milestone: --- => Mageia 4

Addendum: I have a similar desktop PC, AMD A10, and it also has Mageia 4 Cinnamon but with wired keyboard and wired mouse. Have no issues what so ever regarding anthing! Svenska language works like a charm during the whole experience, from boot up to shut down - as intended! :)

(In reply to Edgar Johansen from comment #25)
> I am using KDE with a Norwegian keyboard and have now tested on
> Mageia-3-beta4-LiveDVD-KDE4-i586-DVD.iso. Keyboard settings have been
> configured in the live boot dialig and in the Magaia control centre.
> 
> Symptoms are like Hans have described (except Norwegian instead of Danish
> settings in the config files).
> 
> Running 'setxkbmap' in a terminal corrects the problem for the current
> session.
> 
> I added a line
> setxkbmap
> at the end of /etc/X11/xinit/fixkeyboard and that solved the problem.
> Probably not good enough for a permanent solution, though.

Reminding of the above, because we received a mail from someone who suffers from the same problem with a Logitech K270, so this bug is apparently still valid.

Whiteboard: mga2 3alpha3 3beta4 mga3 4beta1 => MGA5TOO

I tested plugging a Logitech K270.
Its mapping matches the main kbd one.
I guess I'll have to reboot with only the Logitech one for more testing.

commit 08d993981ce3632ca06c76fc9a1744f15bf96668
Author: Thierry Vignaud <thierry.vignaud@...>
Date:   Tue May 3 23:38:38 2016 +0200

    don't class Logitech wired kbd+mouse as unknown
    
    just filter them out as those are duplicates of USB devices (mga#3510)
---
 Commit Link:
   http://gitweb.mageia.org/software/drakx/commit/?id=08d993981ce3632ca06c76fc9a1744f15bf96668

(In reply to Mageia Robot from comment #59)
> commit 08d993981ce3632ca06c76fc9a1744f15bf96668
> Author: Thierry Vignaud <thierry.vignaud@...>
> Date:   Tue May 3 23:38:38 2016 +0200
> 
>     don't class Logitech wired kbd+mouse as unknown
>     
>     just filter them out as those are duplicates of USB devices (mga#3510)
> ---
>  Commit Link:
>   
> http://gitweb.mageia.org/software/drakx/commit/
> ?id=08d993981ce3632ca06c76fc9a1744f15bf96668

Does this mean it's now fixed?

It seems to work now. On Mageia-6-sta1-LiveDVD-PLASMA5-x86_64-DVD.iso the keyboard layout survives logout/login, which it did not on previous versions.

(I was worried when the login dialog had a "Layout" dropdown with "US" as the only available choice, but to my surprise the Norwegian keyboard layout I had chosen at boot still worked.)

With live media I have only tested logout/login, and not reboot. Both failed previously.

Hardware: x86_64 => All

Closing then. Please reopen if the bug is still present.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Actually it only works if one has another input device plugged.
If you only got the "Logitech, Inc. Unifying Receiver", it won't work.

I guess this doesn't trigger /usr/lib/udev/rules.d/61-x11-input.rules and thus /usr/sbin/mageia-setup-keyboard do not get called

@Colin: as you significaly contributed to it, any idea?

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Sorry, false alarm

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED