A fork of Gnome-control-center with some tweaks
Find a file
Ting-Wei Lan 9df14924d4 tests: Don't hard-code the path to python
Python isn't always installed in /usr/bin. If we hard-code the path,
these tests will fail on *BSD because they install python in different
prefixes such as /usr/local and /usr/pkg.
2018-08-13 01:18:16 +00:00
.gitlab/issue_templates project: Add issue templates 2018-05-02 21:02:13 -03:00
build-aux flatpak: Use version 1.12.0 of NetworkManager 2018-07-30 15:59:47 +02:00
data/icons project: Update meson files 2018-05-03 00:45:29 -03:00
docs project: Document maintainers and workflow 2018-07-16 20:50:12 -03:00
gettext/its build: Fix translation context missing from keyboard entries 2018-01-24 20:43:34 +01:00
man project: Update meson files 2018-05-03 00:45:29 -03:00
panels display: Reset the window title after removing custom headerbar 2018-08-03 14:43:47 +02:00
po Update German translation 2018-08-12 12:22:46 +00:00
search-provider project: Update meson files 2018-05-03 00:45:29 -03:00
shell model: Convert panel icons to symbolic variants if possible 2018-07-29 21:45:38 +00:00
subprojects build: Drop libgd 2018-03-16 15:55:10 -03:00
tests tests: Don't hard-code the path to python 2018-08-13 01:18:16 +00:00
.gitignore project: Update gitignore 2018-05-12 20:56:04 -03:00
.gitlab-ci.yml CI: do not run 'pages' if not testing 2018-08-06 21:46:46 +00:00
.gitmodules git: Remove libgd from .gitmodules 2018-03-23 10:46:52 -03:00
COPYING build: Update COPYING with new mailing address 2012-08-22 15:33:18 +01:00
gnome-control-center.doap project: Document maintainers and workflow 2018-07-16 20:50:12 -03:00
meson.build 3.29.90 2018-07-31 13:45:22 -03:00
meson_options.txt window: Warn about development builds 2018-05-14 18:24:03 -03:00
NEWS 3.29.90 2018-07-31 13:45:22 -03:00
README.md docs: add the coverage badge 2018-07-05 23:25:23 +00:00

Build Status Coverage report License

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.

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.

Reporting Bugs

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
How to reproduce the bug if possible
If the bug was a crash, include the exact text that was printed out
A stacktrace where possible [see below]

How to get a stack trace

If the crash is reproducible, it is possible to get a stack trace and attach it to the bug report. The following steps are used to obtain a stack trace -

Run the program in gdb [the GNU debugger] or any other debugger
	ie. gdb gnome-keyboard-properties
Start the program
	ie. (gdb) run
Reproduce the crash and the program will exit to the gdb prompt
Get the back trace
	ie. (gdb) bt full

Once you have the backtrace, copy and paste this either into the 'Comments' field or attach a file with it included.