After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 613155 - handle super+p key combination: monitor setup
handle super+p key combination: monitor setup
Status: RESOLVED DUPLICATE of bug 623223
Product: gnome-settings-daemon
Classification: Core
Component: general
2.29.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks: randr-tracker
 
 
Reported: 2010-03-17 14:22 UTC by Nicolò Chieffo
Modified: 2010-10-05 16:08 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Nicolò Chieffo 2010-03-17 14:22:56 UTC
Super+P key combination in windows 7 shows up the monitor setup dialog (laptop only, clone, extend, external only).
I'm asking for this because my laptop also has a function key (Fn+F8) which triggers exactly the same combination:
keycode 125 press
keycode 25 press
keycode 25 release
keycode 125 release

125 is super, 25 is p.
It could be really useful if the "Monitor preferences" app is started with this key combination
Comment 2 jlee 2010-05-11 00:37:42 UTC
From a i8042 filter, can monitor the scancode sequence like this:

 0xe0 0x5b        //Super_L pressed
 0x19             //p pressed
 0x99             //p released
 wait 0.5 seconds   //don't know why, might be want to workaround the old Start key
 0xe0 0xdb        //Super_L released
Comment 3 Adi Roiban 2010-10-03 11:51:56 UTC
I have the same problem on a Dell Inspiron n3010 (13r) and the hardware should be similar with 14r or 15r.

I just followed the indication from this commend and now the "change monitor" button is doing something useful. 
https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/539477/comments/9

Maybe this can be added as a default value.
Comment 4 Ray Strode [halfline] 2010-10-05 16:08:33 UTC
We have patches for this on another bug.

*** This bug has been marked as a duplicate of bug 623223 ***