A fork of Gnome-control-center with some tweaks
Find a file
Jürg Billeter 356e767473 reviewed by: Sergey V. Udaltsov <svu@gnome.org>
2005-10-10  Jürg Billeter  <j@bitron.ch>

	reviewed by: Sergey V. Udaltsov  <svu@gnome.org>

	* gnome-settings-keyboard.c: (gsd_keyboard_get_hostname_key),
	(numlock_NumLock_modifier_mask), (numlock_set_xkb_state),
	(numlock_gconf_state_key), (numlock_get_gconf_state),
	(numlock_set_gconf_state), (numlock_xkb_callback),
	(numlock_install_xkb_callback), (apply_settings),
	(gnome_settings_keyboard_init): Remember NumLock state between sessions.
	Fixes bug #74215. Patch by Sebastian Kapfer  <sebastian_kapfer@web.de>
2005-10-10 19:32:45 +00:00
archiver Here too 2005-05-11 16:07:51 +00:00
capplets Remove utf8 validate check (gnome_wp_props_wp_set): If the filename we 2005-10-01 21:29:39 +00:00
control-center added a11y support 2005-06-06 21:49:33 +00:00
debian Initial debian directory 2001-10-24 12:49:00 +00:00
gnome-settings-daemon reviewed by: Sergey V. Udaltsov <svu@gnome.org> 2005-10-10 19:32:45 +00:00
help fix the make distcheck. 2005-07-27 13:35:45 +00:00
idl Add IDL for SettingsDaemon 2002-03-11 01:44:21 +00:00
libbackground Make sure that the UTF8 filename is valid and exists before trying to use 2005-10-01 21:18:21 +00:00
libwindow-settings See 2005-07-19 12:32:38 +00:00
m4 switch to gnome-doc-utils, require 1.9 to build the tarball correctly 2005-07-27 12:56:39 +00:00
po Translation updated by Ivar Smolin. 2005-10-08 10:17:29 +00:00
root-manager fixup localedir to work with solaris gettext (fixes bug #83616) 2002-06-18 19:29:45 +00:00
schemas fixing #310513 2005-07-26 20:38:25 +00:00
typing-break Fixes #318231 2005-10-08 16:11:35 +00:00
vfs-methods fix a typo with the StartupNotify option, thanks Vincent Fretin 2005-09-25 21:23:06 +00:00
.cvsignore switch to gnome-doc-utils, require 1.9 to build the tarball correctly 2005-07-27 12:56:39 +00:00
AUTHORS New and better than ever in a new home 1998-12-08 20:47:55 +00:00
autogen.sh switch to gnome-doc-utils, require 1.9 to build the tarball correctly 2005-07-27 12:56:39 +00:00
ChangeLog update for 2.12.1. 2005-10-03 08:47:06 +00:00
configure.in update for 2.12.1. 2005-10-03 08:47:06 +00:00
control-center.spec.in require either xscreensaver or gnome-screensaver. 2005-07-25 11:56:28 +00:00
COPYING add 2002-04-19 19:24:22 +00:00
MAINTAINERS Added new MAINTAINERS 2005-10-10 16:28:21 +00:00
Makefile.am switch to gnome-doc-utils, require 1.9 to build the tarball correctly 2005-07-27 12:56:39 +00:00
NEWS update for 2.12.1. 2005-10-02 22:41:50 +00:00
README remove the png so that it can theme. 2003-12-16 21:38:53 +00:00
TODO update TODO list 2002-04-10 02:04:23 +00:00
TODO.xml Fixed typo in TODO.xml file 2000-10-08 19:19:44 +00:00

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