Baloo File Indexing Closed Unexpectedly

Hey guys, so as far as my search has shown this is an ongoing issue for some users.

I have a fresh boot of Leap 15, after crashing my system. However previously this never popped up when I was running Leap 15, just started after I reinstalled.

Leap 15 KDE.**
Executable: baloo_file PID: 1786 Signal: Aborted (6)**
I get an error message when I try to go through crash report and install debug symbols.

I just want to know if I should simply ignore it or is it effecting anything I may not have noticed yet?
I read through some other posts here and on Google but none I saw were very clear or related to Leap specifically.

Also can you let me know if my repos are as should be?
For whatever reason when I try to install a game (Endless Sky) and run it, it nearly crashes everything and seems to install an abundance of packages which may be causing the problem or something. Plenty of conflicts.

Repository priorities in effect: (See ‘zypper lr -P’ for details)
90 (raised priority) : 1 repository
99 (default priority) : 5 repositories

| Alias | Name | Enabled | GPG Check | Refresh

—±--------------------------±----------------------------------------±--------±----------±-------
1 | openSUSE-Leap-15.0-1 | openSUSE-Leap-15.0-1 | No | ---- | ----
2 | openSUSE_Leap_15.0 | openSUSE Games | Yes | (r ) Yes | Yes
3 | packman-essentials | packman-essentials | Yes | (r ) Yes | Yes
4 | repo-debug | openSUSE-Leap-15.0-Debug | No | ---- | ----
5 | repo-debug-non-oss | openSUSE-Leap-15.0-Debug-Non-Oss | No | ---- | ----
6 | repo-debug-update | openSUSE-Leap-15.0-Update-Debug | No | ---- | ----
7 | repo-debug-update-non-oss | openSUSE-Leap-15.0-Update-Debug-Non-Oss | No | ---- | ----
8 | repo-non-oss | openSUSE-Leap-15.0-Non-Oss | Yes | (r ) Yes | Yes
9 | repo-oss | openSUSE-Leap-15.0-Oss | Yes | (r ) Yes | Yes
10 | repo-source | openSUSE-Leap-15.0-Source | No | ---- | ----
11 | repo-source-non-oss | openSUSE-Leap-15.0-Source-Non-Oss | No | ---- | ----
12 | repo-update | openSUSE-Leap-15.0-Update | Yes | (r ) Yes | Yes
13 | repo-update-non-oss | openSUSE-Leap-15.0-Update-Non-Oss | Yes | (r ) Yes | Yes

Thanks!

This usually points at a corrupted baloo database. Do this, it will rebuild the baloo database, give that some time


balooctl stop
rm ~/.local/share/baloo/*
balooctl start


I assume I’m doing something wrong or I’m unsure what I need to put in place of *

spencer@linux-rqqt:~> balooctl stop
spencer@linux-rqqt:~> rm ~/.local/share/baloo/*
spencer@linux-rqqt:~> balooctl start
spencer@linux-rqqt:~> Power state changed

nothing really happened.

Then there was no database. What did


balooctl start

say ?

it just went to the next line immediately which says “Power State Changed.”
Just as I posted is what happened, nothing in between or anything at all.

What does


ps -ea | grep baloo

give ( please post output always between CODE tags, the # in the editor )
and


ls -lR ~/.local/share/baloo

Can you elaborate on the crash of your previous install ?

spencer@linux-rqqt:~> ps -ea | grep baloo
 1849 ?        00:00:00 baloo_file
spencer@linux-rqqt:~> ls -lR ~/.local/share/baloo
/home/spencer/.local/share/baloo:
total 104
-rw-r--r-- 1 spencer users 102400 Jan 19 18:29 index
-rw-r--r-- 1 spencer users   8192 Jan 19 19:30 index-lock


My previous crash was due to me screwing up removing a repository after asking for help here about KWIN crashing, long story short I screwed something up when endless file conflicts came about. So I just decided to reinstall entirely since I didn’t have anything overly important I needed to save.
It wasn’t during install, I had been running Leap 15 for a few months.