Bug 425599

Summary: akonadi-search 20.08 needs rebuild against KF KRunner 5.73 (or patched 5.72
Product: [KDE Neon] neon Reporter: Friedrich W. H. Kossebau <kossebau>
Component: Packages User EditionAssignee: Neon Bugs <neon-bugs>
Status: RESOLVED FIXED    
Severity: crash CC: chrisbertins, dev, jr, lnxusr, neon-bugs, sitter, tomas.nackaerts
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Friedrich W. H. Kossebau 2020-08-20 16:14:16 UTC
Current Akonadi-search 20.08 packager triggers bug 423003.

Please see https://bugs.kde.org/show_bug.cgi?id=423003#c52 for details
Comment 1 lnxusr 2020-08-21 16:39:11 UTC
Resolved Fixed with no explanation?  Will this be pushed out on the next update?  Is there a file or package we can download and install now if we'd rather not wait until the next update?
Comment 2 Nicola 2020-08-21 16:48:08 UTC
It is already pushed, today I updated the system and now for me it is fixed. From the apt log i think the upgraded packages were:

Start-Date: 2020-08-21  14:28:43
Commandline: packagekit role='update-packages'
Upgrade: libkf5akonadisearchdebug5:amd64 (4:20.08.0-0xneon+20.04+focal+build11, 4:20.08.0-0xneon+20.04+focal+build12), libkf5akonadisearch-data:amd64 (4:20.08.0-0xneon+20.04+focal+build11, 4:20.08.0-0xneon+20.04+focal+build12), libkf5akonadisearchpim5:amd64 (4:20.08.0-0xneon+20.04+focal+build11, 4:20.08.0-0xneon+20.04+focal+build12), libkf5akonadisearchcore5:amd64 (4:20.08.0-0xneon+20.04+focal+build11, 4:20.08.0-0xneon+20.04+focal+build12), libkf5akonadisearch-plugins:amd64 (4:20.08.0-0xneon+20.04+focal+build11, 4:20.08.0-0xneon+20.04+focal+build12), libkf5akonadisearchxapian5:amd64 (4:20.08.0-0xneon+20.04+focal+build11, 4:20.08.0-0xneon+20.04+focal+build12), libkf5akonadisearch-bin:amd64 (4:20.08.0-0xneon+20.04+focal+build11, 4:20.08.0-0xneon+20.04+focal+build12)

Thanks for the fast fix :) .
Comment 3 lnxusr 2020-08-21 17:34:31 UTC
Got it.  I had to manually 'apt update' to get the notification.

Many thanks to the development team for getting this out quickly.
Comment 4 Alexander Lohnau 2020-08-25 05:34:26 UTC
*** Bug 425556 has been marked as a duplicate of this bug. ***