https://bugs.winehq.org/show_bug.cgi?id=52500
--- Comment #39 from O. Nykyforchyn oleh.nyk@gmail.com --- (In reply to Zeb Figura from comment #37)
It's not inexplicable. I can see a couple of ways initialization can fail without any log messages.
I would consider this as a code defect: issues with winex11 initialization arise regularly, then the are kind of solved (or hidden), but users have no possibility to diagnose the root of evil. Why not add some messages after each major step if initialization that can fail?
To tell the truth, I tried to add extra messages to the code of explorer and of winex11 to get more info, the first worked, but the second did not. Maybe no debug messages from x11drv code can be printed until the driver is initialized completely?