http://bugs.winehq.org/show_bug.cgi?id=12369
Summary: MEGA program crashes on startup under wine Product: Wine Version: 0.9.58. Platform: Other URL: http://www.megasoftware.net/mega_linux.html OS/Version: other Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: robert.bradbury@gmail.com
Created an attachment (id=11863) --> (http://bugs.winehq.org/attachment.cgi?id=11863) Trace of running "wine /usr/local/bin/MEGA/MEGA4.exe"
There is a book "Phylogenetic Trees Made Easy", by "Barry G. Hall" which discusses the use of the MEGA4 program for phylogenetic (gene history) analysis. This program is "supposed" to run on Linux under Wine.
It crashes shortly after startup under Gentoo Linux (2.6.23-gentoo-r8) with current versions of wine (0.9.58 and 0.9.59). It displays the first program image (copyright, developer names, etc.) then crashes.
Attached is the console log. More expanded traces will follow. The developers of the program have been notified about the problem, but to date no response has been received.
http://bugs.winehq.org/show_bug.cgi?id=12369
--- Comment #1 from Robert Bradbury robert.bradbury@gmail.com 2008-04-05 07:33:44 --- Created an attachment (id=11864) --> (http://bugs.winehq.org/attachment.cgi?id=11864) Last 1000 lines of trace of MEGA4.exe with WINEDEBUG=relay
http://bugs.winehq.org/show_bug.cgi?id=12369
--- Comment #2 from Dmitry Timoshkov dmitry@codeweavers.com 2008-04-05 09:15:46 --- How did you install the application? How did it happen to appear under /usr/local/bin/MEGA/ ?
http://bugs.winehq.org/show_bug.cgi?id=12369
Robert Bradbury robert.bradbury@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |robert.bradbury@gmail.com
--- Comment #3 from Robert Bradbury robert.bradbury@gmail.com 2008-04-05 10:05:28 --- Dmitry, I downloaded the binary "package" from the MEGA web site which gives me a (MEGA-4-01.i386.rpm) file, used rpm2cpio to convert it to a .cpio.gz file and the extracted the cpio file as root from /). The files appear to be in the cpio archive as "./usr/local/bin/MEGA/...").
They claim to only run under RedHat, but that really shouldn't cause problems under Wine. I didn't install directly from the rpm because I'm unfamiliar with the switches for using rpm and there is no "rpm" database (if such is required) on a Gentoo system.
http://bugs.winehq.org/show_bug.cgi?id=12369
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|critical |normal
--- Comment #4 from Austin English austinenglish@gmail.com 2008-04-05 14:12:30 --- Not critical.
Have you tried using alien to convert the rpm file?
http://bugs.winehq.org/show_bug.cgi?id=12369
--- Comment #5 from Dmitry Timoshkov dmitry@codeweavers.com 2008-04-06 04:23:24 --- You either need to install the application properly under Wine, so that it gets installed under ~/.wine, or request support from the application developers not here.
http://bugs.winehq.org/show_bug.cgi?id=12369
--- Comment #6 from Robert Bradbury robert.bradbury@gmail.com 2008-04-06 08:10:41 --- Dmitry, your last statement IMO is complete caca. For wine to work properly, it is not necessary to install applications under the ~/.wine directory.
I have my old Windows XP C: drive (NTFS) partition mounted as /frodo/c. I create wrapper shell scripts that run both SOL.EXE and EXCEL.EXE from that drive by invoking them with something of the form:
$WINE $SOL or $WINE $EXCEL
where the shell variables are set to the proper UNIX paths for wine and the windows executable ON the old C: NTFS partition.
Now, it is sometimes necessary to make sure the application gets access to various DLL libraries (wine is very good about informing one regarding missing DLLs, e.g. msc42u.dll (which is required for running SkypeMate.exe). One can resolve these problems by either symlinking them from the old /frodo/c/WINDOWS directory into the $HOME/.wine/dosdevices/c:/windows directory, or copy them from the old WINDOWS directory to the wine windows directory if one feels like wasting disk space. One can also setup the WINEDLLPATH environment variable to point to various directories on the old Windows C drive, e.g. /frodo/c/Program\ Files/Microsoft\ Office-various-sub-directories-, if one doesn't want to copy or symlink the various DLL's from their install position on the Windows C: drive into the wine pseudo-windows drives.
If there was a problem with MEGA4.EXE accessing a DLL or file in /usr/local/bin/MEGA/... I would expect that it would inform me of such (trying to run the visual basic editor from Excel.exe generates a host of such errors). This is not the error I get trying to start MEGA4. The fact that the normal file access routines, when searching for DLL's, spew out a number of directories being scanned (and Excel, Word, etc.) find files that are located in sub-directories, suggests to me that the file locating aspects of wine work just fine. The fact that the MEGA4 program does start up and display the copyright window suggests that is is fine as well. The program fault appears to occur when it attempts to bring up the primary program window which has the menus that allow it to load gene sequences.
Now, the fact that MEGA is documented as working on RedHat under wine and the fact that the paths are *in* the distribution RPM as being under /usr/local/bin/MEGA (Do a "strings MEGA-4-01.i386.rpm | grep local") strongly suggests to me that it is *supposed* to be installed in /usr/local/bin and it is supposed to work from that location.
If you give me a good reason why it is supposed to be installed under ~/.wine and tell me how I am supposed to go about doing it (and whether it should be installed under ~/.wine/drive_c, ~/.wine/drive_c/Program Files, ~/.wine/dosdevices/c:/Program Files/ or some other location) I'll be happy to relocate or stick in a symbolic link to the MEGA directory. But from where I sit that doesn't seem to be the problem.
And I have pointed out the problem to both the developers and the book publisher and have yet to receive a response. My primary interest is in determining which version of wine MEGA once ran under as I have had experiences in the past where programs which once worked under wine seemed to stop working as it was upgraded.
http://bugs.winehq.org/show_bug.cgi?id=12369
--- Comment #7 from Dmitry Timoshkov dmitry@codeweavers.com 2008-04-06 23:53:45 --- (In reply to comment #6)
Dmitry, your last statement IMO is complete caca. For wine to work properly, it is not necessary to install applications under the ~/.wine directory. I have my old Windows XP C: drive (NTFS) partition mounted as /frodo/c. I create wrapper shell scripts that run both SOL.EXE and EXCEL.EXE from that drive by invoking them with something of the form: $WINE $SOL or $WINE $EXCEL where the shell variables are set to the proper UNIX paths for wine and the windows executable ON the old C: NTFS partition.
Although that might work for some application that setup is not supported through Wine bugzilla because there are a lot of potential problems with it: missing registry keys, lack of shared write memory mapping support, etc.
Now, the fact that MEGA is documented as working on RedHat under wine and the fact that the paths are *in* the distribution RPM as being under /usr/local/bin/MEGA (Do a "strings MEGA-4-01.i386.rpm | grep local") strongly suggests to me that it is *supposed* to be installed in /usr/local/bin and it is supposed to work from that location.
If it's distributed as RPM and supposed to be installed under /usr/local then presumably that setup has been tested by the program distributors, and in that case you should be able to receive support from them.
If you give me a good reason why it is supposed to be installed under ~/.wine and tell me how I am supposed to go about doing it (and whether it should be installed under ~/.wine/drive_c, ~/.wine/drive_c/Program Files, ~/.wine/dosdevices/c:/Program Files/ or some other location) I'll be happy to relocate or stick in a symbolic link to the MEGA directory. But from where I sit that doesn't seem to be the problem.
There should an install program bundled with your Windows application which should be ran to setup it.
http://bugs.winehq.org/show_bug.cgi?id=12369
--- Comment #8 from Robert Bradbury robert.bradbury@gmail.com 2008-04-07 07:50:32 --- Dimitry, scientists who write software for academic use which is given away for free rarely conform to Microsoft's extreme install/uninstall requirements. Such is the case here.
There are precisely two EXE files as part of the RPM file: MEGA4.exe and MozillaActiveXControl.exe
There is no "index.htm", start.exe or Autorun.inf file -- items one might expect for a typical Windows "install".
Now, perhaps of interest may be the errors: err:ole:CoGetClassObject class {1339b54c-3453-11d2-93b9-000000000000} not registered err:ole:create_server class {1339b54c-3453-11d2-93b9-000000000000} not registered err:ole:CoGetClassObject no class object {1339b54c-3453-11d2-93b9-000000000000} could be created for context 0x5 wine: Unhandled exception 0x0eedfade at address 0x0000:0x7edee15e (thread 0009), starting debugger...
Now, IMO wine should *not* be throwing "Unhandled exceptions". If an object is not registered or registerable, it should provide those errors and then cleanly exit.
I have run strace, looking primarily at the open()s which are taking place and there appear to be no problems locating the files it is seeking.
Furthermore, some help (from wine) in determining what those "classes" mean or how to register them would be helpful to non-windows gurus.
The file distributed with the RPM package: .../part_i__getting_started/installing_mega/rh_system_requirements.htm documents that on the MAC, one should be using VirtualPC while under Linux one should be using VMWare (which I do not have installed).
The book on the other hand suggests that on the MAC one should use parallels, which I tried under Linux a while ago but did not purchase a license for.
Regarding MEGA under Linux, the book says, "The MEGA website says that several users report using MEGA successfully under Wine." But the author has no direct experience with wine and makes no suggestions as to how it should be installed.
http://bugs.winehq.org/show_bug.cgi?id=12369
--- Comment #9 from Robert Bradbury robert.bradbury@gmail.com 2008-04-07 07:53:37 --- Created an attachment (id=11917) --> (http://bugs.winehq.org/attachment.cgi?id=11917) Complete list of the contents of the MEGA-4 rpm file
This is a complete listing of the .rpm file distributed for Linux. This is directly from the RPM, not from the CPIO extract of the RPM.
If anyone can tell me how one does a "Windows Install" under ~/.wine using this I would certainly appreciate it.
http://bugs.winehq.org/show_bug.cgi?id=12369
--- Comment #10 from Dmitry Timoshkov dmitry@codeweavers.com 2008-04-07 08:38:04 --- 1339b54c-3453-11d2-93b9-000000000000 is "Mozilla Web Browser". Have you tried to install /usr/local/bin/MEGA/Installers/MozillaActiveXControl.exe ?
http://bugs.winehq.org/show_bug.cgi?id=12369
--- Comment #11 from Robert Bradbury robert.bradbury@gmail.com 2008-04-07 09:48:12 --- Indeed, that was going to be my next step. And in fact it does appear to resolve at least the startup problem.
To make mega startup properly under wine, one must first run: MozillaActiveXControl.exe which extracts and installs a number of files in: ~/.wine/dosdevices/c:/Program Files/Mozilla ActiveX Control v1.7.12 and may even fiddle with the registry.
After that, MEGA4.exe will start and bring up the standard program window documented in the book. If I can successfully load and perform the tests the book outlines I will consider this bug closed.
I have yet to find anywhere that documents that this is the proper install process for using MEGA under a windows emulator.
http://bugs.winehq.org/show_bug.cgi?id=12369
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #12 from Dmitry Timoshkov dmitry@codeweavers.com 2008-04-07 09:55:40 --- Since the Summary of this bug indicates "startup" this bug is resolved then.
Open a separate bug for other problems if any.
http://bugs.winehq.org/show_bug.cgi?id=12369
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #13 from Dmitry Timoshkov dmitry@codeweavers.com 2008-04-07 09:55:53 --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=12369
--- Comment #14 from Austin English austinenglish@gmail.com 2008-04-07 12:46:40 --- Have you tried installing the windows version using wine? The Linux version may have been tweaked by the applications developers making it harder to support.