[frameworks-baloo] [Bug 389848] baloo_file crashes in mdb_put() in LMDB

[Steven Swart]

https://bugs.kde.org/show_bug.cgi?id=389848

--- Comment #165 from Steven Swart  ---
Good day, all!

Sad to report that after a "zypper dup" and reboot yesterday, still
got the same error.

I couldn't report the stacktrace via the OS reporting mechanism, the
message said that there was no email address associated with the
component.

Kind regards,
Steven.

On Wed, 28 Oct 2020 at 16:36, Steven Swart  wrote:
>
> Hi All!
>
> I am on this thread because I reported the same bug. Since then, there
> have been a lot of duplicates.
>
> On my side, I am running OpenSUSE Tumbleweed on my media server. It's
> a rolling release, and there are frequent updates, pretty much daily,
> most of the time.
>
> Many of these updates require a reboot.
>
> I was only ever getting this problem after I had run a distribution
> update -"zypper dup", and then rebooted.
>
> For a while, I was frequently getting the same error, but not every
> time. I don't recall seeing it for the past few weeks. I will report
> it if I see it again.
>
> Tumbleweed is pretty bleeding-edge as far as the kernel and system
> libraries are concerned, I think SUSE uses us a beta-testers for their
> commercial platforms.
>
> But, this being the case, there is a possibility that the bug has
> already been fixed, and just needs to roll out to the majority of
> distros.
>
> Kind regards,
> Steven.
>
> On Wed, 28 Oct 2020 at 16:21, Papoteur  wrote:
> >
> > https://bugs.kde.org/show_bug.cgi?id=389848
> >
> > --- Comment #162 from Papoteur  ---
> > On my side, I have luks encrypted home partition, too. The index file is 1Go
> > heavy and is on a professional computer, thus I can't deliver it.
> >
> > --
> > You are receiving this mail because:
> > You are on the CC list for the bug.

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

[frameworks-baloo] [Bug 389848] baloo_file crashes in mdb_put() in LMDB

[Steven Swart]

https://bugs.kde.org/show_bug.cgi?id=389848

--- Comment #163 from Steven Swart  ---
Hi All!

I am on this thread because I reported the same bug. Since then, there
have been a lot of duplicates.

On my side, I am running OpenSUSE Tumbleweed on my media server. It's
a rolling release, and there are frequent updates, pretty much daily,
most of the time.

Many of these updates require a reboot.

I was only ever getting this problem after I had run a distribution
update -"zypper dup", and then rebooted.

For a while, I was frequently getting the same error, but not every
time. I don't recall seeing it for the past few weeks. I will report
it if I see it again.

Tumbleweed is pretty bleeding-edge as far as the kernel and system
libraries are concerned, I think SUSE uses us a beta-testers for their
commercial platforms.

But, this being the case, there is a possibility that the bug has
already been fixed, and just needs to roll out to the majority of
distros.

Kind regards,
Steven.

On Wed, 28 Oct 2020 at 16:21, Papoteur  wrote:
>
> https://bugs.kde.org/show_bug.cgi?id=389848
>
> --- Comment #162 from Papoteur  ---
> On my side, I have luks encrypted home partition, too. The index file is 1Go
> heavy and is on a professional computer, thus I can't deliver it.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

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

[frameworks-baloo] [Bug 419917] New: Baloo crash on OpenSUSE Tumbleweed after zypper dup and reboot

[Steven Swart]

https://bugs.kde.org/show_bug.cgi?id=419917

Bug ID: 419917
   Summary: Baloo crash on OpenSUSE Tumbleweed after zypper dup
and reboot
   Product: frameworks-baloo
   Version: 5.68.0
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: Baloo File Daemon
  Assignee: stefan.bru...@rwth-aachen.de
  Reporter: steven.sw...@gmail.com
  Target Milestone: ---

Application: baloo_file (5.68.0)

Qt Version: 5.14.1
Frameworks Version: 5.68.0
Operating System: Linux 5.1.0-rc4-1.g1478096-default x86_64
Windowing system: X11
Distribution: "openSUSE Tumbleweed"

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

Rebooting the system after a distribution upgrade.

> sudo zypper dup

Then rebooting my box.

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8956db1c80 (LWP 1392))]

Thread 3 (Thread 0x7f8951a02700 (LWP 2031)):
[KCrash Handler]
#6  0x7f8956a1 in raise () from /lib64/libc.so.6
#7  0x7f8956ed853d in abort () from /lib64/libc.so.6
#8  0x7f89558a3543 in mdb_assert_fail.constprop.0 (env=0x55eb38c5bc10,
expr_txt=expr_txt@entry=0x7f89558a5477 "rc == 0",
func=func@entry=0x7f89558a59a0 <__func__.7217> "mdb_page_dirty",
line=line@entry=2127, file=0x7f89558a5010 "mdb.c") at mdb.c:1542
#9  0x7f89558a1bd5 in mdb_page_dirty (mp=,
txn=0x55eb38c5d010) at mdb.c:2114
#10 mdb_page_dirty (txn=0x55eb38c5d010, mp=) at mdb.c:2114
#11 0x7f895589ad06 in mdb_page_alloc.isra.0.lto_priv.0 (num=, mp=0x7f8951a00fc8, mc=) at mdb.c:2308
#12 0x7f89558a21b3 in mdb_page_touch (mc=0x7f8951a01510) at mdb.c:2495
#13 0x7f8955899c5c in mdb_cursor_touch (mc=mc@entry=0x7f8951a01510) at
mdb.c:6523
#14 0x7f895589c67d in mdb_cursor_put (mc=mc@entry=0x7f8951a01510,
key=key@entry=0x7f8951a01910, data=data@entry=0x7f8951a01900, flags=, flags@entry=0) at mdb.c:6657
#15 0x7f895589f5bb in mdb_put (txn=0x55eb38c5d010, dbi=5,
key=key@entry=0x7f8951a01910, data=data@entry=0x7f8951a01900,
flags=flags@entry=0) at mdb.c:9022
#16 0x7f8956ca355f in Baloo::DocumentDB::put (this=0x7f8951a01a50,
docId=, list=...) at
/usr/src/debug/baloo5-5.68.0-1.2.x86_64/src/engine/documentdb.cpp:79
#17 0x7f8956c8faa2 in Baloo::WriteTransaction::addDocument
(this=0x7f4944004e10, doc=...) at
/usr/src/debug/baloo5-5.68.0-1.2.x86_64/src/engine/writetransaction.cpp:70
#18 0x7f8956c8faee in Baloo::Transaction::addDocument (doc=...,
this=this@entry=0x7f8951a01b80, this=this@entry=0x7f8951a01b80, doc=...) at
/usr/src/debug/baloo5-5.68.0-1.2.x86_64/src/engine/transaction.cpp:254
#19 0x55eb38711adc in Baloo::UnindexedFileIndexer::run
(this=0x55eb38d1f7e0) at /usr/include/qt5/QtCore/qrefcount.h:60
#20 0x7f89566f3802 in QThreadPoolThread::run (this=0x55eb38d1aaf0) at
thread/qthreadpool.cpp:99
#21 0x7f89566f0698 in QThreadPrivate::start (arg=0x55eb38d1aaf0) at
thread/qthread_unix.cpp:342
#22 0x7f8955903efa in start_thread () from /lib64/libpthread.so.0
#23 0x7f8956fb23bf in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f895252a700 (LWP 1423)):
#0  0x7f8956fa34fc in read () from /lib64/libc.so.6
#1  0x7f89550bc21f in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f8955074e97 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f89550752e2 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f895507545f in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f895691cc0b in QEventDispatcherGlib::processEvents
(this=0x7f894c000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7f89568c4b9b in QEventLoop::exec (this=this@entry=0x7f8952529d70,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:136
#7  0x7f89566ef5ce in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:118
#8  0x7f8956ccb507 in ?? () from /usr/lib64/libQt5DBus.so.5
#9  0x7f89566f0698 in QThreadPrivate::start (arg=0x7f8956d4dda0) at
thread/qthread_unix.cpp:342
#10 0x7f8955903efa in start_thread () from /lib64/libpthread.so.0
#11 0x7f8956fb23bf in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f8956db1c80 (LWP 1392)):
#0  0x7f8956fa7acf in poll () from /lib64/libc.so.6
#1  0x7f895507533e in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f895507545f in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f895691cc0b in QEventDispatcherGlib::processEvents
(this=0x55eb38c44880, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f89568c4b9b in QEventLoop::exec (this=this@entry=0x7ffc88240230,
flags=..., flags@entry=...) at