Unity8 crash while locking/unlocking with HDMI plugged

[Victor gonzalez]

Environment:

current build number: 76
device name: frieza_arm64
channel: ubuntu-touch/staging/ubuntu
last update: 2016-11-07 08:03:44
version version: 76
version ubuntu: 20161105
version device: 20161014.0
version custom: 20161105

Steps to reproduce:

1º Connect hdmi
2º Lock/unlock device several times

Current result: locking/unlocking device causes greeter to misbehave and finally the ubuntu boot logo appears. Attached some logs and crash files, hope it helps

Expected result: unity8 should not crash

Add info: time stamp 16:07

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Daniel van Vugt (vanvugt)]

The crash was a fatal error from QtMir, but I can't find the corresponding message in unity8.log... (?)

Stacktrace:
 #0 0x0000007f9db46528 in raise () from /lib/aarch64-linux-gnu/libc.so.6
 No symbol table info available.
 #1 0x0000007f9db479e0 in abort () from /lib/aarch64-linux-gnu/libc.so.6
 No symbol table info available.
 #2 0x0000007f9dea18cc in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/aarch64-linux-gnu/libQt5Core.so.5
 No symbol table info available.
 #3 0x0000007f98b70c0c in QMirServer::start() () from /usr/lib/aarch64-linux-gnu/qt5/plugins/platforms/libqpa-mirserver.so
 No symbol table info available.
 #4 0x0000007f98b8a294 in MirServerIntegration::initialize() () from /usr/lib/aarch64-linux-gnu/qt5/plugins/platforms/libqpa-mirserver.so
 No symbol table info available.
 #5 0x0000007f9e88a6dc in QGuiApplicationPrivate::eventDispatcherReady() () from /usr/lib/aarch64-linux-gnu/libQt5Gui.so.5
 No symbol table info available.
 #6 0x0000007f9e08e7ac in QCoreApplicationPrivate::init() () from /usr/lib/aarch64-linux-gnu/libQt5Core.so.5
 No symbol table info available.
 #7 0x0000007f9e88c1c8 in QGuiApplicationPrivate::init() () from /usr/lib/aarch64-linux-gnu/libQt5Gui.so.5
 No symbol table info available.
 #8 0x0000007f9e88ce54 in QGuiApplication::QGuiApplication(int&, char**, int) () from /usr/lib/aarch64-linux-gnu/libQt5Gui.so.5
 No symbol table info available.
 #9 0x000000000040a158 in ?? ()
 No symbol table info available.
 #10 0x0000000000406a7c in ?? ()
 No symbol table info available.
 #11 0x0000007f9db348a0 in __libc_start_main () from /lib/aarch64-linux-gnu/libc.so.6
 No symbol table info available.
 #12 0x0000000000406be0 in _start ()
 No symbol table info available.

[Victor gonzalez (victor-gonzalez-0)]

@vanvug, I'll reproduce it again later today and update the bug with new logs

[Victor gonzalez (victor-gonzalez-0)]

With today's image(78) I got a crash when unplugging the hdmi, time stamp 09:26.

Then I tried to reproduce the bug again and after some locking/unlocking cycles the screen stopped to respond, it went black and power button only lights the screen but greeter doesn't appear.Time stamp 09:51/52. Please find attached the crash files and unity8 logs

[Daniel van Vugt (vanvugt)]

OK,

  1. Please provide a copy (as root) of your /var/log/lightdm/unity-system-compositor.log
  2. Please report the crash formally using 'ubuntu-bug _usr_bin_unity8.32011.crash' and provide a link to the error report or new bug that results.

[Daniel van Vugt (vanvugt)]

Please copy all of /var/log/lightdm/unity-system-compositor.log* actually.

[Daniel van Vugt (vanvugt)]

I ask because it sounds like you might have rediscovered bug 1489689 or something like it, which would produce a crash in unity-system-compositor.log that's easy to identify.

[Victor gonzalez (victor-gonzalez-0)]

With today's image(79) I wasn't able to make it crash,but got the black screen once when plugging/unplugging hdmi with the device locked. Unfortunately, the device can't boot completely after this. The splash screen appears and then it turns black, is not even displaying the ubuntu boot image. I'll try again later