This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| GNOME Control Center | |
|---|---|
| Name | GNOME Control Center |
| Title | GNOME Control Center |
| Developer | GNOME Project |
| Released | 2002 |
| Programming language | C, GTK |
| Operating system | Linux, Unix-like |
| License | GNU General Public License |
GNOME Control Center is a settings application for the GNOME desktop environment developed by the GNOME Project, providing a central point to configure system preferences. It serves as the graphical counterpart to configuration backends used by distributions like Fedora, Ubuntu, and Debian and interacts with components such as NetworkManager, BlueZ, and systemd. The application is part of the GNOME Core Applications and integrates with toolkits like GTK and libraries maintained by freedesktop.org.
The application acts as a hub for desktop configuration, exposing settings for hardware, user accounts, display management, and input devices while coordinating with components including NetworkManager, PulseAudio, PipeWire, and systemd-logind. It is packaged by distributions such as Red Hat, Canonical, SUSE, and Arch Linux and aligns with GNOME Shell, Mutter, and gnome-session to provide a cohesive desktop experience. The Control Center communicates with configuration systems such as dconf and GSettings and relies on GLib and libgusb for device enumeration and abstraction.
Initial work on the control collection began during early GNOME releases contemporaneous with GNOME 1 and GNOME 2, with contributions from organizations like Red Hat, Novell, and Collabora. Over time, stewardship transitioned through maintainers associated with the GNOME Foundation and contributors employed by companies including Canonical and Purism. Major milestones corresponded with GNOME 3's development and the introduction of GNOME Shell, and subsequent refactors paralleled upstream projects such as GTK4, Wayland compositor work in Weston, and the evolution of freedesktop.org standards. Development discussions and proposals have appeared on mailing lists like GNOME Discourse and platforms such as GitLab and GitHub mirror repositories.
The Control Center exposes modular panels for audio, network, power, displays, users, region and language, keyboard shortcuts, and privacy, with backend interactions to BlueZ for Bluetooth, ModemManager for mobile broadband, and UPower for power management. It includes panels for input methods that can interface with IBus, for font settings that reference Fontconfig, and for accessibility where Orca and AT-SPI provide screen reading and assistive support. Printing and scanner configuration are delegated to CUPS and SANE; updates or system information panels may surface data from PackageKit or GNOME Software. The modular design encourages third-party modules from projects such as Endless OS and elementary OS to create custom panels.
The visual presentation follows GNOME Human Interface Guidelines and leverages GTK for widgets, Adwaita for theming, and libadwaita for responsive layout patterns suited to both desktop and mobile. Panels are organized into a searchable grid or list, with navigation influenced by Shell design patterns and usability research tied to organizations like the GNOME Foundation and the Linux Foundation. Internationalization efforts coordinate with projects such as Transifex and Weblate, and iconography references the GNOME Icon Theme and upstream freedesktop.org icon naming specifications.
Integration points include Wayland compositors such as Mutter and KWin, X.Org compatibility layers like XWayland, and login/session managers including GDM and LightDM; power and session assertions are managed through systemd and logind. Accessibility integration uses AT-SPI, Orca, and Speech Dispatcher, while language and locale settings interoperate with ICU and glibc locale data. Network and connectivity settings coordinate with NetworkManager and ModemManager, and multimedia routing aligns with PipeWire and PulseAudio for audio streams and JACK for professional audio where present.
Settings storage and retrieval rely on GSettings and dconf as canonical backends, while some device-specific settings are exposed through UDev rules or sysfs attributes mediated by HAL replacement projects. User session preferences propagate via gsettings schemas, and machine-wide defaults are often provisioned by distribution packaging systems or configuration management tools like Ansible, Puppet, and Chef. Integration with system provisioning services leverages cloud-init in cloud images and distribution-specific installers such as Ubiquity or Calamares.
The Control Center surfaces settings that affect authentication, account management, firewall, and privacy; those controls interface with PolicyKit for privilege escalation and system-wide policy enforcement, with pam and NSS modules governing authentication integration. Privacy-related panels expose telemetry, location services, and screen lock behavior, while network controls can adjust firewall rules mediated by firewalld or nftables. Code review and release processes engage the GNOME security team and upstream audits; distributions may apply AppArmor or SELinux profiles to constrain runtime privileges and minimize attack surface.