pwsafe still tries to link to libreadline.so.5

dante4d · 2009-07-11 23:34:28

Hello,

after update of libreadline, this happens to my pwsafe:
pwsafe: error while loading shared libraries: libreadline.so.5: cannot open shared object file: No such file or directory

I did:
$ ldd /usr/bin/pwsafe
linux-gate.so.1 => (0xb7f52000)
libSM.so.6 => /usr/lib/libSM.so.6 (0xb7f38000)
libICE.so.6 => /usr/lib/libICE.so.6 (0xb7f20000)
libXmu.so.6 => /usr/lib/libXmu.so.6 (0xb7f0a000)
libX11.so.6 => /usr/lib/libX11.so.6 (0xb7ded000)
libreadline.so.6 => /lib/libreadline.so.6 (0xb7db9000)
libncursesw.so.5 => /lib/libncursesw.so.5 (0xb7d6c000)
libcrypto.so.0.9.8 => /usr/lib/libcrypto.so.0.9.8 (0xb7c15000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb7b23000)
libm.so.6 => /lib/libm.so.6 (0xb7afd000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0xb7adf000)
libc.so.6 => /lib/libc.so.6 (0xb7999000)
libuuid.so.1 => /lib/libuuid.so.1 (0xb7995000)
libXt.so.6 => /usr/lib/libXt.so.6 (0xb7942000)
libXext.so.6 => /usr/lib/libXext.so.6 (0xb7933000)
libxcb.so.1 => /usr/lib/libxcb.so.1 (0xb791a000)
libdl.so.2 => /lib/libdl.so.2 (0xb7916000)
libz.so.1 => /usr/lib/libz.so.1 (0xb7902000)
/lib/ld-linux.so.2 (0xb7f53000)
libXau.so.6 => /usr/lib/libXau.so.6 (0xb78fe000)
libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xb78f9000)

Ok, come on! What's happening? I'm little puzzled. It says pwsafe links to libreadline.so.6 => /lib/libreadline.so.6 (0xb7db9000) but during startup it wants libreadline.so.5. How come?

I found Did the latest upgrade of libreadline just break lua? post. It says just what I did now. I symlinked /lib/libreadline.so.6 to /lib/libreadline.so.5. And what, pwsafe works again. I'm lost. What is going on? I don't like this solution, feels cheap and dirty to me!

I also tried to rebuild pwsafe from CVS using my own PKGBUILD (pwsafe-cvs 20090712-1). That doesn't prevent pwsafe from wanting libreadline.so.5 either.

Any help would be appreciated, before I waste lot of time googling for what's the reason of this, and it could be something simple. 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). I'm not sure if I should patch current pwsafe or write something new that would be "compatilbe" with old pwsafe...

Regards,
David

Allan · 2009-07-12 01:55:07

It is probably one of its dependencies needing the .5 version. You can try the "lddd" tool from the devtools package to try and track it down.

Edit: pwsafe does not have that many deps and all those should be rebuilt. Your system is fully up to date?

djszapi · 2009-07-12 08:44:15

I've seen this situation more times in the forum
The solution was everywhere the pacman -Syu, if it can't work pls downgrade libreadline package e.g.

dante4d · 2009-07-12 12:35:58

Hello,

thanks for the advices, so:

Allan wrote:

Edit: pwsafe does not have that many deps and all those should be rebuilt. Your system is fully up to date?

djszapi wrote:

I've seen this situation more times in the forum smile
The solution was everywhere the pacman -Syu, if it can't work pls downgrade libreadline package e.g.

I y -Syu (yaourt) on a regular basis, I did that just now... I did break my system too, not doing y -Syu somepackage, but just y -S somepackage that pulled readline 6... I had to boot live cd and downgrade to readline 5 and then do regular -Syu, as I was unable to use most of the CLI tools to fix it online .

Allan wrote:

It is probably one of its dependencies needing the .5 version. You can try the "lddd" tool from the devtools package to try and track it down.

I'm trying to play with lddd, I'm going for some tea . Ok, so it run and spit out some files in /tmp (here: ). Doesn't make much sense to me without deeper analysis. It doesn't look like any of those libs are connected to pwsafe's problem . I think I would honor from recursive ldd on pwsafe binary, i.e. it would run ldd on output of each lib from pwsafe ldd and so on... First google hit gave me Recursive ldd - Andreas Bernauer's personal blog. Output of that is:
$ ldd-rec.pl /usr/bin/pwsafe
ldd: warning: you do not have execution permission for `/usr/lib/libgcc_s.so.1'
/lib/ld-linux.so.2
/lib/libc.so.6
/lib/libdl.so.2
/lib/libm.so.6
/lib/libncursesw.so.5
/lib/libreadline.so.6
/lib/libuuid.so.1
/usr/lib/libICE.so.6
/usr/lib/libSM.so.6
/usr/lib/libX11.so.6
/usr/lib/libXau.so.6
/usr/lib/libXdmcp.so.6
/usr/lib/libXext.so.6
/usr/lib/libXmu.so.6
/usr/lib/libXt.so.6
/usr/lib/libcrypto.so.0.9.8
/usr/lib/libgcc_s.so.1
/usr/lib/libstdc++.so.6
/usr/lib/libxcb.so.1
/usr/lib/libz.so.1
It also gives me linkage to version 6. What the... I don't know if the script found all recursive dependencies though.

It says /lib/libreadline.so.6 everywhere, and if I symlink version 5, pwsafe works. I was expecting that by doing this, pwsafe would crash or something, but it looks like readline 6 can be substituted by readline 5 in some cases without any problems...

Maybe different question - how come nothing found dependency to readline 5 and pwsafe wants it? Maybe the googled script does miss something. I have to investigate some more...

Cheers

Last edited by dante4d (2025-10-18 21:48:08)

Allan · 2009-07-12 12:43:50

You seem to know, but I will give my standard warning: symlinking different sonames is bad...

Anyway, there seems to be nothing linked to libreadine.so.5 on your system. Also, I have no issues running pwsafe. No idea what is going on here...

dante4d · 2009-07-12 12:58:42

Allan wrote:

You seem to know, but I will give my standard warning: symlinking different sonames is bad...
Anyway, there seems to be nothing linked to libreadine.so.5 on your system. Also, I have no issues running pwsafe. No idea what is going on here...

Yes, I know that's some bad smell to symlink it...

Agreed, nothing seems to be linked, I'm confused...

I'm going to read about Linux linker, how it works and study how pwsafe gets assembled. Hopefully, I will find where is the problem at.

Anyway, thanks for the advices.

@Allan
So you too do use pwsafe? Are you happy with it? Because, I have some minor issues with it's usability (for example, I patched it to have colored output, but I can't upload diff to sourceforge...) and it's author seems to be AWOL... I was thinking for quite a long time about rewriting it. To separate libpwsafe and pwsafe CLI interface plus make gtk-tray-icon interface, similar to how for example parcellite, klipper or glipper work, but with pwsafe passwords. I also would like to have compatibility (chance to import) with KeepPass.

Last edited by dante4d (2009-07-12 16:52:12)

Allan · 2009-07-12 13:02:49

I don't use pwsafe. I just took it for a quick spin to see if I could find the issue. That was on i686 btw.

Arch Linux

#1 2009-07-11 23:34:28

pwsafe still tries to link to libreadline.so.5

#2 2009-07-12 01:55:07

Re: pwsafe still tries to link to libreadline.so.5

#3 2009-07-12 08:44:15

Re: pwsafe still tries to link to libreadline.so.5

#4 2009-07-12 12:35:58

Re: pwsafe still tries to link to libreadline.so.5

#5 2009-07-12 12:43:50

Re: pwsafe still tries to link to libreadline.so.5

#6 2009-07-12 12:58:42

Re: pwsafe still tries to link to libreadline.so.5

#7 2009-07-12 13:02:49

Re: pwsafe still tries to link to libreadline.so.5

Board footer