Otherwise glib will make internal calls before setlocale is called: ** (process:1124144): WARNING **: 10:16:58.983: dcgettext("(null)", "", 5) called before setlocale() #0 0x00007ffff7c80f77 in g_logv () at /lib64/libglib-2.0.so.0 #1 0x00007ffff7c81233 in g_log () at /lib64/libglib-2.0.so.0 #2 0x00007ffff7fbb6c6 in dcgettext (__domainname=<optimized out>, __msgid=0x7ffff7ce6c5a "", __category=<optimized out>) at ../../../../Projects/jhbuild/gettext-pseudolocale/gettext-pseudolocale.c:194 #3 0x00007ffff7c6478e in _g_dgettext_should_translate () at /lib64/libglib-2.0.so.0 #4 0x00007ffff7c6484b in g_dgettext () at /lib64/libglib-2.0.so.0 #5 0x00007ffff7e98974 in g_application_class_intern_init () at /lib64/libgio-2.0.so.0 #6 0x00007ffff7d9cfb8 in g_type_class_ref () at /lib64/libgobject-2.0.so.0 #7 0x00007ffff7d9cc95 in g_type_class_ref () at /lib64/libgobject-2.0.so.0 #8 0x00007ffff7d9cc95 in g_type_class_ref () at /lib64/libgobject-2.0.so.0 #9 0x00007ffff7d9cc95 in g_type_class_ref () at /lib64/libgobject-2.0.so.0 #10 0x00007ffff7d8671a in g_object_new_valist () at /lib64/libgobject-2.0.so.0 #11 0x00007ffff7d867fd in g_object_new () at /lib64/libgobject-2.0.so.0 #12 0x0000000000449bcc in cc_application_new () at ../../../../Projects/jhbuild/gnome-control-center/shell/cc-application.c:294 #13 0x0000000000448fa6 in main (argc=1, argv=0x7fffffffd138) at ../../../../Projects/jhbuild/gnome-control-center/shell/main.c:55 |
||
---|---|---|
.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.