Bug 11474 - Settings, Graphic server test page doesn't keep mouse settings according to system settings.
Summary: Settings, Graphic server test page doesn't keep mouse settings according to s...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard: MGA3TOO
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-15 07:31 CEST by Laurent Caruso
Modified: 2014-06-11 18:02 CEST (History)
1 user (show)

See Also:
Source RPM: gtk+3.0
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Laurent Caruso 2013-10-15 07:31:27 CEST 
SOFTWARE VERSION:
Official Mageia 3 release (DVD)

PRECONDITIONS
Mouse settings are set for lefties (inverted buttons) 

STEPS HOW TO REPRODUCE
1- Open "Magaia Control Center"
2- Go to "Hardware"
3- select "Configure display server"
4- select "test"
5- confirm that you want to test your setup.

EXPECTED OUTCOME
Graphic settings test page is shown.
dialog popup is shown "is this correct?" with buttons yes and no.
these buttons can be clicked according to system mouse settings (so for lefties, buttons should be activated/clicked with right button)
 
ACTUAL OUTCOME
Click with right button doesn't do anything. 
A click with left button can activate the button. 

FREQUENCY
Always


Reproducible: 

Steps to Reproduce:
Comment 1 Manuel Hiebel 2013-10-17 23:36:20 CEST 
indeed

Component: Release (media or process) => RPM Packages
Version: 3 => Cauldron
Assignee: bugsquad => thierry.vignaud
Source RPM: (none) => drakx-kbd-mouse-x11
Whiteboard: (none) => MGA3TOO

Comment 2 Laurent Caruso 2014-05-09 07:28:22 CEST 
This is FIXED with Mageia 4 official release.

Thank you.

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

Comment 3 Thierry Vignaud 2014-06-11 18:02:46 CEST 
It was probably a gtk+ issue

Source RPM: drakx-kbd-mouse-x11 => gtk+3.0
Note You need to log in before you can comment on or make changes to this bug.