bad61a2229
The way shortcuts in mutter/gnome-shell work is that it looks up the keycode that generates the shortcut keyval at the lowest shift level and then checks if all the modifiers match. This does not work for shortcuts that for example include "dollar" to represent "<Shift>4", because on some keyboards/layout there is a separate dollar key key with its own keycode. This would be at a lower shift level than "<Shift>4". By always translating such shortcuts to "<Shift>number", we make sure the resulting shortcut will work in the shell and is closer to what the user likely intended the shortcut to be, because numbers are usually assigned to things that can be enumerated, such as workspaces or favorite applications. This also special cases the num-row key on layouts such as AZERTY, where the number is the shifted keyval, to always prefer the number. Due to the way the shell interprets these shortcuts, they still work and by always using numbers they work across different layouts. This change also fixes that pressing "<Shift><Super>4" was turned into "<Shift><Super>dollar", which effectively included the "<Shift>" twice. Fixes: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1528 |
||
|---|---|---|
| .gitlab/issue_templates | ||
| build-aux | ||
| data/icons | ||
| docs | ||
| gettext/its | ||
| man | ||
| panels | ||
| po | ||
| search-provider | ||
| shell | ||
| subprojects | ||
| tests | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .gitmodules | ||
| COPYING | ||
| gnome-control-center.doap | ||
| meson.build | ||
| meson_options.txt | ||
| NEWS | ||
| README.md | ||
GNOME Settings
GNOME Settings is GNOME's main interface for configuration of various aspects of your desktop.
Contributing
See docs/CONTRIBUTING.md for details on the contribution process, and docs/HACKING.md
for the coding style guidelines.
Reporting Bugs
Before reporting any bugs or opening feature requests, read the communication guidelines.
Bugs should be reported to the GNOME bug tracking system under the product gnome-control-center. It is available at GitLab Issues.
In the report please include the following information:
- Operating system and version
- For Linux, version of the C library
- Exact error message
- Steps to reproduce the bug
- If the bug is a visual defect, attach a screenshot
- If the bug is a crash, attach a backtrace if possible [see below]
How to get a backtrace
If the crash is reproducible, follow the steps to obtain a backtrace:
Install debug symbols for gnome-control-center.
Run the program in gdb [the GNU debugger] or any other debugger.
gdb gnome-control-center
Start the program.
(gdb) run
Reproduce the crash and when the program exits to (gdb) prompt, get the backtrace.
(gdb) bt full
Once you have the backtrace, copy and paste it into the 'Comments' field or attach it as a file to the bug report.
Testing Unstable Settings
It is quite easy to test and give feedback about the development version of GNOME Settings. Just access https://gitlab.gnome.org/GNOME/gnome-control-center/environments, get the latest version, download it, double-click the file, install and run.
Note that GNOME Settings Flatpak will only work if you are running the latest GNOME version in your host system.