4 This is GTK+ version 1.2.0. GTK+, which stands for the Gimp ToolKit,
5 is a library for creating graphical user interfaces for the X Window
6 System. It is designed to be small, efficient, and flexible. GTK+ is
7 written in C with a very object-oriented approach.
9 The official ftp site is:
10 ftp://ftp.gtk.org/pub/gtk
12 The official web site is:
15 A mailing list is located at:
18 To subscribe: mail -s subscribe gtk-list-request@redhat.com < /dev/null
19 (Send mail to gtk-list-request@redhat.com with the subject "subscribe")
24 See the file 'INSTALL'
29 Bugs should be reported to the GNOME bug tracking
30 system. (http://bugs.gnome.org). To report a problem
31 about GTK+, send mail to submit@bugs.gnome.org.
33 The subject of the mail should describe your problem.
34 In the body of the mail, you should first include
35 a "pseudo-header" that gives the package and
36 version number. This should be separated by a blank
37 line from the actual headers.
42 [ Please substitute 1.2.0 with the version of GTK+ that
45 Then describe the bug. Include:
47 * Information about your system. For instance:
49 - What operating system and version
51 - For Linux, what version of the C library
53 And anything else you think is relevant.
55 * How to reproduce the bug.
57 If you can reproduce it with the testgtk program that is built
58 in the gtk/ subdirectory, that will be most convenient. Otherwise,
59 please include a short test program that exhibits the behavior.
60 As a last resort, you can also provide a pointer to a larger piece
61 of software that can be downloaded.
63 (Bugs that can be reproduced within the GIMP are almost as good
64 as bugs that can be reproduced in testgtk. If you are reporting a
65 bug found with the GIMP, please include the version number of the GIMP
68 * If the bug was a crash, the exact text that was printed out
69 when the crash occured.
71 * Further information such as stack traces may be useful, but
72 is not necessary. If you do send a stack trace, and the error
73 is an X error, it will be more useful if the stacktrace
74 is produced running the test program with the --sync command
77 An example of a bug report:
80 To: submit@bugs.gnome.org
81 From: yourname@your.address.org
82 Subject: handlebox test in testgtk is misnamed.
87 When I run gtk/testgtk, the button "handle box"
88 is misnamed. There are multiple handle boxes in
89 the demo, so it should be "handle boxes", to
90 be like "buttons" or "check buttons".
96 Patches can be uploaded to the incoming/ directory on
97 ftp.gtk.org. Please follow the instructions there, and include
98 your name and email address in the README file.
100 If the patch fixes a bug, it is usually a good idea to include
101 all the information described in "How to Report Bugs".