| commit | 9c22a5ea63c6be01e257f05bbed23e03d5a7f407 | |
| author | Rémi Bernon <rbernon@codeweavers.com> | |
| Fri, 3 Mar 2023 08:30:37 +0000 (3 09:30 +0100) | ||
| committer | Alexandre Julliard <julliard@winehq.org> | |
| Fri, 3 Mar 2023 17:29:55 +0000 (3 18:29 +0100) | ||
| tree | a4d41b14e016437ab0ac020a30c9cb7b330ad905 | treesnapshot (tar.gz zip) |
| parent | 992d60e1222ef6e6e835ed10e80556235e257bd4 | commitdiff |
win32u: Check GUID_NULL display device if desktop atom is missing.
When using nulldrv, there's no module to call __wine_set_user_driver and
the user driver is still lazy_load_driver when get_display_driver gets
called during desktop windows creation.
Then, load_desktop_driver fails as it cannot find the not-yet-created
desktop window atom, and fails later explorer.exe window creations such
as the systray window.
Other processes don't suffer from this as they wait for the desktop
window to be fully created, and its atom will be eventually set.
This change makes sure that we succeed in the case nulldrv was selected
by explorer.exe, while still failing in case of error with another user
driver as it would fail to open the right display device GUID.
When using nulldrv, there's no module to call __wine_set_user_driver and
the user driver is still lazy_load_driver when get_display_driver gets
called during desktop windows creation.
Then, load_desktop_driver fails as it cannot find the not-yet-created
desktop window atom, and fails later explorer.exe window creations such
as the systray window.
Other processes don't suffer from this as they wait for the desktop
window to be fully created, and its atom will be eventually set.
This change makes sure that we succeed in the case nulldrv was selected
by explorer.exe, while still failing in case of error with another user
driver as it would fail to open the right display device GUID.
| dlls/win32u/driver.c | diffblobblamehistory |