You are not logged in.
Pages: 1
Topic closed
I am using plasma Wayland sessions daily. However, some of the apps I'm using, especially eclipse based IDEs, have poor native wayland support. Problems include wrong text and icon sizes, etc . So I want them to run under xwayland.
I tried export GDK_BACKEND=X11. However, this causes the applications to panic that cannot open display.
I also tried unset WAYLAND_DISPLAY, to make the apps ignore the wayland server and fall back to X11. However, even the environment variable WAYLAND_DISPLAY is unset, the applications still uses native wayland instead of xwayland.
Is there any methods independent of DEs, WMs and GUI toolkits that can force a GUI app to run under xwayland? For example, by making the wayland server undetectable for that app, and making the xwayland xserver detectable.
Offline
I tried export GDK_BACKEND=X11. However, this causes the applications to panic that cannot open display.
printenvCan you run "xterm" on the wayland desktop (which will run on X11 no matter what ![]()
Online
I tried export GDK_BACKEND=X11. However, this causes the applications to panic that cannot open display.
printenvCan you run "xterm" on the wayland desktop (which will run on X11 no matter what
Yes. X11 apps like xterm and electron apps works normally. However, if export GDK_BACKEND=X11, then GTK based apps panic that cannot open display, even if $DISPLAY is correctly set.
Offline
GTK based apps panic that cannot open display
Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
Might be an xauth issue.
Online
The value of the GDK_BACKEND environment variable is case-sensitive. You want “x11” (lowercase), not “X11” (capitalized). (Fwiw, the wiki gets this right.)
Sorry for necroposting, but this thread does rank quite highly in some search results, so I thought it might be helpful to drop a solution here.
In case it helps anyone else find this post, this is the sort of output that Eclipse produces when run with an invalid GDK_BACKEND:
$ env GDK_BACKEND=X11 eclipse
Eclipse: Cannot open display:
Eclipse: Cannot open display:
Jul 07, 2026 11:21:49 A.M. org.apache.aries.spifly.BaseActivator log
INFO: Registered provider ch.qos.logback.classic.spi.LogbackServiceProvider of service org.slf4j.spi.SLF4JServiceProvider in bundle ch.qos.logback.classic
11:21:52.381 [Start Level: Equinox Container: 26580bd4-4107-4189-90b1-4fe2e211815d] DEBUG org.eclipse.jgit.internal.util.ShutdownHook -- register org.eclipse.jgit.util.FS$FileStoreAttributes$$Lambda/0x00007f1ecc21c620@539f41f5 with shutdown hook
11:21:52.381 [Start Level: Equinox Container: 26580bd4-4107-4189-90b1-4fe2e211815d] DEBUG org.eclipse.jgit.internal.util.ShutdownHook -- register org.eclipse.jgit.util.FS$FileStoreAttributes$$Lambda/0x00007f1ecc21c620@539f41f5 with shutdown hook
11:21:53.381 [ForkJoinPool-1-worker-1] DEBUG org.eclipse.jgit.internal.util.ShutdownHook -- Cleanup org.eclipse.jgit.util.FS$FileStoreAttributes$$Lambda/0x00007f1ecc21c620@539f41f5 during JVM shutdown
11:21:53.381 [ForkJoinPool-1-worker-1] DEBUG org.eclipse.jgit.internal.util.ShutdownHook -- Cleanup org.eclipse.jgit.util.FS$FileStoreAttributes$$Lambda/0x00007f1ecc21c620@539f41f5 during JVM shutdown
Eclipse: Cannot open display:
Eclipse:
An error has occurred. See the log file
/home/mrd/.eclipse/org.eclipse.platform_4.40.0_155965261_linux_gtk_x86_64/configuration/1783419707541.log.Offline
Mod note: Closing this old topic.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Pages: 1
Topic closed