Bug 10279 - "Right Win" is proposed as keyboard layout switcher shortcut but this choice has no effect
Summary: "Right Win" is proposed as keyboard layout switcher shortcut but this choice ...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: Mageia 5
Assignee: Nicolas Lécureuil
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-25 16:26 CEST by Henri de Solages
Modified: 2015-10-27 08:44 CET (History)
4 users (show)

See Also:
Source RPM: kdebase4-runtime-4.12.5-1.4.mga4.x86_64
CVE:
Status comment:


Attachments

Description Henri de Solages 2013-05-25 16:26:35 CEST
Description of problem:
The user is proposed a list of shortcuts as keyboard layout switchers, among which the Right Win key. But if this solution is chosen, pressing the said key has no effect. This choice used to work fine in Mageia 2.

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

How reproducible:
Always

Steps to Reproduce:
1.Go to System settings.
2. Choose "Input devices"
3. Choose "Layouts".
4. Check "Configure layouts".
5. Add French and Mongolian, delete US.
6. Click at the right of "Main shortcuts".
7. In "Key(s) to change layout", choose "Right Win".
8. Click on "Apply".
9. Press the Right Win key: the layout doesn't change.

In many languages using non-latin scripts, changing layout is an extremely frequent operation. For instance in editing an HTML file, the mark-up has to be in latin script, but the content in the local script. Even in an ordinary technical text, technical words are often written in English, so in Latin script. Therefore changing layout with one key is often preferred, and the Right Win key is a good candidate because, unlike Alt, Ctrl or Shift, it is usually not used in composition with other keys. So this should work.


Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2013-05-25 19:40:30 CEST

CC: (none) => balcaen.john, lmenut, nicolas.lecureuil

Comment 1 Marja Van Waes 2015-03-31 16:05:51 CEST
Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

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

Comment 2 Henri de Solages 2015-04-01 03:15:33 CEST
Still true in Mageia 4.

Status: RESOLVED => REOPENED
Version: 3 => 4
Resolution: OLD => (none)

Henri de Solages 2015-04-01 03:49:48 CEST

Target Milestone: --- => Mageia 5
Source RPM: kdebase4-runtime-4.10.2-1.mga3.src.rpm => kdebase4-runtime-4.12.5-1.4.mga4.x86_64

Comment 3 Marja Van Waes 2015-04-01 07:23:26 CEST
Assigning

CC: (none) => marja11
Assignee: bugsquad => mageia

Comment 4 Samuel Verschelde 2015-09-21 13:21:17 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/
Comment 5 Marja Van Waes 2015-10-27 06:58:19 CET
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

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

Comment 6 Rémi Verschelde 2015-10-27 08:44:23 CET
Just for the reference, on my laptop I only have a Windows key on the right side, but it is recognised as the "Left Win key". Therefore my "Right Win key" is not recognised as such either, but it works if I assign stuff to "Left Win".

Note You need to log in before you can comment on or make changes to this bug.