A fork of Gnome-control-center with some tweaks
Find a file
Bastien Nocera d28ffc9902 network: Fix gateway entry visibility
From https://bugzilla.gnome.org/show_bug.cgi?id=765969 as explained by
Dan Winship:
"
libnm-util/libnm-glib had a buggy data model, which nm-connection-editor
(and then gnome-control-center) copied, in which each manually-configured
IP address has an associated gateway address. In reality, NM always just
took the first non-empty gateway value from the address array, and
completely ignored any other gateway values.
libnm represents this more accurately, by having a single gateway
value which is separate from the address array. Ideally, the editors should
show it this way as well (eg, like nmtui does). Failing that, it would
be nice to at least make it so that only the first row in the address
table can have a non-empty gateway value.
"

We went for the second option, only showing a gateway entry for the
first address in the list.

This isn't related to route-specific gateway addresses.

https://bugzilla.gnome.org/show_bug.cgi?id=765969
2016-09-20 10:30:27 +02:00
libgd@2899de073f libgd: Update to fix GdNotification theming 2014-09-03 13:14:51 +02:00
m4 build: Import egg-list-box as a git submodule 2012-11-27 11:32:11 +01:00
man man: Drop obsolete region arguments 2013-02-19 17:58:33 +01:00
panels network: Fix gateway entry visibility 2016-09-20 10:30:27 +02:00
po Update Basque language 2016-09-19 18:43:11 +02:00
search-provider build: create another executable for the new layout 2016-06-03 12:32:36 -03:00
shell shell: ensure valid data when loading the panel 2016-07-26 11:59:07 -03:00
.gitmodules build: Drop EggListBox 2013-07-02 16:19:09 +01:00
AUTHORS New and better than ever in a new home 1998-12-08 20:47:55 +00:00
autogen.sh build: Remove PKG_NAME from autogen.sh 2015-10-19 11:19:17 +02:00
ChangeLog Automatically create the ChangeLog file from VCS history 2009-11-14 15:17:28 +00:00
configure.ac 3.21.92 2016-09-13 12:34:36 +02:00
COPYING build: Update COPYING with new mailing address 2012-08-22 15:33:18 +01:00
git.mk Update .gitignore and libgd 2013-10-17 15:01:38 -04:00
gnome-control-center.doap doap: add <programming-language> 2014-07-31 18:56:39 +02:00
MAINTAINERS doap: Add myself as maintainer 2011-04-26 12:03:17 +01:00
Makefile.am Makefile: Move to AM_DISTCHECK_CONFIGURE_FLAGS 2016-04-04 21:47:27 -07:00
Makefile.decl build: Add GTest Makefile snippet 2016-06-10 15:04:44 +02:00
NEWS 3.21.92 2016-09-13 12:34:36 +02:00
README Corrected bugzilla product name in README 2015-02-26 23:20:43 +01: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
gnome-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.

See https://live.gnome.org/GnomeLove/SubmittingPatches for how to create
patches.