Description of problem: after an install with language "french" and keyboard "azerty" (which is OK during the installation) the keyboard returns each time in "qwerty" at reboot (or even when changing of user). Nevertheless in my kde session the parameters seem good (for language and keyboard). Some additionnal changes in the kde configuration solve the issue but only inside the kde session (the connexion screen is still in qwerty). Maybe this problem arises when using a wireless keyboard (mine is a logitech K800) and it has been previously encountered by several users. A sort of solution is given in this thread (in french) : https://www.mageialinux-online.org/forum/topic-15160+clavier-logitech-k520-en-qwerty.php and the same problem seems to be met with ubuntu, see the following bug report : https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1238346 Version-Release number of selected component (if applicable): 5.1 ? How reproducible / steps to reproduce : sorry after some efforts my mageia-5.1 system is OK, see : https://www.mageialinux-online.org/forum/topic-23410.php#m225985 and I have no time to try again a reinstall from scratch (to see if the same problem occurs again). hth
How did you install Mageia, Bruno, from a Live DVD or from a Classical DVD? If from a live DVD, then please run, in a ternminal/konsole as root: journalctl -ab1 > journal.txt and attach journal.txt to this bug report. If from a classical install, then please attach /root/drakx/report.bug.xz from that install
Keywords: (none) => NEEDINFOCC: (none) => marja11
Created attachment 9198 [details] the file /root/drakx/report.bug.xz
Hello Marja, I have installed Mageia from the iso 5.1 and put it on an usb key. I have attached the file /root/drakx/report.bug.xz.
Thanks, Bruno :-) report.bug.xz looks good, afaict, there doesn't seem to be an issue with the installer. This bug reminds me of bug 3510 It would be nice to also get the logs of the first time you booted into the newly installed system, so of the first time you hit this bug. Please run, as root: journalctl -ab1 > journal.txt Then attach journal.txt to this bug report.
Source RPM: (none) => drakx-kbd-mouse-x11 ?Component: Installer => RPM PackagesCC: (none) => mageiatools
Created attachment 9209 [details] log file (result of the command journalctl -ab1 > journal.txt Hello Marja, here is the logs you asked for. Sorry for the delay I was on holidays.
CC: (none) => bruno.pincon
(In reply to bruno pinçon from comment #5) > Created attachment 9209 [details] > log file (result of the command journalctl -ab1 > journal.txt > > Hello Marja, here is the logs you asked for. Sorry for the delay I was on > holidays. No problem, I hope you enjoyed your holidays! The Logitech keyboard & mouse were detected before KDM started. However, unless I miss something, the fix for bug 3510 was never pushed to Mageia 5. I fail to see anything similar to http://gitweb.mageia.org/software/drakx/commit/?id=08d993981ce3632ca06c76fc9a1744f15bf96668 (don't class Logitech wired kbd+mouse as unknown) in http://gitweb.mageia.org/software/drakx/log/?h=distro/mga5
Source RPM: drakx-kbd-mouse-x11 ? => drakxtoolsKeywords: NEEDINFO => (none)Assignee: bugsquad => mageiatools
Hi Bruno, Thank you for having taken the needed time to report this issue! We regret if this issue never got fixed in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/ It only continued to get important security updates since then, but non-security bugs have no chance of still getting fixed. I assume this bug doesn't exist in Mageia 6, because the fix for bug 3510 was pushed before Mageia 6 was released. Closing as OLD. Please reopen this report and change its "Version:" at the top left to "6", if the same bug still exists in Mageia 6. ==> If you didn't reset your password after February 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and change the Version: and comment in this report. <==
Resolution: (none) => OLDStatus: NEW => RESOLVED