Wine/wayland: "Can not activate the second GL rendering context"

jfk · 2025-01-22 19:38:55

wine-10.0-rc6 (64bits prefixe)
mesa 1:24.3.3-2
qtile (wayland) 30.0

$ lspci -k | grep -EA3 'VGA'
0c:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 (rev 06)
	Subsystem: ASUSTeK Computer Inc. Device 8877
	Kernel driver in use: amdgpu
	Kernel modules: amdgpu

I've been trying to load an application through wayland on a wayland session with the"DISPLAY= " variable and got a a popup warning:

Can not activate the second GL rendering context

"WINEDEBUG=fixme-all" gives:

0050:err:system:NtUserChangeDisplaySettings Changing L"\\\\.\\DISPLAY1" display settings returned -2.
0050:err:explorer:initialize_display_settings Failed to initialize registry display settings for L"\\\\.\\DISPLAY1".
0050:err:system:NtUserChangeDisplaySettings Changing L"\\\\.\\DISPLAY2" display settings returned -2.
0050:err:explorer:initialize_display_settings Failed to initialize registry display settings for L"\\\\.\\DISPLAY2".

Appending this here:

$ eglinfo | grep "EGL API"
_amdgpu_device_initialize: amdgpu_query_info(ACCEL_WORKING) failed (-13)
amdgpu: amdgpu_device_initialize failed.
EGL API version: 1.5
EGL API version: 1.5
EGL API version: 1.5
EGL API version: 1.5
EGL API version: 1.5

Last edited by jfk (2025-01-22 20:07:39)

seth · 2025-01-23 09:09:01

I've been trying to load an application through wayland on a wayland session with the"DISPLAY= " variable and got a a popup warning:

I'd assume wine/proton is xwayland only, steam certainly is.
Why are we doing this?

jfk · 2025-01-23 12:23:01

Why are we doing this?

If you meant:

1) The variable DISPLAY= : because this is the way.
2) Why bother to use wayland: to work around xwayland HiDPI scaling limitation.

seth · 2025-01-23 12:34:22

Wine was just updated to 10.x some minutes ago - you can give that a shot. I'd not bother trying native wayland on wine 9.x and still expect 10.x to present you with a bunch of bugs.

work around xwayland HiDPI scaling limitation

https://wok.oblomov.eu/tecnologia/mixed-dpi-x11/
And what exact limitation do you mean? The compositor scales xwayland windows or doesn't…

jfk · 2025-01-23 12:54:58

Wine was just updated to 10.x some minutes ago - you can give that a shot.

As I already tested this on 10.0-rc6, this indeed hasn't solved the problem.

And what exact limitation do you mean? The compositor scales xwayland windows or doesn't…

Yes I implied on qtile. I think only KDE has managed to implement a way to scale xwayland properly. We'll wait for this I guess... https://gitlab.freedesktop.org/xorg/xse … quests/733

However, these are two separate issues. The warning window I get is correctly scaled. I must miss some libraries or should force something to load but I don't know what yet.

Last edited by jfk (2025-01-23 20:47:21)

Arch Linux

#1 2025-01-22 19:38:55

Wine/wayland: "Can not activate the second GL rendering context"

#2 2025-01-23 09:09:01

Re: Wine/wayland: "Can not activate the second GL rendering context"

#3 2025-01-23 12:23:01

Re: Wine/wayland: "Can not activate the second GL rendering context"

#4 2025-01-23 12:34:22

Re: Wine/wayland: "Can not activate the second GL rendering context"

#5 2025-01-23 12:54:58

Re: Wine/wayland: "Can not activate the second GL rendering context"

Board footer