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.