Bug#932808: baloo-kf5: Upon start baloo crashes with Segmentation fault following upgrade to buster

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#932808: baloo-kf5: Upon start baloo crashes with Segmentation fault following upgrade to buster

Leos Pohl
Package: baloo-kf5
Version: 5.54.0-1
Severity: important

Dear Maintainer,

After upgrade to buster (From stretch), every time system starts, baloo
crashess with Executable: baloo_file PID: xxx Signal: Segmentation fault (11).

When I try to enable baloo from terminal, I get:
user@host:~$ balooctl enable
Enabling the File Indexer
user@host:~$ KCrash: Attempting to start /usr/bin/baloo_file from kdeinit
sock_file=/run/user/1000/kdeinit5__0
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = baloo_file path = /usr/bin pid = 6657
KCrash: Arguments: /usr/bin/baloo_file
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0
QSocketNotifier: Invalid socket 9 and type 'Read', disabling...
QSocketNotifier: Invalid socket 12 and type 'Exception', disabling...
QSocketNotifier: Invalid socket 11 and type 'Read', disabling...
QSocketNotifier: Invalid socket 14 and type 'Read', disabling...
QSocketNotifier: Invalid socket 5 and type 'Read', disabling...
QSocketNotifier: Invalid socket 10 and type 'Read', disabling...

This is specifically related to upgrade to Buster. No other issues can
be observed after the update (like reported in similar bugs)


-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages baloo-kf5 depends on:
ii  kio                  5.54.1-1
ii  libc6                2.28-10
ii  libkf5baloo5         5.54.0-1
ii  libkf5balooengine5   5.54.0-1
ii  libkf5configcore5    5.54.0-1
ii  libkf5coreaddons5    5.54.0-1
ii  libkf5crash5         5.54.0-1
ii  libkf5dbusaddons5    5.54.0-1
ii  libkf5filemetadata3  5.54.0-1
ii  libkf5i18n5          5.54.0-1
ii  libkf5idletime5      5.54.0-1
ii  libkf5kiocore5       5.54.1-1
ii  libkf5solid5         5.54.0-1
ii  libqt5core5a         5.11.3+dfsg1-1
ii  libqt5dbus5          5.11.3+dfsg1-1
ii  libqt5gui5           5.11.3+dfsg1-1
ii  libqt5qml5           5.11.3-4
ii  libqt5widgets5       5.11.3+dfsg1-1
ii  libstdc++6           8.3.0-6

baloo-kf5 recommends no packages.

baloo-kf5 suggests no packages.

-- no debconf information

Reply | Threaded
Open this post in threaded view
|

Bug#932808: baloo-kf5: Upon start baloo crashes with Segmentation fault following upgrade to buster

Bernhard Übelacker-3
Control: tags -1 + moreinfo


Hello Leos Pohl,
you write when you execute "balooctl enable" you receive
some lines starting with "KCrash: ...".

When this happened, is there a small sad smiley [1] in the
system tray (normally at the bottom, left of the clock)?
If yes, you should receive by clicking on that a text describing
where the crash happened, which you could forward to this bug.

Kind regards,
Bernhard

[1] https://sources.debian.org/data/main/b/breeze-icons/4:5.54.0-1/icons/actions/16/tools-report-bug.svg

Reply | Threaded
Open this post in threaded view
|

Bug#932808: Fwd: Bug#932808: baloo-kf5: Upon start baloo crashes with Segmentation fault following upgrade to buster

Bernhard Übelacker-3
In reply to this post by Leos Pohl

-------- Weitergeleitete Nachricht --------
Datum: Wed, 7 Aug 2019 15:44:44 -0400
Von: Leoš Pohl



Hello Bernhard,

since I could not find a way to forward the report directly
to this bug, please find screenshots here
https://snag.gy/mpTyWe.jpg and here https://snag.gy/lUKpRc.jpg
and the copied report from the second tab is below.


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

Thread 3 (Thread 0x7fad6bb57700 (LWP 8617)):
[KCrash Handler]
#6  0x00007fad70df671b in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#7  0x00007fad7178405d in ?? () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#8  0x00007fad71771679 in Baloo::PostingDB::get(QByteArray const&) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#9  0x00007fad717818ca in Baloo::WriteTransaction::commit() () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#10 0x00007fad71777ea2 in Baloo::Transaction::commit() () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#11 0x000055f4dcf68f0d in ?? ()
#12 0x00007fad7121d021 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007fad71224aa7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007fad6fdadfa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#15 0x00007fad70d934cf in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 2 (Thread 0x7fad6c68a700 (LWP 8616)):
#0  0x00007fad70d88819 in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007fad6f4e3136 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fad6f4e325c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fad7141d87b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007fad713cb27b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007fad7121aec6 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007fad717a3545 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x00007fad71224aa7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007fad6fdadfa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#9  0x00007fad70d934cf in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 1 (Thread 0x7fad6cbec400 (LWP 8615)):
#0  0x00007fad70d88819 in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007fad6f4e3136 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fad6f4e325c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fad7141d87b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007fad713cb27b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007fad713d3262 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x000055f4dcf63987 in ?? ()
#7  0x00007fad70cbe09b in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
#8  0x000055f4dcf63b2a in ?? ()
[Inferior 1 (process 8615) detached]

Reply | Threaded
Open this post in threaded view
|

Bug#932808: baloo-kf5: Upon start baloo crashes with Segmentation fault following upgrade to buster

Bernhard Übelacker-3
Hello Leoš Pohl,
thanks for the additional information.

Please use the reply-all in your email program, to have
the ...@bugs.debian.org recipient in every answer, so
the debian bug tracker receives the messages too.

Just for future crashes (or if the Mainainter will requests it),
if you install the debug symbol packages, like described in [1],
the backtrace you can receive from DrKonqi gets way better,
and would e.g. already show the line information.

In your case these packages would be helpful:
    baloo-kf5-dbgsym libkf5balooengine5-dbgsym

Kind regards,
Bernhard

[1] https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols

Reply | Threaded
Open this post in threaded view
|

Bug#932808: baloo-kf5: Upon start baloo crashes with Segmentation fault following upgrade to buster

Bernhard Übelacker-3
Control: tags -1 - moreinfo



Dear Maintainer,
I think the top frames with debug symbols would look like this:

    (gdb) bt
    #0  memcpy () in ?? () from /lib/x86_64-linux-gnu/libc.so.6
    #1  0x00007feaa926d05d in Baloo::PostingCodec::decode () at ./src/codecs/postingcodec.cpp:42
    #2  0x00007feaa925a679 in Baloo::PostingDB::get () at ./src/engine/postingdb.cpp:100
    #3  0x00007feaa926a8ca in Baloo::WriteTransaction::commit () at ./src/engine/writetransaction.cpp:275
    #4  0x00007feaa9260ea2 in Baloo::Transaction::commit () at ./src/engine/transaction.cpp:269
    ...

This seems to point to upstream bug report [1].

The return value of function e.g. mdb_get might
not be checked enough.

An attempt to solve this seems to be commit [2].

Kind regards,
Bernhard


[1] https://bugs.kde.org/show_bug.cgi?id=367480
[2] https://cgit.kde.org/baloo.git/commit/src/engine/postingdb.cpp?id=eb68430ae5f4fc4c4a2e5b1798683ff6a639ad3d