Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom keyboard shortcuts not working, loki fresh install #67

Closed
elementaryBot opened this issue Apr 6, 2017 · 8 comments
Closed

Custom keyboard shortcuts not working, loki fresh install #67

elementaryBot opened this issue Apr 6, 2017 · 8 comments

Comments

@elementaryBot
Copy link
Contributor

elementaryBot commented Apr 6, 2017

I've just installed Loki 0.4 (64 bit). I am trying to set up custom keyboard shortcuts using the default system settings program. Clicking on 'Disabled' to set the key brings up "New accelerator" without removing the "Disabled" text, such that it is written as "New Accelerator...Disabled".

Pressing a button to be bound returns the text to "Disabled" and no key/s are bound.

Launchpad Details: #LP1622298 Zach Radge - 2016-09-11 08:32:23 +0000

@elementaryBot
Copy link
Contributor Author

It's working if you assign a combination of keys, for example ctrl + . You can still re-assign a single key via dconf but the new assignment is not shown in the keyboard plug after that.

Launchpad Details: #LPC Deafboy - 2016-09-22 02:22:55 +0000

@elementaryBot
Copy link
Contributor Author

Same here

Launchpad Details: #LPC Jbastardov - 2016-10-01 14:30:08 +0000

@elementaryBot
Copy link
Contributor Author

Confirmed.

Trying to set up some function keys to adjust the volume, and they can't be selected.

Launchpad Details: #LPC Gabriel_P - 2016-10-02 14:11:02 +0000

@elementaryBot
Copy link
Contributor Author

This is workaround:

  1. Add custom shortcut: screenshot-tool –screen
  2. In Dconf-editor go to:
    org → gnome → settings daemon → plugins → media keys → custom keybindings → custom0 (or 1,2... – find command name);
  3. Select binding and put value: Print
  4. Enter / Close;
  5. Test

Launchpad Details: #LPC Quattro - 2016-11-04 14:57:11 +0000

@elementaryBot
Copy link
Contributor Author

Seriously, why is such a trivial thing broken?
I was hoping to enjoy increased simplicity and easy of use,, but so far I have the same bugs and more like this one.
Is anyone looking at these bugs?
This is a quite basic and essential thing in my opinion, I hope this can be fixed soon, happy to test.

Launchpad Details: #LPC Vincent Gerris - 2016-11-14 20:34:52 +0000

@elementaryBot
Copy link
Contributor Author

Hey Vincent,

As you can see, this report came in right after the Loki release. The amount of testing elementary has been subjected to pre-release is in no way comparable with the sheer amount of people who have done so afterwards. The number of reports which have come in are in the ballpark of 3-4000. It will take a while until we will be able to sift through everything.

If you want to volunteer fixing the issue, your merge request would be more than welcome. If you want to find out how, #elementary-dev on irc.freenode.net.

If you can't help yourself, but you want to incentivise the fixing of the issue, consider placing a bounty: https://www.bountysource.com/teams/elementary/bounties

Launchpad Details: #LPC Zisu Andrei - 2016-11-19 14:10:09 +0000

@peteruithoven
Copy link
Collaborator

I would close this one in favor of: #77

@lenemter
Copy link
Member

Closing because I cannot reproduce the issue anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants