| 1 | GNOME Control Center |
|---|
| 2 | ==================== |
|---|
| 3 | Version: 2.1.4 |
|---|
| 4 | |
|---|
| 5 | GNOME Control Center for the GNOME 2.2 Beta Desktop contains the following - |
|---|
| 6 | |
|---|
| 7 | gnome-accessibility-keyboard-properties |
|---|
| 8 | gnome-background-properties |
|---|
| 9 | gnome-default-applications-properties |
|---|
| 10 | gnome-file-types-properties |
|---|
| 11 | gnome-font-properties |
|---|
| 12 | gnome-keybinding-properties |
|---|
| 13 | gnome-keyboard-properties |
|---|
| 14 | gnome-mouse-properties |
|---|
| 15 | gnome-network-preferences |
|---|
| 16 | gnome-sound-properties |
|---|
| 17 | gnome-theme-manager |
|---|
| 18 | gnome-ui-properties |
|---|
| 19 | gnome-window-properties |
|---|
| 20 | gnome-control-center |
|---|
| 21 | gnome-settings-daemon |
|---|
| 22 | |
|---|
| 23 | Requirements - |
|---|
| 24 | |
|---|
| 25 | intltool >= 0.21 |
|---|
| 26 | gtk+ >= 2.0.0 |
|---|
| 27 | gconf >= 2.0.0 |
|---|
| 28 | libgnome >= 2.0.0 |
|---|
| 29 | libgnomeui >= 2.0.0 |
|---|
| 30 | libglade >= 2.0.0 |
|---|
| 31 | libbonobo >= 2.0.0 |
|---|
| 32 | libbonoboui >= 2.0.0 |
|---|
| 33 | libgnomevfs >= 2.0.0 |
|---|
| 34 | gnome-desktop >= 2.0.0 |
|---|
| 35 | |
|---|
| 36 | Installation - |
|---|
| 37 | |
|---|
| 38 | See the file 'INSTALL' |
|---|
| 39 | |
|---|
| 40 | How to report bugs - |
|---|
| 41 | |
|---|
| 42 | Bugs should be reported to the GNOME bug tracking system under the product |
|---|
| 43 | control-center. It is available at http://bugzilla.gnome.org. |
|---|
| 44 | |
|---|
| 45 | In the report please include the following information - |
|---|
| 46 | |
|---|
| 47 | Operating system and version |
|---|
| 48 | For Linux, version of the C library |
|---|
| 49 | How to reproduce the bug if possible |
|---|
| 50 | If the bug was a crash, include the exact text that was printed out |
|---|
| 51 | A stacktrace where possible [see below] |
|---|
| 52 | |
|---|
| 53 | How to get a stack trace - |
|---|
| 54 | |
|---|
| 55 | If the crash is reproducible, it is possible to get a stack trace and |
|---|
| 56 | attach it to the bug report. The following steps are used to obtain a |
|---|
| 57 | stack trace - |
|---|
| 58 | |
|---|
| 59 | Run the program in gdb [the GNU debugger] or any other debugger |
|---|
| 60 | ie. gdb gnome-calculator |
|---|
| 61 | Start the program |
|---|
| 62 | ie. (gdb) run |
|---|
| 63 | Reproduce the crash and the program will exit to the gdb prompt |
|---|
| 64 | Get the back trace |
|---|
| 65 | ie. (gdb) bt |
|---|
| 66 | |
|---|
| 67 | Once you have the backtrace, copy and paste this either into the |
|---|
| 68 | 'Comments' field or attach a file with it included. |
|---|
| 69 | |
|---|
| 70 | |
|---|
| 71 | Patches - |
|---|
| 72 | |
|---|
| 73 | Patches should be submitted to bugzilla.gnome.org or emailed to one of |
|---|
| 74 | the people listed in the MAINTAINERS file. If using bugzilla, attach |
|---|
| 75 | the patch to a new bug report [or preferably, check to see if there is |
|---|
| 76 | already a bug report that corresponds to your patch]. Bug reports |
|---|
| 77 | containing patches should include the 'PATCH' keyword. |
|---|
| 78 | |
|---|
| 79 | Patches should be created using the unified diff form. |
|---|
| 80 | ie. cvs diff -u file-to-be-patched.c > patch.diff |
|---|
