Bug 21951

Summary:	The keyboard can not be configured back as how I installed it.
Product:	Mageia	Reporter:	usr00 usr00 <kepasi>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	mageiatools, marja11
Version:	6	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	drakx-kbd-mouse-x11 ?	CVE:
Status comment:

Description usr00 usr00 2017-10-27 18:49:33 CEST

Description of problem:
The keybard can not be configured back as how I installed it.

Version-Release number of selected component (if applicable):


How reproducible:
Please help!

Steps to Reproduce:
1.can not configure The keybard, the changes do not work (toshiba laptop)
2.
3.

usr00 usr00 2017-10-27 18:50:04 CEST

Summary: The keybard can not be configured back as how I installed it. => The keyboard can not be configured back as how I installed it.

Comment 1 Marja Van Waes 2017-10-27 19:45:19 CEST

Please supply much more information, to begin with:


Did you use a Live iso or a non-Live iso to install Mageia

How (exact steps, please, we need to know whether you used a tool from your Desktop environment or a Mageia tool) and why did you try to configure the keyboard back as how you installed it?

Do you have an en_US keyboard or a localized one?

Component: Release (media or process) => RPM Packages
CC: sysadmin-bugs => mageiatools, marja11
Source RPM: keyboard => drakx-kbd-mouse-x11 ?
Keywords: (none) => NEEDINFO

Comment 2 Marja Van Waes 2017-11-16 09:09:56 CET

Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

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