Bug#673612: Keyboard shortcuts no longer work with gnome-shell 3.4
On 04.06.2012 20:53, Josh Triplett wrote: (Also, why does gnome-core depend on metacity, given that GNOME 3.4 doesn't actually use metacity, just metacity/mutter's libraries and such?) We still require metacity for the fallback mode. That bug report makes the issue pretty clear. With the window manager catching the Super modifier and using it to open the activities overview, nothing other than the window manager can use Super+key for shortcuts. So, all the Super+key shortcuts in gnome-settings-daemon (such as launching a browser) don't work, but those in the window manager (such as moving windows around) work just fine. Just some additional information: The grabby Super handling was already a problem with 3.0 and 3.2. What changed in 3.4 and with the switch from gconf to gsettings, is that a couple of keybindings moved from gnome-shell to gnome-settings-daemon [1], specifically: - custom keybindings - screenshot keybindings - the terminal keybinding was removed and needs to be added as a custom keybinding. As the above keybindings were previously managed by the window manager (i.e. shell or metacity) you could use Super there. This is the specific regression from 3.2 to 3.4 you are experiencing. [1] http://blogs.gnome.org/fmuellner/2011/11/22/gnome-shell-gsettings-and-keybindings/ -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#673612: Keyboard shortcuts no longer work with gnome-shell 3.4
On Mon, Jun 11, 2012 at 12:53:21AM +0200, Michael Biebl wrote: On 04.06.2012 20:53, Josh Triplett wrote: (Also, why does gnome-core depend on metacity, given that GNOME 3.4 doesn't actually use metacity, just metacity/mutter's libraries and such?) We still require metacity for the fallback mode. Then couldn't gnome-session-fallback depend on it, rather than having gnome-core directly depend on it? (I realize gnome-core currently does depend on gnome-session-fallback, but at some point that could become a recommendation or suggestion, at which point the transitive metacity dependency would go away naturally.) That bug report makes the issue pretty clear. With the window manager catching the Super modifier and using it to open the activities overview, nothing other than the window manager can use Super+key for shortcuts. So, all the Super+key shortcuts in gnome-settings-daemon (such as launching a browser) don't work, but those in the window manager (such as moving windows around) work just fine. Just some additional information: The grabby Super handling was already a problem with 3.0 and 3.2. What changed in 3.4 and with the switch from gconf to gsettings, is that a couple of keybindings moved from gnome-shell to gnome-settings-daemon [1], specifically: - custom keybindings - screenshot keybindings - the terminal keybinding was removed and needs to be added as a custom keybinding. As the above keybindings were previously managed by the window manager (i.e. shell or metacity) you could use Super there. This is the specific regression from 3.2 to 3.4 you are experiencing. Right, that makes sense. The upstream bug points out that Super+key shortcuts in gnome-shell work fine, just not Super+key shortcuts in gnome-settings-daemon. - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#673612: Keyboard shortcuts no longer work with gnome-shell 3.4
On Sun, May 20, 2012 at 12:57:54PM -0700, Josh Triplett wrote: - Can you (re)create your shortcuts? I tried recreating my shortcuts via the Keyboard settings dialog. While I can now set keyboard shortcuts using Super as a modifier (which previously did not work and just treated Super_L as a key in itself), hitting those keys does not actually invoke the desired action. I tried setting up a custom shortcut to launch gnome-terminal, and I tried setting the existing Launch web browser shortcut; neither one worked. If I set the shortcuts to use a modifier other than Super, I can invoke them. Any shortcut I set using Super does not seem to work, though the keyboard settings dialog itself recognizes it just fine. Just in case: same here. I'm giving gnome shell a try in a brand new user on my work machine. I've tried to set Super+Return as shortcut to launch gnome-terminal there. The shortcut is accepted in the configuration window, but it doesn't work once set. If I rather try to use a shortcut that does not involve Super, e.g. Alt+Return, it works as expected. (both shell and settings-daemon are at 3.4 versions) Thanks for your work on GNOME! Cheers. -- Stefano Zacchiroli zack@{upsilon.cc,pps.jussieu.fr,debian.org} . o . Maître de conférences .. http://upsilon.cc/zack .. . . o Debian Project Leader... @zack on identi.ca ...o o o « the first rule of tautology club is the first rule of tautology club » signature.asc Description: Digital signature
Bug#673612: Keyboard shortcuts no longer work with gnome-shell 3.4
On 20.05.2012 21:57, Josh Triplett wrote: On Sun, May 20, 2012 at 12:36:09PM +0200, Michael Biebl wrote: On 20.05.2012 09:00, Josh Triplett wrote: Keyboard shortcuts have been switched from gconf to gsettings. - Were existing shortcuts not migrated? Correct. The shortcut for a terminal has disappeared entirely rather than migrating to a custom shortcut or similar. And the section for window management shortcuts seems to have disappeared as well; I don't see any way to add shortcuts for maximize, fullscreen, or move window to top/bottom/left/right. The window manager keybinding definitions for g-c-c are shipped as /usr/share/gnome-control-center/keybindings/50-metacity-*.xml in metacity-common. After installing this package, you should be able to configure those keys in g-c-c again. We've been discussing, where to add a dependency on metacity-common (libmutter, g-c-c, gnome-shell) but haven't quite agreed on something yet. The shortcut for a web browser has stopped working as well. What is gsettings get org.gnome.settings-daemon.plugins.media-keys www set to? None of the shortcuts I've previously set appear anywhere in the keyboard settings dialog. Were those custom shortcuts or did you just re-assign different keys to a predefined shortcut? - Do keyboard shortcuts not work at all? The default shortcuts seem to work, for what they provide: alt-tab, alt-F4, volume keys, screenshots, etc. I can also create keyboard shortcuts using Ctrl+Alt+key and those work fine. Shortcuts using Super+key don't, though. Regarding the poor handling of the Super key, see buxy's email and also https://bugzilla.gnome.org/show_bug.cgi?id=659899 I'm not an expert on this matter, so help with this particular issue would be greatly appreciated. If I set the shortcuts to use a modifier other than Super, I can invoke them. Any shortcut I set using Super does not seem to work, though the keyboard settings dialog itself recognizes it just fine. Also, I see no way to recreate my existing shortcuts for maximization, fullscreen, or moving windows up/down/left/right. See above, wrt. metacity-common Fwiw, the media keys are stored under org.gnome.settings-daemon.plugins.media-keys: gsettings list-recursively org.gnome.settings-daemon.plugins.media-keys The window management keybindings are stored under org.gnome.desktop.wm.keybindings: gsettings list-recursively org.gnome.desktop.wm.keybindings -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#673612: Keyboard shortcuts no longer work with gnome-shell 3.4
clone 673612 -1 -2 retitle 673612 Keyboard shortcuts using Super+key no longer work: Super grabbed by the shell forwarded 673612 https://bugzilla.gnome.org/show_bug.cgi?id=659899 retitle -1 Terminal, window movement, and custom keybindings not migrated from GConf to gsettings reassign -2 gnome-core retitle -2 Please increase versioned dependency on metacity to (= 1:2.34.3-2) for gsettings schemas. thanks On Mon, Jun 04, 2012 at 12:34:03PM +0200, Michael Biebl wrote: On 20.05.2012 21:57, Josh Triplett wrote: On Sun, May 20, 2012 at 12:36:09PM +0200, Michael Biebl wrote: On 20.05.2012 09:00, Josh Triplett wrote: Keyboard shortcuts have been switched from gconf to gsettings. - Were existing shortcuts not migrated? Correct. The shortcut for a terminal has disappeared entirely rather than migrating to a custom shortcut or similar. And the section for window management shortcuts seems to have disappeared as well; I don't see any way to add shortcuts for maximize, fullscreen, or move window to top/bottom/left/right. The window manager keybinding definitions for g-c-c are shipped as /usr/share/gnome-control-center/keybindings/50-metacity-*.xml in metacity-common. After installing this package, you should be able to configure those keys in g-c-c again. We've been discussing, where to add a dependency on metacity-common (libmutter, g-c-c, gnome-shell) but haven't quite agreed on something yet. gnome-core already has a dependency on metacity. However, I didn't install metacity or metacity-common from experimental, so I didn't have a version of metacity-common with the gsettings schemas until May 30th. The window manager keybindings seem to show up now. Might I suggest changing gnome-core's versioned dependency on metacity to (= 1:2.34.3-2)? (Also, why does gnome-core depend on metacity, given that GNOME 3.4 doesn't actually use metacity, just metacity/mutter's libraries and such?) The shortcut for a web browser has stopped working as well. What is gsettings get org.gnome.settings-daemon.plugins.media-keys www set to? ~$ gsettings get org.gnome.settings-daemon.plugins.media-keys www 'Superb' Looks like the bug report below regarding Super handling explains most of this bug. I've retitled this bug accordingly, and cloned it for the other issues. None of the shortcuts I've previously set appear anywhere in the keyboard settings dialog. Were those custom shortcuts or did you just re-assign different keys to a predefined shortcut? Both; I'd defined some new custom shortcuts and also assigned keys to predefined shortcuts: ~$ gconftool-2 --config-source=xml:readwrite:/home/josh/.gconf.shared -R /apps/metacity /apps/metacity/window_keybindings: move_to_side_e = SuperRight move_to_side_s = SuperDown toggle_maximized = Superm move_to_side_n = SuperUp toggle_fullscreen = Superf move_to_side_w = SuperLeft /apps/metacity/keybinding_commands: command_1 = firefox -new-tab about:blank /apps/metacity/global_keybindings: run_command_terminal = Supern run_command_1 = Superb [...] Now that I've upgraded metacity and metacity-common, some of the shortcuts I want to set have shown up again. None of my previous settings appear to have migrated, though. - Do keyboard shortcuts not work at all? The default shortcuts seem to work, for what they provide: alt-tab, alt-F4, volume keys, screenshots, etc. I can also create keyboard shortcuts using Ctrl+Alt+key and those work fine. Shortcuts using Super+key don't, though. Regarding the poor handling of the Super key, see buxy's email and also https://bugzilla.gnome.org/show_bug.cgi?id=659899 I'm not an expert on this matter, so help with this particular issue would be greatly appreciated. That bug report makes the issue pretty clear. With the window manager catching the Super modifier and using it to open the activities overview, nothing other than the window manager can use Super+key for shortcuts. So, all the Super+key shortcuts in gnome-settings-daemon (such as launching a browser) don't work, but those in the window manager (such as moving windows around) work just fine. If I set the shortcuts to use a modifier other than Super, I can invoke them. Any shortcut I set using Super does not seem to work, though the keyboard settings dialog itself recognizes it just fine. Also, I see no way to recreate my existing shortcuts for maximization, fullscreen, or moving windows up/down/left/right. See above, wrt. metacity-common Now that I have the proper version of metacity-common installed, shortcuts for maximize and fullscreen show up again. Shortcuts for moving windows up/down/left/right don't exist anymore, though. However, while I don't see them in the dialog anywhere, Super+left and Super+right now maximize windows to the left and right halves of the screen, which works nicely; Super+up and Super+down got mapped to maximize and restore, which work for me.
Bug#673612: Keyboard shortcuts no longer work with gnome-shell 3.4
Package: gnome-shell Version: 3.4.1-1 Severity: normal After upgrading to gnome-shell 3.4 from experimental, my custom keyboard shortcuts no longer work. In System Settings - Keyboard - Shortcuts, I have shortcuts set for Launch Terminal (Mod4+N), Toggle maximization (Mod4+M), and Toggle fullscreen mode (Mod4+F), but none of them work since I upgraded to 3.4. - Josh Triplett -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.12.1-1 ii gconf-service3.2.5-1 ii gir1.2-accountsservice-1.0 0.6.21-1 ii gir1.2-atk-1.0 2.4.0-2 ii gir1.2-caribou-1.0 0.4.2-2 ii gir1.2-clutter-1.0 1.10.4-3 ii gir1.2-cogl-1.0 1.10.2-3 ii gir1.2-coglpango-1.0 1.10.2-3 ii gir1.2-folks-0.6 0.6.9-1 ii gir1.2-freedesktop 1.32.1-1 ii gir1.2-gconf-2.0 3.2.5-1 ii gir1.2-gcr-3 3.4.1-3 ii gir1.2-gdesktopenums-3.0 3.4.2-1 ii gir1.2-gdkpixbuf-2.0 2.26.1-1 ii gir1.2-gee-1.0 0.6.4-1 ii gir1.2-gkbd-3.0 3.4.0.2-1 ii gir1.2-glib-2.0 1.32.1-1 ii gir1.2-gmenu-3.0 3.4.2-1 ii gir1.2-gnomebluetooth-1.03.2.2-1 ii gir1.2-gtk-3.0 3.4.2-1 ii gir1.2-json-1.0 0.14.2-1 ii gir1.2-mutter-3.03.4.1-2 ii gir1.2-networkmanager-1.00.9.4.0-4 ii gir1.2-pango-1.0 1.30.0-1 ii gir1.2-polkit-1.00.105-1 ii gir1.2-soup-2.4 2.38.1-2 ii gir1.2-telepathyglib-0.120.18.1-2 ii gir1.2-telepathylogger-0.2 0.4.0-1 ii gir1.2-upowerglib-1.00.9.16-2 ii gjs 1.32.0-2 ii gnome-bluetooth 3.2.2-1 ii gnome-icon-theme-symbolic3.4.0-2 ii gnome-settings-daemon3.2.2-3 ii gnome-shell-common 3.4.1-1 ii gsettings-desktop-schemas3.4.2-1 ii libatk1.0-0 2.4.0-2 ii libc62.13-32 ii libcairo-gobject21.12.2-2 ii libcairo21.12.2-2 ii libcamel-1.2-29 3.2.2-3 ii libcanberra0 0.28-4 ii libclutter-1.0-0 1.10.4-3 ii libcogl-pango0 1.10.2-3 ii libcogl9 1.10.2-3 ii libcroco30.6.5-1 ii libdbus-1-3 1.5.12-1 ii libdbus-glib-1-2 0.98-1 ii libebook-1.2-12 3.2.2-3 ii libecal-1.2-10 3.2.2-3 ii libedataserver-1.2-153.2.2-3 ii libedataserverui-3.0-1 3.2.2-3 ii libffi5 3.0.10-3 ii libfolks25 0.6.9-1 ii libgck-1-0 3.4.1-3 ii libgconf-2-4 3.2.5-1 ii libgcr-3-1 3.4.1-3 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libgee2 0.6.4-1 ii libgirepository-1.0-11.32.1-1 ii libgjs0b [libgjs0-libmozjs185-1.0] 1.32.0-2 ii libgl1-mesa-glx [libgl1] 8.0.2-2 ii libglib2.0-0 2.32.3-1 ii libgnome-keyring03.4.1-1 ii libgnome-menu-3-03.4.2-1 ii libgstreamer0.10-0 0.10.36-1 ii libgtk-3-0 3.4.2-1 ii libical0 0.48-2 ii libjson-glib-1.0-0 0.14.2-1 ii libmozjs185-1.0 1.8.5-1.0.0+dfsg-3 ii libmutter0 3.4.1-2 ii libnm-glib4 0.9.4.0-4 ii libnm-util2 0.9.4.0-4 ii libnspr4 2:4.9-3 ii libnspr4-0d 2:4.9-3 ii libnss3
Bug#673612: Keyboard shortcuts no longer work with gnome-shell 3.4
Hi, On 20.05.2012 09:00, Josh Triplett wrote: After upgrading to gnome-shell 3.4 from experimental, my custom keyboard shortcuts no longer work. In System Settings - Keyboard - Shortcuts, I have shortcuts set for Launch Terminal (Mod4+N), Toggle maximization (Mod4+M), and Toggle fullscreen mode (Mod4+F), but none of them work since I upgraded to 3.4. Could you try upgrading gnome-settings-daemon and gnome-control-center to 3.4, too. Keyboard shortcuts have been switched from gconf to gsettings. - Were existing shortcuts not migrated? - Do keyboard shortcuts not work at all? - Can you (re)create your shortcuts? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#673612: Keyboard shortcuts no longer work with gnome-shell 3.4
On Sun, May 20, 2012 at 12:36:09PM +0200, Michael Biebl wrote: On 20.05.2012 09:00, Josh Triplett wrote: After upgrading to gnome-shell 3.4 from experimental, my custom keyboard shortcuts no longer work. In System Settings - Keyboard - Shortcuts, I have shortcuts set for Launch Terminal (Mod4+N), Toggle maximization (Mod4+M), and Toggle fullscreen mode (Mod4+F), but none of them work since I upgraded to 3.4. Could you try upgrading gnome-settings-daemon and gnome-control-center to 3.4, too. OK, I just upgraded all three to the versions from experimental. Keyboard shortcuts have been switched from gconf to gsettings. - Were existing shortcuts not migrated? Correct. The shortcut for a terminal has disappeared entirely rather than migrating to a custom shortcut or similar. And the section for window management shortcuts seems to have disappeared as well; I don't see any way to add shortcuts for maximize, fullscreen, or move window to top/bottom/left/right. The shortcut for a web browser has stopped working as well. None of the shortcuts I've previously set appear anywhere in the keyboard settings dialog. - Do keyboard shortcuts not work at all? The default shortcuts seem to work, for what they provide: alt-tab, alt-F4, volume keys, screenshots, etc. I can also create keyboard shortcuts using Ctrl+Alt+key and those work fine. Shortcuts using Super+key don't, though. - Can you (re)create your shortcuts? I tried recreating my shortcuts via the Keyboard settings dialog. While I can now set keyboard shortcuts using Super as a modifier (which previously did not work and just treated Super_L as a key in itself), hitting those keys does not actually invoke the desired action. I tried setting up a custom shortcut to launch gnome-terminal, and I tried setting the existing Launch web browser shortcut; neither one worked. If I set the shortcuts to use a modifier other than Super, I can invoke them. Any shortcut I set using Super does not seem to work, though the keyboard settings dialog itself recognizes it just fine. Also, I see no way to recreate my existing shortcuts for maximization, fullscreen, or moving windows up/down/left/right. - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org