Bug 1976513 - Digikam Fails to run in 8.4
Summary: Digikam Fails to run in 8.4
Keywords:
Status: CLOSED DUPLICATE of bug 1891610
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: digikam
Version: epel8
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-26 19:47 UTC by centosbugs2019
Modified: 2021-08-04 19:52 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-08-04 19:52:39 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description centosbugs2019 2021-06-26 19:47:51 UTC 
Description of problem:

digikam errors out.

 /usr/bin/digikam
/usr/bin/digikam: symbol lookup error: /lib64/libdigikamcore.so.6.2.0: undefined symbol: _ZN9KContacts13AddresseeListC1ERKS0_

Version-Release number of selected component (if applicable):


How reproducible:

Install and try to run :

Installing:
 digikam                           x86_64                      6.2.0-1.el8.1                         epel                       93 M
Installing dependencies:
 digikam-libs                      x86_64                      6.2.0-1.el8.1                         epel                       11 M
Installing weak dependencies:
 digikam-doc                       noarch                      6.2.0-1.el8.1                         epel                       34 k




Steps to Reproduce:
1. install
2. run


Actual results:

It does not run

Expected results:

IT RUNS

Additional info:
Comment 1 Thomas Doczkal 2021-07-16 07:50:14 UTC 
Seeing the same Error on Centos 8 Stream

/usr/bin/digikam
digikam: symbol lookup error: /lib64/libdigikamcore.so.6.2.0: undefined symbol: _ZN9KContacts13AddresseeListC1ERKS0_

Linux Hostname.example.net 5.13.0-1.el8.elrepo.x86_64 #1 SMP Sun Jun 27 19:44:44 EDT 2021 x86_64 x86_64 x86_64 GNU/Linux
Comment 2 Rex Dieter 2021-08-04 19:52:39 UTC 

*** This bug has been marked as a duplicate of bug 1891610 ***
Note You need to log in before you can comment on or make changes to this bug.