[frameworks-baloo] [Bug 396323] Baloo index service crash

2018-10-12 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=396323

--- Comment #5 from Nate Graham  ---


*** This bug has been marked as a duplicate of bug 367480 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 396323] Baloo index service crash

2018-10-12 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=396323

--- Comment #4 from Nate Graham  ---


*** This bug has been marked as a duplicate of bug 357206 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 396323] Baloo index service crash

2018-10-12 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=396323

Nate Graham  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||n...@kde.org
 Resolution|--- |DUPLICATE

--- Comment #3 from Nate Graham  ---


*** This bug has been marked as a duplicate of bug 394404 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 396323] Baloo index service crash

2018-10-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=396323

--- Comment #2 from asca...@q.com ---
Created attachment 115355
  --> https://bugs.kde.org/attachment.cgi?id=115355=edit
New crash information added by DrKonqi

baloo_file (5.50.0) using Qt 5.11.1

- What I was doing when the application crashed:
Simply attempted to start the file indexer.  It's not enabled, so  I enable it
using the file indexer monitor program.,  It begins nitial indexing, and
crashes less than a minute later, every time.

Each time, It reports a segfault in the little ladybug icon that appears in the
systray, though this time the backtrace says it was a bus error.  Trying to
report this error sometimes causes DrKonqi to segfault too before the report is
complete.

As far as I know, there are no hardware issues with the PC.  It previously ran
Mint 19  Cinnamon flawlessly before I switched to KDE.

-- Backtrace (Reduced):
#6  __memmove_sse2_unaligned_erms () at
../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:371
#7  0x7f214a57f923 in memcpy (__len=1070078608, __src=,
__dest=) at
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:34
#8  Baloo::PostingCodec::decode (this=this@entry=0x7f213fc81a47, arr=...) at
./src/codecs/postingcodec.cpp:42
#9  0x7f214a5713e4 in Baloo::PostingDB::get
(this=this@entry=0x7f213fc81b30, term=...) at ./src/engine/postingdb.cpp:100
#10 0x7f214a57d260 in Baloo::WriteTransaction::commit (this=0x7ee13004d220)
at ./src/engine/writetransaction.cpp:259

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 396323] Baloo index service crash

2018-10-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=396323

asca...@q.com changed:

   What|Removed |Added

 CC||asca...@q.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 396323] Baloo index service crash

2018-08-28 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=396323

caulier.gil...@gmail.com changed:

   What|Removed |Added

Summary|Baloo index service crash   |Baloo index service crash
   |after launching digiKam 5.9 |
 CC||caulier.gil...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 396323] Baloo index service crash after launching digiKam 5.9

2018-08-17 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=396323

Christoph Feck  changed:

   What|Removed |Added

 CC||kde-b...@sufrin.org

--- Comment #1 from Christoph Feck  ---
*** Bug 396973 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.