Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#58598 - [baloo] Baloo crashing at system startup
Attached to Project:
Arch Linux
Opened by Pedro Gabriel Drumond Pereira (pedrogabriel) - Monday, 14 May 2018, 19:53 GMT
Last edited by Antonio Rojas (arojas) - Sunday, 07 October 2018, 07:35 GMT
Opened by Pedro Gabriel Drumond Pereira (pedrogabriel) - Monday, 14 May 2018, 19:53 GMT
Last edited by Antonio Rojas (arojas) - Sunday, 07 October 2018, 07:35 GMT
|
DetailsDescription:
Whenever I start a plasma session I get a random crash of baloo_file_extractor Additional info: Following the issue are both the gdb backtrace and the journalctl log. * package version(s) baloo: 5.16.0-1 * config and/or log files etc. No extra config was done Steps to reproduce: -Start a plasma session -View journalctl log -Do "coredumpctl list" |
gdb.txt
This task depends upon
Closed by Antonio Rojas (arojas)
Sunday, 07 October 2018, 07:35 GMT
Reason for closing: Fixed
Additional comments about closing: baloo 5.50.0-2
Sunday, 07 October 2018, 07:35 GMT
Reason for closing: Fixed
Additional comments about closing: baloo 5.50.0-2
Comment by Antonio Rojas (arojas) -
Thursday, 17 May 2018, 06:24 GMT
https://bugs.kde.org/show_bug.cgi?id=367480