blob: f36dd394db66f9a79fe6c97177a9cdc10c1d97d6 (
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
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
|
GNOME Control Center
====================
Version: 2.1.4
GNOME Control Center for the GNOME 2.2 Beta Desktop contains the following -
gnome-accessibility-keyboard-properties
gnome-background-properties
gnome-default-applications-properties
gnome-file-types-properties
gnome-font-properties
gnome-keybinding-properties
gnome-keyboard-properties
gnome-mouse-properties
gnome-network-preferences
gnome-sound-properties
gnome-theme-manager
gnome-ui-properties
gnome-window-properties
gnome-control-center
gnome-settings-daemon
Requirements -
intltool >= 0.21
gtk+ >= 2.0.0
gconf >= 2.0.0
libgnome >= 2.0.0
libgnomeui >= 2.0.0
libglade >= 2.0.0
libbonobo >= 2.0.0
libbonoboui >= 2.0.0
libgnomevfs >= 2.0.0
gnome-desktop >= 2.0.0
Installation -
See the file 'INSTALL'
How to report bugs -
Bugs should be reported to the GNOME 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 gnome-calculator
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
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 one of
the people listed in the MAINTAINERS file. 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. cvs diff -u file-to-be-patched.c > patch.diff
|
