ubuntu-sdk-bugs team mailing list archive

[Timo Jyrinki <timo.jyrinki@xxxxxxxxxxxxx>]

Adding libusermetrics as upgrade of it in
http://people.canonical.com/~ogra/touch-image-stats/106.changes
apparently caused the problem. However, it's probably just because
libusermetrics started using DBus as explained in comment #7. The Qt bug
itself is probably an old one.

If fixing Qt seems a time consuming process, an option would be to
revert the part of the libusermetrics upgrade that triggers the bug.

Also adding autopilot as at least the current set of patches regressed
on running Autopilot tests which may mean Autopilot is relying on old
behavior and the patches themselves might be correct. We'll know more
when the new 2 patches have built and tests run.

** Also affects: libusermetrics (Ubuntu)
   Importance: Undecided
       Status: New

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

** Also affects: autopilot (Ubuntu)
   Importance: Undecided
       Status: New

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

-- 
You received this bug notification because you are a member of Ubuntu
SDK bug tracking, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1421009

Title:
  unity8 sometimes hangs on boot

Status in autopilot package in Ubuntu:
  Incomplete
Status in libusermetrics package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
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.

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