summaryrefslogtreecommitdiff
path: root/README
blob: 040b236e85efeaba6154ad2526a35cd8161cfe49 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
MATE Control Center
====================

About -

The control center is MATE's main interface for configuration of various
aspects of your desktop.

Installation -

See the file 'INSTALL'

How to report bugs -

Bugs should be reported to the MATE bug tracking system under the product
control-center. It is available at http://bugzilla.gnome.org.

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 mate-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.


Patches -

Patches should be submitted to bugzilla.gnome.org or emailed to the
matecc-list@gnome.org list. If using bugzilla, attach
the patch to a new bug report [or preferably, check to see if there is
already a bug report that corresponds to your patch]. Bug reports
containing patches should include the 'PATCH' keyword.

Patches should be created using the unified diff form.
	ie. svn diff file-to-be-patched.c > patch.diff