[Bug 58734] New: How to disable usage of wayland and use x11 (xwayland) instead
http://bugs.winehq.org/show_bug.cgi?id=58734 Bug ID: 58734 Summary: How to disable usage of wayland and use x11 (xwayland) instead Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: euloanty(a)live.com Distribution: --- After 9.22 it enforces wayland but it does not work correctly on my machine (like UI issues, keyboard issues, no touch support etc). How to disable it? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=58734 cqwrteur <euloanty(a)live.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |euloanty(a)live.com -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=58734 Stian Low <wineryyyyy(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wineryyyyy(a)gmail.com --- Comment #1 from Stian Low <wineryyyyy(a)gmail.com> --- (In reply to cqwrteur from comment #0)
After 9.22 it enforces wayland but it does not work correctly on my machine (like UI issues, keyboard issues, no touch support etc). How to disable it?
Please report each of these bugs as you encounter them if not already reported: "UI issues, keyboard issues, no touch support etc" As for how to disable wayland, please refer to forums: https://forum.winehq.org/viewtopic.php?t=38372 HKEY_CURRENT_USER\Software\Wine\Drivers\Graphics does not exist by default and is set to "mac,x11,wayland" by default according to: ./programs/explorer/desktop.c: static const WCHAR default_driver[] = L"mac,x11,wayland"; ./programs/explorer/desktop.c load_graphics_driver() overrides default_driver with HKEY_CURRENT_USER\Software\Wine\Drivers\Graphics: static void load_graphics_driver( const WCHAR *driver, GUID *guid ) { static const WCHAR device_keyW[] = L"System\\CurrentControlSet\\Control\\Video\\{%08x-%04x-%04x-%02x%02x-%02x%02x%02x%02x%02x%02x}\\0000"; WCHAR buffer[MAX_PATH], libname[32], *name, *next; WCHAR key[ARRAY_SIZE( device_keyW ) + 39]; BOOL null_driver = FALSE; HMODULE module = 0; HKEY hkey; char error[80]; if (!driver) { lstrcpyW( buffer, default_driver ); /* @@ Wine registry key: HKCU\Software\Wine\Drivers */ if (!RegOpenKeyW( HKEY_CURRENT_USER, L"Software\\Wine\\Drivers", &hkey )) { DWORD count = sizeof(buffer); RegQueryValueExW( hkey, L"Graphics", 0, NULL, (LPBYTE)buffer, &count ); RegCloseKey( hkey ); } } else lstrcpynW( buffer, driver, ARRAY_SIZE( buffer )); DISPLAY=wine environment variable mentioned by the forum seems to override registry keys by forcing wayland so it needs to be unset to unforce wayland. Test results via GNOME Wayland session for Debian 13: `WINEDEBUG=+x11drv wine regedit` outputs x11drv logs `WINEDEBUG=+waylanddrv wine regedit` outputs no logs `DISPLAY=wine WINEDEBUG=+waylanddrv wine regedit` outputs waylanddrv logs This bug report highlights WineHQ documentation lacking a bit for wayland and x11 info so maybe it should be improved before this bug report is considered resolved and closed. Registry keys are covered but it does not list wayland as an option as indicated by forums and arch wiki: https://gitlab.winehq.org/wine/wine/-/wikis/Useful-Registry-Key I could not find DISPLAY=wine anywhere in documentation: https://gitlab.winehq.org/wine/wine/-/wikis/Documentation Searching X11 or wayland on the wiki returns no results so that probably needs to be improved to provide more convenient helpful resources. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=58734 --- Comment #2 from Alexandre Julliard <julliard(a)winehq.org> --- (In reply to Stian Low from comment #1)
I could not find DISPLAY=wine anywhere in documentation:
There's no such thing as 'DISPLAY=wine'. The forum post mentions 'DISPLAY=', which means unsetting DISPLAY to force wayland. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=58734 --- Comment #3 from Stian Low <wineryyyyy(a)gmail.com> --- (In reply to Alexandre Julliard from comment #2)
(In reply to Stian Low from comment #1)
I could not find DISPLAY=wine anywhere in documentation:
There's no such thing as 'DISPLAY=wine'. The forum post mentions 'DISPLAY=', which means unsetting DISPLAY to force wayland.
Thanks for clarifying @Julliard. That was a misread on my part. DISPLAY=wine seems to have the same effect as DISPLAY= so it seems setting to a bogus value that X11 does not handle also bypasses X11 allowing wayland override but DISPLAY= is more clear what's actually happening. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=58734 mata <sutupud(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sutupud(a)yahoo.com --- Comment #4 from mata <sutupud(a)yahoo.com> --- But with the x11 driver still being the default if not forced, the only way the wayland driver could be used in this scenario was when running a wayland session without XWayland installed. So first step would be to ensure that XWayland is installed and running. Then the x11 driver should be used automatically again. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla