Difference between revisions of "GNOME"
m (→Configuration: less emphasis on old situation) |
Tag: Rollback |
||
(20 intermediate revisions by 12 users not shown) | |||
Line 14: | Line 14: | ||
[[zh-hant:GNOME]] | [[zh-hant:GNOME]] | ||
{{Related articles start}} | {{Related articles start}} | ||
− | {{Related|GTK | + | {{Related|GTK}} |
{{Related|GDM}} | {{Related|GDM}} | ||
{{Related|GNOME/Tips and tricks}} | {{Related|GNOME/Tips and tricks}} | ||
Line 25: | Line 25: | ||
{{Related|GNOME/Keyring}} | {{Related|GNOME/Keyring}} | ||
{{Related|GNOME/Document viewer}} | {{Related|GNOME/Document viewer}} | ||
+ | {{Related|GNOME/Software}} | ||
{{Related|Official repositories#gnome-unstable}} | {{Related|Official repositories#gnome-unstable}} | ||
{{Related articles end}} | {{Related articles end}} | ||
Line 63: | Line 64: | ||
==== Xorg sessions ==== | ==== Xorg sessions ==== | ||
− | * For the GNOME on Xorg session, add to the {{ic|~/.xinitrc}} file (see [https://gitlab.gnome.org/GNOME/gtk/issues/1390#note_344758 here] for details): {{bc|<nowiki>export GDK_BACKEND=x11 | + | * For the GNOME on Xorg session, add to the {{ic|~/.xinitrc}} file (see [https://gitlab.gnome.org/GNOME/gtk/issues/1390#note_344758 here] for details): {{bc|<nowiki>export XDG_SESSION_TYPE=x11 |
+ | export GDK_BACKEND=x11 | ||
exec gnome-session</nowiki>}} | exec gnome-session</nowiki>}} | ||
* For the GNOME Classic session, add to the {{ic|~/.xinitrc}} file: {{bc|<nowiki>export XDG_CURRENT_DESKTOP=GNOME-Classic:GNOME | * For the GNOME Classic session, add to the {{ic|~/.xinitrc}} file: {{bc|<nowiki>export XDG_CURRENT_DESKTOP=GNOME-Classic:GNOME | ||
Line 69: | Line 71: | ||
exec gnome-session --session=gnome-classic</nowiki>}} | exec gnome-session --session=gnome-classic</nowiki>}} | ||
− | After editing the {{ic|~/.xinitrc}} file, GNOME can be launched with the {{ic|startx}} command (see [[xinitrc]] for additional details, such as preserving the logind session). After setting up the {{ic|~/.xinitrc}} file it can also be arranged to [[Start X at login]]. | + | After editing the {{ic|~/.xinitrc}} file, GNOME can be launched with the {{ic|startx}} command (see [[xinitrc]] for additional details, such as preserving the logind session). After setting up the {{ic|~/.xinitrc}} file it can also be arranged to [[Start X at login]], e.g. on tty2 by adding to {{ic|.bash_profile}}: |
+ | |||
+ | {{bc|<nowiki> | ||
+ | if [[ -z $DISPLAY && $(tty) == /dev/tty2; ]]; then | ||
+ | GDK_BACKEND=x11 exec startx | ||
+ | fi | ||
+ | </nowiki>}} | ||
==== Wayland sessions ==== | ==== Wayland sessions ==== | ||
{{Note| | {{Note| | ||
− | * An X server—provided by the {{Pkg|xorg-server-xwayland}} package—is still necessary to run applications that have not yet been ported to [[Wayland]]. | + | * An X server—provided by the {{Pkg|xorg-server-xwayland}} package—is still necessary to run applications that have not yet been ported to [[Wayland]]. Applications using certain graphics libraries, such as Qt, can be forced to use Wayland by setting environment variables. See [[Wayland#GUI libraries]] for more information. |
− | * | + | * When using the proprietary [[NVIDIA]] driver, non-Wayland-native applications suffer from poor performance because of the lack of hardware accelerated XWayland. This is [https://blogs.gnome.org/uraeus/2019/09/23/fedora-workstation-31-whats-new/ expected] to be resolved in Spring 2020 but there is no committed timeline from [[NVIDIA]]. |
}} | }} | ||
− | Manually starting a Wayland session is possible with {{ic|<nowiki> | + | Manually starting a Wayland session is possible with {{ic|<nowiki>XDG_SESSION_TYPE=wayland dbus-run-session gnome-session</nowiki>}}. |
To start on login to tty1, add the following to your {{ic|.bash_profile}}: | To start on login to tty1, add the following to your {{ic|.bash_profile}}: | ||
− | + | {{bc|<nowiki> | |
− | + | if [[ -z $DISPLAY && $(tty) == /dev/tty1 && $XDG_SESSION_TYPE == tty ]]; then | |
− | fi | + | XDG_SESSION_TYPE=wayland exec dbus-run-session gnome-session |
− | + | fi | |
− | + | </nowiki>}} | |
=== GNOME applications in Wayland === | === GNOME applications in Wayland === | ||
− | When the ''GNOME'' session is used, GNOME applications will be run using Wayland. For debugging cases, the [https://developer.gnome.org/gtk3/stable/gtk-running.html GTK | + | When the ''GNOME'' session is used, GNOME applications will be run using Wayland. For debugging cases, the [https://developer.gnome.org/gtk3/stable/gtk-running.html GTK manual] lists options and environment variables. |
== Navigation == | == Navigation == | ||
Line 229: | Line 237: | ||
=== Advanced settings === | === Advanced settings === | ||
− | As noted above, many configuration options such as changing the [[GTK | + | As noted above, many configuration options such as changing the [[GTK]] theme or the [[window manager]] theme are not exposed in the GNOME System Settings panel (''gnome-control-center''). Those users that want to configure these settings may wish to use the GNOME Tweaks ({{Pkg|gnome-tweaks}}), a convenient graphical tool which exposes many of these settings. |
GNOME settings (which are stored in the DConf database) can also be configured using the [https://developer.gnome.org/dconf/unstable/dconf-editor.html ''dconf-editor''] (a graphical DConf configuration tool) or the [https://developer.gnome.org/gio/stable/GSettings.html ''gsettings''] command line tool. The GNOME Tweaks does not do anything else in the background of the GUI; note though that you will not find all settings described in the following sections in it. | GNOME settings (which are stored in the DConf database) can also be configured using the [https://developer.gnome.org/dconf/unstable/dconf-editor.html ''dconf-editor''] (a graphical DConf configuration tool) or the [https://developer.gnome.org/gio/stable/GSettings.html ''gsettings''] command line tool. The GNOME Tweaks does not do anything else in the background of the GUI; note though that you will not find all settings described in the following sections in it. | ||
Line 237: | Line 245: | ||
===== Themes ===== | ===== Themes ===== | ||
− | GNOME uses Adwaita by default. To apply Adwaita dark only to GTK | + | GNOME uses Adwaita by default. To apply Adwaita dark only to GTK 2 applications use the following symlink: |
$ ln -s /usr/share/themes/Adwaita-dark ~/.themes/Adwaita | $ ln -s /usr/share/themes/Adwaita-dark ~/.themes/Adwaita | ||
Line 243: | Line 251: | ||
To select new themes (move them to the appropriate directory and) use GNOME Tweaks or the GSettings commands below: | To select new themes (move them to the appropriate directory and) use GNOME Tweaks or the GSettings commands below: | ||
− | For the GTK | + | For the GTK theme: |
$ gsettings set org.gnome.desktop.interface gtk-theme ''theme-name'' | $ gsettings set org.gnome.desktop.interface gtk-theme ''theme-name'' | ||
Line 251: | Line 259: | ||
$ gsettings set org.gnome.desktop.interface icon-theme ''theme-name'' | $ gsettings set org.gnome.desktop.interface icon-theme ''theme-name'' | ||
− | {{Note|The window manager theme follows the GTK | + | {{Note|The window manager theme follows the GTK theme. Using {{ic|org.gnome.desktop.wm.preferences theme}} is deprecated and ignored.}} |
− | See [[GTK | + | See [[GTK#Themes]] and [[Icons#Manually]]. |
===== Titlebar height ===== | ===== Titlebar height ===== | ||
Line 343: | Line 351: | ||
===== Icons on the Desktop ===== | ===== Icons on the Desktop ===== | ||
− | Up until GNOME 3.28, icons on the desktop were provided by [[Files]] which would draw a transparent window over the desktop containing the icons. As of GNOME 3.28 this functionality has been removed and desktop icons are no longer available in GNOME. Possible workarounds include using [[Nemo]] (a fork of Files which still has desktop icons functionality) or installing {{AUR|gnome-shell-extension-desktop-icons}}, which replicates the desktop icon functionality available in GNOME 3.26 and prior, but with some minor differences. For more information, please see the following [https://bbs.archlinux.org/viewtopic.php?id=235633 Arch forum thread]. | + | Up until GNOME 3.28, icons on the desktop were provided by [[GNOME/Files|Files]] which would draw a transparent window over the desktop containing the icons. As of GNOME 3.28 this functionality has been removed and desktop icons are no longer available in GNOME. Possible workarounds include using [[Nemo]] (a fork of Files which still has desktop icons functionality) or installing {{AUR|gnome-shell-extension-desktop-icons}}, which replicates the desktop icon functionality available in GNOME 3.26 and prior, but with some minor differences. For more information, please see the following [https://bbs.archlinux.org/viewtopic.php?id=235633 Arch forum thread]. |
===== Lock screen and background ===== | ===== Lock screen and background ===== | ||
Line 359: | Line 367: | ||
===== Disable top left hot corner ===== | ===== Disable top left hot corner ===== | ||
− | + | Starting from GNOME 3.34 you can disable it with this: | |
+ | |||
+ | $ gsettings set org.gnome.desktop.interface enable-hot-corners false | ||
+ | |||
+ | or via {{pkg|gnome-tweaks}}, in ''Top Bar > Activities Overview Hot Corner'' | ||
==== Extensions ==== | ==== Extensions ==== | ||
Line 365: | Line 377: | ||
The catalogue of extensions is available at [https://extensions.gnome.org extensions.gnome.org]. They can be installed and activated in a browser by setting the switch in the top left of the screen to '''ON''' and clicking '''Install''' on the popup window (if the extension in question is not installed). Installed extensions may be seen at [https://extensions.gnome.org/local/ extensions.gnome.org/local], where available updates can be checked. Installed extensions can also be enabled or disabled with {{Pkg|gnome-tweaks}}. | The catalogue of extensions is available at [https://extensions.gnome.org extensions.gnome.org]. They can be installed and activated in a browser by setting the switch in the top left of the screen to '''ON''' and clicking '''Install''' on the popup window (if the extension in question is not installed). Installed extensions may be seen at [https://extensions.gnome.org/local/ extensions.gnome.org/local], where available updates can be checked. Installed extensions can also be enabled or disabled with {{Pkg|gnome-tweaks}}. | ||
− | {{Note|Extensions from [https://extensions.gnome.org extensions.gnome.org] can be installed right away with | + | {{Note|Extensions from [https://extensions.gnome.org extensions.gnome.org] can be installed right away with {{Pkg|gnome-software}}. For other browsers, it is required to install {{pkg|chrome-gnome-shell}} and the appropriate browser extension.}} |
GNOME Shell can be customized with extensions per user or system-wide. Installing extensions with [[pacman]] makes them available for all users of the system and automates the update process. The {{Pkg|gnome-shell-extensions}} package provides a set of extensions maintained as part of the GNOME project (many of the included extensions are used by the GNOME Classic session). Users who want a taskbar but do not wish to use the GNOME Classic session may want to enable the ''Window list'' extension (provided by the {{Pkg|gnome-shell-extensions}} package). | GNOME Shell can be customized with extensions per user or system-wide. Installing extensions with [[pacman]] makes them available for all users of the system and automates the update process. The {{Pkg|gnome-shell-extensions}} package provides a set of extensions maintained as part of the GNOME project (many of the included extensions are used by the GNOME Classic session). Users who want a taskbar but do not wish to use the GNOME Classic session may want to enable the ''Window list'' extension (provided by the {{Pkg|gnome-shell-extensions}} package). |
Latest revision as of 09:01, 8 December 2019
GNOME (/(ɡ)noʊm/) is a desktop environment that aims to be simple and easy to use. It is designed by The GNOME Project and is composed entirely of free and open-source software. GNOME is a part of the GNU Project. The default display is Wayland instead of Xorg.
Contents
- 1 Installation
- 2 GNOME Sessions
- 3 Starting
- 4 Navigation
- 5 Legacy names
- 6 Configuration
- 7 See also
Installation
Two groups are available:
- gnome contains the base GNOME desktop and a subset of well-integrated applications;
- gnome-extra contains further GNOME applications, including an archive manager, disk manager, text editor, and a set of games. Note that this group builds on the gnome group.
The base desktop consists of GNOME Shell, a plugin for the Mutter window manager. It can be installed separately with gnome-shell.
GNOME Sessions
GNOME has three available sessions, all using GNOME Shell.
- GNOME is the default which uses Wayland. Traditional X applications are run through Xwayland.
- GNOME Classic is a traditional desktop layout with a similar interface to GNOME 2, using pre-activated extensions and parameters. [1] Hence it is more a customized GNOME Shell than a truly distinct mode.
- GNOME on Xorg runs GNOME Shell using Xorg.
Starting
GNOME can be started either graphically with a display manager or manually from the console (some features may be missing).
Graphically
Select the session: GNOME, GNOME Classic, or GNOME on Xorg from the display manager's session menu.
Manually
Xorg sessions
- For the GNOME on Xorg session, add to the
~/.xinitrc
file (see here for details):export XDG_SESSION_TYPE=x11 export GDK_BACKEND=x11 exec gnome-session
- For the GNOME Classic session, add to the
~/.xinitrc
file:export XDG_CURRENT_DESKTOP=GNOME-Classic:GNOME export GNOME_SHELL_SESSION_MODE=classic exec gnome-session --session=gnome-classic
After editing the ~/.xinitrc
file, GNOME can be launched with the startx
command (see xinitrc for additional details, such as preserving the logind session). After setting up the ~/.xinitrc
file it can also be arranged to Start X at login, e.g. on tty2 by adding to .bash_profile
:
if [[ -z $DISPLAY && $(tty) == /dev/tty2; ]]; then GDK_BACKEND=x11 exec startx fi
Wayland sessions
- An X server—provided by the xorg-server-xwayland package—is still necessary to run applications that have not yet been ported to Wayland. Applications using certain graphics libraries, such as Qt, can be forced to use Wayland by setting environment variables. See Wayland#GUI libraries for more information.
- When using the proprietary NVIDIA driver, non-Wayland-native applications suffer from poor performance because of the lack of hardware accelerated XWayland. This is expected to be resolved in Spring 2020 but there is no committed timeline from NVIDIA.
Manually starting a Wayland session is possible with XDG_SESSION_TYPE=wayland dbus-run-session gnome-session
.
To start on login to tty1, add the following to your .bash_profile
:
if [[ -z $DISPLAY && $(tty) == /dev/tty1 && $XDG_SESSION_TYPE == tty ]]; then XDG_SESSION_TYPE=wayland exec dbus-run-session gnome-session fi
GNOME applications in Wayland
When the GNOME session is used, GNOME applications will be run using Wayland. For debugging cases, the GTK manual lists options and environment variables.
To learn how to use the GNOME shell effectively read the GNOME Shell Cheat Sheet; it highlights GNOME shell features and keyboard shortcuts. Features include task switching, keyboard use, window control, the panel, overview mode, and more. A few of the shortcuts are:
Super
+m
: show message traySuper
+a
: show applications menuAlt
+Tab
: cycle active applicationsAlt
+`
(the key aboveTab
on US keyboard layouts): cycle windows of the application in the foregroundAlt
+F2
, then enterr
orrestart
: restart the shell in case of graphical shell problems (only in X/legacy mode, not in Wayland mode).
Alt+Tab
switch applications only in current workspace, you can set current-workspace-only
to true
:
$ gsettings set org.gnome.shell.app-switcher current-workspace-only true
Legacy names
Current | Legacy |
---|---|
Files | Nautilus |
Web | Epiphany |
Videos | Totem |
Main Menu | Alacarte |
Document Viewer | Evince |
Disk Usage Analyzer | Baobab |
Image Viewer | EoG (Eye of GNOME) |
Passwords and Keys | Seahorse |
GNOME Translation Editor | Gtranslator |
Configuration
The GNOME System Settings panel (gnome-control-center) and GNOME applications use the dconf configuration system to store their settings.
You can directly access the dconf database using the gsettings
or dconf
command line tools. This also allows you to configure settings not exposed by the user interfaces.
Up until GNOME 3.24 settings were applied by the GNOME settings daemon (located at /usr/lib/gnome-settings-daemon/gnome-settings-daemon
), which could be run outside of a GNOME session.
GNOME 3.24 however replaced the GNOME settings daemon with several separate settings plugins /usr/lib/gnome-settings-daemon/gsd-*
which were later moved to /usr/lib/gsd-*
. These plugins are now controlled via desktop files under /etc/xdg/autostart
(org.gnome.SettingsDaemon.*.desktop). To run these plugins outside of a GNOME session you will now need to copy/edit the appropriate desktop entries to ~/.config/autostart
.
The configuration is usually performed user-specific, this section does not cover how to create configuration templates for multiple users.
System settings
Color
The daemon colord
reads the display's EDID and extracts the appropriate color profile. Most color profiles are accurate and no setup is required; however for those that are not accurate, or for older displays, color profiles can be put in ~/.local/share/icc/
and directed to.
Night Light
GNOME comes with a built-in blue light filter similar to Redshift. You can enable and customise the time you want to enable Night Light from the display settings menu. Furthermore, you can tweak the kelvin temperature with the following dconf setting, where 5000 is an example value:
$ gsettings set org.gnome.settings-daemon.plugins.color night-light-temperature 5000
Date & time
If the system has a configured Network Time Protocol daemon, it will be effective for GNOME as well. The synchronization can be set to manual control from the menu, if required.
To show the date in the top bar, execute:
$ gsettings set org.gnome.desktop.interface clock-show-date true
Additionally, to show week numbers in the calendar opened on the top bar, execute:
$ gsettings set org.gnome.desktop.calendar show-weekdate true
Default applications
Upon installing GNOME for the first time, you may find that the wrong applications are handling certain protocols. For example, totem opens videos instead of a previously used VLC. Some of the associations can be set from system settings via: Details > Default applications.
For other protocols and methods see Default applications for configuration.
Mouse and touchpad
Most touchpad settings can be set from system settings via: Devices > Mouse & Touchpad.
Depending on your device, other configuration settings may be available, but not exposed via the default GUI. For example, a different touchpad click-method
$ gsettings range org.gnome.desktop.peripherals.touchpad click-method
enum 'default' 'none' 'areas' 'fingers'
to be set manually:
$ gsettings set org.gnome.desktop.peripherals.touchpad click-method 'fingers'
or via gnome-tweaks.
Network
NetworkManager is the native tool of the GNOME project to control network settings from the shell. Install the networkmanager package and enable the NetworkManager.service
systemd unit.
While any other network manager can be used as well, NetworkManager provides the full integration via the shell network settings and a status indicator applet network-manager-applet (not required for GNOME).
Online accounts
Backends for the GNOME messaging application empathy as well as the GNOME Online Accounts section of the System Settings panel are provided in a separate group: telepathy. See Unable to add accounts in Empathy and GNOME Online Accounts. Some online accounts, such as ownCloud, require gvfs-goa to be installed for full functionality in GNOME applications such as GNOME Files and GNOME Documents [2].
Search
The GNOME shell has a search that can be quickly accessed by pressing the Super
key and starting to type. The tracker package is installed by default as a part of gnome group and provides an indexing application and metadata database. It can be configured with the Search and Indexing menu item; monitor status with tracker-control. It is started automatically by gnome-session when the user logs in. Indexing can be started manually with tracker-control -s
. Search settings can also be configured in the System Settings panel.
The Tracker database can be queried using the tracker-sparql command. View its manual page tracker-sparql(1) for more information.
Advanced settings
As noted above, many configuration options such as changing the GTK theme or the window manager theme are not exposed in the GNOME System Settings panel (gnome-control-center). Those users that want to configure these settings may wish to use the GNOME Tweaks (gnome-tweaks), a convenient graphical tool which exposes many of these settings.
GNOME settings (which are stored in the DConf database) can also be configured using the dconf-editor (a graphical DConf configuration tool) or the gsettings command line tool. The GNOME Tweaks does not do anything else in the background of the GUI; note though that you will not find all settings described in the following sections in it.
Appearance
Themes
GNOME uses Adwaita by default. To apply Adwaita dark only to GTK 2 applications use the following symlink:
$ ln -s /usr/share/themes/Adwaita-dark ~/.themes/Adwaita
To select new themes (move them to the appropriate directory and) use GNOME Tweaks or the GSettings commands below:
For the GTK theme:
$ gsettings set org.gnome.desktop.interface gtk-theme theme-name
For the icon theme:
$ gsettings set org.gnome.desktop.interface icon-theme theme-name
org.gnome.desktop.wm.preferences theme
is deprecated and ignored.See GTK#Themes and Icons#Manually.
Titlebar height
~/.config/gtk-3.0/gtk.css
headerbar.default-decoration { padding-top: 0px; padding-bottom: 0px; min-height: 0px; font-size: 0.6em; } headerbar.default-decoration button.titlebutton { padding: 0px; min-height: 0px; }
See [3] for more information.
Titlebar button order
To set the order for the GNOME window manager (Mutter, Metacity):
$ gsettings set org.gnome.desktop.wm.preferences button-layout ':minimize,maximize,close'
Hide titlebar when maximized
- Install gnome-shell-extension-no-title-bar-gitAUR or gnome-shell-extension-no-title-barAUR. Maximized windows get the title bar merged into the activity bar.
- Install mutter-hide-legacy-decorationsAUR. It changes a default setting in the window manager, so as to automatically hide the titlebar on legacy (non-headerbar) apps when they are maximized or tiled to the side.
- Install gnome-shell-extension-pixel-saver-gitAUR or gnome-shell-extension-pixel-saverAUR. Maximized windows get the title bar merged into the activity bar, saving precious pixels.
GNOME Shell themes
The theme of GNOME Shell itself is configurable. To use a Shell theme, firstly ensure that you have the gnome-shell-extensions package installed. Then enable the User Themes extension, either through GNOME Tweaks or through the GNOME Shell Extensions webpage. Shell themes can then be loaded and selected using the GNOME Tweaks.
There are a number of GNOME Shell themes available in the AUR. Shell themes can also be downloaded from gnome-look.org.
The default GNOME schema doesn't display any icon on menus. To display icons on menus, issue the following command.
$ gsettings set org.gnome.settings-daemon.plugins.xsettings overrides "{'Gtk/ButtonImages': <1>, 'Gtk/MenuImages': <1>}"
Apps grid folders
~/.local/share/applications-categories
named after each category and containing a list of the desktop files belonging to apps you would like to have inside. Optionally, you can have it cycle through each app without a folder and input the desired category until you Ctrl-c
or run out of apps.In the dconf-editor navigate to org.gnome.desktop.app-folders
and set the value of folder-children
to an array of comma separated folder names:
['Utilities', 'Sundry']
Add applications using gsettings
:
$ gsettings set org.gnome.desktop.app-folders.folder:/org/gnome/desktop/app-folders/folders/Sundry/ apps "['alacarte.desktop', 'dconf-editor.desktop']"
This adds the applications alacarte.desktop
and dconf-editor.desktop
to the Sundry folder. This will also create the folder org.gnome.desktop.app-folders.folders.Sundry
.
To name the folder (if it has no name that appears at the top of the applications):
$ gsettings set org.gnome.desktop.app-folders.folder:/org/gnome/desktop/app-folders/folders/Sundry/ name "Sundry"
Applications can also be sorted by their category (specified in their .desktop file):
$ gsettings set org.gnome.desktop.app-folders.folder:/org/gnome/desktop/app-folders/folders/Sundry/ categories "['Office']"
If certain applications matching a category are not wanted in a certain folder, exclusions can be set:
$ gsettings set org.gnome.desktop.app-folders.folder:/org/gnome/desktop/app-folders/folders/Sundry/ excluded-apps "['libreoffice-draw.desktop']"
For more information, see [4] and [5].
Autostart
GNOME implements XDG Autostart.
The gnome-tweaks allows managing autostart-entries.
gnome-tweaks
. See the following forum thread.Desktop
Icons on the Desktop
Up until GNOME 3.28, icons on the desktop were provided by Files which would draw a transparent window over the desktop containing the icons. As of GNOME 3.28 this functionality has been removed and desktop icons are no longer available in GNOME. Possible workarounds include using Nemo (a fork of Files which still has desktop icons functionality) or installing gnome-shell-extension-desktop-iconsAUR, which replicates the desktop icon functionality available in GNOME 3.26 and prior, but with some minor differences. For more information, please see the following Arch forum thread.
Lock screen and background
When setting the Desktop or Lock screen background, it is important to note that the Pictures tab will only display pictures located in /home/username/Pictures
folder. If you wish to use a picture not located in this folder, use the commands indicated below.
For the desktop background:
$ gsettings set org.gnome.desktop.background picture-uri 'file:///path/to/my/picture.jpg'
For the lock screen background:
$ gsettings set org.gnome.desktop.screensaver picture-uri 'file:///path/to/my/picture.jpg'
Disable top left hot corner
Starting from GNOME 3.34 you can disable it with this:
$ gsettings set org.gnome.desktop.interface enable-hot-corners false
or via gnome-tweaks, in Top Bar > Activities Overview Hot Corner
Extensions
The catalogue of extensions is available at extensions.gnome.org. They can be installed and activated in a browser by setting the switch in the top left of the screen to ON and clicking Install on the popup window (if the extension in question is not installed). Installed extensions may be seen at extensions.gnome.org/local, where available updates can be checked. Installed extensions can also be enabled or disabled with gnome-tweaks.
GNOME Shell can be customized with extensions per user or system-wide. Installing extensions with pacman makes them available for all users of the system and automates the update process. The gnome-shell-extensions package provides a set of extensions maintained as part of the GNOME project (many of the included extensions are used by the GNOME Classic session). Users who want a taskbar but do not wish to use the GNOME Classic session may want to enable the Window list extension (provided by the gnome-shell-extensions package).
To list currently enabled extensions:
$ gsettings get org.gnome.shell enabled-extensions
For more information about GNOME shell extensions, see [6].
Fonts
Fonts can be set for Window titles, Interface (applications), Documents and Monospace. See the Fonts tab in the Tweaks for the relevant options.
For hinting, RGBA will likely be desired as this fits most monitors types, and if fonts appear too blocked reduce hinting to Slight or None.
Input methods
GNOME has integrated support for input methods through IBus, only ibus and the wanted input method engine (e.g. ibus-libpinyin for Intelligent Pinyin) needed to be installed, after installation the input method engine can be added as a keyboard layout in GNOME's Regional & Language Settings.
Power
When you are using a laptop you might want to alter the following settings:
$ gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 3600 $ gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type hibernate $ gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 1800 $ gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type hibernate $ gsettings set org.gnome.settings-daemon.plugins.power power-button-action suspend $ gsettings set org.gnome.desktop.lockdown disable-lock-screen true
To keep the monitor active when the lid is closed:
$ gsettings set org.gnome.settings-daemon.plugins.xrandr default-monitors-setup do-nothing
GNOME 3.24 deprecated the following settings:
org.gnome.settings-daemon.plugins.power button-hibernate org.gnome.settings-daemon.plugins.power button-power org.gnome.settings-daemon.plugins.power button-sleep org.gnome.settings-daemon.plugins.power button-suspend org.gnome.settings-daemon.plugins.power critical-battery-action
Don't suspend, when laptop lid is closed
The settings panel of GNOME doesn't provide an option for the user, to change the action, when laptop lid is closed. However gnome-tweaks can override the setting applied by systemd, on the tab General turn off the switch Suspend when laptop lid is closed. The system will therefore not Suspend to RAM (S3) on lid close.
To change the lid switch action system-wide, ensure that the setting described above is not turned off and edit the systemd settings in /etc/systemd/logind.conf
. To turn off suspend on lid close, set HandleLidSwitch=ignore
, as described in Power management#ACPI events.
Change critical battery level action
The settings panel does not provide an option for changing the critical battery level action. These settings have been removed from dconf as well. They are now managed by upower. Edit the upower settings in /etc/UPower/UPower.conf
. Find these settings and adjust to your needs.
/etc/UPower/UPower.conf
PercentageLow=10 PercentageCritical=3 PercentageAction=2 CriticalPowerAction=HybridSleep
Use a different window manager
GNOME Shell does not support using a different window manager, however GNOME Flashback provides sessions for Metacity and Compiz. Furthermore, it is possible to define your own custom GNOME sessions which use alternative components.
See also
- Official Website
- Wikipedia article
- GNOME-Shell Extensions
- GNOME Shell Cheat Sheet
- Customization (themes, icons...):
- GNOME applications:
- GNOME Source/Mirrors: