diff options
| author | Perberos <[email protected]> | 2011-12-01 21:51:44 -0300 |
|---|---|---|
| committer | Perberos <[email protected]> | 2011-12-01 21:51:44 -0300 |
| commit | 0b0e6bc987da4fd88a7854ebb12bde705e92c428 (patch) | |
| tree | 47d329edd31c67eaa36b2147780e37e197e901b5 /README | |
| download | mate-control-center-0b0e6bc987da4fd88a7854ebb12bde705e92c428.tar.bz2 mate-control-center-0b0e6bc987da4fd88a7854ebb12bde705e92c428.tar.xz | |
moving from https://github.com/perberos/mate-desktop-environment
Diffstat (limited to 'README')
| -rw-r--r-- | README | 53 |
1 files changed, 53 insertions, 0 deletions
@@ -0,0 +1,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 [email protected] 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 |