Package: tracker Version: 2.1.6-1 Followup-For: Bug #910579 I confirm this happens in testing and is quite annoying. It's a regression that was introduced recently because I didn't notice that problem before. My last upgrade was from 2.0.3-3 to 2.1.6-1.
I also confirm the workaround fixes the issue. Another workaround is, of course: systemctl --user stop tracker-store.service systemctl --user disable tracker-store.service :) -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental'), (1, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE=fr_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tracker depends on: ii dbus-user-session [default-dbus-session-bus] 1.12.10-1 ii dbus-x11 [dbus-session-bus] 1.12.10-1 ii dconf-gsettings-backend [gsettings-backend] 0.30.1-1 ii libc6 2.27-8 ii libglib2.0-0 2.58.1-2 ii libglib2.0-bin 2.58.1-2 ii libtracker-control-2.0-0 2.1.6-1 ii libtracker-sparql-2.0-0 2.1.6-1 ii shared-mime-info 1.10-1 Versions of packages tracker recommends: ii tracker-miner-fs 2.1.5-1 tracker suggests no packages. -- debconf-show failed
