Bug 420615 - Baloo chashed after logging in into account
Summary: Baloo chashed after logging in into account
Status: RESOLVED DUPLICATE of bug 389848
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Baloo File Daemon (show other bugs)
Version: 5.68.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Stefan Brüns
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2020-04-26 11:41 UTC by Eugene
Modified: 2020-09-01 01:30 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (5.44 KB, patch)
2020-09-01 01:30 UTC, Leandro
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Eugene 2020-04-26 11:41:23 UTC
Application: baloo_file (5.68.0)

Qt Version: 5.12.8
Frameworks Version: 5.68.0
Operating System: Linux 5.6.6-050606-generic x86_64
Windowing system: X11
Distribution: Ubuntu 20.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:

Just logged in in my system account when Ballo chash notification appeared.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__GI___libc_read (nbytes=16, buf=0x7fffcd214040, fd=3) at ../sysdeps/unix/sysv/linux/read.c:26
[Current thread is 1 (Thread 0x7f3b15d04c80 (LWP 1307))]

Thread 3 (Thread 0x7f3b14985700 (LWP 1414)):
[KCrash Handler]
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#7  0x00007f3b19596859 in __GI_abort () at abort.c:79
#8  0x00007f3b18c18a83 in mdb_assert_fail (env=0x555ee195cc80, expr_txt=expr_txt@entry=0x7f3b18c1b02f "rc == 0", func=func@entry=0x7f3b18c1b978 <__func__.7221> "mdb_page_dirty", line=line@entry=2127, file=0x7f3b18c1b010 "mdb.c") at mdb.c:1542
#9  0x00007f3b18c0d6d5 in mdb_page_dirty (mp=<optimized out>, txn=0x555ee196dd10) at mdb.c:2114
#10 mdb_page_dirty (txn=0x555ee196dd10, mp=<optimized out>) at mdb.c:2114
#11 0x00007f3b18c0e966 in mdb_page_alloc (num=num@entry=1, mp=mp@entry=0x7f3b14984048, mc=<optimized out>) at mdb.c:2308
#12 0x00007f3b18c0eba3 in mdb_page_touch (mc=mc@entry=0x7f3b14984580) at mdb.c:2495
#13 0x00007f3b18c107ec in mdb_cursor_touch (mc=mc@entry=0x7f3b14984580) at mdb.c:6523
#14 0x00007f3b18c138f9 in mdb_cursor_put (mc=mc@entry=0x7f3b14984580, key=key@entry=0x7f3b14984970, data=data@entry=0x7f3b14984980, flags=flags@entry=0) at mdb.c:6657
#15 0x00007f3b18c1676b in mdb_put (txn=0x555ee196dd10, dbi=5, key=key@entry=0x7f3b14984970, data=data@entry=0x7f3b14984980, flags=flags@entry=0) at mdb.c:9022
#16 0x00007f3b1a0ef4c5 in Baloo::DocumentDB::put (this=this@entry=0x7f3b14984a70, docId=<optimized out>, docId@entry=34822310640746548, list=...) at ./src/engine/documentdb.cpp:79
#17 0x00007f3b1a120588 in Baloo::WriteTransaction::addDocument (this=0x555ee19c1e10, doc=...) at ./src/engine/writetransaction.cpp:70
#18 0x00007f3b1a1138d7 in Baloo::Transaction::addDocument (this=<optimized out>, doc=...) at ./src/engine/transaction.cpp:254
#19 0x0000555ee079f0ca in ?? ()
#20 0x00007f3b19b54f82 in QThreadPoolThread::run (this=0x555ee19d1a10) at thread/qthreadpool.cpp:99
#21 0x00007f3b19b519d2 in QThreadPrivate::start (arg=0x555ee19d1a10) at thread/qthread_unix.cpp:361
#22 0x00007f3b18c7a609 in start_thread (arg=<optimized out>) at pthread_create.c:477
#23 0x00007f3b19693103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f3b15498700 (LWP 1317)):
#0  0x00007f3b1968696f in __GI___poll (fds=0x7f3b100029e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007f3b185681ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f3b185682e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f3b19d71583 in QEventDispatcherGlib::processEvents (this=0x7f3b10000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#4  0x00007f3b19d184db in QEventLoop::exec (this=this@entry=0x7f3b15497d70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140
#5  0x00007f3b19b50785 in QThread::exec (this=<optimized out>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120
#6  0x00007f3b1a147efa in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x00007f3b19b519d2 in QThreadPrivate::start (arg=0x7f3b1a1cad80) at thread/qthread_unix.cpp:361
#8  0x00007f3b18c7a609 in start_thread (arg=<optimized out>) at pthread_create.c:477
#9  0x00007f3b19693103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f3b15d04c80 (LWP 1307)):
#0  __GI___libc_read (nbytes=16, buf=0x7fffcd214040, fd=3) at ../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=3, buf=0x7fffcd214040, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24
#2  0x00007f3b185b089f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f3b18567cfe in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f3b18568152 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f3b185682e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007f3b19d71565 in QEventDispatcherGlib::processEvents (this=0x555ee1951ff0, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#7  0x00007f3b19d184db in QEventLoop::exec (this=this@entry=0x7fffcd214250, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140
#8  0x00007f3b19d20246 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:120
#9  0x0000555ee078d109 in ?? ()
#10 0x00007f3b195980b3 in __libc_start_main (main=0x555ee078cd70, argc=1, argv=0x7fffcd2145d8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffcd2145c8) at ../csu/libc-start.c:308
#11 0x0000555ee078d2be in ?? ()
[Inferior 1 (process 1307) detached]

Possible duplicates by query: bug 420414, bug 419917, bug 419788, bug 419346, bug 419172.

Reported using DrKonqi
Comment 1 Nate Graham 2020-04-27 21:47:00 UTC

*** This bug has been marked as a duplicate of bug 389848 ***
Comment 2 Leandro 2020-09-01 01:30:23 UTC
Created attachment 131333 [details]
New crash information added by DrKonqi

baloo_file (5.68.0) using Qt 5.12.8

- What I was doing when the application crashed:
I just logged in and when the desktop appeared drKonqi already appointed the baloo error.

- Unusual behavior I noticed:
baloo has been crashing for a while. It stop crashing for some time after following the steps appointed in comment 33 of the bug 389848, but returned after a few days.

- Custom settings of the application:
None custom settings were applied for baloo.

-- Backtrace (Reduced):
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#7  0x00007fe68cc65859 in __GI_abort () at abort.c:79
#8  0x00007fe68c2e7a83 in mdb_assert_fail (env=0x55a967ebfd90, expr_txt=expr_txt@entry=0x7fe68c2ea02f "rc == 0", func=func@entry=0x7fe68c2ea978 <__func__.7221> "mdb_page_dirty", line=line@entry=2127, file=0x7fe68c2ea010 "mdb.c") at mdb.c:1542
#9  0x00007fe68c2dc6d5 in mdb_page_dirty (mp=<optimized out>, txn=0x55a967ec0140) at mdb.c:2114
#10 mdb_page_dirty (txn=0x55a967ec0140, mp=<optimized out>) at mdb.c:2114