Yes, apparently this issue is known upstream, this makes baloo useless in i386, and of limited use in amd64.
Also baloo upstream needs a new maintainer, my recommendation is to stop using it. :-( We should probably try to remove it from stretch. On October 6, 2016 3:15:57 PM GMT+02:00, "Hans-J. Ullrich" <hans.ullr...@loop.de> wrote: >Package: baloo-kf5 >Version: 5.26.0-1 >Followup-For: Bug #835562 > >Dear Maintainer, > >just want to inform you, that the bug is still existent in the latest >version. > >Thanks for reading this. > >Best regards > >Hans > >-- System Information: >Debian Release: stretch/sid > APT prefers testing > APT policy: (500, 'testing'), (500, 'stable') >Architecture: i386 (i686) > >Kernel: Linux 4.7.0-1-686-pae (SMP w/2 CPU cores) >Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) >Shell: /bin/sh linked to /bin/dash >Init: systemd (via /run/systemd/system) > >Versions of packages baloo-kf5 depends on: >ii libc6 2.24-3 >ii libkf5baloo5 5.26.0-1 >ii libkf5balooengine5 5.26.0-1 >ii libkf5configcore5 5.26.0-1 >ii libkf5coreaddons5 5.26.0-1 >ii libkf5crash5 5.26.0-1 >ii libkf5dbusaddons5 5.26.0-1 >ii libkf5filemetadata3 5.26.0-1 >ii libkf5i18n5 5.26.0-1 >ii libkf5idletime5 5.26.0-1 >ii libkf5kiocore5 5.26.0-1 >ii libkf5solid5 5.26.0-1 >ii libqt5core5a 5.6.1+dfsg-3+b1 >ii libqt5dbus5 5.6.1+dfsg-3+b1 >ii libqt5gui5 5.6.1+dfsg-3+b1 >ii libqt5qml5 5.6.1-8 >ii libqt5widgets5 5.6.1+dfsg-3+b1 >ii libstdc++6 6.1.1-11 > >baloo-kf5 recommends no packages. > >baloo-kf5 suggests no packages. > >-- no debconf information -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
