Please try the package from https://download.opensuse.org/repositories/home:/StefanBruens:/branches:/openSUSE:/Leap:/15.1/standard/

Unfortunately I can only check if it does not break anything, but I already used some workaround to delete all baloo files, so I cannot reproduce the bug now. Will it be sufficient?

Tested (unfortunately) on clean baloo database and it works.

It would probably be good to do an update for Leap 15.0 (which comes with the exact same lmdb package) as well, see bug#1100080.

@ Wolfgang - unfortunately I can't do anything here, as lmdb is inherited from SLE.

@ Peter Varkoly - whats holding this up? The fix is from upstream, and can be directly applied to lmdb 0.9.17.

@ Peter - please answer the raised questions!

This has been open for more then a months now, a confirmed fix is available, but still no progress. This needs 5 minutes at most to finish up.

bug#1100080 has been open for a year now, without any progress.

I'm not the maintainer or lmdb and other openldap stuff anymore.
@dmueller can you have a look at this bug please.

And another week passes without any progress ...

*** Bug 1100080 has been marked as a duplicate of this bug. ***

Sory for delay! Thanks Stefan!
Update was started.

created request id 714434
created request id 714437

This is an autogenerated message for OBS integration:
This bug (1136132) was mentioned in
https://build.opensuse.org/request/show/714434 15.0 / lmdb
https://build.opensuse.org/request/show/714437 15.1 / lmdb

My error messages are slightly different from those above. But maybe it's the same error. Please check.
------------------------------------
Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe26f604900 (LWP 5016))]

Thread 3 (Thread 0x7fa25fcfa700 (LWP 5343)):
[KCrash Handler]
#6  0x00007fe26e5dc581 in ?? () from /usr/lib64/libKF5BalooEngine.so.5
#7  0x00007fe26e5bf661 in Baloo::DocumentDB::get(unsigned long long) () from /usr/lib64/libKF5BalooEngine.so.5
#8  0x00007fe26e5d99e8 in Baloo::WriteTransaction::replaceDocument(Baloo::Document const&, QFlags<Baloo::DocumentOperation>) () from /usr/lib64/libKF5BalooEngine.so.5
#9  0x00005644d0689e75 in ?? ()
#10 0x00007fe26da1fe22 in ?? () from /usr/lib64/libQt5Core.so.5
#11 0x00007fe26da22ced in ?? () from /usr/lib64/libQt5Core.so.5
#12 0x00007fe26adea569 in start_thread () from /lib64/libpthread.so.0
#13 0x00007fe26cfdb9ef in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fe26489a700 (LWP 5028)):
#0  0x00007fe26938eff4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x00007fe2693490ce in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007fe2693492bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007fe26dc5a96b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#4  0x00007fe26dbff90a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#5  0x00007fe26da1ddaa in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x00007fe26e8019e5 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x00007fe26da22ced in ?? () from /usr/lib64/libQt5Core.so.5
#8  0x00007fe26adea569 in start_thread () from /lib64/libpthread.so.0
#9  0x00007fe26cfdb9ef in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fe26f604900 (LWP 5016)):
#0  0x00007fe26cfd119b in poll () from /lib64/libc.so.6
#1  0x00007fe2693491a9 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007fe2693492bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007fe26dc5a96b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#4  0x00007fe26dbff90a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#5  0x00007fe26dc089b4 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x00005644d067f13c in ?? ()
#7  0x00007fe26cf03f8a in __libc_start_main () from /lib64/libc.so.6
#8  0x00005644d067f3aa in ?? ()
[Inferior 1 (process 5016) detached]

sorry, I forgot to mention that it happened on
Linux 4.12.14-lp151.28.7-default
NAME="openSUSE Leap"
VERSION="15.1 "
freshly installed.

Thanks for assigning to me, but I cannot do anything about it - I am not maintainer nor bugowner of that package and have no write permission in the parent project. I just happened to have touched the package two years ago. 

Klaus, are you still maintaining this?

(In reply to Peter Varkoly from comment #11)
> created request id 714434
> created request id 714437

I just accepted both review requests.

Thanks Peter !

I copied it over to SLE15 maintenance, which will then get inherited by Leap 15.

Whats the current state?
It is quite annoying to get another duplicate bugreport in KDE bugzilla every day. It also reflects badly on (open)SUSE having to wait 3 months for a bugfix.

Why was this patch declined? 
For what I see it did build without failure. 
https://build.opensuse.org/request/show/714437#request_history

But: declined?
I have Kontact crashing every day because of this, and the bugzilla kde is full of duplicates from opensuse user. So at least I would like to understand technically what is the issue.

> I have Kontact crashing every day because of this

Kontact does not use lmdb, neither through baloo nor directly ...

(In reply to Stefan Brüns from comment #21)
> > I have Kontact crashing every day because of this
> 
> Kontact does not use lmdb, neither through baloo nor directly ...

Oh, then forgive me my ignorance caused by circumstances. Here baloo indexer crashes, this causes (on my system) a memory hole that consumes all RAM then all SWAP, of course when you shutdown kontact (with kmail running) you see that kontact is a zombi process after the baloo crash and you also have to kill about 15 http.so processes that are lingering around. For a layperson that induces in error to thing your system gets down because of kontact. Instead it is just because it runs out of memory. 
So, since this is not the reason, but the baloo crash is deleterious per se, why has the patch been declined?

Maintenance, in case this needs even longer in the SLE maintenance queue, could the package be fast tracked to Leap maintenance please?

lmdb is already quite high in the QA queue, i would say it will be released within the next week.

SUSE-RU-2019:2357-1: An update that has one recommended fix can now be installed.

Category: recommended (moderate)
Bug References: 1136132
CVE References: 
Sources used:
SUSE Linux Enterprise Module for Open Buildservice Development Tools 15-SP1 (src):    lmdb-0.9.17-4.3.1
SUSE Linux Enterprise Module for Open Buildservice Development Tools 15 (src):    lmdb-0.9.17-4.3.1
SUSE Linux Enterprise Module for Basesystem 15-SP1 (src):    lmdb-0.9.17-4.3.1

NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.

openSUSE-RU-2019:2141-1: An update that has one recommended fix can now be installed.

Category: recommended (moderate)
Bug References: 1136132
CVE References: 
Sources used:
openSUSE Leap 15.1 (src):    lmdb-0.9.17-lp151.4.3.1

openSUSE-RU-2019:2165-1: An update that has one recommended fix can now be installed.

Category: recommended (moderate)
Bug References: 1136132
CVE References: 
Sources used:
openSUSE Leap 15.0 (src):    lmdb-0.9.17-lp150.3.3.1

openSUSE-RU-2019:2179-1: An update that has one recommended fix can now be installed.

Category: recommended (moderate)
Bug References: 1136132
CVE References: 
Sources used:
openSUSE Backports SLE-15 (src):    lmdb-0.9.17-bp150.3.3.1

.