A fork of Gnome-control-center with some tweaks
bdd4d0142e
2005-01-08 Rodney Dawes <dobey@novell.com> * background.desktop.in.in: Add %F to Exec command line * gnome-wp-capplet.[ch] (gnome_wp_remove_wp): Check that the tree path is not NULL before removing items from the list store (gnome_wp_load_stuffs): Don't duplicate the code from gnome_wp_add_image/gnome_wp_capplet_scroll_to_item here Load any images we were passed on the command line, and free the GSList that they were stored in after doing so (gnome_wp_file_changed): Clean up to just call gnome_wp_add_image and gnome_wp_capplet_scroll_to_item rather than duplicating the code (wallpaper_properties_init): Take a poptContext argument now Parse the poptContext into a GSList for loading the images from (main): Use a clearer variable name for the GnomeProgram object Get the poptContext from the GnomeProgram object and pass it through to wallpaper_properties_init Fixes #120720 |
||
|---|---|---|
| archiver | ||
| capplets | ||
| control-center | ||
| debian | ||
| gnome-settings-daemon | ||
| help | ||
| idl | ||
| libbackground | ||
| libwindow-settings | ||
| po | ||
| root-manager | ||
| schemas | ||
| typing-break | ||
| vfs-methods | ||
| .cvsignore | ||
| AUTHORS | ||
| autogen.sh | ||
| ChangeLog | ||
| configure.in | ||
| control-center.spec.in | ||
| COPYING | ||
| MAINTAINERS | ||
| Makefile.am | ||
| NEWS | ||
| README | ||
| TODO | ||
| TODO.xml | ||
GNOME Control Center ==================== Requirements - intltool >= 0.21 gtk+ >= 2.3.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 gnome-icon-theme >= 1.1.3 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