Zen

Source string Source string

178/10000 · 178

The string is read only.

English Actions
$ GDK_BACKEND=x11 command
Vice versa, you can also force a XWayland app to run using Wayland (in case it has just experimental support):
$ GDK_BACKEND=wayland command
QT 5 apps run with XWayland by default. You can force Wayland backend:
$ QT_QPA_PLATFORM=wayland-egl command
All of this applies to just GTK+ 3 and QT 5 apps.
Hardware description is useful for some hardware-related bugs:
$ lspci -nn > lspci.out
Package versions. You can collect the list and versions of all your packages installed using:
$ rpm -qa | sort > packages.out
The link:Bugs_and_feature_requests#Things_Every_Bug_Should_Have[usual information] that every bug report should have.
Debugging gnome-shell
If gnome-shell gets stuck and unresponsive, it's very helpful to obtain a backtrace from its process and attach it to the report. If this happens, switch to a different VT if possible (`Ctrl+Alt+F3` through `F7`), or log in using ssh. First install debug symbols:
$ sudo dnf debuginfo-install `rpm -q gnome-shell`
Then attach gdb debugger to your gnome-shell process:
$ gdb -p `pgrep -U $(id -un) -x gnome-shell`
...
(gdb) set logging on
(gdb) thread apply all backtrace full
... press Enter until the whole backtrace is displayed ...
(gdb) quit
You should have the backtrace saved in `gdb.txt` file.
Debugging mutter
You can debug mutter (used in gnome-shell) by setting its https://developer.gnome.org/meta/stable/running-mutter.html[environment variables]. These need to be set prior to run gnome-shell, so if you want to log into GNOME from GDM, you need to create a wrapper script called from a desktop file in `/usr/share/wayland-sessions`.
*FIXME: Putting the wrapper script and desktop file here would be
helpful.*
Known issues, frequent complaints, fundamental changes
Here we will list high-profile issues which are known to be broken, not yet implemented, or intentionally behaving differently from regular X11 apps. Also please look at link:Wayland_features[Wayland features] which lists all current missing or in-progress features and their details.
To see all known issues, look at Bugzilla reports as mentioned in link:#Looking_for_similar_reports[Looking for similar reports].
Graphical applications can't be run as root from terminal
It is not possible to start graphical apps under the root account from terminal when using `su` or `sudo`. Apps which use polkit to request administrator permissions for just certain operations and only when needed are not affected (they are not started as root right away). The discussion is ongoing about the best approach to take, see https://bugzilla.redhat.com/show_bug.cgi?id=1274451[bug 1274451] and https://lists.fedoraproject.org/archives/list/devel%40lists.fedoraproject.org/thread/A6VXI4WAGSIIWGOTAVNDBVS4VFYXITHA/#2YU2RBYCXQSCGHGP772W5LRXUMTSINHA["On running gui applications as root" thread in fedora-devel mailing list].
Many well-known X11 utilities don't work
Power users are familiar with a large range of X11-related utilities, like `xkill`, `xrandr`, `xdotool`, `xsel`. These tools won't work under Wayland session, or will only work with XWayland applications but not Wayland applications. Some tools might have a replacement which allows to perform similar tasks.
*FIXME: add some Wayland-ready replacements for popular X11 tools*
Games and other apps can't change monitor resolution
It is no longer possible for an app to change monitor resolution. Usually this was done by games to increase performance. Wayland-based games will use a different approach - scaling its output. But for X11 games (running through XWayland) this solution is not available. This results in a number of different types of behavior, based on how the game is written - the game might be fixed in the desktop resolution, or rendered as a small centered image with black bars around it, or crash on startup, or something different. See https://bugzilla.redhat.com/show_bug.cgi?id=1289714[bug 1289714].
For some games, a possible workaround is to manually set custom monitor resolution before running the game, if you really need it. It will not help always, though.

Loading…

User avatar None

String updated in the repository
$ gdb -p `pgrep -U $(id -un) -x gnome-shell`
...
(gdb) set logging on
(gdb) thread apply all backtrace full
... press Enter until the whole backtrace is displayed ...
(gdb) quit
$ gdb -p `pgrep -U $(id -un) -x gnome-shell`
...
(gdb) set logging on
(gdb) thread apply all backtrace full
... press Enter until the whole backtrace is displayed ...
(gdb) quit
11 months ago
Browse all string changes

Things to check

Ellipsis

The string uses three dots (...) instead of an ellipsis character (…)

Reset

Glossary

English English
No related strings found in the glossary.

String information

Source string description
type: delimited block .
Flags
no-wrap, read-only
Source string location
./pages/troubleshooting-wayland-problems.adoc:397
String age
11 months ago
Last updated
11 months ago
Source string age
11 months ago
Translation file
pot/master/pages/troubleshooting-wayland-problems.pot, string 117