Bug 428810 - Error: Process (baloo_file) of user 1000 dumped core.
Summary: Error: Process (baloo_file) of user 1000 dumped core.
Status: RESOLVED NOT A BUG
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Baloo File Daemon (show other bugs)
Version: 5.75.0
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Stefan Brüns
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-11-07 22:31 UTC by Aadniz
Modified: 2020-11-10 07:00 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Crash report generated by KDE crash handler (2.55 KB, text/vnd.kde.kcrash-report)
2020-11-07 22:31 UTC, Aadniz
Details
Output of journalctl -g baloo (4.94 KB, text/plain)
2020-11-07 22:34 UTC, Aadniz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Aadniz 2020-11-07 22:31:55 UTC
Created attachment 133121 [details]
Crash report generated by KDE crash handler

SUMMARY
baloo_file crashes, and are not able to start.

STEPS TO REPRODUCE
Not sure, it happened after an update on my computer (6th of November)

OBSERVED RESULT
Files in dolphin file manager appear white, and are not possible to "click to run".
Some applications like Deluge-gtk are unable to start.
Dragging tab out from firefox (to extend the application to 2 windows) makes it crash.
Firefox choose file function (Like the Add an attachment function in this bug report) also makes it crash.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Linux arch 5.9.4-arch1-1 #1 SMP PREEMPT Wed, 04 Nov 2020 21:41:09 +0000 x86_64 GNU/Linux
(available in About System)
KDE Plasma Version: 5.20.2
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1

ADDITIONAL INFORMATION
I posted a thread on Reddit before I came here: https://www.reddit.com/r/kde/comments/jpgv03/im_having_issue_with_baloo_it_does_not_want_to/
The post includes screenshots of various errors
Comment 1 Aadniz 2020-11-07 22:34:23 UTC
Created attachment 133122 [details]
Output of journalctl -g baloo
Comment 2 Nate Graham 2020-11-09 17:39:06 UTC

*** This bug has been marked as a duplicate of bug 389848 ***
Comment 3 Aadniz 2020-11-10 07:00:57 UTC
Managed to get this fixed by reinstalling all packages with pacman using this command:

    pacman -Qqn | pacman -S -

Possible broken package(s) caused the issues to begin with