[Bug 53928] New: ChangeDisplaySettingsExW Changing L"\\\\.\\DISPLAY1" display settings returned -1
https://bugs.winehq.org/show_bug.cgi?id=53928
Bug ID: 53928 Summary: ChangeDisplaySettingsExW Changing L"\\.\DISPLAY1" display settings returned -1 Product: Wine Version: 7.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: alandms123@gmail.com Distribution: ---
Created attachment 73486 --> https://bugs.winehq.org/attachment.cgi?id=73486 wine.log
OS: Arch Linux x86_64 Kernel: 6.0.8-arch1-1 nvidia drivers: 520.56.06-2 mesa: 22.2.3-1 WM: dwm cpu: i5-11400h dgpu: rtx 3050 laptop igpu: intel uhd graphics (tgl gt1)
The only application I tried with was The Elder Scrolls Online. Basically with these versions of wine (6.16, 6.23, 7.0, 7.19, 7.20, 7.21) when using PRIME render offload (prime-run or setting the environment variables manually) a black screen will appear, killing the game processes or wine will not make X display anything again, the only way is switching to another tty and killing X from there.
I did tried bisecting for a regression but couldn't go far, for example compiling 6.1-6.23 fails with something like conflicting types for ‘ldap_connect’.
Also as I don't know which debug channel to provide the debug details the logs doesn't say much besides:
016c:err:system:ChangeDisplaySettingsExW Changing L"\\.\DISPLAY1" display settings returned -1.
The only versions which works, are the wine-tkg (https://github.com/Frogging-Family/wine-tkg-git/releases/tag/7.6.r12.g514723...) and ge-proton (https://github.com/GloriousEggroll/wine-ge-custom/releases/tag/GE-Proton7-33)
If I can figure how to solve the conflicting types for ‘ldap_connect’, I'll try bisecting.
https://bugs.winehq.org/show_bug.cgi?id=53928
--- Comment #1 from Rafał Mużyło galtgendo@o2.pl --- Out of curiosity, if by 'killing X' you mean killing xserver, did you try to kill just the window manager ?
I've seen cases in a couple apps, where a Windows app captured input so successfully that it went past its lifetime, but killing the window manager too let things recover almost completely (as long as the *session* manager restarted wm).
Though given you're talking effectively about a gpu switch, this might be completely unrelated...
https://bugs.winehq.org/show_bug.cgi?id=53928
--- Comment #2 from Alan alandms123@gmail.com --- Yeah, I'm simply typing "pkill -15 Xorg", but "pkill -15 dwm" from another tty (say tty2) will get me access to the tty1 again and I can use startx and my xinitrc will get read and start dwm again.
(Also just tried compiling 7.6 and is happening there, my idea was the 7.6 in "proton-tkg 7.6.r12.g51472395" maybe the 7.6 was hinting something for me, but no, still the same behavior, I was trying to compile from git too and doing a checkout for g51472395 didn't work.)
https://bugs.winehq.org/show_bug.cgi?id=53928
--- Comment #3 from Alan alandms123@gmail.com --- Like, I don't know if this is important, but when I say that "I'm having a black screen", is somewhat different from the usual black screen when X simply freeze, but you still see a black screen with some bright like indicating that something is there, that you monitor is turned on, you can tell that there's something drawn (I don't know how to explain). Because in my case the monitor is like "turned off", you know what I mean? There's nothing, no bright in it, no nothing, as when the notebook is turned off.
https://bugs.winehq.org/show_bug.cgi?id=53928
--- Comment #4 from Hans Leidekker hans@meelstraat.net --- (In reply to Alan from comment #0)
If I can figure how to solve the conflicting types for ‘ldap_connect’, I'll try bisecting.
You can apply 7f1d6a8ee2c72409f4f840df23401c9702adee5e during the bisect.
https://bugs.winehq.org/show_bug.cgi?id=53928
--- Comment #5 from Alan alandms123@gmail.com --- Thanks Hans Leidekker, I've been using the fix that arch seems to be using to compile wine:
sed 's/-lldap_r/-lldap/' -i configure
https://bugs.winehq.org/show_bug.cgi?id=53928
--- Comment #6 from Alan alandms123@gmail.com --- But about the issue, it's fixed if I apply this patch https://github.com/Frogging-Family/wine-tkg-git/blob/master/wine-tkg-git/win...
As I think it's a known problem, I guess this is a "WON'T FIX" then?
Because I don't think it should, it may scare someone, like you open a application with wine and all of sudden your monitor "dies", you may think you burnt your gpu or something.
https://bugs.winehq.org/show_bug.cgi?id=53928
--- Comment #7 from Alan alandms123@gmail.com --- Created attachment 73492 --> https://bugs.winehq.org/attachment.cgi?id=73492 valve_proton_fullscreen_hack-staging.patch
https://bugs.winehq.org/show_bug.cgi?id=53928
mrdeathjr28@yahoo.es changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mrdeathjr28@yahoo.es
-
WineHQ Bugzilla