touch-packages team mailing list archive

[Michał Sawicz <michal.sawicz@xxxxxxxxxxxxx>]

Something's wrong with the setup there, as it's trying to use the xcb
backend instead of Mir.

** Information type changed from Private to Public

** Changed in: unity8 (Ubuntu)
       Status: New => Incomplete

** Also affects: unity8-desktop-session (Ubuntu)
   Importance: Undecided
       Status: New

** Summary changed:

- unity8 crashed with SIGABRT in qt_message_fatal()
+ Wrong Qt backend used in desktop session (xcb vs. Mir)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1407556

Title:
  Wrong Qt backend used in desktop session (xcb vs. Mir)

Status in unity8 package in Ubuntu:
  Incomplete
Status in unity8-desktop-session package in Ubuntu:
  New

Bug description:
  I installed unity8-desktop-session-mir in my vmplayer vivid guest and
  tried logging into it, got only a black screen, and found a unity8
  crash file in the /var/crash afterwards.

  I also almost always (9 out of 10 times) get a black screen if I try
  to log into a ubuntu-desktop-mir session, and if I do manage to get a
  normal screen with ubuntu-desktop-mir, resizing it gives me the black
  screen. So this might be related to a bug in mir.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20141216.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  Date: Mon Jan  5 11:03:29 2015
  ExecutablePath: /usr/bin/unity8
  ExecutableTimestamp: 1418728702
  InstallationDate: Installed on 2015-01-03 (1 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141220)
  ProcCmdline: unity8
  ProcCwd: /home/rocko
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: unity8
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
   ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
   ?? () 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: unity8 crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  upstart.unity8.log:
   ()
   QXcbConnection: Could not connect to display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1407556/+subscriptions