A fork of Gnome-control-center with some tweaks
Find a file
2012-10-16 08:34:43 +02:00
m4 m4: Add stub directory so gnome-autogen.sh doens't blow up 2010-10-08 15:46:10 -04:00
man Add a man page 2012-08-04 12:54:49 -04:00
panels info: Don't block for PackageKit 2012-10-15 16:41:50 +02:00
po Updated Slovenian translation 2012-10-16 08:34:43 +02:00
shell shell: Fix entering the same panel twice 2012-09-25 21:25:19 +02:00
AUTHORS New and better than ever in a new home 1998-12-08 20:47:55 +00:00
autogen.sh autogen.sh: Remove unnneded lines in autogen.sh 2010-10-14 04:29:09 +02:00
ChangeLog Automatically create the ChangeLog file from VCS history 2009-11-14 15:17:28 +00:00
configure.ac 3.6.1 2012-10-08 18:55:14 +02:00
COPYING build: Update COPYING with new mailing address 2012-08-22 15:33:18 +01:00
git.mk git.mk: Update from upstream 2012-05-09 13:14:32 -04:00
gnome-control-center.doap Update DOAP file to reflect reality 2012-10-09 10:31:53 +02:00
MAINTAINERS doap: Add myself as maintainer 2011-04-26 12:03:17 +01:00
Makefile.am build: Add --disable-documentation option 2012-08-06 18:19:24 -04:00
NEWS 3.6.1 2012-10-08 18:55:14 +02:00
README remove obsolete list of dependencies, and update references to cvs (closes 2007-03-11 20:05:46 +00:00
TODO update TODO list 2002-04-10 02:04:23 +00:00
update-from-gsd.sh wacom: Move update-from-gsd.sh to root 2012-04-19 12:01:14 +01:00

GNOME Control Center  
====================

About -

The control center is GNOME'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 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-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 
gnomecc-list@gnome.org 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