Bug 468798

Summary:	Digikam not starting after upgrade to 8.0
Product:	[KDE Neon] neon	Reporter:	Dominique Lebrun <dominique.lebrun>
Component:	Packages User Edition	Assignee:	Neon Bugs <neon-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	carlosd.kde, jr, metzpinguin, neon-bugs-null, sitter
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:	8.1.0
Sentry Crash Report:

Description Dominique Lebrun 2023-04-22 09:08:20 UTC

SUMMARY

After applying all the updates suggested by Discover (as of 2023-04-22), Digikam is upgraded to version 8.0 but does not start anymore.

STEPS TO REPRODUCE
1. Apply all the updates suggested by Discover
2. Try launching Digikam

OBSERVED RESULT
Digikam does not start. When launching it in the console, the following error message is shown:

```
digikam: error while loading shared libraries: libKF5AkonadiContact.so.5: cannot open shared object file: No such file or directory
```

EXPECTED RESULT

Digikam starting normally.

SOFTWARE/OS VERSIONS

Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Kernel Version: 5.19.0-40-generic (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION

I have supposed that this is a packaging-related problem, which is why I reported it on KDE neon.

Comment 1 Maik Qualmann 2023-04-22 09:48:20 UTC

Yes, that's a neon package problem. digiKam is compiled with Akonadi address book support for create new tags. The Akonadi library is not present in your system. It should install automatically as a dependency. Try installing the package manually.

Maik

Comment 2 Dominique Lebrun 2023-04-22 10:30:01 UTC

Which package(s) should I install exactly? The following are already installed on my system:
- akonadi-contacts-data
- libkf5akonadi-data
- libkf5akonadicontact5:amd64
- libkf5akonadicore5:amd64
- libkf5akonadiprivate5:amd64
- libkf5akonadiwidgets5:amd64

Comment 3 Carlos De Maine 2023-04-23 09:46:05 UTC

Now fixed in user.  Please update by your preferred method.

Comment 4 Dominique Lebrun 2023-04-26 06:06:01 UTC

I confirm that the last update fixed the problem. Thanks.