[regression] Unity8 is just a black screen on zesty

Bug #1651617 reported by Daniel van Vugt
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical System Image
Fix Released
Critical
Michał Sawicz
qtmir (Ubuntu)
Fix Released
Critical
Michał Sawicz

Bug Description

[regression] Unity8 no longer visible (just a black screen) on zesty, although the process is running...

Full unity8 log:

[2016-12-21:09:20:26.624] qtmir.screens: ScreensModel::ScreensModel
[2016-12-21 09:20:26.626872] mirplatform: Found graphics driver: mir:mesa-kms (version 0.25.0)
[2016-12-21 09:20:26.626907] mirplatform: Found graphics driver: mir:mesa-x11 (version 0.25.0)
[2016-12-21 09:20:26.627018] mirplatform: Found graphics driver: mir:stub-graphics (version 0.25.0)
[2016-12-21 09:20:26.627028] mirplatform: Found graphics driver: throw-on-creation (version 0.25.0)
[2016-12-21:09:20:26.627] qtmir.mir: MirServer created
[2016-12-21:09:20:26.627] qtmir.mir: Command line arguments passed to Qt: ("unity8", "--mode=full-shell")
[2016-12-21:09:20:26.628] QSocketNotifier: Can only be used with threads started with QThread
[2016-12-21 09:20:26.629763] mirserver: Starting
[2016-12-21 09:20:26.646283] mirserver: Using nested cursor
[2016-12-21 09:20:26.646812] mirserver: Initial display configuration:
[2016-12-21 09:20:26.646838] mirserver: Output 36: VGA disconnected
[2016-12-21 09:20:26.646843] mirserver: Output 39: DisplayPort disconnected
[2016-12-21 09:20:26.646846] mirserver: Output 45: HDMI-A disconnected
[2016-12-21 09:20:26.646850] mirserver: Output 48: DisplayPort connected, used
[2016-12-21 09:20:26.646856] mirserver: Physical size 24.0" 520x320mm
[2016-12-21 09:20:26.646860] mirserver: Current mode 1920x1200 59.95Hz
[2016-12-21 09:20:26.646863] mirserver: Preferred mode 1920x1200 59.95Hz
[2016-12-21 09:20:26.646866] mirserver: Logical position +0+0
[2016-12-21 09:20:26.646870] mirserver: Output 52: HDMI-A disconnected
[2016-12-21:09:20:26.646] qtmir.mir: PromptSessionListener::PromptSessionListener - this= PromptSessionListener(0x7fd54c1c09d0)
[2016-12-21:09:20:26.646] qtmir.mir: SessionListener::SessionListener - this= SessionListener(0x7fd54c1c0660)
[2016-12-21:09:20:26.647] qtmir.mir: MirWindowManagerImpl::MirWindowManagerImpl
[2016-12-21 09:20:26.647386] mirserver: Mir version 0.25.0
[2016-12-21:09:20:26.647] qtmir.screens: QtCompositor::start
[2016-12-21:09:20:26.656] qtmir.screens: ScreensModel::update
[2016-12-21:09:20:26.657] qtmir.sensor: Screen - nativeOrientation is: Qt::ScreenOrientation(LandscapeOrientation)
[2016-12-21:09:20:26.657] qtmir.sensor: Screen - initial currentOrientation is: Qt::ScreenOrientation(LandscapeOrientation)
[2016-12-21:09:20:26.659] qtmir.screens: Added Screen with id 48 and geometry QRect(0,0 1920x1200)
[2016-12-21:09:20:26.659] qtmir.screens: Screen::setMirDisplayBuffer Screen(0x5608b9ff8fd0) 0x7fd54c140a30 0x7fd54c140b80
[2016-12-21:09:20:26.659] qtmir.screens: =======================================
[2016-12-21:09:20:26.659] qtmir.screens: Screen(0x5608b9ff8fd0) - id: 48 geometry: QRect(0,0 1920x1200) window: 0x0 type: "DisplayPort" scale: 1
[2016-12-21:09:20:26.659] qtmir.screens: =======================================
[2016-12-21:09:20:26.725] qtmir.applications: UnityApplicationPlugin::registerTypes - this= UnityApplicationPlugin(0x7fd5340ee440) uri= Unity.Application
[2016-12-21:09:20:26.758] QObject::connect: No such signal QDBusAbstractInterface::FlightModeChanged(bool) in /build/telephony-service-GdIWd2/telephony-service-0.1+17.04.20161129/libtelephonyservice/telepathyhelper.cpp:99
[2016-12-21:09:20:27.365] file:///usr/share/unity8//OrientedShell.qml:253:5: Type Shell unavailable
         Shell {
         ^
[2016-12-21:09:20:27.366] file:///usr/share/unity8//Shell.qml:267:9: Element is not creatable.
             SurfaceManager {
             ^
[2016-12-21:09:20:27.366] qtmir.screens: Screen::setWindow - new geometry for shell surface ShellView(0x5608ba0ee230) QRect(0,0 1920x1200)
[2016-12-21:09:20:27.366] qtmir.screens: ScreenWindow 0x5608ba118190 with window ID 1 backed by Screen(0x5608b9ff8fd0) with ID 48
[2016-12-21:09:20:27.366] qtmir.screens: QWindow ShellView(0x5608ba0ee230) with geom QRect(0,0 1920x1200) is backed by a Screen(0x5608b9ff8fd0) with geometry QRect(0,0 1920x1200)
[2016-12-21:09:20:27.367] qtmir.screens: ScreensModel::onCompositorStarting
[2016-12-21:09:20:27.367] qtmir.screens: ScreensModel::update
[2016-12-21:09:20:27.367] qtmir.screens: Screen::setMirDisplayBuffer Screen(0x5608b9ff8fd0) 0x7fd54c140a30 0x7fd54c140b80
[2016-12-21:09:20:27.367] qtmir.screens: =======================================
[2016-12-21:09:20:27.367] qtmir.screens: Screen(0x5608b9ff8fd0) - id: 48 geometry: QRect(0,0 1920x1200) window: 0x5608ba118190 type: "DisplayPort" scale: 1
[2016-12-21:09:20:27.367] qtmir.screens: =======================================
[2016-12-21:09:20:27.367] qtmir.screens: ScreenWindow::setExposed 0x5608ba118190 true 0x5608b9ff8fe0

Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Download full text (4.5 KiB)

And again. Same result:

[2016-12-21:09:33:51.644] qtmir.screens: ScreensModel::ScreensModel
[2016-12-21 09:33:51.647464] mirplatform: Found graphics driver: mir:mesa-kms (version 0.25.0)
[2016-12-21 09:33:51.647496] mirplatform: Found graphics driver: mir:mesa-x11 (version 0.25.0)
[2016-12-21 09:33:51.647662] mirplatform: Found graphics driver: mir:stub-graphics (version 0.25.0)
[2016-12-21 09:33:51.647672] mirplatform: Found graphics driver: throw-on-creation (version 0.25.0)
[2016-12-21:09:33:51.647] qtmir.mir: MirServer created
[2016-12-21:09:33:51.647] qtmir.mir: Command line arguments passed to Qt: ("unity8", "--mode=full-shell")
[2016-12-21:09:33:51.648] QSocketNotifier: Can only be used with threads started with QThread
[2016-12-21 09:33:51.649228] mirserver: Starting
[2016-12-21 09:33:51.666761] mirserver: Using nested cursor
[2016-12-21 09:33:51.667204] mirserver: Initial display configuration:
[2016-12-21 09:33:51.667227] mirserver: Output 36: VGA disconnected
[2016-12-21 09:33:51.667232] mirserver: Output 39: DisplayPort disconnected
[2016-12-21 09:33:51.667235] mirserver: Output 45: HDMI-A disconnected
[2016-12-21 09:33:51.667249] mirserver: Output 48: DisplayPort connected, used
[2016-12-21 09:33:51.667256] mirserver: Physical size 24.0" 520x320mm
[2016-12-21 09:33:51.667260] mirserver: Current mode 1920x1200 59.95Hz
[2016-12-21 09:33:51.667263] mirserver: Preferred mode 1920x1200 59.95Hz
[2016-12-21 09:33:51.667266] mirserver: Logical position +0+0
[2016-12-21 09:33:51.667270] mirserver: Output 52: HDMI-A disconnected
[2016-12-21:09:33:51.667] qtmir.mir: PromptSessionListener::PromptSessionListener - this= PromptSessionListener(0x7fc0ec1c09d0)
[2016-12-21:09:33:51.667] qtmir.mir: SessionListener::SessionListener - this= SessionListener(0x7fc0ec1c0660)
[2016-12-21:09:33:51.667] qtmir.mir: MirWindowManagerImpl::MirWindowManagerImpl
[2016-12-21 09:33:51.667834] mirserver: Mir version 0.25.0
[2016-12-21:09:33:51.667] qtmir.screens: QtCompositor::start
[2016-12-21:09:33:51.676] qtmir.screens: ScreensModel::update
[2016-12-21:09:33:51.676] qtmir.sensor: Screen - nativeOrientation is: Qt::ScreenOrientation(LandscapeOrientation)
[2016-12-21:09:33:51.676] qtmir.sensor: Screen - initial currentOrientation is: Qt::ScreenOrientation(LandscapeOrientation)
[2016-12-21:09:33:51.678] qtmir.screens: Added Screen with id 48 and geometry QRect(0,0 1920x1200)
[2016-12-21:09:33:51.678] qtmir.screens: Screen::setMirDisplayBuffer Screen(0x55908c35bfd0) 0x7fc0ec140a30 0x7fc0ec140b80
[2016-12-21:09:33:51.678] qtmir.screens: =======================================
[2016-12-21:09:33:51.678] qtmir.screens: Screen(0x55908c35bfd0) - id: 48 geometry: QRect(0,0 1920x1200) window: 0x0 type: "DisplayPort" scale: 1
[2016-12-21:09:33:51.678] qtmir.screens: =======================================
[2016-12-21:09:33:51.735] qtmir.applications: UnityApplicationPlugin::registerTypes - this= UnityApplicationPlugin(0x7fc0d413ee40) uri= Unity.Application
[2016-12-21:09:33:51.768] QObject::connect: No such signal QDBusAbstractInterface::FlightModeChanged(bool) in /build/telephony-service-GdIWd2/telephony-service-0.1+17.04.20161129/libtele...

Read more...

tags: added: black-screen
Changed in canonical-devices-system-image:
importance: Undecided → Critical
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Here's the offending upgrade log. Although Mesa 13 was also introduced today, that does not seem to be the problem, since mir-demos still work fine.

Start-Date: 2016-12-21 09:14:27
Commandline: apt full-upgrade
Requested-By: dan (1000)
Install: unity8-fake-env:amd64 (8.15+17.04.20161215-0ubuntu1, automatic)
Upgrade: gnome-calendar:amd64 (3.22.1-1, 3.22.2-1), libgles2-mesa:amd64 (12.0.3-1ubuntu2, 13.0.2-1ubuntu1), libcups2:amd64 (2.2.1-41-g49c592936-1, 2.2.1-46-g10887d272-2), unity8:amd64 (8.15+17.04.20161207.1-0ubuntu1, 8.15+17.04.20161215-0ubuntu1), libegl1-mesa-dev:amd64 (12.0.3-1ubuntu2, 13.0.2-1ubuntu1), repowerd-data:amd64 (2016.11+17.04.20161124-0ubuntu1, 2016.12+17.04.20161212.1-0ubuntu1), ubuntu-keyboard-data:amd64 (0.100+17.04.20161116-0ubuntu1, 0.100+17.04.20161214.1-0ubuntu1), libglapi-mesa:amd64 (12.0.3-1ubuntu2, 13.0.2-1ubuntu1), mesa-common-dev:amd64 (12.0.3-1ubuntu2, 13.0.2-1ubuntu1), binutils:amd64 (2.27.51.20161212-1ubuntu1, 2.27.51.20161220-1ubuntu1), libxatracker2:amd64 (12.0.3-1ubuntu2, 13.0.2-1ubuntu1), unity8-private:amd64 (8.15+17.04.20161207.1-0ubuntu1, 8.15+17.04.20161215-0ubuntu1), libegl1-mesa:amd64 (12.0.3-1ubuntu2, 13.0.2-1ubuntu1), cups-server-common:amd64 (2.2.1-41-g49c592936-1, 2.2.1-46-g10887d272-2), cmake-data:amd64 (3.7.0-1ubuntu1, 3.7.1-1ubuntu1), binutils-arm-linux-gnueabihf:amd64 (2.27.51.20161212-1ubuntu1, 2.27.51.20161220-1ubuntu1), cups-common:amd64 (2.2.1-41-g49c592936-1, 2.2.1-46-g10887d272-2), libgbm1:amd64 (12.0.3-1ubuntu2, 13.0.2-1ubuntu1), repowerd:amd64 (2016.11+17.04.20161124-0ubuntu1, 2016.12+17.04.20161212.1-0ubuntu1), cups-filters:amd64 (1.13.0-2, 1.13.1-1), cups-ppdc:amd64 (2.2.1-41-g49c592936-1, 2.2.1-46-g10887d272-2), libcupsmime1:amd64 (2.2.1-41-g49c592936-1, 2.2.1-46-g10887d272-2), libunity-api0:amd64 (7.121+17.04.20161205-0ubuntu1, 8.0+17.04.20161215-0ubuntu1), libcupsfilters1:amd64 (1.13.0-2, 1.13.1-1), libwayland-egl1-mesa:amd64 (12.0.3-1ubuntu2, 13.0.2-1ubuntu1), libgles2-mesa-dev:amd64 (12.0.3-1ubuntu2, 13.0.2-1ubuntu1), libfontembed1:amd64 (1.13.0-2, 1.13.1-1), libgl1-mesa-dev:amd64 (12.0.3-1ubuntu2, 13.0.2-1ubuntu1), libgl1-mesa-dri:amd64 (12.0.3-1ubuntu2, 13.0.2-1ubuntu1), cups-filters-core-drivers:amd64 (1.13.0-2, 1.13.1-1), libgl1-mesa-glx:amd64 (12.0.3-1ubuntu2, 13.0.2-1ubuntu1), unity8-common:amd64 (8.15+17.04.20161207.1-0ubuntu1, 8.15+17.04.20161215-0ubuntu1), libcupsppdc1:amd64 (2.2.1-41-g49c592936-1, 2.2.1-46-g10887d272-2), cmake:amd64 (3.7.0-1ubuntu1, 3.7.1-1ubuntu1), cups-bsd:amd64 (2.2.1-41-g49c592936-1, 2.2.1-46-g10887d272-2), libgbm-dev:amd64 (12.0.3-1ubuntu2, 13.0.2-1ubuntu1), cups-core-drivers:amd64 (2.2.1-41-g49c592936-1, 2.2.1-46-g10887d272-2), cups-daemon:amd64 (2.2.1-41-g49c592936-1, 2.2.1-46-g10887d272-2), libcupsimage2:amd64 (2.2.1-41-g49c592936-1, 2.2.1-46-g10887d272-2), cups:amd64 (2.2.1-41-g49c592936-1, 2.2.1-46-g10887d272-2), libcupscgi1:amd64 (2.2.1-41-g49c592936-1, 2.2.1-46-g10887d272-2), cups-client:amd64 (2.2.1-41-g49c592936-1, 2.2.1-46-g10887d272-2), cups-browsed:amd64 (1.13.0-2, 1.13.1-1)
End-Date: 2016-12-21 09:15:01

Revision history for this message
Albert Astals Cid (aacid) wrote :

This is because everything in https://bileto.ubuntu.com/#/ticket/2160 landed except qtmir.

IMO Silos should be atomic, but they are not it seems, so that is what caused the breakage.

According to http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#qtmir qtmir depends on libmiral1 that doesn't even seem to exist?

$ apt-cache search libmiral1
$

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

That would be bug 1651384 :P

Revision history for this message
Michał Sawicz (saviq) wrote :

That's because miral 1.0 was released in the mean time, with SONAME 2, so it's libmiral2 now.

Apart from that, old qtmir is used (instead of the fake one in unity8-fake-env that gets installed).

Third issue is that miral needs to get MIR'd (bug #1651384).

Changed in canonical-devices-system-image:
status: New → Triaged
Changed in unity8 (Ubuntu):
status: New → In Progress
Changed in canonical-devices-system-image:
status: Triaged → In Progress
assignee: nobody → Michał Sawicz (saviq)
Changed in unity8 (Ubuntu):
assignee: nobody → Michał Sawicz (saviq)
summary: - [regression] Unity8 no longer visible (just a black screen) on zesty,
- although the process is running
+ [regression] Unity8 fails to start on zesty
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Minor correction: The process starts and logs stuff. So that's not really failing to start. Depending on your view of "started" :)

summary: - [regression] Unity8 fails to start on zesty
+ [regression] Unity8 is just a black screen on zesty
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

qtmir (0.5.1+17.04.20161216-0ubuntu2) zesty; urgency=medium

  * No-change rebuild against latest miral.

 -- Łukasz 'sil2100' Zemczak <email address hidden> Wed, 21 Dec 2016 10:07:36 +0100

affects: unity8 (Ubuntu) → qtmir (Ubuntu)
Changed in qtmir (Ubuntu):
status: In Progress → Fix Released
Changed in canonical-devices-system-image:
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.