Settings issueshttps://gitlab.gnome.org/GNOME/gnome-control-center/-/issues2024-01-30T13:22:11Zhttps://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2850Keyboard: Custom Shortcuts page triggers a warning saying that AdwNavigationP...2024-01-30T13:22:11ZAutomeris naranjaKeyboard: Custom Shortcuts page triggers a warning saying that AdwNavigationPage is missing a title## Affected version
gnome-control-center-45.2-1.fc39.x86_64
## Steps to reproduce
1. Run Settings from terminal
2. Go to Keyboards > View and Customize Shortcuts
3. Click in the Custom Shortcuts row at the bottom of the list
## Seen b...## Affected version
gnome-control-center-45.2-1.fc39.x86_64
## Steps to reproduce
1. Run Settings from terminal
2. Go to Keyboards > View and Customize Shortcuts
3. Click in the Custom Shortcuts row at the bottom of the list
## Seen behavior
In terminal, the following warning will show:
`Adwaita[17920]: WARNING: AdwNavigationPage 0x559f42000180 is missing a title. To hide a header bar title, consider using AdwHeaderBar:show-title instead.`https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2814Keyboard shortcut rows don't indicate that a window will be opened2024-03-12T12:54:02ZAllan DayKeyboard shortcut rows don't indicate that a window will be openedgnome-control-center 45.2 on Fedora 39. The lists of keyboard shortcuts in the keyboard settings look like this:
![image](/uploads/67a033c53ddb7dcd2090920584a6adfe/image.png)
The standard design pattern is to show an arrow icon on the ...gnome-control-center 45.2 on Fedora 39. The lists of keyboard shortcuts in the keyboard settings look like this:
![image](/uploads/67a033c53ddb7dcd2090920584a6adfe/image.png)
The standard design pattern is to show an arrow icon on the right of the list, to show that something will be opened when the user clicks on it. Otherwise it's a bit unclear what will happen.
In this case I would deviate slightly from the standard pattern and use an edit icon:
![image](/uploads/8c2df5cc6b07200aee5a3c39c7fc4860/image.png)
This provides additional clarity on what action will be triggered by the row.https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2802Ctrl-Shift or Alt-Shift doesn't work in Keyboard Shortcuts > Typing > Switch ...2023-12-21T16:19:22Zdarkblaze69Ctrl-Shift or Alt-Shift doesn't work in Keyboard Shortcuts > Typing > Switch to next input source* OS: Arch
* GNOME 45
Ctrl-Shift or Alt-Shift doesn't work in Keyboard Shortcuts > Typing > Switch to next input source.
I am accustomed since ancient times to this combination - Alt-Shift, but unable to accomplish this via g-c-c.
Th...* OS: Arch
* GNOME 45
Ctrl-Shift or Alt-Shift doesn't work in Keyboard Shortcuts > Typing > Switch to next input source.
I am accustomed since ancient times to this combination - Alt-Shift, but unable to accomplish this via g-c-c.
Though manually it allows me to set it via dconf-editor as `['<Shift>Alt_L']`https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2787Keyboard Shortcuts dialog looks weird2023-12-08T15:12:29ZInam Ul HaqKeyboard Shortcuts dialog looks weird![image](/uploads/fc653376bfc3ff616afdfe07b018a5a0/image.png)
Look at the header bar, the content feels packed so tightly.
<details><summary>System Details Report</summary>
## Report details
- **Date generated:** ...![image](/uploads/fc653376bfc3ff616afdfe07b018a5a0/image.png)
Look at the header bar, the content feels packed so tightly.
<details><summary>System Details Report</summary>
## Report details
- **Date generated:** 2023-12-07 22:12:28
## Hardware Information:
- **Hardware Model:** ASUSTeK COMPUTER INC. ROG Zephyrus G15 GA503QM_GA503QM
- **Memory:** 16.0 GiB
- **Processor:** AMD Ryzen™ 9 5900HS with Radeon™ Graphics × 16
- **Graphics:** AMD Radeon™ Graphics
- **Graphics 1:** NVIDIA GeForce RTX™ 3060 Laptop GPU
- **Disk Capacity:** (null)
## Software Information:
- **Firmware Version:** GA503QM.412
- **OS Name:** Fedora Linux 39 (Workstation Edition)
- **OS Build:** (null)
- **OS Type:** 64-bit
- **GNOME Version:** Not Available
- **Windowing System:** Wayland
- **Kernel Version:** Linux 6.6.4-200.fc39.x86_64
</details>https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2767Keyboard layout dialog text badly formatted2023-11-27T09:45:13ZSteve RainwaterKeyboard layout dialog text badly formattedOn my high resolution (4k) display, the keyboard layout window text is badly formatted, with mis-wrapped lines, overlapping text, truncated words, text hidden by going outside bounds of keys, etc. No other settings dialog or Gnome dialog...On my high resolution (4k) display, the keyboard layout window text is badly formatted, with mis-wrapped lines, overlapping text, truncated words, text hidden by going outside bounds of keys, etc. No other settings dialog or Gnome dialog seems to have similar formatting issues; only the keyboard layout window. Perhaps it's not checking the display resolution or system font settings before rending?
## Relevant information
* GNOME Settings version
<!-- Find with the command "gnome-control-center --version" -->
```
$ gnome-control-center --version
gnome-control-center 44.3
```
* Operating system (distribution)
<!-- Find with the command "cat /etc/os-release" -->
```
$ cat /etc/os-release
NAME="Fedora Linux"
VERSION="38 (Workstation Edition)"
ID=fedora
VERSION_ID=38
VERSION_CODENAME=""
PLATFORM_ID="platform:f38"
PRETTY_NAME="Fedora Linux 38 (Workstation Edition)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:38"
DEFAULT_HOSTNAME="fedora"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f38/system-administrators-guide/"
SUPPORT_URL="https://ask.fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=38
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=38
SUPPORT_END=2024-05-14
VARIANT="Workstation Edition"
VARIANT_ID=workstation
```
* Screenshots
![Screenshot_from_2023-11-25_17-37-19](/uploads/a1b61430a6d145ddcbda939032cf23dc/Screenshot_from_2023-11-25_17-37-19.png)
## Steps to reproduce:
1. Open GNOME Settings
2. Select Keyboard in left panel
3. Click hamburger menu to the left of language under "Input Sources" in right panel
4. Select "View Keyboard Layout" to open keyboard layout view
Other information that may help reproduce:
```
resolution: 3840x2160
aspect ratio: 16:9
scaling: 100%
font: Cantarell Regular 11
hinting: slight
antialiasing: subpixel for LCD screens
font scaling: 1.60
```https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2766Keyboard Shortcut: duplicate shortcut message does not appear generating a Gt...2023-11-27T11:04:45ZMarcos MillerKeyboard Shortcut: duplicate shortcut message does not appear generating a Gtk warningWhen defining a new shortcut, and this shortcut combination has already been defined, the duplicate shortcut message does not appear, generating a Gtk warning.
Terminal message:
`
Gtk[154896]: WARNING: Failed to set text '<b>Ctrl+Alt+...When defining a new shortcut, and this shortcut combination has already been defined, the duplicate shortcut message does not appear, generating a Gtk warning.
Terminal message:
`
Gtk[154896]: WARNING: Failed to set text '<b>Ctrl+Alt+A está sendo usado para test. Se você substituí-lo, test será desabilitada' from markup due to error parsing markup: Erro na linha 1 caractere 107: Elemento “markup” foi fechado, mas o elemento atualmente aberto é “b”
`
Affected version: gnome-control-center main
Observation: if we add spaces in `<b> %s </b>` [1], the message is displayed normally.
[1]:
`
/* TRANSLATORS: Don't translate/transliterate <b>%s</b>, which is the accelerator used */
collision_text = g_markup_printf_escaped (_("<b>%s</b> is already being used for %s. If you "
"replace it, %s will be disabled"),
friendly_accelerator,
cc_keyboard_item_get_description (collision_item),
cc_keyboard_item_get_description (collision_item));
`https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2765Insert key ('ins') not listed as valid compose key option while supported by xkb2023-11-27T11:04:45ZAnthony HsebInsert key ('ins') not listed as valid compose key option while supported by xkb<!--
Not following the communication guidelines [1] will mean your issue or comment
will be removed. Read it carefully before submitting this issue.
[1] https://gitlab.gnome.org/GNOME/gnome-control-center/blob/main/docs/CODE_OF_CONDUCT...<!--
Not following the communication guidelines [1] will mean your issue or comment
will be removed. Read it carefully before submitting this issue.
[1] https://gitlab.gnome.org/GNOME/gnome-control-center/blob/main/docs/CODE_OF_CONDUCT.md#communication-guidelines
Detailed description of the issue. Put as much information as you can, potentially
with images showing the issue.
-->
The Gnome Settings GUI does not allow "Insert" to be selected as Compose Key, whereas it is supported by the underlying utilities.
Manually setting the property `/org/gnome/desktop/input-sources/xkb-options` to `['compose:ins']` yields the expected behavior.
## Relevant information
* GNOME Settings version
45.1
* xkb version (`xkbcli --version`):
1.6.0
* Operating system (distribution)
<!-- Find with the command "cat /etc/os-release" -->
```
NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://bugs.archlinux.org/"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=archlinux-logo
```
* Error message
(not applicable)
* Backtrace (if you are experiencing a crash)
(not applicable)
* Screenshots
![Screenshot_from_2023-11-22_12-03-48](/uploads/3c58c11b249e8a79e304d9ccf6404954/Screenshot_from_2023-11-22_12-03-48.png)
![Screenshot_from_2023-11-22_11-34-10](/uploads/b7475124d621a423446acafd936e3aee/Screenshot_from_2023-11-22_11-34-10.png)
## Steps to reproduce:
1. Open Settings
2. Go to "Keyboard"
3. Click on "Compose Key"
4. Look for "Insert" in the options list (Not found)
5. Manually set the property `/org/gnome/desktop/input-sources/xkb-options` to `['compose:ins']`
6. Now the Insert key works as expected as compose key, however gnome-control-center shows that the compose key is disabled likely because 'ins' is not recognized.
## Additional Information:
`xkbcli list` output section relevant to the compose key, showing 'ins' is valid (third to last option):
```
- name: 'Compose key'
description: Position of Compose key
allows_multiple: true
options:
- name: 'compose:ralt'
brief: ''
description: 'Right Alt'
- name: 'compose:lwin'
brief: ''
description: 'Left Win'
- name: 'compose:lwin-altgr'
brief: ''
description: '3rd level of Left Win'
- name: 'compose:rwin'
brief: ''
description: 'Right Win'
- name: 'compose:rwin-altgr'
brief: ''
description: '3rd level of Right Win'
- name: 'compose:menu'
brief: ''
description: 'Menu'
- name: 'compose:menu-altgr'
brief: ''
description: '3rd level of Menu'
- name: 'compose:lctrl'
brief: ''
description: 'Left Ctrl'
- name: 'compose:lctrl-altgr'
brief: ''
description: '3rd level of Left Ctrl'
- name: 'compose:rctrl'
brief: ''
description: 'Right Ctrl'
- name: 'compose:rctrl-altgr'
brief: ''
description: '3rd level of Right Ctrl'
- name: 'compose:caps'
brief: ''
description: 'Caps Lock'
- name: 'compose:caps-altgr'
brief: ''
description: '3rd level of Caps Lock'
- name: 'compose:102'
brief: ''
description: 'The "< >" key'
- name: 'compose:102-altgr'
brief: ''
description: '3rd level of the "< >" key'
- name: 'compose:paus'
brief: ''
description: 'Pause'
- name: 'compose:ins'
brief: ''
description: 'Insert'
- name: 'compose:prsc'
brief: ''
description: 'PrtSc'
- name: 'compose:sclk'
brief: ''
description: 'Scroll Lock'
```https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2703Crash when i try to edit keyboard shortcut2024-01-11T13:09:26ZBartosz PłotkaCrash when i try to edit keyboard shortcut<!--
Not following the communication guidelines [1] will mean your issue or comment
will be removed. Read it carefully before submitting this issue.
[1] https://gitlab.gnome.org/GNOME/gnome-control-center/blob/main/docs/CODE_OF_CONDUCT...<!--
Not following the communication guidelines [1] will mean your issue or comment
will be removed. Read it carefully before submitting this issue.
[1] https://gitlab.gnome.org/GNOME/gnome-control-center/blob/main/docs/CODE_OF_CONDUCT.md#communication-guidelines
Detailed description of the issue. Put as much information as you can, potentially
with images showing the issue.
--> GNOME Settings crashes when I click "View and customize shortcuts" in "Custom Shortcuts" section in keyboard settings.
## Relevant information
* GNOME Settings version : gnome-control-center 45.0
<!-- Find with the command "gnome-control-center --version" -->
* Operating system (distribution) : Ubuntu 23.10
<!-- Find with the command "cat /etc/os-release" -->
* Error message
<!-- Reproduce the issue while running with the command "G_MESSAGES_DEBUG=all gnome-control-center" -->
```
13:19:44.3580 GLib-GIO[63308]:CRITICAL: g_settings_new_with_path: assertion 'path_is_valid (path)' failed
13:19:44.3580 GLib-GIO[63308]:CRITICAL: g_settings_is_writable: assertion 'G_IS_SETTINGS (settings)' failed
13:19:44.3580 GLib-GIO[63308]:CRITICAL: g_settings_is_writable: assertion 'G_IS_SETTINGS (settings)' failed
13:19:44.3580 GLib-GIO[63308]:CRITICAL: g_settings_is_writable: assertion 'G_IS_SETTINGS (settings)' failed
13:19:44.3580 GLib-GIO[63308]:CRITICAL: g_settings_get_value: assertion 'G_IS_SETTINGS (settings)' failed
13:19:44.3580 GLib[63308]:CRITICAL: g_variant_get_type: assertion 'value != NULL' failed
13:19:44.3580 GLib[63308]:CRITICAL: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed
13:19:44.3580 GLib-GIO[63308]:CRITICAL: g_settings_bind_with_mapping: assertion 'G_IS_SETTINGS (settings)' failed
13:19:44.3580 GLib-GIO[63308]:CRITICAL: g_settings_bind_with_mapping: assertion 'G_IS_SETTINGS (settings)' failed
13:19:44.3580 GLib-GIO[63308]:CRITICAL: g_settings_get_value: assertion 'G_IS_SETTINGS (settings)' failed
13:19:44.3580 GLib[63308]:CRITICAL: g_variant_get_type: assertion 'value != NULL' failed
13:19:44.3580 GLib[63308]:CRITICAL: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed
13:19:44.3581 GLib[63308]:CRITICAL: g_variant_get_type: assertion 'value != NULL' failed
13:19:44.3581 GLib[63308]:CRITICAL: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed
```
* Backtrace (if you are experiencing a crash)
<!-- Check for instructions at https://wiki.gnome.org/GettingInTouch/Bugzilla/GettingTraces -->
```
#0 0x0000560d49b81b97 in ??? ()
#1 0x0000560d49bbc716 in cc_keyboard_item_load_from_gsettings_path ()
#2 0x0000560d49bbcd72 in ??? ()
#3 0x0000560d49bbe349 in cc_keyboard_manager_load_shortcuts ()
#4 0x0000560d49bbf702 in ??? ()
#5 0x00007fe50ada1cdb in g_type_create_instance ()
at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#6 0x00007fe50ad881f0 in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#7 0x00007fe50ad89746 in g_object_new_with_properties ()
at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#8 0x00007fe50ad8a5f1 in g_object_new ()
at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#9 0x0000560d49bc03fb in ??? ()
#10 0x00007fe50ad96add in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#11 0x00007fe50ad96bd6 in g_signal_emit_valist ()
at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#12 0x00007fe50ad96c93 in g_signal_emit ()
at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#13 0x00007fe50ad76c15 in g_cclosure_marshal_VOID__OBJECTv ()
at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#14 0x00007fe50ad96add in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#15 0x00007fe50ad96bd6 in g_signal_emit_valist ()
at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
--Type <RET> for more, q to quit, c to continue without paging--c
#16 0x00007fe50ad96c93 in g_signal_emit ()
at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#17 0x00007fe50a381f6f in ??? () at /lib/x86_64-linux-gnu/libgtk-4.so.1
#18 0x00007fe50a2b2295 in ??? () at /lib/x86_64-linux-gnu/libgtk-4.so.1
#19 0x00007fe50ad96add in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#20 0x00007fe50ad96bd6 in g_signal_emit_valist ()
at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#21 0x00007fe50ad96c93 in g_signal_emit ()
at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#22 0x00007fe50a351786 in ??? () at /lib/x86_64-linux-gnu/libgtk-4.so.1
#23 0x00007fe50ad7bdf6 in g_cclosure_marshal_VOID__BOXEDv ()
at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#24 0x00007fe50ad96add in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#25 0x00007fe50ad96bd6 in g_signal_emit_valist ()
at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#26 0x00007fe50ad96c93 in g_signal_emit ()
at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#27 0x00007fe50a34ba77 in ??? () at /lib/x86_64-linux-gnu/libgtk-4.so.1
#28 0x00007fe50a34c79b in ??? () at /lib/x86_64-linux-gnu/libgtk-4.so.1
#29 0x00007fe50a352006 in ??? () at /lib/x86_64-linux-gnu/libgtk-4.so.1
#30 0x00007fe50a462d68 in ??? () at /lib/x86_64-linux-gnu/libgtk-4.so.1
#31 0x00007fe50a463099 in ??? () at /lib/x86_64-linux-gnu/libgtk-4.so.1
#32 0x00007fe50a6a368e in ??? () at /lib/x86_64-linux-gnu/libgtk-4.so.1
#33 0x00007fe50a38e54d in ??? () at /lib/x86_64-linux-gnu/libgtk-4.so.1
#34 0x00007fe50a47b00c in ??? () at /lib/x86_64-linux-gnu/libgtk-4.so.1
#35 0x00007fe50a5cc740 in ??? () at /lib/x86_64-linux-gnu/libgtk-4.so.1
#36 0x00007fe50a63bafb in ??? () at /lib/x86_64-linux-gnu/libgtk-4.so.1
#37 0x00007fe50ad96add in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#38 0x00007fe50ad96bd6 in g_signal_emit_valist ()
at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#39 0x00007fe50ad96c93 in g_signal_emit ()
at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#40 0x00007fe50a698086 in ??? () at /lib/x86_64-linux-gnu/libgtk-4.so.1
#41 0x00007fe50a5df04e in ??? () at /lib/x86_64-linux-gnu/libgtk-4.so.1
#42 0x00007fe50ac76b2c in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#43 0x00007fe50acd246f in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#44 0x00007fe50ac74d20 in g_main_context_iteration ()
at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#45 0x00007fe50aea5b5d in g_application_run ()
at /lib/x86_64-linux-gnu/libgio-2.0.so.0
#46 0x0000560d49b81e93 in main ()
```
* Screenshots
## Steps to reproduce:
1. Open GNOME Settings
2. Go to "Keyboard" settings
3. Click at "View and customize shortcuts"https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2669Keyboard > View and Customize Shortcuts: "Reset all shortcuts to their defaul...2023-11-27T09:54:36ZAutomeris naranjaKeyboard > View and Customize Shortcuts: "Reset all shortcuts to their default keybindings" tooltip doesn't follow HIG guidelines## Affected version
gnome-control-center-45.0-1.fc39.x86_64
## Description
When going to Keyboard > View and Customize Shortcuts, the Reset All button shows a tooltip, which is "Reset all shortcuts to their default keybindings". However...## Affected version
gnome-control-center-45.0-1.fc39.x86_64
## Description
When going to Keyboard > View and Customize Shortcuts, the Reset All button shows a tooltip, which is "Reset all shortcuts to their default keybindings". However, HIG advises to use short tooltips and to use header capitalization.
![Screenshot_from_2023-09-20_12-23-32](/uploads/bfe3f998b77ac76af4cc0a77a58f3376/Screenshot_from_2023-09-20_12-23-32.png)
I wonder if this tooltip is actually necessary, since the button already has a label and shows a confirmation dialog:
![Screenshot_from_2023-09-24_14-45-55](/uploads/abdc3bcb8be5d5a0a7e9ca061613e6b2/Screenshot_from_2023-09-24_14-45-55.png)https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2479Keyboard shortcuts dialog only shows "Add Custom Shortcut" when there are no ...2023-05-31T08:16:10ZSam Hewittsnwh@gnome.orgKeyboard shortcuts dialog only shows "Add Custom Shortcut" when there are no shortcutsClicking the "Custom Shortcuts" row, when there are no custom shortcuts on the device, traps the dialog into only showing the "Add Custom Shortcut" view for all sections afterwards, see below where it's shown for "Sound and Media".
![im...Clicking the "Custom Shortcuts" row, when there are no custom shortcuts on the device, traps the dialog into only showing the "Add Custom Shortcut" view for all sections afterwards, see below where it's shown for "Sound and Media".
![image](/uploads/e5bcd9c2161f82b585981211881ed3e4/image.png)https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2412cancel button doesn't work on reset all, keyboard shortcut2023-11-21T04:31:01ZMuhammad Akbar Yanuar Mantaricancel button doesn't work on reset all, keyboard shortcut<!--
Not following the communication guidelines [1] will mean your issue or comment
will be removed. Read it carefully before submitting this issue.
[1] https://gitlab.gnome.org/GNOME/gnome-control-center/blob/main/docs/CODE_OF_CONDUC...<!--
Not following the communication guidelines [1] will mean your issue or comment
will be removed. Read it carefully before submitting this issue.
[1] https://gitlab.gnome.org/GNOME/gnome-control-center/blob/main/docs/CODE_OF_CONDUCT.md#communication-guidelines
-->
if i want cancel button on reset all, keyboard shortcut. its doesn't work. only work if press ESC on keyboard.
Steps to reproduce:
1. Open GNOME Settings
2. Select Keyboard
3. Select View and Customize Shortcut
4. Select Reset All
5. Select Cancel
![Screencast_from_2023-03-21_20-32-55](/uploads/dc0bd9f238bf2ae6245e2ddbf5c04ed3/Screencast_from_2023-03-21_20-32-55.webm)https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2394Compose Key Not in Overview/Settings Search2023-04-04T20:10:48ZBarrettCompose Key Not in Overview/Settings Search<!--
Not following the communication guidelines [1] will mean your issue or comment
will be removed. Read it carefully before submitting this issue.
[1] https://gitlab.gnome.org/GNOME/gnome-control-center/blob/main/docs/CODE_OF_CONDUC...<!--
Not following the communication guidelines [1] will mean your issue or comment
will be removed. Read it carefully before submitting this issue.
[1] https://gitlab.gnome.org/GNOME/gnome-control-center/blob/main/docs/CODE_OF_CONDUCT.md#communication-guidelines
-->
Hi,
The compose key setting doesn't appear when searching in the Activities Overview or Setting app itself.
[Here's some screenshots!](https://imgur.com/a/mliqEw1) (Yeah, you see those Firefox results? I tried A LOT for this lol)
Please consider adding a "Compose Key" option to show up in the Activities Overview and Settings search results, at least as a keyword to bring up the Keyboard tab.
This may be out of scope for this program (maybe for other parts of GNOME, like the shell itself?). That said, I've been copying and pasting from Characters for months in a language class since I never found the Compose key option in GNOME Settings. In general, I just search for settings from the GNOME Overview, so I never tried it in the Settings search bar.
The GNOME [documentation on this topic](https://help.gnome.org/users/gnome-help/stable/tips-specialchars.html.en) doesn't note that GNOME Settings now has the functionality to set the Compose Key directly. It says to change it in GNOME Tweaks. When I checked, and it wasn't there, I assumed it was removed. Very little online mentions anything about the compose key. When I tried using the dconf method of enabling the key, it failed, then filled my logs with error messages, so that was a no-go...
Anyways, point is: please take adding a Compose Key search term into consideration for future releases of the GNOME Settings application. It would help many dumb people such as myself, and also help smarter people find the real menu faster. :-)
If you can give some basic advice on where to start, I'm happy to PR some changes myself... Or at least look into what changes need to be made in order to fix the problem.
Thank you,
Barrett
----
Steps to reproduce:
1. Open GNOME Overview
2. Type "Compose Key" in the fun little box
3. See nothing :-(
or
1. Open GNOME Settings
2. Type "Compose Key" in the high-tech little box
3. See nothing :-(
I'm running the newest version of Fedora 37, on a MacBook Pro. I am using a patched Asahi kernel, though I doubt that changes this issue. Just in case, [here's my system information](https://linux-hardware.org/?probe=8a8b88087b)!https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2390Create keyboard shortcut screen is displayed in the other shortcut lists2023-05-30T08:30:50ZChardinson VenturaCreate keyboard shortcut screen is displayed in the other shortcut lists<!--
Not following the communication guidelines [1] will mean your issue or comment
will be removed. Read it carefully before submitting this issue.
[1] https://gitlab.gnome.org/GNOME/gnome-control-center/blob/main/docs/CODE_OF_CONDUC...<!--
Not following the communication guidelines [1] will mean your issue or comment
will be removed. Read it carefully before submitting this issue.
[1] https://gitlab.gnome.org/GNOME/gnome-control-center/blob/main/docs/CODE_OF_CONDUCT.md#communication-guidelines
-->
When you open the session to create a new shortcut, go back and enter one of the shortcut lists, the creation new shortcut session is displayed except if you have a custom shortcut added. Yes, delete that custom shortcut and go back and enter one of the lists, the creation new shortcut session is shown again.
System Information:
<pre>
Operative System: Fedora Linux 38 Workstation
GNOME Control Center: 44~beta
Windowing System: Wayland
</pre>
Steps to reproduce:
1. Open GNOME Settings
2. Go to Keyboard
3. Enter custom shortcuts
4. Exit custom shortcuts and go to one of the default shortcut lists.
Video demonstration:
![Screencast_from_2023-03-09_01-53-55](/uploads/4e023339a3ca865496ee3df6eff075c9/Screencast_from_2023-03-09_01-53-55.webm)https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2282keyboards: The menu options from the input source entry are grayed out2023-01-30T11:44:16ZGhost Userkeyboards: The menu options from the input source entry are grayed out## Steps to reproduce
1. Go to Keyboard & Shortcuts
2. Make sure you have one input source added
3. Click in the ellipsis menu
4. Click in "Move Up" or "Move Down"
## Seen behavior
All options will be grayed out:
![Screencast_from_20...## Steps to reproduce
1. Go to Keyboard & Shortcuts
2. Make sure you have one input source added
3. Click in the ellipsis menu
4. Click in "Move Up" or "Move Down"
## Seen behavior
All options will be grayed out:
![Screencast_from_2023-01-06_02-18-04](/uploads/5d0b88ba4ebebb8da2cd1dfd5f0e1adb/Screencast_from_2023-01-06_02-18-04.webm)
After reopening the Settings window, this issue goes away.
## Additional info
- gnome-control-center-43.2-1.fc37.x86_64https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2202Keyboard Shortcuts revamp followups2023-03-13T15:48:50ZTobias BernardKeyboard Shortcuts revamp followupsFollowup issues from !1510
- [x] There's a single headerbar across main view and sub-views, which is not how we usually do the deck/leafet pattern. Instead, there should be multiple headerbars attached to the actual views. This would al...Followup issues from !1510
- [x] There's a single headerbar across main view and sub-views, which is not how we usually do the deck/leafet pattern. Instead, there should be multiple headerbars attached to the actual views. This would also enable back gestures, which are currently not working.
- [x] The search bar spacing looks good during scrolling, but it's unbalanced in the non-scrolling case (too much spacing below, not enough above). Could we make it dynamic, i.e. have more spacing above the search bar in the initial state, which shrinks as you scroll and the divider is added? If not, I'd go with a regular search bar here, with an always-visible divider and headerbar background color.
![image](/uploads/b3aba7d9a9e995c5240cdc3eae8f9263/image.png)
![image](/uploads/7450d659011080653a2249f731918668/image.png)
- [ ] The dialog to actually set the shortcut should not be a dialog, but rather an inline deck/leaflet sub-view. That way it could also be closed in a more standard way (Esc-only is quite odd).
![image](/uploads/298a17c31eec90111a05b3743821ad76/image.png)
- [x] The search entry needs 6px horizontal margins on it, currently it's possible to resize the window to this:
![image](/uploads/3e471fec379bb4f823ba0f50aca18d46/image.png)
- [x] The content of the custom shortcuts empty state view should be vertically centered
![image](/uploads/dd0ac4d8084e2200b2a34288fd9b0a98/image.png)
cc @pksadiq @snwhhttps://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2169Error when using the German language in the "Custom Shortcuts" Menu2022-12-08T10:28:42ZSimon MaximilianError when using the German language in the "Custom Shortcuts" Menu<!--
Not following the communication guidelines [1] will mean your issue or comment
will be removed. Read it carefully before submitting this issue.
[1] https://gitlab.gnome.org/GNOME/gnome-control-center/blob/main/docs/CODE_OF_CONDUC...<!--
Not following the communication guidelines [1] will mean your issue or comment
will be removed. Read it carefully before submitting this issue.
[1] https://gitlab.gnome.org/GNOME/gnome-control-center/blob/main/docs/CODE_OF_CONDUCT.md#communication-guidelines
-->
Detailed description of the issue. Put as much information as you can, potentially
with images showing the issue.
Steps to reproduce:
1. Activate the German language in settings
2. Open GNOME Settings
2. Go to Keyboard > Shortcuts
3. Click on "Custom Shortcuts"
Hello, it seems this bug is coming from one of the last releases of the gnome-control-center. It was found with EndeavourOS. It seems when using the German language, the text somehow gets too long to be rendered in the "Custom Shortcuts" Menu. Although the window gets a bit wider, it wont redraw anymore and causes a weird looking window. As soon as I switch to English, all problems are fixed and there is no problem anymore. I'll put some pictures explaining the problem below.
## "Shortcuts" Screen in German
![1](/uploads/5ac13cf0e738fc4cbbaeb28d56c4eadd/1.png)
## Weird looking "Custom Shortcuts" Screen in German
![2](/uploads/be9a27f5902efa87f9870aa8eb04ee31/2.png)
## In English everything is normal
![3](/uploads/b791c1a8f45b5696d3d714ff9a3c17ba/3.png)https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2160Keyboard shortcuts: Top-level rows should have arrows2022-12-08T10:28:42ZTobias BernardKeyboard shortcuts: Top-level rows should have arrowsRows opening sub-pages should have arrows on the right side to indicate that, but the ones in the keyboard shortcut dialog don't:
![image](/uploads/94ed25240d9c6eaebd931403a9ef69ae/image.png)Rows opening sub-pages should have arrows on the right side to indicate that, but the ones in the keyboard shortcut dialog don't:
![image](/uploads/94ed25240d9c6eaebd931403a9ef69ae/image.png)https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2159Keyboard shortcuts: Search header styling2022-12-08T10:28:42ZTobias BernardKeyboard shortcuts: Search header stylingThe category headers during search don't look great currently. I'd style them like regular list headers rather than list rows, and have the separate categories be separate lists.
![image](/uploads/e73674e6ec91d1ff2591a1818113da03/image....The category headers during search don't look great currently. I'd style them like regular list headers rather than list rows, and have the separate categories be separate lists.
![image](/uploads/e73674e6ec91d1ff2591a1818113da03/image.png)https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2133Unable to interact with Input Sources filter search in Keyboard settings on X112022-11-12T17:07:39ZDomenico IezziUnable to interact with Input Sources filter search in Keyboard settings on X11<!--
Not following the communication guidelines [1] will mean your issue or comment
will be removed. Read it carefully before submitting this issue.
[1] https://gitlab.gnome.org/GNOME/gnome-control-center/blob/main/docs/CONTRIBUTING.m...<!--
Not following the communication guidelines [1] will mean your issue or comment
will be removed. Read it carefully before submitting this issue.
[1] https://gitlab.gnome.org/GNOME/gnome-control-center/blob/main/docs/CONTRIBUTING.md#communication-guideline
-->
Fresh Archlinux installation. In the first boot, keyboard layout is US so I open gnome settings to add Italian keyboard layout. I go to "Keyboard", "Input sources" and click the "+" icon. In the windows that opens I click "Other" to show other possible layouts, but if I try to interact with the search box on the bottom nothing happens, I cannot type anything and the cursor does not blink.
Journalctl reports following logs, not sure if it's related:
```
Nov 11 19:12:43 myhostname gnome-shell[1193]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1c00049
Nov 11 19:12:44 myhostname gnome-shell[1193]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x559d183dce20] is on because it needs an allocation.
Nov 11 19:12:44 myhostname gnome-shell[1193]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x559d12502c60] is on because it needs an allocation.
```
Steps to reproduce:
1. Open GNOME Settings
2. go to "Keyboard", "Input sources" and click the "+" icon
3. click "Other" and try to interact with window
System details:
- gnome-shell 1:43.1-1
- gnome-control-center 43.1-2
- linux 6.0.8-arch1-1
- nvidia 520.56.06-10https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2107Keyboard: Align button to create shortcut to the other elements of the window2023-07-05T17:30:58ZChardinson VenturaKeyboard: Align button to create shortcut to the other elements of the windowThe "set shortcut" button is not at the same distance as the other elements of the window.
Keyboard > Keyboard Shortcuts > Custom Shortcuts > Add Shortcut
![Untitled](/uploads/63125c87fb6dd4ccc8771163cb2bfc57/Untitled.png)
![Untitled_1...The "set shortcut" button is not at the same distance as the other elements of the window.
Keyboard > Keyboard Shortcuts > Custom Shortcuts > Add Shortcut
![Untitled](/uploads/63125c87fb6dd4ccc8771163cb2bfc57/Untitled.png)
![Untitled_1](/uploads/18fa231aa0a2f28198cd278037a306b4/Untitled_1.png)