openSUSE 13.1 hugin - libhuginbase.so.0.0: cannot open shared object

English Applications
#1

I upgraded 12.3 ==> 13.1
Since then hugin doesn’t work anymore (and Digikam has problems with these parts, too).

Starting from command-line gives me:

xxxxxx@DellPC:/home/xxxxxxx> hugin --version
hugin: error while loading shared libraries: libhuginbase.so.0.0: cannot open shared object file: No such file or directory

I tried to re-install hugin (and finally digikam) but didn’t help.

One idea is that changes in ld.so.conf might have caused the problem. So here my ld.so.conf:

xxxxxxx@DellPC:/etc> cat ld.so.conf
/usr/local/lib64
/usr/local/lib
include /etc/ld.so.conf.d/*.conf

/lib64, /lib, /usr/lib64 and /usr/lib gets added

automatically by ldconfig after parsing this file.

So, they do not need to be listed.

======================================

Any idea?
Does anybody have similar problems after upgrade 12.3 ==> 13.1 final?

Tx

#2

Please post output of

rpm -qa | grep hugin
#3

On 2013-11-23 13:46, fiesta88 wrote:
>
> I upgraded 12.3 ==> 13.1

Which type of upgrade? Online upgrade (zypper dup) or offline upgrade (DVD)?

Online upgrade
method
Offline upgrade
method
Chapter 16. Upgrading the System and System Changes
openSUSE 12.3 Release Notes
openSUSE 13.1 Release Notes

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

#4

This is a bug in the hugin package.

See here for a fix: http://forums.opensuse.org/english/get-technical-help-here/applications/492323-opensuse-13-1-digikam-tools-missing.html#post2601671

#5

And actually, this was already reported a while ago (and fixed in Factory, but not 13.1):
https://bugzilla.novell.com/show_bug.cgi?id=846944

#6

Hi wolfi 323!

your answer

https://forums.opensuse.org/english/get-technical-help-here/applications/492323-opensuse-13-1-digikam-tools-missing.html

solved this one, too! :wink:

Tx

#7

Of course. It is the same problem. Those tools that digikam uses/needs do come from the hugin package and use libhuginbase.

I’ll mention it here as well, maybe someone else reads this thread:
A fixed package has already been created and should be released as online update soon (next week maybe?).

I just tried it and it works fine.