585fe8c94a
The current DNS priority settings for WWAN were set far too low. Most connections (including WiFi) do not set DNS priority (set to 0) and per https://developer.gnome.org/NetworkManager/stable/nm-settings.html : "A lower value is better (higher priority). Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs and 100 for other connections." By setting both the "low" and "high" settings to 15 and 20 respectively, the WWAN DNS servers were always appearing above WiFi, even though WiFi had routing priority. This caused latency and other problems when the wwan connection was slow because the system would query those DNS servers before WiFi ones. Beyond that, it would even cause WWAN to override VPN DNS settings which isn't what we want. This change puts the "low priority" setting above the default 100 that connections get when they don't otherwise set a priority, and the "high priority" slightly below 100. I did this instead of setting the values to 0 because I noticed that NM doesn't seem to be aware it should prioritize WiFi in that case so WWAN DNS servers were still sometimes taking precedence. |
||
|---|---|---|
| .gitlab/issue_templates | ||
| build-aux | ||
| data/icons | ||
| docs | ||
| gettext/its | ||
| man | ||
| panels | ||
| po | ||
| search-provider | ||
| shell | ||
| subprojects | ||
| tests | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .gitmodules | ||
| COPYING | ||
| gnome-control-center.doap | ||
| meson.build | ||
| meson_options.txt | ||
| NEWS | ||
| README.md | ||
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/HACKING.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.