Page 1 of 2

Application failed to initialize

Posted: Thu Apr 09, 2009 2:12 pm
by Kurtnoise
Hi,

I got a popup error message during loading: Application failed to initialize

What's wrong ?

Re: Application failed to initialize

Posted: Fri Apr 10, 2009 7:29 am
by mike admin
Did you install binary package? Can you run makemkvcon? What is the output of "ldd /usr/bin/makemkvcon" ?

Re: Application failed to initialize

Posted: Mon Apr 13, 2009 8:41 am
by rgeorge
I have a similar problem, having built 1.4 as per http://www.makemkv.com/forum2/viewtopic.php?f=3&t=224 (but for Fedora 10 x86_64) and running makemkv I get /usr/bin/makemkvcon: /lib64/libcrypto.so.0.9.8: no version information available (required by /usr/bin/makemkvcon)

running ldd on makemkvcon (libcrypto.so.0.9.8g is being used by symlink) gives:
ldd /usr/bin/makemkvcon
/usr/bin/makemkvcon: /lib64/libcrypto.so.0.9.8: no version information available (required by /usr/bin/makemkvcon)
linux-vdso.so.1 => (0x00007fff7fdff000)
libmakemkv.so.0 => /usr/lib/libmakemkv.so.0 (0x00007f8977975000)
libdriveio.so.0 => /usr/lib/libdriveio.so.0 (0x00007f897776f000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00000036f4e00000)
libcrypto.so.0.9.8 => /lib64/libcrypto.so.0.9.8 (0x0000003702800000)
libc.so.6 => /lib64/libc.so.6 (0x00000036f4200000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00000036ff800000)
librt.so.1 => /lib64/librt.so.1 (0x00000036f5e00000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00000036ff000000)
/lib64/ld-linux-x86-64.so.2 (0x00000036f3e00000)
libdl.so.2 => /lib64/libdl.so.2 (0x00000036f4600000)
libz.so.1 => /lib64/libz.so.1 (0x00000036f5200000)
libm.so.6 => /lib64/libm.so.6 (0x00000036f4a00000)

Thanks for your time.

Re: Application failed to initialize

Posted: Mon Apr 13, 2009 9:40 am
by rgeorge
running ldd -v /usr/bin/makemkvcon
gives
.
.
.
Version information:
/usr/bin/makemkvcon:
librt.so.1 (GLIBC_2.2.5) => /lib64/librt.so.1
libcrypto.so.0.9.8 (OPENSSL_0.9.8) => not found
libpthread.so.0 (GLIBC_2.3.2) => /lib64/libpthread.so.0
libpthread.so.0 (GLIBC_2.2.5) => /lib64/libpthread.so.0
libc.so.6 (GLIBC_2.2.5) => /lib64/libc.so.6
libstdc++.so.6 (GLIBCXX_3.4) => /usr/lib64/libstdc++.so.6
libstdc++.so.6 (CXXABI_1.3) => /usr/lib64/libstdc++.so.6
.
.
.

the OPENSSL_0.9.8 not found is interesting given that /lib64/libssl.so.0.9.8g exists
and I've created symlinks to it of /lib64/libssl.so.0.9.8 and /lib64/libssl.so for good measure.

Re: Application failed to initialize

Posted: Tue Apr 14, 2009 7:33 am
by mike admin
Thanks for the info, we'll investigate.

Re: Application failed to initialize

Posted: Fri Apr 17, 2009 5:31 am
by NameLessJedi
Hi!
I've compiled MakeMKV and have the same issue. Strangely enough ldd out/makemkv does not show libmakemkv or libdriveio. I'm using Debina Sid/Unstable amd64
out dir contains this files:

-rw-r--r-- 1 nlj nlj 28032 2009-04-17 07:08 libdriveio.so.0
-rwxr-xr-x 1 nlj nlj 39037 2009-04-17 07:08 libdriveio.so.0.full
-rw-r--r-- 1 nlj nlj 618800 2009-04-17 07:09 libmakemkv.so.0
-rwxr-xr-x 1 nlj nlj 904514 2009-04-17 07:09 libmakemkv.so.0.full
-rwxr-xr-x 1 nlj nlj 355680 2009-04-17 07:09 makemkv
-rwxr-xr-x 1 nlj nlj 404477 2009-04-17 07:09 makemkv.full

Compilation went without any errors or even warnings.

Two other questions:
Have you considered using some sort of autoconfig tools (like configure and all that stuff)?
I see that you included a libmatroska (0.8.0 while I have 0.8.1 installed from .deb) and libebml sources. Wouldn't it be better to use system installed files and eventually link to them.

Re: Application failed to initialize

Posted: Mon Apr 20, 2009 4:34 am
by mike admin
NameLessJedi wrote:Hi!
I've compiled MakeMKV and have the same issue. Strangely enough ldd out/makemkv does not show libmakemkv or libdriveio.
I see where confusion comes from. makemkv is jut a GUI for a console program named makemkvcon. It is installed from binary package andis not open source. You must install both packages for MakeMKV to work. Make sure that "ldd /usr/bin/makemkvcon" works.
NameLessJedi wrote: Have you considered using some sort of autoconfig tools (like configure and all that stuff)?
There is no need for that for now.
NameLessJedi wrote: I see that you included a libmatroska (0.8.0 while I have 0.8.1 installed from .deb) and libebml sources. Wouldn't it be better to use system installed files and eventually link to them.
As I remember we've made some changes to these libraries so default system libraries will not provide necessary functionality.

Re: Application failed to initialize

Posted: Mon Apr 20, 2009 11:59 am
by NameLessJedi
mike admin wrote: I see where confusion comes from. makemkv is jut a GUI for a console program named makemkvcon. It is installed from binary package andis not open source. You must install both packages for MakeMKV to work. Make sure that "ldd /usr/bin/makemkvcon" works.
OK. My fault. Was too excited to read carefully announcement =o))
mike admin wrote:
NameLessJedi wrote: Have you considered using some sort of autoconfig tools (like configure and all that stuff)?
There is no need for that for now.
Well... It depends. In a thread around someone is asking for /opt as default instalation path. Tho I don't mind /opt, I don't like /usr/bin & /usr/lib as it pollutes systems dirs most of the time controlled by packaging system (like deb or rpm). It would be nice if it allowed installation path to be chosen at the build stage (either as some define for Makefile or some ./configure-type build system). Of course this is just kind request that you can easily trash =o)))) but if you are considering things like that it's better to that from start than fight with this later (I work as a sysadm so this side of me is quite strong even on private systems like laptops)
mike admin wrote:
NameLessJedi wrote: I see that you included a libmatroska (0.8.0 while I have 0.8.1 installed from .deb) and libebml sources. Wouldn't it be better to use system installed files and eventually link to them.
As I remember we've made some changes to these libraries so default system libraries will not provide necessary functionality.
=o) That explains it well. Have you considered sending patches upstream?

Re: Application failed to initialize

Posted: Mon Apr 20, 2009 1:46 pm
by NameLessJedi
Just to let you all know:
Installing makemkv_v1.4.1_beta_bin.tar.gz made the error from thread's title disappear =o)
Of course there is no neeed to install binaries from above tgz in /usr/bin. They just need to be in $PATH.
Thanks again for effort to bring this app to Linux =o)

Re: Application failed to initialize

Posted: Thu Apr 23, 2009 9:41 am
by mike admin
NameLessJedi wrote:Just to let you all know:
Installing makemkv_v1.4.1_beta_bin.tar.gz made the error from thread's title disappear =o)
Of course there is no neeed to install binaries from above tgz in /usr/bin. They just need to be in $PATH.
Thanks again for effort to bring this app to Linux =o)
Good to hear. Next version should have openssl incompatibility corrected.

Re: Application failed to initialize

Posted: Fri May 01, 2009 6:26 pm
by mike admin
rgeorge wrote:
the OPENSSL_0.9.8 not found is interesting given that /lib64/libssl.so.0.9.8g exists
and I've created symlinks to it of /lib64/libssl.so.0.9.8 and /lib64/libssl.so for good measure.
This is corrected in 1.4.2

Re: Application failed to initialize

Posted: Sat Jan 30, 2010 1:48 pm
by orobertg
Received the "Application failed to initialize" error message when attempting to run the "/usr/bin/makemkv" :(

The problem seems to be that I only extracted and installed the first file on the linux makemkv download page called "http://www.makemkv.com/download/makemkv ... bin.tar.gz":

The solution was to extract and install the "http://www.makemkv.com/download/makemkv ... oss.tar.gz" file as well. Only after I did this was I able to run the application correctly.

Many thanks for the software, happy to see a version for linux. :D

The Linux download page is here: http://www.makemkv.com/forum2/viewtopic.php?f=3&t=224

Re: Application failed to initialize

Posted: Wed Jun 15, 2011 7:20 pm
by vidsquibber
Sal,

I run a firewall in Ubuntu and I feel like it is pretty necessary when working in makemkv or any kind of youtube to mp3 converter. I have been playing around with also protecting the system by adding files to a cloud server that need a bit more protection. I am at three layers of security at the moment and am trying to find a way to add a fourth. If you all have any good recommendations I am more than willing to listen up.

Re: Application failed to initialize

Posted: Mon Sep 05, 2011 8:37 am
by Jugin
Dear All,
I am in a big problem. After some times, my system stop responding to
the applications.
I got the message.
THE application failed to initialize properly(0XC0000142).Click on OK
to terminate the application
in nearly every application(still I found it in all .EXE files).
Apart from it, When I try to open a webpage, to load complete web page.
I have to refresh the page many times. I tried everything, I got only
one problem. iKernel.dll i.e. PROXY-OSS installed on my system.
Operating System: WINDOWS 2000 SERVER SP4.
Please help me out with this problem.
I also got the message "Application popup: Explorer.EXE - Application
Error : The instruction at "0x35f77d5a" referenced memory at
"0x000000e4". The memory could not be "read".

Click on OK to terminate the program
Click on CANCEL to debug the program "

Thanks and regards

Re: Application failed to initialize

Posted: Tue Nov 22, 2011 10:37 pm
by kugel
I had the "Application failed to initialize" problem. ldd showed the libraries were OK in both makemkvcon and makemkv. makemkvcon didn't fail abruptly.

What happened: I'd altered the makefile to install in /usr/local/bin rather than /usr/bin.
Somehow makemkvcon still got installed in /usr/bin. However it happened, it looks like the "Application failed to initialize" problem was that makemkvcon was in a different directory than makemkv:
1. When I copied makemkv to /usr/bin, it worked.
2. When I copied makemkvcon to /usr/local/bin, and then ran /usr/local/bin/makemkv, /usr/local/bin/makemkv now worked.
So I suspect a relative path is hard-coded into makemkv.

So if you've modified the Makefile, and are getting this error, check to see if makemkv and makemkvcon are in the same directory.