[frameworks-baloo] [Bug 396218] Crash on log-in

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

--- Comment #7 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 396218] Crash on log-in

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

--- Comment #6 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 396218] Crash on log-in

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #5 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 396218] Crash on log-in

2018-10-02 Thread Woods Wannamaker
https://bugs.kde.org/show_bug.cgi?id=396218

Woods Wannamaker  changed:

   What|Removed |Added

 CC||wanna...@gmail.com

--- Comment #4 from Woods Wannamaker  ---
I've been getting this at login after boot-up since I upgraded from Kubuntu
16.04.5 to Kubuntu 18.04.1. I tried installing -dbg tools to capture more
useful info but that failed when trying to install baloo-dbg. I have diabled
baloo completely and did not experience crash after restart and login. 

Here is the crash report.

Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f760f3e3200 (LWP 1861))]

Thread 3 (Thread 0x7f35f700 (LWP 2159)):
[KCrash Handler]
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#7  0x7f760ccda801 in __GI_abort () at abort.c:79
#8  0x7f760aa974d2 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#9  0x7f760aa8c5d5 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#10 0x7f760aa8d803 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#11 0x7f760aa8da79 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#12 0x7f760aa8f764 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#13 0x7f760aa92992 in mdb_cursor_put () from
/usr/lib/x86_64-linux-gnu/liblmdb.so.0
#14 0x7f760aa955a0 in mdb_put () from
/usr/lib/x86_64-linux-gnu/liblmdb.so.0
#15 0x7f760e19b49f in Baloo::DocumentDB::put(unsigned long long,
QVector const&) () from
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#16 0x7f760e1b3e80 in Baloo::WriteTransaction::addDocument(Baloo::Document
const&) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#17 0x560dbb93eb69 in ?? ()
#18 0x7f760d85b2a2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x7f760d85e16d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7f760bde16db in start_thread (arg=0x7f35f700) at
pthread_create.c:463
#21 0x7f760cdbb88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f7604a61700 (LWP 1875)):
#0  0x7ffd8e980a44 in clock_gettime ()
#1  0x7f760cdcaea6 in __GI___clock_gettime (clock_id=1, tp=0x7f7604a60ae0)
at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f760da95221 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f760da93a59 in QTimerInfoList::updateCurrentTime() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f760da94035 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f760da9567e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f7609512998 in g_main_context_prepare () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f760951336b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f760951354c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f760da9590b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f760da3a9ea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f760d85922a in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f760eca9d45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#13 0x7f760d85e16d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7f760bde16db in start_thread (arg=0x7f7604a61700) at
pthread_create.c:463
#15 0x7f760cdbb88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f760f3e3200 (LWP 1861)):
#0  0x7f760cdaa0b4 in __GI___libc_read (fd=3, buf=0x7ffd8e87aa80,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x7f7609557a00 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f7609512f27 in g_main_context_check () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f76095133e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f760951354c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f760da958ef in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f760da3a9ea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f760da43a84 in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x560dbb93980c in ?? ()
#9  0x7f760ccbbb97 in __libc_start_main (main=0x560dbb939560, argc=1,
argv=0x7ffd8e87aff8, init=, fini=,
rtld_fini=, stack_end=0x7ffd8e87afe8) at ../csu/libc-start.c:310
#10 0x560dbb939a7a in _start ()

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

[frameworks-baloo] [Bug 396218] Crash on log-in

2018-08-07 Thread Brett Keller
https://bugs.kde.org/show_bug.cgi?id=396218

--- Comment #2 from Brett Keller  ---
Created attachment 114363
  --> https://bugs.kde.org/attachment.cgi?id=114363&action=edit
New crash information added by DrKonqi

baloo_file (5.44.0) using Qt 5.9.5

- What I was doing when the application crashed:

Noticed this just after untarring a file via Dolphin's context menu, but this
was not long after login, so it may have simply been triggered by login.

-- Backtrace (Reduced):
#6  __memmove_avx_unaligned_erms () at
../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:370
#7  0x7f4dbd4d7973 in memcpy (__len=2050, __src=,
__dest=) at
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:34
#8  Baloo::PostingCodec::decode (this=this@entry=0x7f4db3377a77, arr=...) at
./src/codecs/postingcodec.cpp:42
#9  0x7f4dbd4c93e4 in Baloo::PostingDB::get
(this=this@entry=0x7f4db3377b60, term=...) at ./src/engine/postingdb.cpp:100
#10 0x7f4dbd4d5060 in Baloo::WriteTransaction::commit (this=0x7f4dac035160)
at ./src/engine/writetransaction.cpp:259

--- Comment #3 from Brett Keller  ---
Created attachment 114365
  --> https://bugs.kde.org/attachment.cgi?id=114365&action=edit
New crash information added by DrKonqi

baloo_file (5.44.0) using Qt 5.9.5

- What I was doing when the application crashed:

Noticed this just after untarring a file via Dolphin's context menu, but this
was not long after login, so it may have simply been triggered by login.

-- Backtrace (Reduced):
#6  __memmove_avx_unaligned_erms () at
../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:370
#7  0x7f4dbd4d7973 in memcpy (__len=2050, __src=,
__dest=) at
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:34
#8  Baloo::PostingCodec::decode (this=this@entry=0x7f4db3377a77, arr=...) at
./src/codecs/postingcodec.cpp:42
#9  0x7f4dbd4c93e4 in Baloo::PostingDB::get
(this=this@entry=0x7f4db3377b60, term=...) at ./src/engine/postingdb.cpp:100
#10 0x7f4dbd4d5060 in Baloo::WriteTransaction::commit (this=0x7f4dac035160)
at ./src/engine/writetransaction.cpp:259

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

[frameworks-baloo] [Bug 396218] Crash on log-in

2018-08-07 Thread Brett Keller
https://bugs.kde.org/show_bug.cgi?id=396218

--- Comment #2 from Brett Keller  ---
Created attachment 114363
  --> https://bugs.kde.org/attachment.cgi?id=114363&action=edit
New crash information added by DrKonqi

baloo_file (5.44.0) using Qt 5.9.5

- What I was doing when the application crashed:

Noticed this just after untarring a file via Dolphin's context menu, but this
was not long after login, so it may have simply been triggered by login.

-- Backtrace (Reduced):
#6  __memmove_avx_unaligned_erms () at
../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:370
#7  0x7f4dbd4d7973 in memcpy (__len=2050, __src=,
__dest=) at
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:34
#8  Baloo::PostingCodec::decode (this=this@entry=0x7f4db3377a77, arr=...) at
./src/codecs/postingcodec.cpp:42
#9  0x7f4dbd4c93e4 in Baloo::PostingDB::get
(this=this@entry=0x7f4db3377b60, term=...) at ./src/engine/postingdb.cpp:100
#10 0x7f4dbd4d5060 in Baloo::WriteTransaction::commit (this=0x7f4dac035160)
at ./src/engine/writetransaction.cpp:259

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

[frameworks-baloo] [Bug 396218] Crash on log-in

2018-08-07 Thread Brett Keller
https://bugs.kde.org/show_bug.cgi?id=396218

Brett Keller  changed:

   What|Removed |Added

 CC||blkel...@comcast.net

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

[frameworks-baloo] [Bug 396218] Crash on log-in

2018-07-18 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=396218

kde-b...@sufrin.org changed:

   What|Removed |Added

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

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