QA has found an app installation problem sometimes happening with the
silo 018, fixed at least by removing and re-adding U1 account. I did not
see such problem, but I also flashed clean, updated and only then added
the U1 account for installing apps so it maybe the reason I was able to
install apps without problems.
I did see both with and without the PPA that sometimes adding U1 account
in general stalls on vivid, so that's not a regression.
On IRC I got some info about how DBus is used with app installations:
"dbus is used to monitor installation progress (for the progress bar in
the preview). apps store scope just passes dbus object path to unity8
dash and doesn't interact with dbus directly (at least when it comes to
installation); probably unity8/dash logs are first to look at"
I now updated to latest image, added U1 account, installed an app, and then
upgraded to silo 018, and I can see the problem now. When I click "Install",
dbus.log gets:
---
Activating service name='com.ubuntu.OnlineAccountsUi'
Successfully activated service 'com.ubuntu.OnlineAccountsUi'
---
but unity8-dash.log gets:
---
RequestAccess failed: QDBusError("org.freedesktop.DBus.Error.UnknownObject",
"No such object path '/'")
---
Then when I clicked back arrow from the app page, I got a request for U1
credentials, which I canceled. When I go to u-s-s the U1 account is not
there anymore. After adding U1 account, it appears that app installation
work smoothly.
It seems to me the pattern is that the U1 account gets removed randomly
when a reboot is involved. One time I observed the account had survived
a reboot, but disappeared at the moment I clicked "Install". But it
seems that without a reboot and with account added app installation
seems to work for multiple apps without problems.
I did clean QML cache at one point so it does not seem to be related
(also, qtdeclarative isn't touched in the PPA).
After ppa-purging the problem doesn't occur anymore. So the problem has
to come from the QDBus changes in the silo, even if those provably fix
the Unity 8 hanging issue during boot and no issues were seen in any of
the autopilot tests.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to autopilot in Ubuntu.
https://bugs.launchpad.net/bugs/1421009
Title:
unity8 sometimes hangs on boot
Status in the base for Ubuntu mobile products:
In Progress
Status in autopilot package in Ubuntu:
Fix Released
Status in libusermetrics package in Ubuntu:
Invalid
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.
---
Timeline/Updates:
2015-02-20: libusermetrics lands, causing (apparently) this boot problem to
start happening rarely.
http://people.canonical.com/~ogra/touch-image-stats/106.changes /
http://launchpadlibrarian.net/198152771/libusermetrics_1.1.1%2B14.10.20141020-0ubuntu1_1.1.1%2B15.04.20150219-0ubuntu1.diff.gz
”I got a symbolic trace out of all the threads. It seems to be a dbus lock
between usermetrics and networkmanager bits. We suspect a relation to QTBUG
https://bugreports.qt.io/browse/QTBUG-44836.”
2015-03-25: qtbase dbus update to support threads (instead of one main
thread) in PPA 018 fixes the boot issue, but autopilot test suites start
failing randomly.
2015-03-27: an autopilot fix fixes a simple test case, and seems to fix UITK
suite as a whole, but on krillin only
Currently mako still fails a lot of tests when the silo is enabled.
The nature of failures is random (different tests fail on each run).
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421009/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
