README.md 2.11 KB
Newer Older
Claudio André's avatar
Claudio André committed
1
[![Build Status](https://gitlab.gnome.org/GNOME/gnome-control-center/badges/master/build.svg)](https://gitlab.gnome.org/GNOME/gnome-control-center/pipelines)
Claudio André's avatar
Claudio André committed
2
[![Coverage report](https://gitlab.gnome.org/GNOME/gnome-control-center/badges/master/coverage.svg)](https://gnome.pages.gitlab.gnome.org/gnome-control-center/)
Claudio André's avatar
Claudio André committed
3 4
[![License](https://img.shields.io/badge/License-GPL%20v2-blue.svg)](https://gitlab.gnome.org/GNOME/gnome-control-center/blob/master/COPYING)

5
GNOME Settings
6 7
====================

8 9
GNOME Settings is GNOME's main interface for configuration of various aspects of
your desktop.
10

11
## Contributing
12

13 14
See `docs/CONTRIBUTING.md` for details on the contribution process, and `docs/HACKING.md`
for the coding style guidelines.
15

Claudio André's avatar
Claudio André committed
16 17 18 19 20 21 22 23 24
## 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.

25
## Reporting Bugs
26 27

Bugs should be reported to the GNOME bug tracking system under the product
28
gnome-control-center. It is available at [GitLab Issues](https://gitlab.gnome.org/GNOME/gnome-control-center/issues).
29 30 31 32 33 34 35 36 37

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]

38
### How to get a stack trace
39 40 41 42 43 44

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
45
		ie. gdb gnome-keyboard-properties
46 47 48 49
	Start the program
		ie. (gdb) run
	Reproduce the crash and the program will exit to the gdb prompt
	Get the back trace
50
		ie. (gdb) bt full
51 52

Once you have the backtrace, copy and paste this either into the 
Claudio André's avatar
Claudio André committed
53
'Comments' field or attach a file with it included.