window-stack-bridge crashed with SIGABRT in QMessageLogger::fatal()

Bug #1753393 reported by Thomas A. F. Thorne
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
hud (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

After powering on my PC and logging in I was presented with two automated error reporting windows. The first led me to +bug1748844 the second prompted me to create a new error reporting message. By the time this second report happened I had Google Chrome and Synergy running.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: hud 14.10+16.04.20160415-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Mon Mar 5 08:20:42 2018
ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge
InstallationDate: Installed on 2017-11-16 (108 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge
ProcEnviron:
 PATH=(custom, user)
 SHELL=/bin/bash
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
 XDG_RUNTIME_DIR=<set>
Signal: 6
SourcePackage: hud
StacktraceTop:
 QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5
 QObjectPrivate::QObjectPrivate(int) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
 ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
 QDBusAbstractInterface::QDBusAbstractInterface(QString const&, QString const&, char const*, QDBusConnection const&, QObject*) () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
 QDBusConnectionInterface::QDBusConnectionInterface(QDBusConnection const&, QObject*) () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
Title: window-stack-bridge crashed with SIGABRT in QMessageLogger::fatal()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo
upstart.hud.log:
 This application failed to start because it could not find or load the Qt platform plugin "minimal"
 in "".

 Reinstalling the application may fix this problem.

Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in hud (Ubuntu):
status: New → Invalid
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:

no debug symbol package found for debianutils
no debug symbol package found for perl-base
no debug symbol package found for debianutils
no debug symbol package found for perl-base

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!

tags: removed: need-amd64-retrace
Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :

The problem happened again this morning.

As requested above I have filed a new report at #1756835. Hopefully this will include more useful diagnostic information.

information type: Private → Public
Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :

Changing report to Public so that others can see it.

Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :

Would +bug1756835 work better as a link?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.