Bug 467901 - digiKam cannot be installed in Neon through Discover
Summary: digiKam cannot be installed in Neon through Discover
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: neon
Classification: KDE Neon
Component: Packages Testing Edition (other bugs)
Version First Reported In: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-03-28 21:41 UTC by Valter Mura
Modified: 2025-09-20 09:35 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Valter Mura 2023-03-28 21:41:10 UTC 
SUMMARY
***
The program *digiKam* cannot be installed from Discover
***


STEPS TO REPRODUCE
1. open Discover
2. search and try to install digiKam
3. 

OBSERVED RESULT
Discover returns an error pop-up, warning: "dependency resolution failed"

EXPECTED RESULT
It should be work as expected, digiKam should be installed regularly

SOFTWARE/OS VERSIONS
Operating System: KDE neon Testing Edition
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.8
Kernel Version: 5.19.0-38-generic (64-bit)
Graphics Platform: X11
Graphics Processor: NVE7

ADDITIONAL INFORMATION
Comment 1 Valter Mura 2023-04-30 10:03:28 UTC 
The problem is still present while my system has changed:

Operating System: KDE neon Testing Edition
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Kernel Version: 5.19.0-41-generic (64-bit)
Graphics Platform: X11
Graphics Processor: NVE7
Comment 2 Carlos De Maine 2025-09-20 09:35:42 UTC 
Thank you for your bug report! 
However this bug report was created/provided previous to 01/01/2023 and also has not received any updates since  before 01/01/2025. 
Unfortunately KDE neon no longer provides updates for anything older than noble 24.04 based edition's.
Please upgrade to KDE neon noble and if you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report.
Thanks for understanding!