| Summary: | baloo_file_extractor crashes on first login following cold boot, or following a warm reboot | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-kfilemetadata | Reporter: | Bosco Robinson <gjbr> |
| Component: | general | Assignee: | Pinak Ahuja <pinak.ahuja> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | gjbr, nate, stefan.bruens |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 5.54.0 | ||
| Target Milestone: | --- | ||
| Platform: | Debian stable | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Bosco Robinson
2020-11-05 13:27:00 UTC
This crash does not happen when I log back in on a system that was previously booted up and left up and running. You're using old versions of KDE software. Please consider upgrading. *** This bug has been marked as a duplicate of bug 405210 *** Thanks! I'll upgrade KDE. Just an FYI, the version of KDE I'm running is the default version provided by the stable Debian 10 buster distro. I will report this information back to the appropriate Debian folks if you can tell me the minimum version of KDE in which this issue is resolved. (In reply to Bosco Robinson from comment #3) > Thanks! I'll upgrade KDE. Just an FYI, the version of KDE I'm running is the > default version provided by the stable Debian 10 buster distro. Yeah, and Debian ships really really old software :) The current version of KDE Frameworks is 5.75; you've got 5.54. It's 21 months old. You're missing a lot of bugfixes. > I will report this information back to the appropriate Debian folks if you > can tell me the minimum version of KDE in which this issue is resolved. Thanks. I think the fix was in 5.58, but it's always recommended to use the newest version of KDE frameworks if possible. It was designed as a rolling release product and distros that lock a particular version and never update it are deviating from the developers' intentions for how it should be offered to users. (In reply to Nate Graham from comment #4) > (In reply to Bosco Robinson from comment #3) > > I will report this information back to the appropriate Debian folks if you > > can tell me the minimum version of KDE in which this issue is resolved. > Thanks. I think the fix was in 5.58, but it's always recommended to use the > newest version of KDE frameworks if possible. It was designed as a rolling > release product and distros that lock a particular version and never update > it are deviating from the developers' intentions for how it should be > offered to users. It is not only the packages provided by the KDE project (Frameworks, Applications), but also third party dependencies. For metadata extraction, baloo uses KFileMetadata, which in turn uses many third party libraries, e.g. taglib, ffmpeg, libepub. We try to keep the effects of upstream library bugs as small as possible, by doing extra checks, and by running this code in separate processes. We have found several bugs in taglib and libepub (that I can remember), and where fixes have been incorporated upstream (Taglib), or at least patches been created to pick up for distributions (libepub, dormant/nonexisting upstream). In this case, the crash is in the Exiv2 library, which is horribly outdated. Buster uses libexiv 0.25, which is from 2015. Debian is doing a very bad job here. |