[Bug 50299] New: Application tried to create a window, but no driver could be loaded.

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=50299

            Bug ID: 50299
           Summary: Application tried to create a window, but no driver
                    could be loaded.
           Product: Wine
           Version: 5.22
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: minor
          Priority: P2
         Component: -unknown
          Assignee: wine-bugs(a)winehq.org
          Reporter: bernhardu(a)mailbox.org
      Distribution: ---

0050:err:winediag:nodrv_CreateWindow Application tried to create a window, but
no driver could be loaded.

Running e.g. "wine notepad" in a quite slow environment for example within
rr-debugger inside a VM leads to the above message.

As far as I could follow in above line 0050 is "explorer.exe".
Unfotunately winemenubuilder.exe was a little bit earlier with requesting
the first window in WIN_CreateWindowEx
before explorer.exe reached manage_desktop.
Therefore explorer.exe never SetPropW("__wine_display_device_guid")
in DesktopWndProc.

This race might not show up under normal conditions, but I thought to
document it here to be findable.

Making winemenubuilder.exe sleep some time in wWinMain before CoInitialize
works around 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.

[Bug 50299] Application tried to create a window, but no driver could be loaded.

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=50299

--- Comment #1 from Bernhard Übelacker <bernhardu(a)mailbox.org> ---
Created attachment 68907
  --> https://bugs.winehq.org/attachment.cgi?id=68907
Avoid winemenubuilder to startup explorer.exe.

I further looked into the issue and found that in that environment
winemenubuilder is faster and triggers startup of explorer.exe.
But started with that parent explorer.exe cannot properly setup the desktop.

This hack creates an event __wine_desktop_created that is released just after
explorer.exe reaches the SetPropW(__wine_display_device_guid).

-- 
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.

[Bug 50299] Running winemenubuilder in a slow environment may trigger a race condition that prevents window creation

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=50299

Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Application tried to create |Running winemenubuilder in
                   |a window, but no driver     |a slow environment may
                   |could be loaded.            |trigger a race condition
                   |                            |that prevents window
                   |                            |creation
                 CC|                            |o.dierick(a)piezo-forte.be

-- 
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.

[Bug 50299] Running winemenubuilder in a slow environment may trigger a race condition that prevents window creation

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=50299

François Gouget <fgouget(a)codeweavers.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |patch
                 CC|                            |fgouget(a)codeweavers.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.