![](https://seccdn.libravatar.org/avatar/fcddee211ea9dd5e95f4be2d0c89273f.jpg?s=120&d=mm&r=g)
Back in 15.1, these Baloo errors were a frequent occurance. They seem to have returned recently with 15.2. Has anyone else experienced this? I'm seeing this on my ThinkPad E520, but not my desktop system, both running KDE on 15.2. tnx jk Executable: baloo_file PID: 26090 Signal: Aborted (6) Time: 2020-12-11 09:38:41 Application: baloo_file (baloo_file), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f38acd3a900 (LWP 26090))] Thread 3 (Thread 0x7f38a12b5700 (LWP 30943)): [KCrash Handler] #4 0x00007f38aab0d520 in raise () from /lib64/libc.so.6 #5 0x00007f38aab0eb01 in abort () from /lib64/libc.so.6 #6 0x00007f38a887fa82 in ?? () from /usr/lib64/liblmdb-0.9.17.so #7 0x00007f38a8874d85 in ?? () from /usr/lib64/liblmdb-0.9.17.so #8 0x00007f38a8875f6a in ?? () from /usr/lib64/liblmdb-0.9.17.so #9 0x00007f38a88761d9 in ?? () from /usr/lib64/liblmdb-0.9.17.so #10 0x00007f38a8877cf4 in ?? () from /usr/lib64/liblmdb-0.9.17.so #11 0x00007f38a887ae8e in mdb_cursor_put () from /usr/lib64/liblmdb-0.9.17.so #12 0x00007f38a887db1b in mdb_put () from /usr/lib64/liblmdb-0.9.17.so #13 0x00007f38abd0651c in Baloo::PostingDB::put(QByteArray const&, QVector<unsigned long long> const&) () from /usr/lib64/libKF5BalooEngine.so.5 #14 0x00007f38abd18bb5 in Baloo::WriteTransaction::commit() () from /usr/lib64/libKF5BalooEngine.so.5 #15 0x00007f38abd0e371 in Baloo::Transaction::commit() () from /usr/lib64/libKF5BalooEngine.so.5 #16 0x000055efca7ba9f5 in ?? () #17 0x00007f38ab658132 in ?? () from /usr/lib64/libQt5Core.so.5 #18 0x00007f38ab6539c2 in ?? () from /usr/lib64/libQt5Core.so.5 #19 0x00007f38a8cdf4f9 in start_thread () from /lib64/libpthread.so.0 #20 0x00007f38aabcffbf in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f38a1db8700 (LWP 26184)): #0 0x00007f38aabc56db in poll () from /lib64/libc.so.6 #1 0x00007f38a7197779 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007f38a719788c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x00007f38ab88bcdb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #4 0x00007f38ab82ce8a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #5 0x00007f38ab65221a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x00007f38abf39cd5 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x00007f38ab6539c2 in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x00007f38a8cdf4f9 in start_thread () from /lib64/libpthread.so.0 #9 0x00007f38aabcffbf in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f38acd3a900 (LWP 26090)): #0 0x00007f38aabc56db in poll () from /lib64/libc.so.6 #1 0x00007f38a7197779 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007f38a719788c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x00007f38ab88bcdb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #4 0x00007f38ab82ce8a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #5 0x00007f38ab836090 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x000055efca7ab392 in ?? () #7 0x00007f38aaaf834a in __libc_start_main () from /lib64/libc.so.6 #8 0x000055efca7ab5da in ?? () [Inferior 1 (process 26090) detached]
![](https://seccdn.libravatar.org/avatar/27aacf61a13c66fcc083fcf8a84823bc.jpg?s=120&d=mm&r=g)
On 12/11/20 9:42 AM, James Knott wrote:
Back in 15.1, these Baloo errors were a frequent occurance. They seem to have returned recently with 15.2. Has anyone else experienced this? I'm seeing this on my ThinkPad E520, but not my desktop system, both running KDE on 15.2.
tnx jk
Baloo, just like the "dreaded dog Beagle" is the first app that gets shot in the head on install -- never have any problems with it :) $ balooctl suspend $ balooctl disable -- David C. Rankin, J.D.,P.E.
![](https://seccdn.libravatar.org/avatar/fcddee211ea9dd5e95f4be2d0c89273f.jpg?s=120&d=mm&r=g)
On 2020-12-11 4:06 p.m., David C. Rankin wrote:
Back in 15.1, these Baloo errors were a frequent occurance. They seem to have returned recently with 15.2. Has anyone else experienced this? I'm seeing this on my ThinkPad E520, but not my desktop system, both running KDE on 15.2.
tnx jk Baloo, just like the "dreaded dog Beagle" is the first app that gets shot in
On 12/11/20 9:42 AM, James Knott wrote: the head on install -- never have any problems with it :)
$ balooctl suspend $ balooctl disable
That didn't do it. What's baloo supposed to do?
![](https://seccdn.libravatar.org/avatar/0e482cdf263bd0e0421da766878b774c.jpg?s=120&d=mm&r=g)
On 11/12/2020 22.34, James Knott wrote:
On 2020-12-11 4:06 p.m., David C. Rankin wrote:
Back in 15.1, these Baloo errors were a frequent occurance. They seem to have returned recently with 15.2. Has anyone else experienced this? I'm seeing this on my ThinkPad E520, but not my desktop system, both running KDE on 15.2.
tnx jk Baloo, just like the "dreaded dog Beagle" is the first app that gets shot in
On 12/11/20 9:42 AM, James Knott wrote: the head on install -- never have any problems with it :)
$ balooctl suspend $ balooctl disable
That didn't do it.
You have to relogin
What's baloo supposed to do?
Content indexer. It allows you to search for a file knowing some content, like a phrase in an office document. https://wiki.archlinux.org/index.php/Baloo -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
![](https://seccdn.libravatar.org/avatar/27aacf61a13c66fcc083fcf8a84823bc.jpg?s=120&d=mm&r=g)
On 12/11/20 3:58 PM, James Knott wrote:
On 2020-12-11 4:53 p.m., Carlos E.R. wrote:
That didn't do it. You have to relogin
I shut down and rebooted the computer.
KDE has a nasty habit of starting things in /etc/xdg/autostart -- double check there. -- David C. Rankin, J.D.,P.E.
![](https://seccdn.libravatar.org/avatar/abdee805d4df05af9a496107100c582c.jpg?s=120&d=mm&r=g)
* David C. Rankin <drankinatty@suddenlinkmail.com> [12-12-20 02:21]:
On 12/11/20 3:58 PM, James Knott wrote:
On 2020-12-11 4:53 p.m., Carlos E.R. wrote:
That didn't do it. You have to relogin
I shut down and rebooted the computer.
KDE has a nasty habit of starting things in /etc/xdg/autostart -- double check there.
perhaps I am just very dense, but the purpose of /etc/xdg/autostart iiuc is to do *exactly* that, automagically start instances that for the most part the <user> has specified. how does that qualify as a nasty KDE habit? and, yes, baloo_file.desktop is included there and should be automagically removed if baloo_ was disabled. but <user> should not have to perform that operation, it would be done when "Enable file search" was unchecked. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
![](https://seccdn.libravatar.org/avatar/27aacf61a13c66fcc083fcf8a84823bc.jpg?s=120&d=mm&r=g)
On 12/12/20 5:09 AM, Patrick Shanahan wrote:
perhaps I am just very dense, but the purpose of /etc/xdg/autostart iiuc is to do *exactly* that, automagically start instances that for the most part the <user> has specified.
how does that qualify as a nasty KDE habit?
That's just a handover adjective from then they first started doing it with kde 4.04a? and then Gnome joined the party, and soon if you has a few gnome apps on kde, or vice-versa you would have a gaggle of apps all launching from xdg/autostart you would have to deal with. I'm mean they are just apps. Not all nasty -- boy but some of the sure are :p -- David C. Rankin, J.D.,P.E.
![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
On 11/12/2020 22.58, James Knott wrote:
On 2020-12-11 4:53 p.m., Carlos E.R. wrote:
That didn't do it. You have to relogin
I shut down and rebooted the computer.
I musst say that I see error messages from baloo often, but they are not important to the computer, unless you actually use baloo. Yes, I find a content indexer a good feature. Used sporadically, but good to be there. If it works (I don't use KDE, yet baloo runs). -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
![](https://seccdn.libravatar.org/avatar/12100f1497f7c0b346606b8b4a32ae8d.jpg?s=120&d=mm&r=g)
On 2020-12-11 4:06 p.m., David C. Rankin wrote:
On 12/11/20 9:42 AM, James Knott wrote:
Back in 15.1, these Baloo errors were a frequent occurance. They seem to have returned recently with 15.2. Has anyone else experienced this? I'm seeing this on my ThinkPad E520, but not my desktop system, both running KDE on 15.2.
tnx jk
Baloo, just like the "dreaded dog Beagle" is the first app that gets shot in
$ balooctl suspend $ balooctl disable
Baloo is part of the akonadi framework. Its purpose would be, in combination with a working KDE PIM and e.g. the milou app, to index all kind of files and to present the results of the researches to the user. That is you could search your file with keywords and wherever it has been deposited, you should find it, whether the original author did give a meaningful name or not. Imagine your file is about a contract with xy industries, but your secretary gave it a filename of her puppy. No matter, you type in a keyword "xy industries" and the framework will give you all document be it emails, contracts or wanting even photos that bear somewhere the description "xy industries". The problem is that either the predecessor of baloo, as baloo itself, has had history of troubles. Whether you are running into this is depending a lot on your personal use
In data venerdì 11 dicembre 2020 22:34:35 CET, James Knott ha scritto: the head on install -- never have any problems with it :) pattern. Personally I do use KDE PIM and although that is broken beyond repair for me in 15.2, the baloo indexer works without problems. If you encounter this problem and stopping baloo does not help, chances are good that you have an index issue. Try to (after backup) erase the indexes in ".local/akonadi give it time to reindex because I have seen that process on older machines may be a bit shaky and resource hungry. Often after a complete new indexing you problems disappear. Before you can try: stop kde PIM if you are running it or Kmail if applicable. run akonadictl fsck, and akonadictl vacuum. then akonadictl restart then restart you application to see if things are better. In case not you are left with the option of trying to re-indexing.
![](https://seccdn.libravatar.org/avatar/fcddee211ea9dd5e95f4be2d0c89273f.jpg?s=120&d=mm&r=g)
On 2020-12-11 5:06 p.m., Stakanov wrote:
Before you can try: stop kde PIM if you are running it or Kmail if applicable. run akonadictl fsck, and akonadictl vacuum. then akonadictl restart then restart you application to see if things are better. In case not you are left with the option of trying to re-indexing. _______________________________________________
I don't use any of those things. The bug appears when I boot the computer. However, I will try those things.
![](https://seccdn.libravatar.org/avatar/12100f1497f7c0b346606b8b4a32ae8d.jpg?s=120&d=mm&r=g)
In data venerdì 11 dicembre 2020 23:11:12 CET, James Knott ha scritto:
On 2020-12-11 5:06 p.m., Stakanov wrote:
Before you can try: stop kde PIM if you are running it or Kmail if applicable. run akonadictl fsck, and akonadictl vacuum. then akonadictl restart then restart you application to see if things are better. In case not you are left with the option of trying to re-indexing.
this is odd in so far that you do not need akonadi and hence baloo running if you do not use them. Could you try to open a terminal and write the output of akonadictl status before you do anything else? I am assuming here that you are running KDE Plasma as default desktop. Please correct me if I am wrong.
![](https://seccdn.libravatar.org/avatar/12100f1497f7c0b346606b8b4a32ae8d.jpg?s=120&d=mm&r=g)
In data venerdì 11 dicembre 2020 23:11:12 CET, James Knott ha scritto:
On 2020-12-11 5:06 p.m., Stakanov wrote:
And since you say: I do not use any of these. To answer the next question that is coming to your mind - that is: what application start akonadi? Akonadi is starte by a bunch of application that you may use when you use KDE Plasma (without knowing it). In order to have a AFAIK complete list of programs that trigger it you can do the following in a terminal (CLI / command line) window: sudo zypper se -i --requires akonadi this will give you a mostly complete list of applications that require the use of akonadi, hence will start forcefull akonadi if you make use of them. (e.g. kalarm etc). If you encounter in the list a program that you need and like you shall run akonadi. If you do NOT encounter ANY of these, you should check whether a forgotten instance of one of them is not running e.g. in the tray. (Often Korganizer daemon or kalarm etc). If you stop all programs depending on akonadi, it will not start at session start. Same for "baloo".
![](https://seccdn.libravatar.org/avatar/12100f1497f7c0b346606b8b4a32ae8d.jpg?s=120&d=mm&r=g)
In data venerdì 11 dicembre 2020 23:25:23 CET, Stakanov ha scritto:
In data venerdì 11 dicembre 2020 23:11:12 CET, James Knott ha scritto:
On 2020-12-11 5:06 p.m., Stakanov wrote:
And since you say: I do not use any of these. To answer the next question And it comes to my mind:
provided you run the plasma desktop and the digital clock e.g. in the tray, then it will start akonadi (because it has a plugin that makes it possible to see the festivities of a country or even the events. As these are part of calendar and of organizer, it will start akonadi. If may therefore be of your interest to fix the index problem.
![](https://seccdn.libravatar.org/avatar/db61becba2ff9d091e7d462f1b3178ac.jpg?s=120&d=mm&r=g)
On Saturday 12 December 2020, James Knott wrote:
On 2020-12-11 4:06 p.m., David C. Rankin wrote:
Back in 15.1, these Baloo errors were a frequent occurance. They seem to have returned recently with 15.2. Has anyone else experienced this? I'm seeing this on my ThinkPad E520, but not my desktop system, both running KDE on 15.2.
tnx jk Baloo, just like the "dreaded dog Beagle" is the first app that gets shot in
On 12/11/20 9:42 AM, James Knott wrote: the head on install -- never have any problems with it :)
$ balooctl suspend $ balooctl disable
That didn't do it. What's baloo supposed to do?
As already mentioned it's a file indexer, it can be disabled via System Settings->Workspace->Search-File Search untick Enable File Search. That's the least drastic way of keeping it from getting in the way. I suppose you might have to logout or reboot before the setting change would be enacted. (It's a per user thing, so a reboot probably isn't necessary, except that sometimes logging out leaves remnant session processes running.)
participants (7)
-
Carlos E. R.
-
Carlos E.R.
-
David C. Rankin
-
James Knott
-
Michael Hamilton
-
Patrick Shanahan
-
Stakanov