I guess rather sooner than later you will need to look into supporting Wayland sessions No, it's the other way around. Keybase doesn't need to do anything. However users need to make sureDISPLAYandWAYLAND_DISPLAYare correctly set when Keybase starts. This can be achieved by runningsystemctl ...
Message ".. cannot open display: :0" in terminal andIllegal instructionlogged to /mnt/wslg/stderr.log: (EE) Illegal instruction at address 0x7f26b2a00c5c (EE) Fatal server error: (EE) Caught signal 4 (Illegal instruction). Server aborting ...
wayland-0 does not exists inside /run/user/1000 When I try to open any gui aplication I get: failed to connect to Wayland display: No such file or directoryfailed to create display: No such file or directory The only way I've found to make it work is to chmod /run/user/0 and /...
_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_vg_parent_image EGL_IMG_cl_image EGL_KHR_fence_sync EGL_IMG_context_priority EGL_IMG_hibernate_process EGL_IMG_image_plane_attribs EGL_KHR_surfaceless_context EGL_K...
Wayland 1.18 NoMachine 6.12.3 When I try to log into my server from either a Linux client (also on arch) for from android the error is “Cannot detect any display running” selecting create a new one give “Cannot create a new display” ...
*-display description: VGA compatible controller product: GK106GL [Quadro K4000] vendor: NVIDIA Corporation physical id: 0 bus info: pci@0000:02:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nvidia lat...
[ 1.734391] imx-drm display-subsystem: bound imx-drm-dpu-bliteng.2 (ops dpu_bliteng_ops)[ 1.742830] imx-drm display-subsystem: bound imx-dpu-crtc.0 (ops dpu_crtc_ops)[ 1.750349] imx-drm display-subsystem: bound imx-dpu-crtc.1 (ops dpu_crtc_ops)[ 1.757732] nwl_dsi-imx mipi_dsi@...
*-display description: VGA compatible controller product: UHD Graphics 630 (Desktop 9 Series) vendor: Intel Corporation physical id: 2 bus info: pci@0000:00:02.0 version: 00 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: drive...
(it implies GTK is trying and failing to open the X11 display :0, which is not actually the case). The cause turned out to be that we were settingGDK_BACKEND=waylandin Mir startup. This was originally introduced before GTK used Wayland by default and before Mir supported XWayland. ...