← Back to team overview

touch-packages team mailing list archive

[Bug 1421009] Re: unity8 sometimes hangs on boot

 

Unfortunately I couldn't reproduce success with my mako last night with
018 (qtbase + autopilot) + 013 (Mir 0.12.1) + rsalveti (glibc fix). Here
are the results until aborted:
http://people.canonical.com/~tjyrinki/qt5/fail/vivid-ap-mir013/ - for
example 6 + 8 failures in UITK.

I'll try again with the new #151 image including Mir, glibc and other
things + 018, but I doubt it'll change this picture.

@Albert did you test on krillin or mako?

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

Title:
  unity8 sometimes hangs on boot

Status in autopilot package in Ubuntu:
  New
Status in libusermetrics package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  The following gdbus call is failing with a "Error: Timeout was
  reached" message:

  gdbus call --session --dest com.canonical.UnityGreeter --object-path /
  --method org.freedesktop.DBus.Properties.Get
  com.canonical.UnityGreeter IsActive

  This is being seen on krillin devices starting with image 106 from
  ubuntu-touch/devel-proposed. It doesn't happen every time, so far
  today, I've seen it 3 times from about 12 tests. On the most recent
  failure, I grabbed a console and tried repeatedly to run the command
  from the shell, even after 2 hours the timeout was still being
  returned (after about 28 seconds).

  A copy of ~/.cache/upstart/unity8.log is here:
  http://paste.ubuntu.com/10179482/

  I have 3 test cases where the problem was observed:
  http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-qtchooser/1/console
  http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-gsettings-ubuntu-touch-schemas/1/console
  http://d-jenkins.ubuntu-ci:8080/job/fjg-boottest/3/console

  In all cases, the test is using adt-run (from autopkgtest) to drive a
  test on the phone device. adt-run uses the above gdbus call to
  determine if the desktop is active. In all the examples, the device
  was freshly flashed.

  Update 2015-03-25: the qtbase dbus update in silo 018 seems to address
  the boot issue, but causes autopilot to have problems seeing an
  application start, randomly

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


References