Bug 1384033 - Cannot enter custom shortcuts for keyboard in settings anymore
Summary: Cannot enter custom shortcuts for keyboard in settings anymore
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-settings-daemon
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-12 12:04 UTC by Alexander Volovics
Modified: 2016-10-12 15:49 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-12 15:49:17 UTC
Type: Bug

Attachments (Terms of Use)
Picture of result (30.77 KB, image/png)
2016-10-12 12:04 UTC, Alexander Volovics 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Alexander Volovics 2016-10-12 12:04:53 UTC 
Created attachment 1209555 [details]
Picture of result

Description of problem:

Click on settings icon in gnome in fedora workstation 25 beta.
Go to keyboard entry. Go to custom shortcuts. Click on "+" sign.
A edit window appears. Fill in the necessary fields. Click add.
Go to the added entry under custum shortcuts. Click on "disabled".
Instead of the 'schematic keyboard' window to enter key combination
the edit window appears again with your entries and a big red 
"remove" button at the bottom.
This happen under wayland and under Xserver.


Version-Release number of selected component (if applicable):

gnome-settings-daemon-3.22.0-1.fc25.x86_64

How reproducible:

allways


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Bastien Nocera 2016-10-12 15:49:17 UTC 
You need to click the "edit" button to set the keyboard shortcut you want to use.

If you have any more questions or doubts about the, completely upstream, keyboard shortcuts configuration, please file bugs at https://bugzilla.gnome.org
Note You need to log in before you can comment on or make changes to this bug.