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

4
GNOME Settings
5 6
====================

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

10
## Contributing
11

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

15
## Reporting Bugs
16 17

Bugs should be reported to the GNOME bug tracking system under the product
18
gnome-control-center. It is available at https://gitlab.gnome.org.
19 20 21 22 23 24 25 26 27

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]

28
### How to get a stack trace
29 30 31 32 33 34

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
35
		ie. gdb gnome-keyboard-properties
36 37 38 39
	Start the program
		ie. (gdb) run
	Reproduce the crash and the program will exit to the gdb prompt
	Get the back trace
40
		ie. (gdb) bt full
41 42

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