Comment 7 for bug 1605882

Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libqt5widgets5 version 5.7.0+dfsg-1+16.04+build5 required, but 5.5.1+dfsg-17ubuntu2~2 is available
no debug symbol package found for xdg-user-dirs
libqt5svg5 version 5.7.0-0neon+16.04+build2 required, but 5.5.1-2build1 is available
libqt5dbus5 version 5.7.0+dfsg-1+16.04+build5 required, but 5.5.1+dfsg-17ubuntu2~2 is available
libqt5script5 version 5.7.0+dfsg-0neon+16.04+build3 required, but 5.5.1+dfsg-2build1 is available
no debug symbol package found for sed
libqt5core5a version 5.7.0+dfsg-1+16.04+build5 required, but 5.5.1+dfsg-17ubuntu2~2 is available
libqt5xml5 version 5.7.0+dfsg-1+16.04+build5 required, but 5.5.1+dfsg-17ubuntu2~2 is available
libqt5network5 version 5.7.0+dfsg-1+16.04+build5 required, but 5.5.1+dfsg-17ubuntu2~2 is available
package libpng12-0 does not exist, ignoring
package qt5-gtk-platformtheme does not exist, ignoring
no debug symbol package found for debianutils
package libicu55 does not exist, ignoring
libqt5gui5 version 5.7.0+dfsg-1+16.04+build5 required, but 5.5.1+dfsg-17ubuntu2~2 is available
adwaita-icon-theme version 3.18.0+p16.04+git20160603.1312 required, but 3.18.0-2ubuntu4 is available
no debug symbol package found for libavahi-common-data
no debug symbol package found for perl-base
no debug symbol package found for libflac8
libqt5network5 version 5.7.0+dfsg-1+16.04+build5 required, but 5.5.1+dfsg-17ubuntu2~2 is available
libqt5svg5 version 5.7.0-0neon+16.04+build2 required, but 5.5.1-2build1 is available
no debug symbol package found for libwebp5
libqt5gui5 version 5.7.0+dfsg-1+16.04+build5 required, but 5.5.1+dfsg-17ubuntu2~2 is available

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!