digikam fails to launch after current update

ilgazcl · 2021-05-06T08:05:25.000Z

Hello

I noticed today’s update included some of its shared libraries and now when I try to launch digikam, it fails with

digikam
capi::version: 0.6.0
QCommandLineParser: already having an option named “h”
QCommandLineParser: already having an option named “help-all”
QCommandLineParser: already having an option named “v”
digikam: symbol lookup error: /usr/lib64/libdigikamgui.so.7.2.0: undefined symbol: _ZN2cv3dnn14dnn4_v202011173NetC1Ev

opensuseinmanila · 2021-05-06T09:11:32.000Z

I experienced exactly the same here. Looks like bug.

tannington · 2021-05-06T10:01:07.000Z

Also able to confirm… bug reported:

https://bugzilla.opensuse.org/show_bug.cgi?id=1185700

tannington · 2021-05-06T12:16:12.000Z

Just as a follow up…

A temporary “fix” which will get digikam working again is to install a prior build from:

https://download.opensuse.org/history/20210503/tumbleweed/repo/oss/x86_64/

tannington · 2021-05-06T13:46:00.000Z

As a further follow up…

Snapshot 20210504, which included an update to libopencv* has solved this issue.

karlmistelberger · 2021-05-06T15:09:43.000Z

tannington:

As a further follow up…

Snapshot 20210504, which included an update to libopencv* has solved this issue.

I have upgraded to 20210504, but alas: digikam: symbol lookup error: /usr/lib64/libdigikamgui.so.7.2.0: undefined symbol: _ZN2cv3dnn14dnn4_v202011173NetC1Ev

**erlangen:~ #** zypper se -is libopencv   
Loading repository data... 
Reading installed packages... 

S | Name                   | Type    | Version   | Arch   | Repository 
--+------------------------+---------+-----------+--------+------------------------ 
i | libopencv4_5           | package | 4.5.2-1.1 | x86_64 | openSUSE-Tumbleweed-Oss 
i | libopencv_imgcodecs4_5 | package | 4.5.2-1.1 | x86_64 | openSUSE-Tumbleweed-Oss 
i | libopencv_videoio4_5   | package | 4.5.2-1.1 | x86_64 | openSUSE-Tumbleweed-Oss 
i | libopencv_ximgproc4_5  | package | 4.5.2-1.1 | x86_64 | openSUSE-Tumbleweed-Oss 
**erlangen:~ #**

Budgie2 · 2021-05-06T15:12:10.000Z

tannington:

As a further follow up…

Snapshot 20210504, which included an update to libopencv* has solved this issue.

Hi Paul,
Not here it doesn’t. I was using digiKam yesterday and all was well. Just did s zypper dup today and no digiKam.

Being a simple soul I could,t work out what I needed to revert and found the Tumbleweed snapshots - usage notes.
Thought I would give it a try.

Budgie2 · 2021-05-06T15:27:56.000Z

Budgie2:

Hi Paul,
Not here it doesn’t. I was using digiKam yesterday and all was well. Just did s zypper dup today and no digiKam.

Being a simple soul I could,t work out what I needed to revert and found the Tumbleweed snapshots - usage notes.
Thought I would give it a try.

Sorry I missed the edit window as reverting and rebooting took too long but here is my reversion result:-

alastair@ibmserv2:~> tumbleweed status 
latest   : 20210504 
target   : 20210430 
installed: 20210430 
alastair@ibmserv2:~>

And I am pleased to report digiKam is back up and working.
I went back a couple of snapshots because I have had some odd erratic behaviour on my machine. I have no idea what has caused it as I have also changed mouse but only noticed it in the last few days so went back to April and will see how I get on.

tannington · 2021-05-06T15:42:58.000Z

All working OK here now with 20210504

paul@Orion-15:~$ zypper se -is libopencv
Loading repository data...
Reading installed packages...

S  | Name                   | Type    | Version    | Arch   | Repository
---+------------------------+---------+------------+--------+------------------------
i+ | libopencv3_4           | package | 3.4.10-2.4 | x86_64 | openSUSE-Tumbleweed-Oss
i  | libopencv4_5           | package | 4.5.2-1.1  | x86_64 | openSUSE-Tumbleweed-Oss
i  | libopencv_imgcodecs4_5 | package | 4.5.2-1.1  | x86_64 | openSUSE-Tumbleweed-Oss
i  | libopencv_ximgproc4_5  | package | 4.5.2-1.1  | x86_64 | openSUSE-Tumbleweed-Oss
paul@Orion-15:~$ zypper se -is *digikam*
Loading repository data...
Reading installed packages...

S  | Name            | Type    | Version      | Arch   | Repository
---+-----------------+---------+--------------+--------+-----------------------
i+ | digikam         | package | 7.2.0-214.19 | x86_64 | KDE Extra (Tumbleweed)
i+ | digikam-plugins | package | 7.2.0-214.19 | x86_64 | KDE Extra (Tumbleweed)
i+ | libdigikamcore7 | package | 7.2.0-214.19 | x86_64 | KDE Extra (Tumbleweed)
paul@Orion-15:~$

Although I should note I’m using digikam from KDE:Extra

tannington · 2021-05-06T15:46:26.000Z

Hmm… indeed it still fails when using digikam from the “standard” TW repository

paul@Orion-15:~$ zypper se -is *digikam*
Loading repository data...
Reading installed packages...

S  | Name            | Type    | Version   | Arch   | Repository
---+-----------------+---------+-----------+--------+------------------------
i+ | digikam         | package | 7.2.0-1.2 | x86_64 | openSUSE-Tumbleweed-Oss
i+ | digikam-plugins | package | 7.2.0-1.2 | x86_64 | openSUSE-Tumbleweed-Oss
i+ | libdigikamcore7 | package | 7.2.0-1.2 | x86_64 | openSUSE-Tumbleweed-Oss
paul@Orion-15:~$

Edit: Re-opened bugzilla report.

karlmistelberger · 2021-05-06T16:03:41.000Z

Ran successfully:

zypper ar -cfp 90 http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_Tumbleweed/KDE:Extra.repo
zypper dup

tannington · 2021-05-06T16:13:47.000Z

Digikam from both KDE:Extra and TW OSS are the same version, only the build levels are different.

So… the question now is, does digikam from TW OSS need to be rebuilt for it to work, or, is digikam from KDE:extra going to fail on it’s next rebuild?

Confused…

PerfMonk · 2021-05-07T23:58:53.000Z

Just zypper dup and find out digikam is still in problem :

bt@linux-0rk5:~> digikam 
qt.core.logging: Ignoring malformed logging rule: '’*=false’' 
QCommandLineParser: already having an option named "h" 
QCommandLineParser: already having an option named "help-all" 
QCommandLineParser: already having an option named "v" 
Icon theme "adwaita" not found. 
Icon theme "ubuntu-mono" not found. 
Icon theme "yaru" not found. 
Icon theme "Mint-X" not found. 
Icon theme "elementary" not found. 
libpng error: Read Error 
qt.svg: Could not create image from "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAMAAAADACAYAAABS3GwHAAAgAElEQVR42u29eXxU5fU/fs5z7+wz" 
qt.svg: <input>:20: Could not resolve property: #pattern0 
qt.svg: link #image0 is undefined! 
digikam: symbol lookup error: /usr/lib64/libdigikamgui.so.7.2.0: undefined symbol: _ZN2cv3dnn14dnn4_v202011173NetC1Ev 
bt@linux-0rk5:~>

I’m on Tumbleweed 20210506.

Any idea when digikam will be repaired ?

Regards,
BT

karlmistelberger · 2021-05-08T07:58:58.000Z

PerfMonk:

Just zypper dup and find out digikam is still in problem :

bt@linux-0rk5:~> digikam 
qt.core.logging: Ignoring malformed logging rule: '’*=false’' 
QCommandLineParser: already having an option named "h" 
QCommandLineParser: already having an option named "help-all" 
QCommandLineParser: already having an option named "v" 
Icon theme "adwaita" not found. 
Icon theme "ubuntu-mono" not found. 
Icon theme "yaru" not found. 
Icon theme "Mint-X" not found. 
Icon theme "elementary" not found. 
libpng error: Read Error 
qt.svg: Could not create image from "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAMAAAADACAYAAABS3GwHAAAgAElEQVR42u29eXxU5fU/fs5z7+wz" 
qt.svg: <input>:20: Could not resolve property: #pattern0 
qt.svg: link #image0 is undefined! 
digikam: symbol lookup error: /usr/lib64/libdigikamgui.so.7.2.0: undefined symbol: _ZN2cv3dnn14dnn4_v202011173NetC1Ev 
bt@linux-0rk5:~>

I’m on Tumbleweed 20210506.

Any idea when digikam will be repaired ?

Regards,
BT

For a working version see post #11.

opensuseinmanila · 2021-05-09T06:28:16.000Z

The problem was solved on my machine with the update to snapshot 20210507. Digikam is working again. A big thank you to the developers.

system · 2024-03-17T18:55:42.529Z