On 16 January 2017 at 22:39, John Andersen <jsamyth@gmail.com> wrote:
Crashes how exactly? Is it on specific files?
Right now it has crashed when I was saving a DOCX file. The message has: Executable: baloo_file PID: 2541 Signal: Segmentation fault (11) Time: 17/01/2017 02:53:49
You can put files and file types in the exclude list. You have to dig that out and do it manually because the kde people keep hiding the System Settings plug in for that feature.
Look in baloofilerc
locate baloofilerc /home/misha/.kde4/share/config/baloofilerc
I have added *.pdf,*.docx and will see if this resolves the issue, but really, this looks like a bug anyway. I wonder how I can get the debug symbols so I can file it meaningfully. -- Yours, Mikhail Ramendik Unless explicitly stated, all opinions in my mail are my own and do not reflect the views of any organization -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 17 January 2017 at 02:57, Mikhail Ramendik <mr@ramendik.ru> wrote:
On 16 January 2017 at 22:39, John Andersen <jsamyth@gmail.com> wrote:
Crashes how exactly? Is it on specific files?
Right now it has crashed when I was saving a DOCX file.
It appears that the backtrace might be useful despite the alleged lack of debug data: http://pastebin.com/MQ8G0RmE It seems (to my untrained eye) that the crash happens in mdb_get. So the Baloo database might be corrupt, causing crashes when baloo tried to add something? ~/.local/share/baloo/index is 306M in size and was last changed in October, around the time when the issue first started. If this is the database, it appears to have gone corrupt for some reason back then. Can I somehow get baloo to repair or regenerate its database? Thanks! -- Yours, Mikhail Ramendik Unless explicitly stated, all opinions in my mail are my own and do not reflect the views of any organization -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On January 16, 2017 7:06:21 PM PST, Mikhail Ramendik <mr@ramendik.ru> wrote:
On 17 January 2017 at 02:57, Mikhail Ramendik <mr@ramendik.ru> wrote:
On 16 January 2017 at 22:39, John Andersen <jsamyth@gmail.com> wrote:
Crashes how exactly? Is it on specific files?
Right now it has crashed when I was saving a DOCX file.
It appears that the backtrace might be useful despite the alleged lack of debug data:
It seems (to my untrained eye) that the crash happens in mdb_get. So the Baloo database might be corrupt, causing crashes when baloo tried to add something?
~/.local/share/baloo/index is 306M in size and was last changed in October, around the time when the issue first started. If this is the database, it appears to have gone corrupt for some reason back then.
Can I somehow get baloo to repair or regenerate its database? Thanks!
Try balooctl or something like that... On my phone right now so I can't look up the exact command. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 17 January 2017 at 03:09, John Andersen <jsamyth@gmail.com> wrote:
On January 16, 2017 7:06:21 PM PST, Mikhail Ramendik <mr@ramendik.ru> wrote:
Can I somehow get baloo to repair or regenerate its database? Thanks!
Try balooctl or something like that...
balooctl did not have anything useful. But I rigged a way: - deleted the ~/.local/share/baloo/index file - in the ~/.kde4/share/config/baloorc file, changed initianIndexingDone to false - rebooted Now indexing is apparently ongoing. Might or might not be stuck. I'll report progress in the coming days. -- Yours, Mikhail Ramendik Unless explicitly stated, all opinions in my mail are my own and do not reflect the views of any organization -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/16/2017 07:22 PM, Mikhail Ramendik wrote:
balooctl did not have anything useful. But I rigged a way:
Its my recollection that "balooctl disable" nukes the database and balooctl enable dead starts it again. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Mikhail Ramendik <mr@ramendik.ru> [01-16-17 22:06]:
On 17 January 2017 at 02:57, Mikhail Ramendik <mr@ramendik.ru> wrote:
On 16 January 2017 at 22:39, John Andersen <jsamyth@gmail.com> wrote:
Crashes how exactly? Is it on specific files?
Right now it has crashed when I was saving a DOCX file.
It appears that the backtrace might be useful despite the alleged lack of debug data:
It seems (to my untrained eye) that the crash happens in mdb_get. So the Baloo database might be corrupt, causing crashes when baloo tried to add something?
~/.local/share/baloo/index is 306M in size and was last changed in October, around the time when the issue first started. If this is the database, it appears to have gone corrupt for some reason back then.
small, ls -la .local/share/baloo/index -rw-r--r-- 1 paka users 6496280576 Jan 14 20:46 .local/share/baloo/index
Can I somehow get baloo to repair or regenerate its database? Thanks!
https://community.kde.org/Baloo/Configuration google is your friend. (in this case). -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
John Andersen -
Mikhail Ramendik -
Patrick Shanahan