Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Baloo File Extractor Crashes on every boot.[SOLVED]
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
Budoka
l33t
l33t


Joined: 03 Jun 2012
Posts: 733
Location: Tokyo, Japan

PostPosted: Thu May 02, 2019 12:59 am    Post subject: Baloo File Extractor Crashes on every boot.[SOLVED] Reply with quote

The title says it all. Every boot I get a
Code:
Executable: baloo_file_extractor PID: 22188 Signal: Segmentation fault (11)


It is mostly just annoying but would be nice to make it go away. Any ideas? Thanks


Last edited by Budoka on Thu May 02, 2019 4:52 am; edited 1 time in total
Back to top
View user's profile Send private message
Fitzcarraldo
Veteran
Veteran


Joined: 30 Aug 2008
Posts: 1786
Location: United Kingdom

PostPosted: Thu May 02, 2019 4:01 am    Post subject: Reply with quote

I find Baloo fragile and a nuisance. Sometimes it works OK on my amd64 and ~amd64 machines, other times not. If you are not interested in file indexing, you can disable it:

Code:
$ balooctl disable


See also https://forums.gentoo.org/viewtopic-t-1092732.html
_________________
Clevo W230SS: amd64 nvidia-drivers & xf86-video-intel.
Compal NBLB2: ~amd64 xf86-video-ati. Dual boot Win 7 Pro 64-bit.
OpenRC eudev elogind & KDE on both.

Fitzcarraldo's blog
Back to top
View user's profile Send private message
Budoka
l33t
l33t


Joined: 03 Jun 2012
Posts: 733
Location: Tokyo, Japan

PostPosted: Thu May 02, 2019 4:51 am    Post subject: Reply with quote

[quote="Fitzcarraldo"]I find Baloo fragile and a nuisance. Sometimes it works OK on my amd64 and ~amd64 machines, other times not. If you are not interested in file indexing, you can disable it:

[code]$ balooctl disable[/code]

See also https://forums.gentoo.org/viewtopic-t-1092732.html[/quote]
Thanks. I'll disable it.
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 7428
Location: Austria

PostPosted: Thu May 02, 2019 9:25 am    Post subject: Reply with quote

It would have been nice to know the reason for the segfault, saving the crash dump and using `balooctl monitor` to maybe see on what file it crashed. I understand dealing with it is a nuisance, but bugs can only be fixed when they get reported. Just recently I got multiple crashes of baloo (turns out certain binary testfiles with an invalid file extension in a git repository I had just cloned before were not flagged invalid by taglib), reported it with the aforementioned debug info and got it fixed within a day.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
Budoka
l33t
l33t


Joined: 03 Jun 2012
Posts: 733
Location: Tokyo, Japan

PostPosted: Thu May 02, 2019 10:42 am    Post subject: Reply with quote

[quote="asturm"]It would have been nice to know the reason for the segfault, saving the crash dump and using `balooctl monitor` to maybe see on what file it crashed. I understand dealing with it is a nuisance, but bugs can only be fixed when they get reported. Just recently I got multiple crashes of baloo (turns out certain binary testfiles with an invalid file extension in a git repository I had just cloned before were not flagged invalid by taglib), reported it with the aforementioned debug info and got it fixed within a day.[/quote]

I agree and understand. I repeatedly tried to submit the bug report when prompted and every time without fail would get a message saying something to the effect of "there isn't enough in the crash dump for the developers to use". I am paraphrasing.
Back to top
View user's profile Send private message
Goverp
l33t
l33t


Joined: 07 Mar 2007
Posts: 796

PostPosted: Fri May 03, 2019 9:10 am    Post subject: Reply with quote

Budoka wrote:
...
I agree and understand. I repeatedly tried to submit the bug report when prompted and every time without fail would get a message saying something to the effect of "there isn't enough in the crash dump for the developers to use". I am paraphrasing.
I believe the cause of that message is that the programs executing at the time have had their symbols stripped - that's the Gentoo default, and perhaps not having gdb support. So if you want to send a useful dump, you need to recompile all the relevant programs with FEATURES="nostrip" and CFLAGS="-ggdb". Which is a pain. You might be able to find out which programs to recompile if the KDE dump thingy shows you the execution stack entries (I forget if it does, and have nothing crashing at the moment with which to check).

I recall reading that a recent baloo update should cure the crashes, but requires deleting the old baloo database. baloo should then recreate it properly and all should be well. But I've read that before :-)
_________________
Greybeard
Back to top
View user's profile Send private message
Fitzcarraldo
Veteran
Veteran


Joined: 30 Aug 2008
Posts: 1786
Location: United Kingdom

PostPosted: Fri May 03, 2019 9:57 am    Post subject: Reply with quote

Goverp wrote:
I recall reading that a recent baloo update should cure the crashes, but requires deleting the old baloo database. baloo should then recreate it properly and all should be well. But I've read that before :-)

https://bugs.kde.org/show_bug.cgi?id=389848#c33 perhaps?

Don Curtis wrote:
For the case of the user which was suffering the Baloo crashes I did the following from a VT with the Display Manager stopped:
1. Removed the following files in '~/.config/':
baloorc
baloofilerc
baloofileinformationrc
2. Removed the entire contents of '~/.local/share/baloo/':
index
index-lock
KDE PIM Kontact directories
3. Restarted the Display Manager and logged in the user with the "Baloo
crashing issue".
------------------------------------------------------------
Baloo doesn't crash any more.
------------------------------------------------------------
My guess at the root cause:
* Outdated Baloo configuration files and an outdated index database cause
an exception with the current Baloo implementation.

_________________
Clevo W230SS: amd64 nvidia-drivers & xf86-video-intel.
Compal NBLB2: ~amd64 xf86-video-ati. Dual boot Win 7 Pro 64-bit.
OpenRC eudev elogind & KDE on both.

Fitzcarraldo's blog
Back to top
View user's profile Send private message
bronzeboyvn
n00b
n00b


Joined: 31 Mar 2009
Posts: 57
Location: Vietnam

PostPosted: Sun Mar 15, 2020 11:00 am    Post subject: Reply with quote

Don Curtis wrote:
For the case of the user which was suffering the Baloo crashes I did the following from a VT with the Display Manager stopped:
1. Removed the following files in '~/.config/':
baloorc
baloofilerc
baloofileinformationrc
2. Removed the entire contents of '~/.local/share/baloo/':
index
index-lock
KDE PIM Kontact directories
3. Restarted the Display Manager and logged in the user with the "Baloo
crashing issue".
------------------------------------------------------------
Baloo doesn't crash any more.
------------------------------------------------------------
My guess at the root cause:
* Outdated Baloo configuration files and an outdated index database cause
an exception with the current Baloo implementation.


I reinstall Gentoo plasma at least 1 time per year and always keep /home partition.
It appeared crash on baloo file extractor after logged in, but it doesn't crash on new user.

1. Removed the following files in '~/.config/': ...
2. Removed the entire contents of '~/.local/share/baloo/': ...

Thanks, it works for me
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum