-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2019-11-20 at 10:11 -0500, James Knott wrote:

On 15.1/KDE, there has long been a bug where on desktop startup, I get an error "Baloo File Indexing Daemon closed unexpectedly".  I recall seeing some discussion about that here and it was being worked on.  This "feature" has now appeared on a system running 15.0.  Is there anything happening with this?  I don't see any mention about this issue in bugzilla.

I was about to report it and forgot. Hopefully this evening. <1.7> 2019-11-18 15:52:38 Telcontar drkonqi 5475 - - Sending SIGCONT to process <1.4> 2019-11-18 15:52:38 Telcontar baloo_file 5230 - - QSocketNotifier: Invalid socket 9 and type 'Read', disabling... <1.4> 2019-11-18 15:52:38 Telcontar baloo_file 5230 - - QSocketNotifier: Invalid socket 5 and type 'Read', disabling... <1.4> 2019-11-18 15:52:38 Telcontar baloo_file 5230 - - QSocketNotifier: Invalid socket 12 and type 'Exception', disabling... <1.4> 2019-11-18 15:52:38 Telcontar baloo_file 5230 - - QSocketNotifier: Invalid socket 10 and type 'Read', disabling... <1.4> 2019-11-18 15:52:38 Telcontar baloo_file 5230 - - QSocketNotifier: Invalid socket 11 and type 'Read', disabling... <1.4> 2019-11-18 15:52:38 Telcontar baloo_file 5230 - - QSocketNotifier: Invalid socket 14 and type 'Read', disabling... <3.6> 2019-11-18 15:52:39 Telcontar systemd 1 - - Created slice system-systemd\x2dcoredump.slice. <3.6> 2019-11-18 15:52:39 Telcontar systemd 1 - - Started Process Core Dump (PID 5567/UID 0). <1.2> 2019-11-18 15:52:39 Telcontar systemd-coredump 5568 - - Process 5230 (baloo_file) of user 1000 dumped core.#012#012Stack trace of thread 5464:#012#0 0x00007f2d07ea7160 __GI_raise (libc.so.6)#012#1 0x00007f2d09c4d2f7 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5)#012#2 0x00007f2d07ea71e0 __restore_rt (libc.so.6)#012#3 0x00007f2d095413fb _ZN5Baloo12IdFilenameDB3getEy (libKF5BalooEngine.so.5)#012#4 0x00007f2d0953ad1f _ZNK5Baloo13DocumentUrlDB3getEy (libKF5BalooEngine.so.5)#012#5 0x00007f2d0954b734 _ZNK5Baloo11Transaction11documentUrlEy (libKF5BalooEngine.so.5)#012#6 0x00005565d084e71e n/a (baloo_file)#012#7 0x00007f2d089a1e22 n/a (libQt5Core.so.5)#012#8 0x00007f2d089a4ced n/a (libQt5Core.so.5)#012#9 0x00007f2d05d9e569 start_thread (libpthread.so.0)#012#10 0x00007f2d07f699ef __clone (libc.so.6)#012#012Stack trace of thread 5462:#012#0 0x00007f2d07f5f19b __GI___poll (libc.so.6)#012#1 0x00007f2d0431a1a9 g_main_context_poll (libglib-2.0.so.0)#012#2 0x00007f2d0431a2 bc g_main_context_iteration (libglib-2.0.so.0)#012#3 0x00007f2d08bdc96b _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)#012#4 0x00007f2d08b8190a _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)#012#5 0x00007f2d0899fdaa _ZN7QThread4execEv (libQt5Core.so.5)#012#6 0x00007f2d097729e5 n/a (libQt5DBus.so.5)#012#7 0x00007f2d089a4ced n/a (libQt5Core.so.5)#012#8 0x00007f2d05d9e569 start_thread (libpthread.so.0)#012#9 0x00007f2d07f699ef __clone (libc.so.6)#012#012Stack trace of thread 5230:#012#0 0x00007f2d07f5f19b __GI___poll (libc.so.6)#012#1 0x00007f2d0431a1a9 g_main_context_poll (libglib-2.0.so.0)#012#2 0x00007f2d0431a2bc g_main_context_iteration (libglib-2.0.so.0)#012#3 0x00007f2d08bdc96b _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)#012#4 0x00007f2d08b8190a _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)#012#5 0x00007f2 d08b8a9b4 _ZN16QCoreApplication4execEv (libQt5Core.so..5)#012#6 0x00005565d084213c n/a (baloo_file)#012#7 0x00007f2d07e91f8a __libc_start_main (libc.so.6)#012#8 0x00005565d08423aa n/a (baloo_file) I should be able to obtain data from that coredump. - -- Cheers, Carlos E. R. (from openSUSE 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXdVZZxwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVSD8AnROhmFbJNK140Ey/UOWP IQPn4flkAJ9wvXK/oVyHEgwBVtn/SJzjP4SvNg== =335W -----END PGP SIGNATURE-----