tracker-extract crashed with SIGABRT in g_malloc0()

[starkus]

last update needed "sudo dpkg --configure -a" to continue.
something within systemd-sysv and systemd was corrupted
when i tried to install "apt apt-transport-https apt-utils aptdaemon aptdaemon-data gir1.2-gudev-1.0 gnome-calculator init init-system-helpers libapt-inst1.5 libapt-pkg4.12 libgudev-1.0-0 libpam-systemd libsystemd0 libsystemd0:i386 libudev1 libudev1:i386 libvlc5 libvlccore8 python-aptdaemon python-aptdaemon.gtk3widgets python3-aptdaemon python3-aptdaemon.gtk3widgets python3-aptdaemon.pkcompat systemd systemd-sysv udev vlc vlc-data vlc-nox vlc-plugin-fluidsynth vlc-plugin-jack vlc-plugin-notify vlc-plugin-pulse vlc-plugin-samba vlc-plugin-sdl" due to an update.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: tracker-extract 1.2.5-0ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
Uname: Linux 3.19.0-12-generic x86_64
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Tue Apr 7 19:57:19 2015
ExecutablePath: /usr/lib/tracker/tracker-extract
InstallationDate: Installed on 2014-08-23 (227 days ago)
InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
ProcCmdline: /usr/lib/tracker/tracker-extract
Signal: 6
SourcePackage: tracker
StacktraceTop:
 g_malloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slice_free1 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_queue_pop_tail () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: tracker-extract crashed with SIGABRT in g_malloc0()
UpgradeStatus: Upgraded to vivid on 2015-03-21 (17 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1364780, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.