#Pwsafe linux update
#Pwsafe linux Patch

It doesn't look like any of those libs are connected to pwsafe's problem. Doesn't make much sense to me without deeper analysis. Ok, so it run and spit out some files in /tmp (here: ). I'm trying to play with lddd, I'm going for some tea. You can try the 'lddd' tool from the devtools package to try and track it down. It is probably one of its dependencies needing the.

#Pwsafe linux Patch

I'm not sure if I should patch current pwsafe or write something new that would be 'compatilbe' with old pwsafe. Also, as pwsafe looks dead now (unmantained for about two years), I'm thinking about rewriting it and adding some new features (like colored output). That doesn't prevent pwsafe from wanting libreadline.so.5 either.Īny help would be appreciated, before I waste lot of time googling for what's the reason of this, and it could be something simple. I also tried to rebuild pwsafe from CVS using my own PKGBUILD ( pwsafe-cvs 20090712-1). What is going on? I don't like this solution, feels cheap and dirty to me! I symlinked /lib/libreadline.so.6 to /lib/libreadline.so.5. I found Did the latest upgrade of libreadline just break lua? post. It says pwsafe links to libreadline.so.6 => /lib/libreadline.so.6 (0xb7db9000) but during startup it wants libreadline.so.5. Ok, come on! What's happening? I'm little puzzled. Pwsafe: error while loading shared libraries: libreadline.so.5: cannot open shared object file: No such file or directory

#Pwsafe linux update

After update of libreadline, this happens to my pwsafe: