[Bug 41235] New: msiexec fails to show installer window
https://bugs.winehq.org/show_bug.cgi?id=41235 Bug ID: 41235 Summary: msiexec fails to show installer window Product: Wine Version: 1.7.51 Hardware: x86-64 URL: https://dl.bintray.com/supertux/SuperTux-Nightly/:Supe rTux-v0.5.0-rc.3-23-g470349f-win32.msi OS: Mac OS X Status: UNCONFIRMED Severity: major Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: tobbi.bugs(a)googlemail.com When I try to install an MSI file, it doesn't open. I am only getting the following error messages on the console: fixme:ntdll:NtLockFile I/O completion on lock not implemented yet err:winediag:nulldrv_CreateWindow Application tried to create a window, but no driver could be loaded. err:winediag:nulldrv_CreateWindow The explorer process failed to start. err:msi:dialog_run_message_loop Failed to create dialog L"PrepareDlg" err:msi:dialog_run_message_loop Failed to create dialog L"MaintenanceWelcomeDlg" err:msi:dialog_run_message_loop Failed to create dialog L"ProgressDlg" err:msi:dialog_run_message_loop Failed to create dialog L"ExitDialog" This has also been reported on the forums: https://forum.winehq.org/viewtopic.php?f=9&t=27223 I tried with the following msi file: https://dl.bintray.com/supertux/SuperTux-Nightly/:SuperTux-v0.5.0-rc.3-23-g4... SHA1(SuperTux-v0.5.0-rc.3-23-g470349f-win32.msi)= 4343922f3f0342d86088ac286fb8d3a32e039330 -- 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.
https://bugs.winehq.org/show_bug.cgi?id=41235 Tobias (:Tobbi) Markus <tobbi.bugs(a)googlemail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|1.7.51 |1.9.17 -- 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.
https://bugs.winehq.org/show_bug.cgi?id=41235 Nikolay Sivov <bunglehead(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal -- 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.
https://bugs.winehq.org/show_bug.cgi?id=41235 Nikolay Sivov <bunglehead(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|msi |-unknown -- 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.
https://bugs.winehq.org/show_bug.cgi?id=41235 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download -- 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.
https://bugs.winehq.org/show_bug.cgi?id=41235 mfuhrer(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mfuhrer(a)gmail.com --- Comment #1 from mfuhrer(a)gmail.com --- This appears to be a more general problem in the latest wine releases (I encountered it in 1.9.16). Running any executable that attempts to open a window (e.g. winemine, regedit) fails to do so, generating the "Application tried to create a window, but no driver could be loaded" console error. Another forum thread about the problem is here: https://forum.winehq.org/viewtopic.php?f=9&t=27305 -- 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.
https://bugs.winehq.org/show_bug.cgi?id=41235 mrpuck69(a)yahoo.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrpuck69(a)yahoo.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.
https://bugs.winehq.org/show_bug.cgi?id=41235 --- Comment #2 from Tobias (:Tobbi) Markus <tobbi.bugs(a)googlemail.com> --- (In reply to Martin Fuhrer from comment #1)
This appears to be a more general problem in the latest wine releases (I encountered it in 1.9.16). Running any executable that attempts to open a window (e.g. winemine, regedit) fails to do so, generating the "Application tried to create a window, but no driver could be loaded" console error.
Another forum thread about the problem is here: https://forum.winehq.org/viewtopic.php?f=9&t=27305
Martin and others: I just re-installed wine via homebrew (as opposed to Macports, previously) and things have started to work again. I am not sure if this has something to do with one of the releases in the meantime or whether it's a bug with how Macports installs wine. Can you re-test? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=41235 winetest(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |00cpxxx(a)gmail.com, | |austinenglish(a)gmail.com, | |winetest(a)luukku.com --- Comment #3 from winetest(a)luukku.com --- (In reply to Tobias (:Tobbi) Markus from comment #2)
(In reply to Martin Fuhrer from comment #1)
This appears to be a more general problem in the latest wine releases (I encountered it in 1.9.16). Running any executable that attempts to open a window (e.g. winemine, regedit) fails to do so, generating the "Application tried to create a window, but no driver could be loaded" console error.
Another forum thread about the problem is here: https://forum.winehq.org/viewtopic.php?f=9&t=27305
Martin and others: I just re-installed wine via homebrew (as opposed to Macports, previously) and things have started to work again. I am not sure if this has something to do with one of the releases in the meantime or whether it's a bug with how Macports installs wine.
Can you re-test?
I think this is safe to close now. The thread mentioned here has 2 last comments as following: Solution has been found for this problem. It is related to fontconfig 2.12.1. To fix the issue, revert to 2.12.0 I can confirm that after reverting to fontconfig 2.12.0, wine is back to normal and will display windows just fine. But does wine even support homebrew installs??? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=41235 Bruno Jesus <00cpxxx(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Bruno Jesus <00cpxxx(a)gmail.com> ---
From the forum thread the other bug 41240 was closed as duplicate and the problem was very similar to this one so I'm assuming as duplicate.
*** This bug has been marked as a duplicate of bug 41152 *** -- 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.
https://bugs.winehq.org/show_bug.cgi?id=41235 Bruno Jesus <00cpxxx(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #5 from Bruno Jesus <00cpxxx(a)gmail.com> --- Closing duplicate bugs. -- 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)
-
wine-bugs＠winehq.org