Closed kriswema closed 11 years ago
I've never seen THAT before. Can you post the contents of your /tmp/ynab4_install.log (either directly here or link to pastbin or something)?
Also, is that error showing up during the INSTALL or when you try to run it after the install is done?
It shows up after the install, probably when it's trying to start YNAB. Which is confusing, since I saw an adobeair.dll or something along those line get installed..
Fri Jun 7 15:26:35 2013: BEGIN INSTALLATION OF '/home/orangensaft/Downloads/YNAB 4_4.3.75_Setup.exe'
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
fixme:storage:create_storagefile Storage share mode not implemented.
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
fixme:iphlpapi:NotifyAddrChange (Handle 0xebe92c, overlapped 0xebe910): stub
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
wine: configuration in '/home/orangensaft/.wine_YNAB4' has been updated.
fixme:process:SetProcessDEPPolicy (1): stub
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
fixme:process:SetProcessDEPPolicy (1): stub
fixme:win:DisableProcessWindowsGhosting : stub
fixme:msg:ChangeWindowMessageFilter c059 00000001
fixme:msg:ChangeWindowMessageFilter c059 00000001
fixme:msg:ChangeWindowMessageFilter c059 00000001
fixme:msg:ChangeWindowMessageFilter c059 00000001
fixme:shell:SHAutoComplete stub
fixme:win:WINNLSEnableIME hwnd 0x100b2 enable 0: stub!
fixme:win:WINNLSEnableIME hwnd 0x100b2 enable -1: stub!
fixme:win:WINNLSEnableIME hwnd 0x100b2 enable 0: stub!
fixme:win:WINNLSEnableIME hwnd 0x100b2 enable -1: stub!
fixme:win:WINNLSEnableIME hwnd 0x100b0 enable 0: stub!
fixme:sfc:SfcIsFileProtected ((nil), L"C:\\Program Files\\YNAB 4\\unins000.exe") stub
fixme:win:WINNLSEnableIME hwnd 0x100b0 enable -1: stub!
err:module:import_dll Library mscms.dll (which is needed by L"C:\\Program Files\\YNAB 4\\Adobe AIR\\Versions\\1.0\\Adobe AIR.dll") not found
Fri Jun 7 15:26:51 2013: END INSTALLATION OF '/home/orangensaft/Downloads/YNAB 4_4.3.75_Setup.exe'
I've tried installing YNAB4 manually before this, may that have caused these problems?
Ah, yes, if this is a reinstall or an upgrade over the top of an existing install, I've seen odd problems crop up. Your log looks great, so nothing obvious there.
If you are storing your budget in Dropbox, it should be safe to do a reinstall from scratch. From a command prompt: mv .wine_YNAB4 .wine_YNAB4.old
Also, if you manually installed in the past, you may have installed it into the default WINE location. As long as you don't have any other applications installed using WINE, you can do this: mv .wine .wine.old
Then run the install script again. If everything works, you can delete the ".old" directories. Maybe I should add an option to do a clean install to the script...
I just tried it again after renaming the .wine and .wine_YNAB4 folders, same result.
I forgot to ask, what Distro/Wine versions are you running? I just reinstalled on Mint 13 (and I've done Ubuntu 12.04 and 12.10 recently) with the same version of YNAB above with no issues. Definitely an interesting problem here.
Debian Wheezy wine (1.4.1-4)
I haven't tried the installer on anything that recent so I suppose I could give that a shot in a VM. You could try WINE 1.5 (which I've been using a fair amount) but I don't see why 1.4 would be failing.
I just installed Wheezy in a VM and it fails for me there. So from here I can play around and see if I can figure out what's wrong.
Thank you, it means a lot to me, since I'm really not that great with Wine. If you need me to test something, please tell me. :)
Solved!! It looks like one of the libraries that AIR requires isn't installed by default on Debian (I found articles going back years, so this doesn't seem to be new to Wheezy). The package changed names fairly recently though, so on Wheezy the fix is to run this as root:
apt-get install libwine-cms:i386
Enjoy! Oh, and please confirm if this fixes your issue so I can close this report. Thanks!
Yes, that works perfectly. Thank you so very much! :)
Just on a side note, is it possible to check whether a package is installed with Perl? I don't know it at all, so I was just wondering.
I presume you want to know if the script could check this for you. Yes, it could be expand to do more checking along those lines, but that gets into distro-specific and WINE-specific issues. On Debian-based distros you can call something like:
dpkg-query --list libwine-cms:i386
The output is easily parsed. Unfortunately that doesn't work on RPM distros. To make matters more compilcated, my Mint and Ubuntu boxes don't even have any libwine packages, and on WINE 1.5 on Debian may not need this package. Linux is awesome, but the ecosystem sure is complicated...
For those on 64-bit ArchLinux getting this error. Installing lib32-cms2
instead of lib32-cms
is what solved it for me.
As of today: the package is lib32-lcms2
, i guess that was a typo from @adampetrovic
@PaBLoX-CL yep you're correct. Remember to enable to multilib repository in pacman.conf if you are on ArchLinux!
Hej, after executing the script I'm getting this error. I don't think it's supposed to be this way.![fullscreen_201306071529_terminal](https://f.cloud.github.com/assets/2233810/623934/e29e82c2-cf76-11e2-87dc-385f4fd63b44.png)