Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

In ubuntu 11.04 there was a workaround using gconf-editor and setting key /apps/gnome_settings_daemon/plugins/xrandr/active to false.

However there is no such key in gconf-manager using ubuntu 11.10 (gnome 3).

share|improve this question
up vote 12 down vote accepted

The new version of gnome-settings-daemon stores its configuration information in dconf rather than gconf.

To do the equivalent of what you were doing on 11.04, try the following:

  1. Install the dconf-tools package, and then run dconf-editor.
  2. In the tree on the left, navigate org -> gnome -> settings-daemon -> plugins -> xrandr.
  3. Uncheck the active checkbox.
share|improve this answer
I've fixed up the answer now. Would you mind marking it as accepted if it solved your problem? – James Henstridge Oct 19 '11 at 1:23
The way to do this from the command line is: dconf write /org/gnome/settings-daemon/plugins/xrandr/active false – aculich Nov 7 '12 at 2:26
I found that w/ Ubuntu 13.04 it's also necessary to do dconf write /org/gnome/settings-daemon/plugins/media-keys/active false – Mark Aug 20 '13 at 20:46
@elgalu: doing this will disable all media keys - including volume up, down, screenshots, etc. Certainly not what the OP wanted. – Gui Ambros Jun 28 '14 at 21:28
Yes @GuiAmbros it sucks, i still have no solution for this issue on Ubuntu 14.04 – Leo Gallucci Jul 1 '14 at 16:56

This is still an issue as of Ubuntu 12.10 released October 18, 2012. A bug fix for this seemed to be in the works so that at least there is an easier way to re-configure the key bindings, but it has since been marked invalid because this was supposedly fixed in gnome-settings-daemon.

Ultimately this problem is supposedly due to some hardware vendors hard-coding video out to Super-P.

There have been updated conversations on the bug tracker since the currently-accepted answer that suggest not turning off xrandr, but instead turning off media-keys:

Try the following:

  1. Install the dconf-tools package, and then run dconf-editor.
  2. In the tree on the left, navigate org -> gnome -> settings-daemon -> plugins -> media-keys.
  3. Uncheck the active checkbox.

Or the command-line version of this is:

dconf write /org/gnome/settings-daemon/plugins/media-keys/active false

share|improve this answer

In order to disable global <Super>p keybindings, and NOT any other media keys (tested in Ubuntu 15.04) I had to 'emtpy' the following dconf keys. I ran (in a terminal):

dconf write /org/gnome/settings-daemon/plugins/media-keys/video-out ''
dconf write /org/gnome/settings-daemon/plugins/media-keys/screenshot ''

Before, I searched with the next bash commands for values that contained '<Super>p':

for i in `dconf list $b | sort`; do echo -n "$i: "; dconf read $b$i; done

To search all dconf keys, use the command:

dconf dump / | grep '<Super>p'

If you want to avoid the terminal, run the program dconf-editor and search for the key(s) there...


After some upgrades and restarts, I had the keybinding not working any more. I found, that there is/was a bug in gnome-settings-daemon that defines <Super>p. A hack is described here.

In the startup process, /usr/bin/xbindkeys_autostart is executed on login. This script searches for the file in $HOME/.xbindkeysrc and loads the settings.

Since I wanted to map gnome-screenshot -c to <Super>p, I created the this file with the following content (and unmapped the settings in ubuntu/compiz):

# Content of $HOME/.xbindkeysrc
"gnome-screenshot -c"
mod4 + p
share|improve this answer
Lovely! you finally solved my Super+P nightmare – Leo Gallucci Feb 13 '15 at 21:16
@LeoGallucci, if you have problems after restarts/updates, try the .xbindkeysrc modification (see the edit of my answer). – setempler Feb 14 '15 at 13:28
The linked solution was exactly what I needed. Thanks! – legoscia Feb 11 at 16:45

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.