The `-nosplash` option causes the display protocol (x11/wayland) to be incorrectly identified
Author: agitateCreated Sep 14, 2026Updated Sep 17, 2026
Labelsxo:linuxwait for reviewxqa:need-testing
Description
Using -nosplash causes the main window to open in xwayland mode when running on a Wayland display. Running without -nosplash opens the main window correctly in wayland mode.
I reverted to version 26.0.1 (as that was the version I had installed previously) and the wayland detection works as expected with or without the -nosplash option.
DBeaver Version
Community Edition 26.2.0
Operating System
Ubuntu 26.04.1
Database and driver
N/A
Steps to reproduce
- Run
dbeaver -nosplash - Run
xwininfoand note that the crosshair appears when hovering over the dbeaver main window - The fonts will also be blurry if you have fractional font scaling enabled in your wayland window manager
- Exit and run
dbeaver(without the-nosplashoption) - Run
xwininfoand note that the crosshair does not appear when hovering over the dbeaver main window - The fonts will be clear
Additional context
- Running under labwc
- Launching from a terminal that has the appropriate
WAYLAND_DISPLAY=wayland-0andXDG_SESSION_TYPE=waylandenv vars set.
Source: dbeaver/dbeaver