touch-packages team mailing list archive

[Albert Astals Cid <albert.astals@xxxxxxxxxxxxx>]

Timo if you could create a silo with 
https://codereview.qt-project.org/#/c/102762/
https://codereview.qt-project.org/#/c/103731/
https://codereview.qt-project.org/#/c/103732/
https://codereview.qt-project.org/#/c/103733/
https://codereview.qt-project.org/#/c/103734/
https://codereview.qt-project.org/#/c/103735/
https://codereview.qt-project.org/#/c/103736/
https://codereview.qt-project.org/#/c/103737/
https://codereview.qt-project.org/#/c/103738/

It'd be great, suposedly that will land in Qt 5.5 and makes all the dbus
threading "better"

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

Title:
  unity8 sometimes hangs on boot

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
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/qtbase-opensource-src/+bug/1421009/+subscriptions