A fork of Gnome-control-center with some tweaks
Find a file
Ian Douglas Scott f40d4865fa power: Use CcBatteryRow for devices section as well
This had another slightly different version of the same code.
2020-10-14 22:56:16 +00:00
.gitlab/issue_templates docs: Document the Communication Guidelines 2019-04-02 09:06:00 -03:00
build-aux flatpak: Migrate to libhandy 1 and the GNOME repo 2020-07-20 08:04:28 +02:00
data/icons icon: minor update to the app icon 2020-06-02 14:54:36 +02:00
docs docs: Fix markdown formatting 2019-07-22 20:23:19 +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 power: Use CcBatteryRow for devices section as well 2020-10-14 22:56:16 +00:00
po power: Refactor battery row code into a CcBatteryRow type 2020-10-14 22:56:16 +00:00
search-provider search-provider: Replace ifdefs with #pragma once 2019-11-27 21:56:10 +00:00
shell Stop using HANDY_USE_UNSTABLE_API 2020-08-18 02:51:04 +00:00
subprojects subprojects: Update libgvc 2020-09-25 01:45:42 +00:00
tests Disable the canonicalization test 2020-09-05 11:56:24 -03:00
.gitignore project: Update gitignore 2018-05-12 20:56:04 -03:00
.gitlab-ci.yml ci: Correctly update the submodules on build. 2020-10-03 22:58:21 +00:00
.gitmodules meson: Replace libhandy-0.0 by libhandy-1 2020-07-20 08:04:28 +02:00
COPYING build: Update COPYING with new mailing address 2012-08-22 15:33:18 +01:00
gnome-control-center.doap project: Add Benjamin as the maintainer of Display 2018-10-04 11:12:02 -03:00
meson.build meson: Use summary instead of manually built string 2020-10-12 03:25:59 +00:00
meson_options.txt applications: Integrate with malcontent's restrictions 2020-06-17 12:56:43 +01:00
NEWS 3.38.0 2020-09-12 13:23:08 -03:00
README.md docs: Fix pipeline badge in README.md 2020-08-07 00:02:57 +00:00

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/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.