linux - Slow hotkey response in GNOME 3.12

07
2014-07
  • 2mac

    I run Arch, and I recently grabbed the 3.12 upgrade for GNOME. I've had F12 bound to terminator for a while, since I often have to summon new terminals.

    Ever since the upgrade, using a hotkey for a command can take up to 30 seconds, when it used to be instant. Launching the program graphically is still instant.

    I've tried using different hotkeys, and I've tried binding the hotkeys to different commands, and they all behave this way.

    • Answers
    Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

    Related Question

    linux - Shortcuts to move windows across multiple screens in Gnome
  • Roberto Aloi

    I've two screens next each other and I'm running Gnome (Metacity 2.22). I use Xinerama to setup resolution and position for the screens. Using OpenSuse 11.1.

    I would like to use the keyboard to move windows from one screen to the other one. I found some apparently useful keys under gconf-editor:

    * /apps/metacity/window_keybindings/move_to_side_n
* /apps/metacity/window_keybindings/move_to_side_e
* /apps/metacity/window_keybindings/move_to_side_w
* /apps/metacity/window_keybindings/move_to_side_s

    I setup some bindings, but they seem not to work properly for all windows (for example, with Firefox or Thunderbird). Sometimes, the windows return to their original position when I press a key.

    Do you have any other alternative to easily move windows across multiple screens (and possibly to tile them?). I would prefer to keep the Gnome window manager, not to switch to ratpoison or whatever else.


    • Related Answers
  • John T

    If your screens are on separate workspaces, you can use Shift + Ctrl + Alt and an arrow key in the specified direction you wish to move it.

  • goldPseudo

    If your bindings are working normally except under certain windows, this might mean that whatever window it is uses that binding for something else and is hijacking the shortcut. Try again by setting a different key combination, or disable the offending key combination in Firefox/whatever.

  • Natim

    You can use the compiz PUT plugins to set the keyboard shortcut for Put To Next Output