pasted crashed with SIGABRT in qt_message_fatal()

Bug #1666472 reported by dinamic
46
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Libertine
Status tracked in Devel
Devel
Fix Committed
Medium
Christopher Townsend
Trunk
Fix Committed
Medium
Christopher Townsend
libertine (Ubuntu)
Fix Released
Medium
Christopher Townsend

Bug Description

pasted crashed with SIGABRT in QMessageLogger::fatal()

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: libertine-xmir-tools 1.6+17.04.20170209-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
Uname: Linux 4.10.0-9-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Tue Feb 21 12:40:50 2017
ExecutablePath: /usr/bin/pasted
InstallationDate: Installed on 2016-12-12 (70 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161108)
ProcCmdline: pasted
Signal: 6
SourcePackage: libertine
StacktraceTop:
 QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
 QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, char const*) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
 QXcbIntegration::QXcbIntegration(QStringList const&, int&, char**) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
 ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
 QPlatformIntegrationFactory::create(QString const&, QStringList const&, int&, char**, QString const&) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
Title: pasted crashed with SIGABRT in QMessageLogger::fatal()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Related branches

Revision history for this message
dinamic (dinamic6661) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 qt_message_fatal (context=..., message=<synthetic pointer>) at global/qlogging.cpp:1682
 QMessageLogger::fatal (this=this@entry=0x7ffd292ca7a0, msg=msg@entry=0x7f16ac63fd40 "QXcbConnection: Could not connect to display %s") at global/qlogging.cpp:793
 QXcbConnection::QXcbConnection (this=0x5578e4344e60, nativeInterface=0x5578e4336f30, canGrabServer=<optimized out>, defaultVisualId=<optimized out>, displayName=<optimized out>) at qxcbconnection.cpp:595
 QXcbIntegration::QXcbIntegration (this=<optimized out>, parameters=..., argc=@0x7ffd292cad8c: 1, argv=0x7ffd292cafd8) at qxcbintegration.cpp:186
 QXcbIntegrationPlugin::create (this=<optimized out>, system=..., parameters=..., argc=@0x7ffd292cad8c: 1, argv=0x7ffd292cafd8) at qxcbmain.cpp:56

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 libertine (Ubuntu):
importance: Undecided → Medium
summary: - pasted crashed with SIGABRT in QMessageLogger::fatal()
+ pasted crashed with SIGABRT in qt_message_fatal()
tags: removed: need-amd64-retrace
Revision history for this message
Christopher Townsend (townsend) wrote :

I'm pretty sure this occurs when closing an application. What happens is that ubuntu-app-launch is not very nice when closing X apps and will just kill Xmir out from underneath the applications. pasted sees that the X server is gone and produces this crash.

I have been working on moving all of the Xmir handling into Libertine and out of ubuntu-app-launch. When that is complete, Libertine will be responsible for killing Xmir, at which point, we can shut it down after all applications needing the display have closed.

information type: Private → Public
Changed in libertine (Ubuntu):
status: New → Triaged
Revision history for this message
dinamic (dinamic6661) wrote :

i don't remember what exactly i've done to trigger this bug :) usually i see the automated reports when i log into unity7. from what i remember recently i see a lot of app freezes while using libertine, for ex with geany, open a child window (help/about) select, copy the info text, paste into geany. geany freezes and then i'm force to close the window and then i see Xmir 100% CPU in top. i think this is triggering this bug

Revision history for this message
Christopher Townsend (townsend) wrote :

After further analysis, it appears xmir is failing to start, yet pasted is getting started and fails to find the x server and crashes.

An interim solution is to check first if the x server, ie, xmir is running before trying to open the DISPLAY in pasted and if it's not, fail gracefully instead of crashing.

The longer term solution is the luancher should check that Xmir starts successfully before moving on and launching pasted and the intended application.

Revision history for this message
Libertine CI Bot (libertine-ci-bot) wrote :

Fix committed into lp:libertine at revision 443, scheduled for release in libertine, milestone Unknown

Changed in libertine:
status: In Progress → Fix Committed
Changed in libertine (Ubuntu):
status: Triaged → In Progress
assignee: nobody → Christopher Townsend (townsend)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libertine - 1.7.1+17.04.20170331-0ubuntu1

---------------
libertine (1.7.1+17.04.20170331-0ubuntu1) zesty; urgency=medium

  [ Chris Townsend ]
  * When starting pasted, ensure DISPLAY is set and valid before continuing to
    run. (LP: #1666472)
  * Fix pasted to work with rootless Xmir. (LP: #1671257)
  * Add a '-x' option to pkill so it only kills the libertined process(es)
    and nothing else. (LP: #1676005)
  * Remove hard-coded dependency on libraries.

  [ Larry Price ]
  * Bump version to 1.7.1
  * Gracefully handle creating a LibertineContainer object when the container
    backend is unavailable.
  * Update libertine xmir components to not depend on container backends.
    (LP: #1671938)
  * Catch all errors and gracefully shutdown libertined. (LP: #1671009)
  * Fix method call from ContainerControl d-bus to interfaces.
  * Update signal handlers in test_libertine_service to reflect new API.
  * Inject client for accessing ContainerControl within containers.
  * Rearchitect libertine service python backend for simpler access to running
    tasks. (LP: #1669091)
  * Ignore completions from dependencies during snapcraft build.
  * LXD needs to forward host environment to container when running arbitrary
    commands.
  * Add client object to list_app_ids_task to avoid making reentrant service
    calls.
  * Take advantage of new network subcommand during lxd init on newer
    installs.
  * Prevent installing empty package names and appropriately update status for
    unstopped containers.
  * Modifications to make test_libertine_service more stable.
  * Reopen the database file after every failure to grab the lock.
    (LP: #1662655)

 -- Larry Price <email address hidden> Fri, 31 Mar 2017 20:09:39 +0000

Changed in libertine (Ubuntu):
status: In Progress → Fix Released
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.