applications/gnome-control-center
3
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
A fork of Gnome-control-center with some tweaks
22237 commits 324 branches 641 tags 195 MiB
Find a file
Simon Arlott 019cbc6a54 network: Increase maximum MTU value from 10000 to 65536 
The maximum MTU value of 10000 is too low for USB Ethernet, which has a
maximum (for Linux USB gadgets) of 15412 bytes (although the upper limit
is the USB wMaxPacketSize which goes up to 4294967295 bytes):
  linux/drivers/usb/gadget/function/u_ether.c:#define GETHER_MAX_MTU_SIZE 15412

Multiple Intel NICs can use an MTU of 16110 bytes:
  linux/drivers/net/ethernet/intel/e1000/e1000_hw.h:#define MAX_JUMBO_FRAME_SIZE         0x3F00
  linux/drivers/net/ethernet/intel/e1000e/defines.h:#define MAX_JUMBO_FRAME_SIZE    0x3F00
  linux/drivers/net/ethernet/intel/igbvf/defines.h:#define MAX_JUMBO_FRAME_SIZE         0x3F00

The NetworkManager limit is 4294967295 bytes but this is unreasonable
in a typical enivornment because of the memory required for packets of
that size.

The maximum IPv4 and IPv6 (without using Jumbograms) packet size is 65535
bytes so increase the maximum MTU value to 65536 allow full size IP
packets to be used.

There is a corresponding change in network-manager-applet.
2023-03-24 01:47:09 +00:00
.gitlab/issue_templates Split code of conduct into separate document 2022-11-13 22:04:37 +01:00
build-aux build-aux: switch flatpak manifest to librest-1.0 2023-02-27 18:00:06 +00:00
data/icons icon: Remove circle outside of drawing area 2022-01-01 18:26:49 +00:00
docs Rename HACKING.md to the more standard CODING_STYLE.md 2022-11-15 13:15:07 +00:00
gettext/its build: Fix translation context missing from keyboard entries 2018-01-24 20:43:34 +01:00
man Updating "info" to "info-overview" in man page 2020-03-15 08:07:51 +00:00
panels network: Increase maximum MTU value from 10000 to 65536 2023-03-24 01:47:09 +00:00
po Update Lithuanian translation 2023-03-22 20:43:25 +00:00
search-provider Rename app-id to org.gnome.Settings 2022-01-21 13:08:50 +00:00
shell search: Add tooltip 2023-03-15 13:28:59 +00:00
subprojects meson: Add GTK as a subproject 2023-02-14 18:15:33 +00:00
tests wifi: Add QR code to share Wi-Fi networks 2023-02-14 19:11:07 -03:00
.gitignore gitignore: Ignore Meson subprojects 2023-01-16 12:56:02 +00:00
.gitlab-ci.yml ci: Build own GTK version 2023-03-14 19:42:59 +01:00
.gitmodules Switch to GTK4 & libadwaita 2021-12-14 22:34:21 -03:00
COPYING build: Update COPYING with new mailing address 2012-08-22 15:33:18 +01:00
gnome-control-center.doap doap: Remove gicmo from DOAP file 2023-03-06 13:00:20 -03:00
meson.build Post-release version bump 2023-03-06 12:29:46 -03:00
meson_options.txt log: Improve logging 2022-12-01 11:44:17 +00:00
NEWS 44.rc 2023-03-06 12:22:35 -03:00
README.md Rename HACKING.md to the more standard CODING_STYLE.md 2022-11-15 13:15:07 +00:00

README.md

Build Status Coverage report License

GNOME Settings

GNOME Settings is GNOME's main interface for configuration of various aspects of your desktop.

Contributing

See docs/CONTRIBUTING.md for details on the contribution process, and docs/CODING_STYLE.md for the coding style guidelines.

Reporting Bugs

Before reporting any bugs or opening feature requests, read the communication guidelines.

Bugs should be reported to the GNOME bug tracking system under the product gnome-control-center. It is available at GitLab Issues.

In the report please include the following information:

  • Operating system and version
  • For Linux, version of the C library
  • Exact error message
  • Steps to reproduce the bug
  • If the bug is a visual defect, attach a screenshot
  • If the bug is a crash, attach a backtrace if possible [see below]

How to get a backtrace

If the crash is reproducible, follow the steps to obtain a backtrace:

Install debug symbols for gnome-control-center.

Run the program in gdb [the GNU debugger] or any other debugger.

gdb gnome-control-center

Start the program.

(gdb) run

Reproduce the crash and when the program exits to (gdb) prompt, get the backtrace.

(gdb) bt full

Once you have the backtrace, copy and paste it into the 'Comments' field or attach it as a file to the bug report.

Testing Unstable Settings

It is quite easy to test and give feedback about the development version of GNOME Settings. Just access https://gitlab.gnome.org/GNOME/gnome-control-center/environments, get the latest version, download it, double-click the file, install and run.

Note that GNOME Settings Flatpak will only work if you are running the latest GNOME version in your host system.