http://bugs.winehq.org/show_bug.cgi?id=58421
Bug ID: 58421 Summary: Meta Trader 4 still does not start under Wine 10.9 Product: Wine Version: 10.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: tst1@mixbox.pl Distribution: ---
After upgrading wine to 10.9 Meta Trader 4 still does not start. But with this wine version it seams to be not the same issue as under wine 10.3 to 10.7 (described in https://bugs.winehq.org/show_bug.cgi?id=58011 and https://bugs.winehq.org/show_ug.cgi?id=57950 ). This time there in no error message window (as it was under wine 10.3 to 10.7) and a try to start MT4 in the linux terminal generates other error (not the same as previously) as shown below: https://pastebin.com/kBLVS6G8
Downgrading to wine 10.2-2 temporary solves the issue (MT4 starts, at least under Manjaro Linux, with Windows 11 set in wine settings).
http://bugs.winehq.org/show_bug.cgi?id=58421
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Meta Trader 4 still does |Meta Trader 4 does not |not start under Wine 10.9 |start
http://bugs.winehq.org/show_bug.cgi?id=58421
--- Comment #1 from Ken Sharp imwellcushtymelike@gmail.com ---
003c:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
How are you running this? Is it in a chroot/container?
Please show the result of $ echo $DISPLAY
http://bugs.winehq.org/show_bug.cgi?id=58421
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO
http://bugs.winehq.org/show_bug.cgi?id=58421
--- Comment #2 from win.user tst1@mixbox.pl --- Normally, I start Meta Trader 4 by clicking on the MT4 icon. When I tried to start Meta Trader 4 under wine 10.9 in this way, nothing was happening (no error message window as it was under wine 10.3 to 10.7).
To see the errors under wine 10.9, I started MT4 (without any chroot/container) in my default Linux terminal (xfce4-terminal) by typing the command "wine terminal.exe" (and being in MT4 directory).
The result of "echo $DISPLAY" command is one line only: :0.0
http://bugs.winehq.org/show_bug.cgi?id=58421
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |ArchLinux Keywords| |download URL| |https://web.archive.org/web | |/20101228171757/http://www. | |metatrader4.com/files/mt4se | |tup.exe
--- Comment #3 from Ken Sharp imwellcushtymelike@gmail.com ---
wine terminal.exe
This is the 32-bit application, and as of 10.8-2 Arch, and therefore Manjaro, switched to the new (experimental) WoW64. https://gitlab.archlinux.org/archlinux/packaging/packages/wine/-/commit/b92e...
sha1: f6d9fd62eb68acfb25d169caab3fde43c653223e mt4-227.exe https://web.archive.org/web/20101228171757/http://www.metatrader4.com/files/...
I tested on Manjaro but cannot recreate the issue. We probably have slightly different versions, however.
With Wine 10.2-2: $ winetricks -q mfc42 $ wine mt4-227.exe Application starts fine.
$ echo disabled > ~/.wine/.update-timestamp # Only way to trigger any kind of issue
With Wine 10.9: $ wine terminal.exe Crash caught by MT4 and exits
$ wineboot -u $ wine terminal.exe Application starts fine.
My guess is that you are using an old wineprefix.
Can you try running "wineboot -u" and then run MT4 again? If this fails can you try a fresh install in a clean wineprefix?
http://bugs.winehq.org/show_bug.cgi?id=58421
--- Comment #4 from win.user tst1@mixbox.pl --- I tried everything you suggested and it seems that this (experimental) WoW64 mode is responsible for all those problems - with every Windows program (not just MT4) under wine-10.9. So under wine-10.9: "wineboot -u" generates errors and "winecfg" generates the same errors and neither MT4 nor any other Windows program is starting.
After creating a new clean winprefix, there are still errors (although slightly different) and nothing starts up.
All the errors generated by the individual attempts I posted below: https://pastebin.com/3RDNRnri
Fortunately, wine-10.2-2 is working.
http://bugs.winehq.org/show_bug.cgi?id=58421
--- Comment #5 from win.user tst1@mixbox.pl --- After upgrading to wine 10.11 this issue still persists.
Additionally, I discovered that creating a new clean winprefix under Wine 10.9 (and under Wine 10.11) consists of only 6 folders with a total of 3 files.
Now the following error message seems to be understandable, because in this new winprefix, in the directory ~/.wine/drive_c/windows/system32/, where files like .dll should be located, there are no files. ~~~ winecfg wine: created the configuration directory '~/.wine' 002c:err:seh:NtRaiseException Unhandled exception code c0000005 flags 0 addr 0x6fffffc0daff wine: could not load kernel32.dll, status c0000135 ~~~
(And creating a new clean winprefix under wine 10.2-2 consists of 157 folders with a total of 1767 files. And under this Wine version, everything works correctly.)
http://bugs.winehq.org/show_bug.cgi?id=58421
win.user tst1@mixbox.pl changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Meta Trader 4 does not |Since Wine 10.9 it in not |start |possible to run any program | |and create a new working | |wineprefix
http://bugs.winehq.org/show_bug.cgi?id=58421
--- Comment #6 from win.user tst1@mixbox.pl --- I created this bug report because of MetaTrader 4 (the only application I use under Wine).
Now, however, I see that: - the problem affects literally all programs under Wine, including those pre-installed like: winecfg, wineboot or notepad. None of them can be started, - in addition, since Wine 10.9, it is not possible to create a new and working clean wineprefix (there are only three files in this new folder, instead of about 1800 files).
This issue is similar as in the bug report: https://bugs.winehq.org/show_bug.cgi?id=58335 Like the author of this bug report, my computer does not support AVX. However, we differ in the Linux distribution. I use Manjaro Linux (based on ArchLinux), and the author of Bug 58335 uses Fedora. And there is no info about any problems with new wineprefix in Bug 58335.
I hope that the additional information will help you to diagnose the problem and fix it. In the meantime, I'm changing the title of this thread to be more adequate to this issue.