global alt-f1 shortcut resets after system restart

Bug #994486 reported by Egon Kidmose
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

As far as I can tell the the default behaviour when pressing ALT+F1 in 12.04 is to highlight the "Dash Home" button in the launcher, allowing for selection between locked and open applications using the arrow keys and return. I would however prefer to customise this keyboard shortcut to something else (gnome-terminal).

Steps to reproduce:
1. Go to System Setting > Keyboard > Shortcuts > Custom Shortcuts and add an entry by pressing "+"(Name: Terminal, Command: gnome-terminal)
2. Click the text "disabled" on the "Terminal" row
3. Press ALT+F1
4. Verify that ALT-F1 opens the terminal window
5. Restart the PC
6. Look in: System Setting > Keyboard > Shortcuts > Custom Shortcuts - looks like custom shortcut is still set.
7. Press ALT+F1 => dash home is highlighted, no terminal is opened

By clicking the "Terminal" row in Custom shortcuts and pressing "apply" it seems like the shortcut is rewritten to produce a terminal window, but doing this after every restart seems ridiculous.

I'm not sure if this problem lies specifically with gnome-control-center..

I suspect that other "standard shortcuts" be affected in a similar way.

Thanks :)

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.4.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
Uname: Linux 3.2.0-24-generic-pae i686
NonfreeKernelModules: openafs
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
Date: Fri May 4 11:16:05 2012
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.4-0ubuntu3
 deja-dup 22.0-0ubuntu2
 gnome-bluetooth 3.2.2-0ubuntu5
 indicator-datetime 0.3.94-0ubuntu2

Revision history for this message
Egon Kidmose (kidmose) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-control-center (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

not sure that's a bug, the shortcut is used by unity, re-defining it during the session seems to override unity but on next restart unity takes over it again as it's supposed to do

Changed in gnome-control-center (Ubuntu):
importance: Undecided → Low
Revision history for this message
Egon Kidmose (kidmose) wrote :

I guess it depends on how you define a bug. Some say a system behaving in a way the user did not expect, is a bug..
Anyway, it is not clear to me as a user that short-cut-settings are only for a the current session. (Does that hold for all the short-cuts or just some? If the latter, how do I know which are per-session and which are persistent? This information should be available to the user..)

It can't see how it is not a bug that the key combination is shown as been assigned to one thing actually performs another...

Anyway, just wrote because I found this to be a possibility for a small but obvious improvement.
If the experienced behaviour is the intended behaviour, this ticket should obviously just be closed..

Revision history for this message
Sebastien Bacher (seb128) wrote :

well, you can see it as a bug "the dialog shouldn't let you use alt-f1 as a custom shortcut since it's an unity reserved one" or as a wishlist "it should be possible to rebind alt-f1 to a different function", but it's like asking to be able to rebind "backspace" to do something different from deleting chars in a text entry...

Revision history for this message
Nikolaus Waxweiler (madleser) wrote :

The same happens when I assign global keys to the media functions play and next/previous track. I respectively use "Super+C", "Super+." and "Super+," for that, those are unassigned by default I think. It works when I set them, but on the next start, they do nothing until I apply them again in the settings. So this may really be a bug.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.