Bug 27278 - Unable to use hugin due to undefined symbol
Summary: Unable to use hugin due to undefined symbol
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal normal
Target Milestone: Mageia 7
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2020-09-15 02:06 CEST by Bruno Cornec
Modified: 2020-09-19 21:37 CEST (History)
4 users (show)

See Also:
Source RPM: hugin-2019.0.0-2.mga7.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Bruno Cornec 2020-09-15 02:06:47 CEST 
Description of problem:

I'm unable to launch hugin anymore:
hugin: symbol lookup error: /usr/lib64/hugin/libhuginbase.so.0.0: undefined symbol: __glewGetObjectParameterivARB


Version-Release number of selected component (if applicable):
hugin-2019.0.0-2.mga7.src.rpm

How reproducible:
Each time, but used to work till recently. I'm not seeing an obvious new package installed that would produce this result :-(
Seems to be linked to libglew, but mine is old:

Name        : lib64glew2.1
Install Date: mer. 27 nov. 2019 02:21:35 CET

Name        : hugin
Install Date: mer. 27 nov. 2019 02:22:50 CET

So something else changed that prevent these binaries to work
I detected it through digikam which ddn't allow me to do a panorama as most of the needed tool coming from hugin exhibit the same issue:
$ cpfind
cpfind: symbol lookup error: /usr/lib64/hugin/libhuginbase.so.0.0: undefined symbol: __glewGetObjectParameterivARB
Comment 1 Aurelien Oudelet 2020-09-16 20:56:36 CEST 
Hi, thanks for reporting this,

Assigning to all packagers as there is no registered one.
(Packagers: Please set the status to 'assigned' if you are working on it)

Keywords: (none) => Triaged
Target Milestone: --- => Mageia 7

Comment 2 Aurelien Oudelet 2020-09-16 21:00:13 CEST 
Added recent commiters.

CC: (none) => geiger.david68210, jani.valimaa, ouaurelien

Aurelien Oudelet 2020-09-17 20:01:23 CEST

Assignee: bugsquad => pkg-bugs

Comment 3 Lewis Smith 2020-09-17 22:07:24 CEST 
> used to work till recently.
> I'm not seeing an obvious new package installed that would produce this result
Are you able to say what date it stopped working? If you can, then
 $ rpm -qa --last | less
would enable you to see what updates were done on that date, and might give a clue.

On my up-to-date Mageia 7 system, I see no updates to hugin or lib64glew2.1 since what looks like the post install system update, in my case 29 May 2019 - older than yours.
 hugin-2019.0.0-2.mga7
 lib64glew2.1-2.1.0-4.mga7
and I have no other 'glew' package installed.

I can launch 'hugin' from menu; or command line, where it shows a lot of failure messages but seems to stand up. 'cpfind' on its own complains "No project file given", but does not give the error you show.

CC: (none) => lewyssmith

Comment 4 Bruno Cornec 2020-09-18 01:07:53 CEST 
Due to an electricity shutdown today, I rebooted my system. And after that, I don't have the issue anymore. I really don't like it to not being able to explain what happened. 

As I do nightly update that could be lined to any of the packages that were updated between the last time it works (for me the 5th of septembre, last pano I made with hugin) and now.

Here is the list of packages updated in between, but I don't see the rationale, and now I can't reproduce, so will close this BR, sorry.

hpmyroom-12.1.1.0242-1.x86_64                 mer. 16 sept. 2020 18:11:53 CEST
phpmyadmin-4.9.5-2.mga7.noarch                mer. 16 sept. 2020 03:29:09 CEST
lib64zmq5-4.3.3-1.1.mga7.x86_64               mer. 16 sept. 2020 03:29:09 CEST
tellico2html-0.9.8-1.mga7.noarch              mer. 16 sept. 2020 00:35:06 CEST
perl-Devel-SimpleTrace-0.80.0-8.mga7.noarch   mar. 15 sept. 2020 19:33:00 CEST
tellico-3.3.3-1.mga7.x86_64                   lun. 14 sept. 2020 11:03:40 CEST
libllvm8.0-8.0.0-1.1.mga7.i586                sam. 12 sept. 2020 03:29:16 CEST
flash-player-plugin-32.0.0.433-1.mga7.nonfree.x86_64 sam. 12 sept. 2020 03:29:14 CEST
lib64llvm-devel-8.0.0-1.1.mga7.x86_64         sam. 12 sept. 2020 03:29:13 CEST
llvm-8.0.0-1.1.mga7.x86_64                    sam. 12 sept. 2020 03:29:12 CEST
lib64llvm8.0-8.0.0-1.1.mga7.x86_64            sam. 12 sept. 2020 03:29:11 CEST
xfsprogs-5.8.0-1.mga7.x86_64                  mar. 08 sept. 2020 03:29:12 CEST
python2-rsa-4.0-1.1.mga7.noarch               mar. 08 sept. 2020 03:29:12 CEST
lib64pq5-11.9-1.mga7.x86_64                   mar. 08 sept. 2020 03:29:12 CEST
postgresql9.6-devel-9.6.19-1.mga7.x86_64      mar. 08 sept. 2020 03:29:11 CEST
postgresql9.6-9.6.19-1.mga7.x86_64            mar. 08 sept. 2020 03:29:11 CEST
lib64xfs-devel-5.8.0-1.mga7.x86_64            mar. 08 sept. 2020 03:29:11 CEST
lib64xfs1-5.8.0-1.mga7.x86_64                 mar. 08 sept. 2020 03:29:11 CEST
lib64ecpg9.6_6-9.6.19-1.mga7.x86_64           mar. 08 sept. 2020 03:29:11 CEST
lib64pq5.9-9.6.19-1.mga7.x86_64               mar. 08 sept. 2020 03:29:10 CEST


Now I have another issue with the nvidia setup, that I'll put in another thread on the dev ML and that one *may* be related.
Comment 5 Lewis Smith 2020-09-19 21:37:01 CEST 
(In reply to Bruno Cornec from comment #4)
> Due to an electricity shutdown today, I rebooted my system. And after that,
> I don't have the issue anymore.
> now I can't reproduce, so will close this BR, sorry
Thank you Bruno for this. It will have to be one of those numerous unexplained happenings.

Resolution: (none) => WORKSFORME
Assignee: pkg-bugs => bugsquad
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.