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 671448 - Cannot assign ctrl-Q as a personal shortcut because it quits the application
Cannot assign ctrl-Q as a personal shortcut because it quits the application
Status: RESOLVED FIXED
Product: gnome-control-center
Classification: Core
Component: Keyboard
3.3.x
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-03-06 09:19 UTC by arno_b
Modified: 2012-07-16 16:06 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description arno_b 2012-03-06 09:19:30 UTC
Ubuntu Precise
Version: 1:3.3.90-0ubuntu4

I want to remove the annoying shortcut ctrl-Q for all gnome applications through the gnome-control-center and its keyboard panel.
I created a new personal shortcut but when I click on 'deactivated' to choose my shortcut and I press 'ctrl-Q' instead of selecting this key combination the application just leaves...

See: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/947800
Comment 1 Bastien Nocera 2012-03-07 11:41:49 UTC
A bit bizarre, I admit, but what's the use case for using Ctrl+Q exactly? Making non-GNOME applications be able to close? Seems like a bad thing to do...
Comment 2 arno_b 2012-03-07 12:36:34 UTC
I just want Gnome applications not to quit when I press ctrl-Q (which is just near ctrl-S for AZERTY keyboards).
But nevermind the use case, it is not possible to assign shortcuts that are already mapped to Gnome actions (ctrl-Q is one of these shortcuts and it may exist other ones).
Comment 3 Bastien Nocera 2012-03-07 12:58:24 UTC
(In reply to comment #2)
> But nevermind the use case

The use case is everything. Without it, there's no point fixing this bug.
Comment 4 arno_b 2012-03-07 13:16:03 UTC
Ha ok you need the use case to reproduce the bug; in this case I agree.
I just said that even if setting a shortcut with ctrl-Q is strange, it is for the moment not possible through the UI but certainly possible through dconf or a tool like that.
Comment 5 Matthias Clasen 2012-07-15 22:42:35 UTC
I think this is essentially the same as bug 675475, which complains about the inability to assign keyboard shortcuts that are used by the control-center shell.

I think it might be possible to disable all shortcuts while editing the cell, by temporarily removing accel groups from the toplevel.
Comment 6 Bastien Nocera 2012-07-16 16:06:18 UTC
(In reply to comment #5)
> I think this is essentially the same as bug 675475, which complains about the
> inability to assign keyboard shortcuts that are used by the control-center
> shell.

Bug 675475 is actually about us not checking the modifiers properly (in addition to being afflicted with this particular bug).

> I think it might be possible to disable all shortcuts while editing the cell,
> by temporarily removing accel groups from the toplevel.

We used to do that, of sorts, and removed it in 3d3f949f376af1596f73338e60d125683df66523. Even re-adding that code wouldn't have fixed it though, as the handler at the shell level got called first.

The fix is a nice one-liner.


commit 3b4f577652bf0544a2070df5ea473ba08b926ab0
Author: Bastien Nocera <hadess@hadess.net>
Date:   Mon Jul 16 17:03:36 2012 +0100

    shell: Fix not being able to assign Ctrl+Q to a shortcut
    
    Because the shell window was capturing it before the key editing
    cell had a change to get to it.
    
    s/g_signal_connect/g_signal_connect_after/
    
    https://bugzilla.gnome.org/show_bug.cgi?id=671448