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
