Bug 8388 - Brightness change using keyboard results in display configuration being opened in XFCE
Summary: Brightness change using keyboard results in display configuration being opene...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-14 21:10 CET by Philippe Leblanc
Modified: 2015-03-31 16:06 CEST (History)
1 user (show)

See Also:
Source RPM: xfce4-settings-4.11.0-3.mga3.src.rpm,fglrx-13.200.16-1.mga4.nonfree.src.rpm,setxkbmap-1.3.0-2.mga3.src.rpm
CVE:
Status comment:


Attachments

Description Philippe Leblanc 2012-12-14 21:10:17 CET
Description of problem:
When I press the shortcuts keys on my keyboard to change the brightness of the screen, this results in unintended results. A single press of either increasing or decreasing the brightness causes the opening of two windows of the display configuration tool of XFCE. As you can imagine, pressing the increase or decrease buttons in rapide succession to rapidly increase/decrease the brightness can lead very quickly to dozens of display windows being opened simultaneously.

I wish to add that I did not change any keybindings. This bug showed up out of nowhere this morning. At this point, I have tried rebooting but the bug survived once logged into xfce. I also deleted the ~/.config/xfce4 and ~/.config/xfce4-session folders to reset the session to its default state. Yet the bug persists.

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


How reproducible:
Currently, the bug is 100% reproducible at every log in.

Steps to Reproduce:
1. Log in to xfce
2. Change brightness using keyboard shortcuts
3. See brightness change up or down
4. See 2 display configuration windows open automatically.
Comment 1 Jani Välimaa 2012-12-15 11:37:36 CET
Try also to remove ~/.cache/sessions directory.

CC: (none) => jani.valimaa

Comment 2 Philippe Leblanc 2012-12-16 18:48:52 CET
I removed the sessions directory and the problem is still present.
Comment 3 Philippe Leblanc 2012-12-17 20:23:36 CET
Just tried XFCE with the free ati driver instead of the binary blob. This bug did not occur when switching the driver. Just to make sure I wasn't going insane, I switched back to the closed driver and again the bug was present. I do not understand how switching the graphics driver affects the key bindings.
Comment 4 Philippe Leblanc 2013-02-27 23:11:48 CET
Still present as of M3b2. Can anybody reproduce this?
Comment 5 Philippe Leblanc 2013-02-28 16:52:13 CET
I've added to a bug reported to the folks at XFCE. Hopefully they will fix this. Here's the link: https://bugzilla.xfce.org/show_bug.cgi?id=8186
Comment 6 Philippe Leblanc 2013-04-11 18:23:08 CEST
Still valid as of MGA3b4. And no activity on the XFCE front end.
Philippe Leblanc 2013-04-15 18:34:51 CEST

Source RPM: (none) => xfce4-settings-4.11.0-3.mga3.src.rpm,fglrx-9.012-1.mga3.nonfree.src.rpm

Comment 7 Philippe Leblanc 2013-04-15 19:12:21 CEST
I discovered "showkey", a nifty little tool which gives interesting information.

[root@localhost ~]# showkey --keycodes
le mode clavier était ?INCONNU?
[ si vous essayez cela sous X Window, cela peut ne pas fonctionner
étant donné que le serveur X utilise également /dev/console ]

appuyer sur n'importe quelle touche (le programme terminera 10s après la dernière touche enfoncée)...
code clavier  28 relâcher
code clavier 225 appuyer
code clavier 225 relâcher
code clavier 227 appuyer
code clavier 227 relâcher
code clavier 227 appuyer
code clavier 227 relâcher

======================================================

It basically outputs keycodes as you press them. Here, we see that keycode 28, which is the "return" key, is released after I pressed enter to launch the command. I then press the brightness up key once and this is what results. Keyboard code 225 is registered as being pressed and released once, and somehow a second keycode is registered with code 227, and that registers as being pressed/released twice. I'm not sure how to troubleshoot this from here. I don't know where these keycodes are controlled.
Comment 8 Philippe Leblanc 2013-04-15 19:31:10 CEST
After some additional testing, I no longer believe this is an XFCE problem. I logged out of XFCE and logged back into GNOME, and ran the same command and both keycodes (225 and 227) were registered from one press. I didn't notice this quirk before when using gnome probably due to gnome not mapping keycode 227 to any command.

This indicates the problem lies with FGLRX. I rebooted once more to try this with the free radeon driver and ran showkey once more. This time, only keycode 225 was registered which confirms that something is up with FGRLX and X. Hope this information helps.
Comment 9 Philippe Leblanc 2013-04-25 17:55:11 CEST
Still present with new catalyst driver version 13.4.
Comment 10 Philippe Leblanc 2013-05-15 20:10:54 CEST
Still valid in MGA3RC.
Comment 11 Philippe Leblanc 2013-05-16 22:03:17 CEST
Adding setxkbmap as a potential area where this bug may originate from.

Source RPM: xfce4-settings-4.11.0-3.mga3.src.rpm,fglrx-9.012-1.mga3.nonfree.src.rpm => xfce4-settings-4.11.0-3.mga3.src.rpm,fglrx-9.012-1.mga3.nonfree.src.rpm,setxkbmap-1.3.0-2.mga3.src.rpm

Philippe Leblanc 2013-05-26 18:06:09 CEST

Version: Cauldron => 3

Comment 12 Philippe Leblanc 2013-10-24 16:55:07 CEST
Still seeing this in MGA4 alpha 3. To reiterate, when using XFCE along with the proprietary FGLRX driver, pressing the brightness changing shortcuts brings up the display configuration tool. However, the brightness no longer changes at all so that functionality is now lost. 

In MGA3, the brightness use to work correctly in Gnome, but now it is also glitchy. As in XFCE, pressing brightness change shortcuts not longer changes the brightness. It still brings up the brightness OSD, but the brightness remains constant. Using the gnome GUI tool from the top right menu is also ineffective at changing brightness by slidding the bar. So in all, the problem has gotten worse since upgrading to cauldron.

Source RPM: xfce4-settings-4.11.0-3.mga3.src.rpm,fglrx-9.012-1.mga3.nonfree.src.rpm,setxkbmap-1.3.0-2.mga3.src.rpm => xfce4-settings-4.11.0-3.mga3.src.rpm,fglrx-13.200.16-1.mga4.nonfree.src.rpm,setxkbmap-1.3.0-2.mga3.src.rpm

Comment 13 Marja Van Waes 2015-03-31 16:06:43 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


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