Difference between revisions of "GNOME/Troubleshooting"
(→Gnome Crashes while installing gnome-extra: Added link to Codecs page solution for Gnome video playback failure)
m (→Tear-free video with Intel HD Graphics: remove trailing bracket)
|(One intermediate revision by the same user not shown)|
|Line 150:||Line 150:|
Enabling the [[Intel graphics#Tear-free video|Xorg Intel TearFree option]] is a known workaround for tearing problems on Intel adapters. However, the way this option acts
Enabling the [[Intel graphics#Tear-free video|Xorg Intel TearFree option]] is a known workaround for tearing problems on Intel adapters. However, the way this option acts increases memory consumption and lowers performance, see [https://bugs.freedesktop.org/show_bug.cgi?id=37686#c123 the original bug report's final comment].
Revision as of 21:50, 17 December 2016
- 1 Shell freezes
- 2 Incorrect application defaults
- 3 Tracker & Documents do not list any local files
- 4 Unable to add accounts in Empathy and GNOME Online Accounts
- 5 Empathy does not use GNOME Online Accounts
- 6 Cannot change settings in dconf-editor
- 7 When an extension breaks the shell
- 8 Extensions do not work after GNOME 3 update
- 9 Extensions disabled at every system startup
- 10 Keyboard shortcut do not work with only conky running
- 11 Unable to apply stored configuration for monitors
- 12 Consistent cursor theme
- 13 Windows cannot be modified with Alt-Key + mouse-button
- 14 Slow loading of system icons/slow GDM login
- 15 Artifacts when maximizing windows
- 16 Tear-free video with Intel HD Graphics
- 17 Window opens behind other windows when using multiple monitors
- 18 Lock button fails to re-enable touchpad
- 19 GNOME Shell keyboard sources menu not visible
- 20 Mouse cursor missing
- 21 No restart button in session menu when screen is locked
- 22 PulseAudio system-wide causes delay in GNOME and GDM
- 23 GNOME crashes when trying to reorder applications in the GNOME Shell Dash
- 24 Setting global Wayland environment with an environment variable
- 25 Gnome Crashes while installing gnome-extra
- 26 No H264 Video in Gnome Video Player (Totem)
In the event of a Shell freeze (which might be caused by certain appearance tweaks, malfunctioning extensions or perhaps a lack of available memory) restarting the Shell by pressing
F2 and then entering r may not be possible.
In this case, try switching to another TTY (Ctrl + Alt + F2) and entering the following command:
pkill -HUP gnome-shell. It may take a few seconds before the Shell successfully restarts. Restarting the shell in this fashion should not log the user out but it is a good idea to try and ensure that all work is saved anyway.
If this fails, the Xorg server will need to be restarted either by:
pkill X for console logins or:
systemctl restart gdm for GDM logins. Bear in mind that restarting the Xorg server will log the user out so try to ensure that all work is saved before attempting this.
Incorrect application defaults
When installing applications for the first time you may find that GNOME has the wrong application associated to a certain protocols - for instance, easytag becomes the folder handler instead of GNOME Files.
For GNOME Files see the following page: GNOME Files#Files is no longer the default file manager.
For Document Viewer, run the following command:
$ xdg-mime default evince.desktop application/pdf
For other applications, default handler settings are detailed on the following page: Default applications.
Optionally, you can install AUR. It will place your configuration file at
Tracker & Documents do not list any local files
In order for Tracker (and, therefore, Documents) to detect your local files, they must be stored in an XDG compliant directory (such as 'Documents' or 'Music'). For more information, see XDG user directories.
You can also configure Tracker to recursively search inside specific directories such as your home directory. These settings can be made using
Unable to add accounts in Empathy and GNOME Online Accounts
Empathy, the engine behind integrated messaging, GNOME Online Accounts, and all other system settings based on messaging accounts will not function correctly unless the installed. View descriptions of telepathy components on the freedesktop.org telepathy wiki.group of packages or at least one of the backends ( , or , for example) is
Empathy does not use GNOME Online Accounts
Restart is necessary to enable Empathy to recognize and use GNOME Online Accounts.
Cannot change settings in dconf-editor
When one cannot set settings in
~/.config/dconf/user* and set the settings in dconf-editor after.
When an extension breaks the shell
When enabling shell extensions causes GNOME breakage, you should first remove the user-theme and auto-move-windows extensions from their installation directory.
The installation directory could be one of
/usr/local/share/gnome‑shell/extensions. Removing these two extension-containing folders may fix the breakage. Otherwise, isolate the problem extension with trial‑and‑error.
Removing or adding an extension-containing folder to the aforementioned directories removes or adds the corresponding extension to your system. Details on GNOME Shell extensions are available at the GNOME web site.
If you have trouble with uninstalling an extension via extensions.gnome.org/local, then probably they have been installed as system-wide extensions with the package. Removing the package again obviously affects all user accounts.
Extensions do not work after GNOME 3 update
Before trying the workarounds below, check if an update is available for the extension by visiting extensions.gnome.org/local.
If there is no update for your current GNOME version yet, use the following command to disable version validation for extensions:
$ gsettings set org.gnome.shell disable-extension-version-validation true
Alternatively, you could modify the extension itself, changing the supported shell version to satisfy the version validation. See the method below.
Locate the folder where your extensions are installed. It might be
Edit each occurrence of
metadata.json which appears in each extension sub-folder.
|Instead of (for example):|
"3.x" indicates the extension works with every shell version. If it breaks, you will know to change it back.
Extensions disabled at every system startup
This is a known bug . Until it is fixed, the following workaround can be helpful.
Get the active extensions:
$ gsettings get org.gnome.shell enabled-extensions
Create a desktop entry in
active_extensions with the output from the above command:
[Desktop Entry] Type=Application Exec=gsettings set org.gnome.shell enabled-extensions active_extensions Hidden=false NoDisplay=false X-GNOME-Autostart-enabled=true Name=Restore Extensions Comment=Restore enabled extensions on login
Keyboard shortcut do not work with only conky running
The GNOME shell keyboard shortcuts like
Alt+F1, and the media key shortcuts do not work if conky is the only program running. However, if another application like gedit is running, then the keyboard shortcuts work.
own_window yes own_window_transparent yes own_window_argb_visual yes own_window_type dock own_window_class Conky own_window_hints undecorated,below,sticky,skip_taskbar,skip_pager
Unable to apply stored configuration for monitors
If you encounter this message try to disable the xrandr
$ dconf write /org/gnome/settings-daemon/plugins/xrandr/active false
Consistent cursor theme
In GNOME 3.6 and above, the mouse button modifier (the key that allows you to drag a window from a location other than the titlebar) is the
Super key instead of the
Alt key which was used in the past. The change was made in response to the following bug report.
To change the mouse button modifier back to the
Alt key, execute the following:
$ gsettings set org.gnome.desktop.wm.preferences mouse-button-modifier '<Alt>'
Slow loading of system icons/slow GDM login
Problems with the loading of system icons, such the ones in the title bar of Files, might be solved by executing the following command:
# gdk-pixbuf-query-loaders --update-cache
Running the aforementioned command may also fix repeated occurrences of the "Oh no! Something has gone wrong!" error screen and/or very slow loading and login with GDM as described in the following forum thread.
Artifacts when maximizing windows
Tear-free video with Intel HD Graphics
According to this bug report, DRI3 includes the
buffer_age extension that allows GNOME Shell's Mutter compositor to sync windows to vblank in an efficient way. Enable[broken link: invalid section] it in the Xorg driver. You can change
AccelMethod to your preference in the configuration file created, but the line must be included when the file is created; otherwise,
gnome-session will crash upon login in a non-Wayland session.
- Intel TearFree
Enabling the Xorg Intel TearFree option is a known workaround for tearing problems on Intel adapters. However, the way this option acts increases memory consumption and lowers performance, see the original bug report's final comment.
- Mutter tweaks
GNOME Shell's Mutter compositor has a tweak known to address tearing problems (see the original suggestion for this fix and its mention in the Freedesktop bug report). To enable this tweak, append the following line to
CLUTTER_PAINT=disable-clipped-redraws:disable-culling. Then restart the Xorg server.
Window opens behind other windows when using multiple monitors
This is possibly a bug in GNOME Shell which causes new windows to open behind others. To fix this issue, one can run the following command:
$ gsettings set org.gnome.shell.overrides workspaces-only-on-primary false
Some laptops have a touchpad lock button that disables the touchpad so that users can type without worrying about touching the touchpad. Currently, it appears that although GNOME can lock the touchpad by pressing this button, it cannot unlock it. If the touchpad gets locked you can run the following to unlock it:
$ xinput set-prop "SynPS/2 Synaptics TouchPad" "Device Enabled" 1
A menu showing the keyboard input sources (for example 'en' for an English keyboard layout) should be visible next to the status area containing icons for network, volume and power sources. If the keyboard sources menu is not visible, this is probably because you have configured your Xorg keyboard layout in a way which GNOME does not recognise.
To ensure that the menu is visible, remove any Xorg keyboard configuration you might have created and set the keyboard locale using localectl.
Upon running the command and then logging out, you should find that the keyboard input sources menu is visible in GDM and in the GNOME Shell desktop. See Input sources in GNOME for more information.
Mouse cursor missing
When using a separate window manager with gnome-settings-daemon, the mouse cursor may vanish. Run:
$ gsettings set org.gnome.settings-daemon.plugins.cursor active false
PulseAudio system-wide causes delay in GNOME and GDM
GNOME crashes when trying to reorder applications in the GNOME Shell Dash
The dash is the "toolbar" that appears, by default, on the left when you click Activities. Applications can be reordered in the dash by dragging and dropping. If this fails, and/or causes GNOME to crash, try changing your icon theme.
Setting global Wayland environment with an environment variable
Setting a global Wayland environment, by running
env GDK_BACKEND=wayland gnome-session --session=gnome-wayland, currently does not work - gnome-session will exit immediately. Instead, use
export GDK_BACKEND='wayland,x11' in your bash profile, or use
env GDK_BACKEND='wayland,x11' gnome-session --session=gnome-wayland on the command line. But in general, neither of these environment settings are necessary, and running
gnome-session with the
--session=gnome-wayland switch is sufficient. Without the
GDK_BACKEND environment variable, the GNOME Application must be "Wayland aware" to run as a Wayland application, or default to running on Xwayland otherwise. See also
GDK_BACKEND under GNOME Environment variables.
Gnome Crashes while installing gnome-extra
Attempting to install the gnome-extra group while a gnome environment is running will crash gnome while installing gnome-getting-started-docs. X will continue to run, but gnome will not work until fixed. To fix, simply install gnome-extra from a terminal rather than inside gnome. When complete, gnome should work again.