[SOLVED] geeqie

przemo · 08-11-2016, 03:43 PM

problem with running geeqie

Code:

geeqie 
geeqie: error while loading shared libraries: libjbig.so.0: cannot open shared object file: No such file or directory

STDOUBT · 08-11-2016, 03:58 PM

That's weird. Did you install it separately on a non-Full Slackware installation?
What type of install did you do? Are you still on 14.1? Need more info.

przemo · 08-11-2016, 04:12 PM

i`ve upgraded to 14.2 from 14.1

bassmadrigal · 08-11-2016, 04:32 PM

Out of curiosity, what package do you have installed for it?

Code:

jbhansen@febtober:~$ ls -la /var/log/packages/geeqie*
-rw-r--r-- 1 root root 8631 Jul  2 14:51 /var/log/packages/geeqie-1.3-x86_64-1

Either way, I would reinstall that package. I can run it on my 14.2 installation without having libjbig.so.0 on the filesystem.

Code:

slackpkg reinstall geeqie

przemo · 08-11-2016, 04:35 PM

Code:

ls -la /var/log/packages/geeqie*
-rw-r--r-- 1 root root 8602 Aug 11 21:28 /var/log/packages/geeqie-1.3-x86_64-1

solved

https://www.rpmfind.net/linux/rpm2ht...%29%2864bit%29

ponce · 08-11-2016, 05:16 PM

you probably have some library to which geeqie links to, also indirectly, that, in turns, links to libjbig.so.0.

to find it you can use objdump

Code:

$ objdump -x /usr/bin/geeqie | grep NEEDED
  NEEDED               libgtk-3.so.0
  NEEDED               libgdk-3.so.0
  NEEDED               libpangocairo-1.0.so.0
  NEEDED               libpango-1.0.so.0
  NEEDED               libatk-1.0.so.0
  NEEDED               libcairo-gobject.so.2
  NEEDED               libcairo.so.2
  NEEDED               libgdk_pixbuf-2.0.so.0
  NEEDED               libgio-2.0.so.0
  NEEDED               libgobject-2.0.so.0
  NEEDED               libglib-2.0.so.0
  NEEDED               libgthread-2.0.so.0
  NEEDED               libjpeg.so.62
  NEEDED               libtiff.so.5
  NEEDED               liblcms2.so.2
  NEEDED               libexiv2.so.14
  NEEDED               libstdc++.so.6
  NEEDED               libm.so.6
  NEEDED               libgcc_s.so.1
  NEEDED               libpthread.so.0
  NEEDED               libc.so.6

use objdump on the resulting libraries, and so on until you find what links to libjbig.so.0.

when you find it check which package contains it (grepping /var/log/packages/*) and you most probably will understand why this is happening.

Richard Cranium · 08-11-2016, 06:03 PM

Quote:

Originally Posted by przemo

Code:

ls -la /var/log/packages/geeqie*
-rw-r--r-- 1 root root 8602 Aug 11 21:28 /var/log/packages/geeqie-1.3-x86_64-1

solved

https://www.rpmfind.net/linux/rpm2ht...%29%2864bit%29

How did that solve your problem?

dugan · 08-12-2016, 04:12 PM

Quote:

Originally Posted by przemo

solved

https://www.rpmfind.net/linux/rpm2ht...%29%2864bit%29

No wonder you're having problems like this.

przemo · 08-12-2016, 04:31 PM

re: @dougan
have you better solution???
i know this one wasn`t clean but at least it works.

bassmadrigal · 08-12-2016, 05:20 PM

Quote:

Originally Posted by przemo

re: @dougan
have you better solution???
i know this one wasn`t clean but at least it works.

The best solution would've been to follow ponce's advice and find what is linking to libjbig. If you've installed other programs using rpmfind or another packaging repo, that is probably your issue. You would need to install any dependencies that the rpm was compiled against to prevent other linking issues like this.

But if you at least wanted a better solution than what you did, I would've probably compiled jbigkit from SBo (although, I would've done ponce's route, as that helps you find the installed program that is causing you problems... if it's one you need, then you can recompile it with the dependencies on your computer).

https://slackbuilds.org/repository/1...aries/jbigkit/

przemo · 08-12-2016, 05:52 PM

it looks like i will have to spend whole night to find that package.

bassmadrigal · 08-12-2016, 06:08 PM

You could save the following as a file and then run it. It only checks one level, and has the location hardcoded to /usr/lib64/, but it might be enough to find what is causing your problem (otherwise, I would need to try and find an easy way to loop it further).

Code:

for i in $(objdump -x /usr/bin/geeqie | grep NEEDED | awk '{print $2}'); do
  echo ===== For $i =====
  objdump -x /usr/lib64/$i | grep NEEDED
done

If you save it as something like objdump-check, you could then run sh objdump-check and scroll through the results to see if it finds anything.

NOTE: I tried using a grep on the output of objdump-check, but it broke it (not sure why), but you can redirect the output to a file and then search the file for jbig.