You are not logged in.

Pages: 1

#1 2024-10-24 18:23:05

miguel04685
Member
From: Rio de Janeiro, Brasil
Registered: 2024-09-24
Posts: 54

[SOLVED] Can't log into a Wayland session, regardless of the WM/DE

So, when I try to log into a Wayland session, either the display manager freezes or the monitor gives a "No Signal" message. When I tried to log into KDE Wayland session with 

dbus-run-session startplasma-wayland

on a TTY, it gave me a "no backend specified automatically choosing drm" error and then the monitor gave a "No Signal" message.

PC INFO:
Intel Celeron E3300
Intel 82G33/G31 Express (Integrated Graphics)
Mesa Amber lastest version
2 GB RAM
320 HDD

Last edited by miguel04685 (2024-11-15 21:40:25)

Offline

#2 2024-10-24 19:31:01

seth
Member
Registered: 2012-09-03
Posts: 59,324

Re: [SOLVED] Can't log into a Wayland session, regardless of the WM/DE

Probably skip the "dbus-run-session" but the output issues will rather be unrelated to that (you're just breaking the logind integration)
The output is fine before starting KDE? Are other environments affected?

=> https://wiki.archlinux.org/title/KDE#Un … lution_set ?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#3 2024-10-25 18:36:55

miguel04685
Member
From: Rio de Janeiro, Brasil
Registered: 2024-09-24
Posts: 54

Re: [SOLVED] Can't log into a Wayland session, regardless of the WM/DE

I tried "startplasma-wayland" and had the same issue of the monitor giving "No Signal" error

Last edited by miguel04685 (2024-10-25 18:37:12)

Offline

#4 2024-11-11 21:58:44

miguel04685
Member
From: Rio de Janeiro, Brasil
Registered: 2024-09-24
Posts: 54

Re: [SOLVED] Can't log into a Wayland session, regardless of the WM/DE

Is there any solution for this?

Offline

#5 2024-11-11 22:18:26

seth
Member
Registered: 2012-09-03
Posts: 59,324

Re: [SOLVED] Can't log into a Wayland session, regardless of the WM/DE

Did you see the wiki and remove hte kscreen configs?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#6 2024-11-12 14:06:12

miguel04685
Member
From: Rio de Janeiro, Brasil
Registered: 2024-09-24
Posts: 54

Re: [SOLVED] Can't log into a Wayland session, regardless of the WM/DE

Haven't tried it yet. Also, the problem isn't exclusive to KDE, happening to other DEs/WMs too such as Hyprland, Cinnamon Wayland session, Sway, etc

Offline

#7 2024-11-12 14:08:54

seth
Member
Registered: 2012-09-03
Posts: 59,324

Re: [SOLVED] Can't log into a Wayland session, regardless of the WM/DE

We'll need a system journal for this - see whether you can
1. switch to a different TTY (ctrl+alt+F3)
2. ssh into the system
3. reboot using the entire REISUB dance from https://wiki.archlinux.org/title/Keyboa … el_(SysRq)
after failign to start a wayland session.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#8 2024-11-12 16:56:27

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 23,331

Re: [SOLVED] Can't log into a Wayland session, regardless of the WM/DE

What level of GL do you even have on this thing? Afaik the minimum for proper EGL/GL is minimally 2.1 compliance, what output do you get from 

eglinfo -B
glxinfo -B #From a xorg session

You might have to break out software emulation of certain instructions: https://wiki.archlinux.org/title/Intel_ … 915_driver

Last edited by V1del (2024-11-13 16:57:52)

Offline

#9 2024-11-13 16:46:01

miguel04685
Member
From: Rio de Janeiro, Brasil
Registered: 2024-09-24
Posts: 54

Re: [SOLVED] Can't log into a Wayland session, regardless of the WM/DE

I get this:

[miguel@archmiguel ~]$ eglinfo -B
GBM platform:
EGL API version: 1.4
EGL vendor string: Mesa Project (Amber)
EGL version string: 1.4
EGL client APIs: OpenGL OpenGL_ES 
OpenGL compatibility profile vendor: Intel Open Source Technology Center
OpenGL compatibility profile renderer: Mesa DRI Intel(R) G33 
OpenGL compatibility profile version: 2.1 Mesa 21.3.9-arch.6 Amber
OpenGL compatibility profile shading language version: 1.20
OpenGL ES profile vendor: Intel Open Source Technology Center
OpenGL ES profile renderer: Mesa DRI Intel(R) G33 
OpenGL ES profile version: OpenGL ES 2.0 Mesa 21.3.9-arch.6 Amber
OpenGL ES profile shading language version: OpenGL ES GLSL ES 1.0.16

Wayland platform:
eglinfo: eglInitialize failed

X11 platform:
EGL API version: 1.4
EGL vendor string: Mesa Project (Amber)
EGL version string: 1.4
EGL client APIs: OpenGL OpenGL_ES 
OpenGL compatibility profile vendor: Intel Open Source Technology Center
OpenGL compatibility profile renderer: Mesa DRI Intel(R) G33 
OpenGL compatibility profile version: 2.1 Mesa 21.3.9-arch.6 Amber
OpenGL compatibility profile shading language version: 1.20
OpenGL ES profile vendor: Intel Open Source Technology Center
OpenGL ES profile renderer: Mesa DRI Intel(R) G33 
OpenGL ES profile version: OpenGL ES 2.0 Mesa 21.3.9-arch.6 Amber
OpenGL ES profile shading language version: OpenGL ES GLSL ES 1.0.16

Surfaceless platform:
EGL API version: 1.4
EGL vendor string: Mesa Project (Amber)
EGL version string: 1.4
EGL client APIs: OpenGL OpenGL_ES 
OpenGL compatibility profile vendor: Intel Open Source Technology Center
OpenGL compatibility profile renderer: Mesa DRI Intel(R) G33 
OpenGL compatibility profile version: 2.1 Mesa 21.3.9-arch.6 Amber
OpenGL compatibility profile shading language version: 1.20
OpenGL ES profile vendor: Intel Open Source Technology Center
OpenGL ES profile renderer: Mesa DRI Intel(R) G33 
OpenGL ES profile version: OpenGL ES 2.0 Mesa 21.3.9-arch.6 Amber
OpenGL ES profile shading language version: OpenGL ES GLSL ES 1.0.16

Device platform:
Device #0:

Platform Device platform:
EGL API version: 1.4
EGL vendor string: Mesa Project (Amber)
EGL version string: 1.4
EGL client APIs: OpenGL OpenGL_ES 
OpenGL compatibility profile vendor: Intel Open Source Technology Center
OpenGL compatibility profile renderer: Mesa DRI Intel(R) G33 
OpenGL compatibility profile version: 2.1 Mesa 21.3.9-arch.6 Amber
OpenGL compatibility profile shading language version: 1.20
OpenGL ES profile vendor: Intel Open Source Technology Center
OpenGL ES profile renderer: Mesa DRI Intel(R) G33 
OpenGL ES profile version: OpenGL ES 2.0 Mesa 21.3.9-arch.6 Amber
OpenGL ES profile shading language version: OpenGL ES GLSL ES 1.0.16

Device #1:

Platform Device platform:
EGL API version: 1.4
EGL vendor string: Mesa Project (Amber)
EGL version string: 1.4
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Mesa/X.org
OpenGL core profile renderer: softpipe
OpenGL core profile version: 3.3 (Core Profile) Mesa 21.3.9-arch.6 Amber
OpenGL core profile shading language version: 3.30
OpenGL compatibility profile vendor: Mesa/X.org
OpenGL compatibility profile renderer: softpipe
OpenGL compatibility profile version: 3.3 (Compatibility Profile) Mesa 21.3.9-arch.6 Amber
OpenGL compatibility profile shading language version: 3.30
OpenGL ES profile vendor: Mesa/X.org
OpenGL ES profile renderer: softpipe
OpenGL ES profile version: OpenGL ES 3.1 Mesa 21.3.9-arch.6 Amber
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.10

[miguel@archmiguel ~]$ glxinfo -B
name of display: :0.0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel Open Source Technology Center (0x8086)
    Device: Mesa DRI Intel(R) G33  (0x29c2)
    Version: 21.3.9
    Accelerated: yes
    Video memory: 384MB
    Unified memory: yes
    Preferred profile: compat (0x2)
    Max core profile version: 0.0
    Max compat profile version: 1.4
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 2.0
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) G33 
OpenGL version string: 2.1 Mesa 21.3.9-arch.6 Amber
OpenGL shading language version string: 1.20

OpenGL ES profile version string: OpenGL ES 2.0 Mesa 21.3.9-arch.6 Amber
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16

[miguel@archmiguel ~]$

Offline

#10 2024-11-13 17:37:29

miguel04685
Member
From: Rio de Janeiro, Brasil
Registered: 2024-09-24
Posts: 54

Re: [SOLVED] Can't log into a Wayland session, regardless of the WM/DE

Yes, I can switch into a different TTY and do REISUB (if I log into Wayland session from a display manager)

Offline

#11 2024-11-13 19:46:42

seth
Member
Registered: 2012-09-03
Posts: 59,324

Re: [SOLVED] Can't log into a Wayland session, regardless of the WM/DE

No need for that, from the TTY please post your complete system journal for the boot: 

sudo journalctl -b | curl -F 'file=@-' 0x0.st

*after* failing to start a wayland session.
You do get EGL through software emulation, but the compositor might not be happy w/ that.
You could "export LIBGL_ALWAYS_SOFTWARE=true", but probably don't want to run the display server in complete software emulation anyway?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#12 2024-11-15 20:18:23

miguel04685
Member
From: Rio de Janeiro, Brasil
Registered: 2024-09-24
Posts: 54

Re: [SOLVED] Can't log into a Wayland session, regardless of the WM/DE

Sorry for the delay, this is what I get:
http://0x0.st/XkhY.txt

(In this case I logged in via LightDM after the screen froze with the Hyprland session)

Last edited by miguel04685 (2024-11-15 20:22:49)

Offline

#13 2024-11-15 20:28:10

miguel04685
Member
From: Rio de Janeiro, Brasil
Registered: 2024-09-24
Posts: 54

Re: [SOLVED] Can't log into a Wayland session, regardless of the WM/DE

I also tried to log into Hyprland from the TTY, going to send the output soon

Offline

#14 2024-11-15 20:30:19

miguel04685
Member
From: Rio de Janeiro, Brasil
Registered: 2024-09-24
Posts: 54

Re: [SOLVED] Can't log into a Wayland session, regardless of the WM/DE

From the Hyprland crash report stored in cache:

--------------------------------------------
   Hyprland Crash Report
--------------------------------------------
Vaxry is going to be upset.

Hyprland received signal 6(ABRT)
Version: 
Tag: 
Date: 
Flags:

System info:
	System name: Linux
	Node name: archmiguel
	Release: 6.11.7-1-cachyos
	Version: #1 SMP PREEMPT_DYNAMIC Sat, 09 Nov 2024 08:37:52 +0000

GPU:
	00:02.0 VGA compatible controller [0300]: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 10) (prog-if 00 [VGA controller])


os-release:
	NAME="Arch Linux"
	PRETTY_NAME="Arch Linux"
	ID=arch
	BUILD_ID=rolling
	ANSI_COLOR="38;2;23;147;209"
	HOME_URL="https://archlinux.org/"
	DOCUMENTATION_URL="https://wiki.archlinux.org/"
	SUPPORT_URL="https://bbs.archlinux.org/"
	BUG_REPORT_URL="https://gitlab.archlinux.org/groups/archlinux/-/issues"
	PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
	LOGO=archlinux-logo
Backtrace:
	# | hyprland(_Z12getBacktracev+0x61) [0x631882dd7d71]
		getBacktrace()
		??:?
	#1 | hyprland(_ZN13CrashReporter18createAndSaveCrashEi+0xb80) [0x631882d57260]
		CrashReporter::createAndSaveCrash(int)
		??:?
	#2 | hyprland(_Z25handleUnrecoverableSignali+0x71) [0x631882ccf491]
		handleUnrecoverableSignal(int)
		??:?
	#3 | /usr/lib/libc.so.6(+0x3d1d0) [0x70b2d3f5d1d0]
		??
		??:0
	#4 | /usr/lib/libc.so.6(+0x963f4) [0x70b2d3fb63f4]
		??
		??:0
	#5 | /usr/lib/libc.so.6(gsignal+0x20) [0x70b2d3f5d120]
		??
		??:0
	#6 | hyprland(_ZN15CHyprOpenGLImpl7initEGLEb+0x90e) [0x631882fc0cce]
		CHyprOpenGLImpl::initEGL(bool)
		??:?
	#7 | hyprland(_ZN15CHyprOpenGLImplC1Ev+0xc0a) [0x631882fc7d8a]
		CHyprOpenGLImpl::CHyprOpenGLImpl()
		??:?
	#8 | hyprland(_ZN11CCompositor12initManagersE18eManagersInitStage+0xc99) [0x631882cd4b89]
		CCompositor::initManagers(eManagersInitStage)
		??:?
	#9 | hyprland(_ZN11CCompositor10initServerENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEi+0xd65) [0x631882cd6315]
		CCompositor::initServer(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, int)
		??:?
	#1 | hyprland(main+0xb15) [0x631882c8a035]
		main
		??:?
	#11 | /usr/lib/libc.so.6(+0x25e08) [0x70b2d3f45e08]
		??
		??:0
	#12 | /usr/lib/libc.so.6(__libc_start_main+0x8c) [0x70b2d3f45ecc]
		??
		??:0
	#13 | hyprland(_start+0x25) [0x631882ccb6d5]
		_start
		??:?


Log tail:
[LOG] [AQ] drm: Scanning connectors for /dev/dri/card0
[LOG] [AQ] drm: Scanning connector id 48
[LOG] [AQ] drm: Initializing connector id 48
[LOG] [AQ] drm: Connector gets name VGA-1
[LOG] [AQ] drm: Connector 48 connection state: 1
[LOG] [AQ] drm: Rechecking CRTCs
[LOG] [AQ] drm: Skipping connector VGA-1, has crtc 39 and is connected
[LOG] [AQ] drm: slot 0 crtc 39 taken by VGA-1, skipping
[LOG] [AQ] drm: slot 1 crtc 47 unassigned
[LOG] [AQ] drm: rescanning after realloc
[LOG] [AQ] drm: Scanning connectors for /dev/dri/card0
[LOG] [AQ] drm: Scanning connector id 48
[LOG] [AQ] drm: Connector id 48 already initialized
[LOG] [AQ] drm: Connector 48 connection state: 1
[LOG] [AQ] drm: Connector VGA-1 connected
[LOG] [AQ] drm: Connecting connector VGA-1, CRTC ID 39
[LOG] [AQ] drm: Dumping detected modes:
[LOG] [AQ] drm: Mode 0: 1366x768@59.79Hz  (preferred)
[LOG] [AQ] drm: Mode 1: 1280x1024@75.03Hz 
[LOG] [AQ] drm: Mode 2: 1280x1024@60.02Hz 
[LOG] [AQ] drm: Mode 3: 1280x960@60.00Hz 
[LOG] [AQ] drm: Mode 4: 1280x800@59.81Hz 
[LOG] [AQ] drm: Mode 5: 1152x864@75.00Hz 
[LOG] [AQ] drm: Mode 6: 1280x720@60.00Hz 
[LOG] [AQ] drm: Mode 7: 1024x768@75.03Hz 
[LOG] [AQ] drm: Mode 8: 1024x768@70.07Hz 
[LOG] [AQ] drm: Mode 9: 1024x768@60.00Hz 
[LOG] [AQ] drm: Mode 10: 832x624@74.55Hz 
[LOG] [AQ] drm: Mode 11: 800x600@75.00Hz 
[LOG] [AQ] drm: Mode 12: 800x600@72.19Hz 
[LOG] [AQ] drm: Mode 13: 800x600@60.32Hz 
[LOG] [AQ] drm: Mode 14: 800x600@56.25Hz 
[LOG] [AQ] drm: Mode 15: 640x480@75.00Hz 
[LOG] [AQ] drm: Mode 16: 640x480@72.81Hz 
[LOG] [AQ] drm: Mode 17: 640x480@66.67Hz 
[LOG] [AQ] drm: Mode 18: 640x480@59.94Hz 
[LOG] [AQ] drm: Mode 19: 720x400@70.08Hz 
[LOG] [AQ] drm: Physical size [Vector2D: x: 430, y: 240] (mm)
[LOG] [AQ] drm: Description Acer Technologies V206HQL LY6AA0128509 (VGA-1)
[LOG] [AQ] drm: connector VGA-1 crtc is incapable of vrr: props.vrr_capable -> 0, crtc->props.vrr_enabled -> 0
[LOG] [AQ] drm: Explicit sync unsupported
[LOG] [AQ] drm: connector VGA-1 crtc doesn't support CTM
[LOG] [AQ] drm: gpu /dev/dri/card0 becomes primary drm
[LOG] [AQ] DRM Dumb: created a dumb allocator
[LOG] [AQ] Starting the Aquamarine backend!
[LOG] [AQ] Starting the Wayland backend!
[ERR] [AQ] Wayland backend cannot start: wl_display_connect failed (is a wayland compositor running?)
[ERR] [AQ] Requested backend (wayland) could not start, enabling fallbacks
[ERR] [AQ] Implementation wayland failed, erasing.
[LOG] [AQ] Created a GBM allocator with drm fd 26
[LOG] [AQ] drm: Connectors size2 1
[LOG] [AQ] Created a GBM allocator with drm fd 27
[ERR] [AQ] CDRMRenderer: fail, no EXT_image_dma_buf_import_modifiers ext
[ERR] [AQ] drm: onReady: no renderer for gl formats
[LOG] [AQ] drm: onReady: connector 48
[LOG] [AQ] drm: onReady: connector 48 has output name VGA-1
[LOG] [AQ] Swapchain: Clearing
[LOG] New aquamarine output with name VGA-1
[ERR] [AQ] CDRMRenderer: fail, no EXT_image_dma_buf_import_modifiers ext
[ERR] [AQ] drm: initMgpu: no renderer
[ERR] [AQ] drm: Failed initializing mgpu
[LOG] Running on DRMFD: 25
[LOG] wl_display_add_socket for wayland-1 succeeded with 0
[LOG] Creating the CHyprOpenGLImpl!
[LOG] Supported EGL extensions: (15) EGL_EXT_device_base EGL_EXT_device_enumeration EGL_EXT_device_query EGL_EXT_platform_base EGL_KHR_client_get_all_proc_addresses EGL_EXT_client_extensions EGL_KHR_debug EGL_EXT_platform_device EGL_EXT_platform_wayland EGL_KHR_platform_wayland EGL_EXT_platform_x11 EGL_KHR_platform_x11 EGL_MESA_platform_xcb EGL_MESA_platform_gbm EGL_KHR_platform_gbm EGL_MESA_platform_surfaceless
[LOG] eglDeviceFromDRMFD: Using device /dev/dri/card0
[ERR] [EGL] Command eglCreateContext errored out with EGL_BAD_MATCH (0x12297): dri2_create_context
[WARN] EGL: Failed to create a context with GLES3.2, retrying 3.0
[ERR] [EGL] Command eglCreateContext errored out with EGL_BAD_MATCH (0x12297): dri2_create_context
[CRITICAL] 
==========================================================================================
ASSERTION FAILED! 

EGL: failed to create a context with either GLES3.2 or 3.0

at: line 172 in OpenGL.cpp

Offline

#15 2024-11-15 20:56:42

seth
Member
Registered: 2012-09-03
Posts: 59,324

Re: [SOLVED] Can't log into a Wayland session, regardless of the WM/DE

nov 15 17:14:40 archmiguel lightdm[510]: pam_unix(lightdm-autologin:session): session opened for user miguel(uid=1000) by miguel(uid=0)
nov 15 17:14:44 archmiguel lightdm[510]: gkr-pam: couldn't unlock the login keyring.
nov 15 17:15:25 archmiguel lightdm[510]: pam_unix(lightdm-autologin:session): session closed for user miguel
nov 15 17:15:26 archmiguel lightdm[960]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=957) by (uid=0)
nov 15 17:15:26 archmiguel systemd-logind[433]: New session c1 of user lightdm.
nov 15 17:15:26 archmiguel (systemd)[968]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[lightdm] ruser=[<unknown>] rhost=[<unknown>]
nov 15 17:15:26 archmiguel (systemd)[968]: pam_unix(systemd-user:session): session opened for user lightdm(uid=957) by lightdm(uid=0)
nov 15 17:15:26 archmiguel systemd-logind[433]: New session 3 of user lightdm.
nov 15 17:15:27 archmiguel systemd[1]: Started Session c1 of User lightdm.
nov 15 17:15:34 archmiguel lightdm[1030]: gkr-pam: unable to locate daemon control file
nov 15 17:15:34 archmiguel lightdm[1030]: gkr-pam: stashed password to try later in open session
nov 15 17:15:34 archmiguel lightdm[1050]: Error opening display!

So you're logging in, (some xfce stuff starts) and then about 45s later log out, but lightdm cannot take control over the display (likely because the wayland compositor doesn't release it)

Hyprland still aborts from 

	#6 | hyprland(_ZN15CHyprOpenGLImpl7initEGLEb+0x90e) [0x631882fc0cce]
		CHyprOpenGLImpl::initEGL(bool)
		??:?
	#7 | hyprland(_ZN15CHyprOpenGLImplC1Ev+0xc0a) [0x631882fc7d8a]
		CHyprOpenGLImpl::CHyprOpenGLImpl()

==> Did you try w/ exporting "LIBGL_ALWAYS_SOFTWARE=true"?


However, regardless of that Hyprland will not run well on that hardware (because it's always some sort of software emulation)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#16 2024-11-15 21:18:52

miguel04685
Member
From: Rio de Janeiro, Brasil
Registered: 2024-09-24
Posts: 54

Re: [SOLVED] Can't log into a Wayland session, regardless of the WM/DE

With exporting "LIBGL_ALWAYS_SOFTWARE=true" it also crashes

Offline

#17 2024-11-15 21:21:48

miguel04685
Member
From: Rio de Janeiro, Brasil
Registered: 2024-09-24
Posts: 54

Re: [SOLVED] Can't log into a Wayland session, regardless of the WM/DE

I think I have to stick with Xorg on this machine, or at least get a better GPU to run Wayland

Last edited by miguel04685 (2024-11-15 21:22:03)

Offline

#18 2024-11-15 21:23:03

seth
Member
Registered: 2012-09-03
Posts: 59,324

Re: [SOLVED] Can't log into a Wayland session, regardless of the WM/DE

Same errors as

[ERR] [AQ] CDRMRenderer: fail, no EXT_image_dma_buf_import_modifiers ext
[ERR] [AQ] drm: initMgpu: no renderer
[ERR] [AQ] drm: Failed initializing mgpu
[LOG] Running on DRMFD: 25
[LOG] wl_display_add_socket for wayland-1 succeeded with 0
[LOG] Creating the CHyprOpenGLImpl!
[LOG] Supported EGL extensions: (15) EGL_EXT_device_base EGL_EXT_device_enumeration EGL_EXT_device_query EGL_EXT_platform_base EGL_KHR_client_get_all_proc_addresses EGL_EXT_client_extensions EGL_KHR_debug EGL_EXT_platform_device EGL_EXT_platform_wayland EGL_KHR_platform_wayland EGL_EXT_platform_x11 EGL_KHR_platform_x11 EGL_MESA_platform_xcb EGL_MESA_platform_gbm EGL_KHR_platform_gbm EGL_MESA_platform_surfaceless
[LOG] eglDeviceFromDRMFD: Using device /dev/dri/card0
[ERR] [EGL] Command eglCreateContext errored out with EGL_BAD_MATCH (0x12297): dri2_create_context
[WARN] EGL: Failed to create a context with GLES3.2, retrying 3.0
[ERR] [EGL] Command eglCreateContext errored out with EGL_BAD_MATCH (0x12297): dri2_create_context

?

I think I have to stick with Xorg on this machine, or at least get a better GPU to run Wayland

Yes. You could try weston though, if you want.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#19 2024-11-15 21:29:10

miguel04685
Member
From: Rio de Janeiro, Brasil
Registered: 2024-09-24
Posts: 54

Re: [SOLVED] Can't log into a Wayland session, regardless of the WM/DE

Yes, I get the same EGL issue with the flag "LIBGL_ALWAYS_SOFTWARE". Weston works normally though

Offline

Pages: 1

Board footer

Powered by FluxBB