Qt 5.6 now in yakkety and xenial-overlay with largely re-engineered
QDBus (...with new but different bugs).
** Changed in: qtbase-opensource-src (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribe
This bug was fixed in the package ubuntu-system-settings-online-accounts
- 0.6+15.10.20150624-0ubuntu1
---
ubuntu-system-settings-online-accounts (0.6+15.10.20150624-0ubuntu1) wily;
urgency=medium
[ Alberto Mardegan ]
* Fix build with Qt 5.5 (LP: #1387537, #1421009, #1448878, #14
** Branch linked: lp:ubuntu/wily-proposed/ubuntu-system-settings-online-
accounts
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetrics in Ubuntu.
https://bugs.launchpad.net/bugs/1421009
Title:
unity8 sometimes hangs on boot
St
Upstream has postponed their QDBus rework to Qt 5.6, so it seems there
won't be anything to test for some time.
** Changed in: qtbase-opensource-src (Ubuntu)
Status: In Progress => Incomplete
** Changed in: qtbase-opensource-src (Ubuntu)
Assignee: Timo Jyrinki (timo-jyrinki) => (unass
** Branch linked: lp:ubuntu/libusermetrics
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetrics in Ubuntu.
https://bugs.launchpad.net/bugs/1421009
Title:
unity8 sometimes hangs on boot
Status in the base for Ubuntu mobile prod
Removing it from the landing team tracker as in theory this is no longer
a real issue.
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetrics in Ubuntu.
https://bugs.launchpad.net/bugs/1421009
Title:
unity8 sometimes hangs on boo
** Changed in: qtbase-opensource-src (Ubuntu)
Importance: High => Medium
** Changed in: unity8 (Ubuntu)
Importance: High => Undecided
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetrics in Ubuntu.
https://bugs.launchpad.ne
** Tags removed: lt-blocker
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetrics in Ubuntu.
https://bugs.launchpad.net/bugs/1421009
Title:
unity8 sometimes hangs on boot
Status in the base for Ubuntu mobile products:
Fix Rel
** Changed in: canonical-devices-system-image
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetrics in Ubuntu.
https://bugs.launchpad.net/bugs/1421009
Title:
unity8 sometimes hangs on
This bug is now fixed (workarounded) in the overlay PPA, ie the unity8
doesn't hang anymore on boot:
libusermetrics (1.1.1+15.04.20150427-0ubuntu1) vivid; urgency=medium
[ Pete Woods ]
* Stop using shared DBus connections (LP: #1421009)
-- CI Train Bot Mon, 27 Apr 2015 15:38:43
+
The
** Description changed:
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 k
arale testing stopped at 127 successful reboots, mako at 83. Now in QA
sign-off.
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetrics in Ubuntu.
https://bugs.launchpad.net/bugs/1421009
Title:
unity8 sometimes hangs on boot
Sta
** Branch unlinked: lp:~mardy/ubuntu-system-settings-online-
accounts/lp1421009
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetrics in Ubuntu.
https://bugs.launchpad.net/bugs/1421009
Title:
unity8 sometimes hangs on boot
Stat
** Branch linked: lp:~mardy/ubuntu-system-settings-online-
accounts/lp1447175
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetrics in Ubuntu.
https://bugs.launchpad.net/bugs/1421009
Title:
unity8 sometimes hangs on boot
Status
Ok 007 was validated on mako and arale (>= 100 reboots), but we're
switching silos now. Also qt5-proper was tested but it won't be needed
at this point.
A new commit on Pete's libusermetrics branch combines his and my changes
in a better way and that is now being built in silo _017_. We're going
t
"+ similar changes to unity8 from Albert", the 010 description was meant
to be.
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetrics in Ubuntu.
https://bugs.launchpad.net/bugs/1421009
Title:
unity8 sometimes hangs on boot
Stat
** Changed in: libusermetrics (Ubuntu)
Status: Invalid => In Progress
** Changed in: libusermetrics (Ubuntu)
Importance: Undecided => Critical
** Changed in: libusermetrics (Ubuntu)
Assignee: (unassigned) => Pete Woods (pete-woods)
--
You received this bug notification because yo
There was a tip from tvoss to try to use QDBusConnection::connectToBus
instead of QDBusConnection::sessionBus() / systemBus(), to minimize
sharing of DBus connections.
There are 3 PPA:s now all doing that:
- https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-007/ -
Pete's change
** Description changed:
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 k
** Description changed:
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 k
** Description changed:
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 k
** Branch linked: lp:~timo-jyrinki/libusermetrics/dont-share-dbus-
sessionbus-connections
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetrics in Ubuntu.
https://bugs.launchpad.net/bugs/1421009
Title:
unity8 sometimes hangs on
** Branch linked: lp:~aacid/unity8/useOwnDbusConnections
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetrics in Ubuntu.
https://bugs.launchpad.net/bugs/1421009
Title:
unity8 sometimes hangs on boot
Status in the base for Ubun
** Branch linked: lp:~unity-api-team/libusermetrics/dont-share-dbus-
connections
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetrics in Ubuntu.
https://bugs.launchpad.net/bugs/1421009
Title:
unity8 sometimes hangs on boot
Sta
(note that the "path" and "member" may be different on each hang)
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetrics in Ubuntu.
https://bugs.launchpad.net/bugs/1421009
Title:
unity8 sometimes hangs on boot
Status in the base
Some weekend numbers of how many reboots needed to reproduce the problem
on mako: 30, 12, 15, 59, 15, 9, 26, 10, 6. There's no clear upper limit.
In other testing, reverting the libusermetrics landing from February
does not seem to cure the problem - I was able to reproduce the problem
also with t
** Attachment added: "Full backtrace of the crash"
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1421009/+attachment/4385368/+files/usermetrics-fullbacktrace.txt
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetrics in
** Description changed:
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 k
** Description changed:
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 k
@Pat: Just in case, I'm on vivid and use autopkgtest 3.13, that may be
related.
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetrics in Ubuntu.
https://bugs.launchpad.net/bugs/1421009
Title:
unity8 sometimes hangs on boot
Stat
@Pat: Can you re-try adding '-d' to your adt-run options and share the
log ?
/tmp/autopkgtest-reboot is created by adt-run on the testbed at run
time.
I'm eager to learn how such a failure can happen and where it needs to
be fixed.
--
You received this bug notification because you are a member
Tried running the new test but I get /tmp/autopkgtest-reboot: not found
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetrics in Ubuntu.
https://bugs.launchpad.net/bugs/1421009
Title:
unity8 sometimes hangs on boot
Status in t
Also reproduced on arale with the branch above after 25 reboots.
$ adb shell system-image-cli -i
current build number: 22
device name: arale
channel: ubuntu-touch/arale-vivid-proposed
last update: 2010-01-01 00:29:22
version version: 22
version ubuntu: 30e975dd988b3be7886017b6d46b2821da187d7b8e5e4
** Branch linked: lp:~canonical-platform-qa/unity8/1421009-hangs-on-boot
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetrics in Ubuntu.
https://bugs.launchpad.net/bugs/1421009
Title:
unity8 sometimes hangs on boot
Status in t
I've created https://code.launchpad.net/~canonical-platform-
qa/unity8/1421009-hangs-on-boot/+merge/257408 to reproduce this bug.
Given the last comment above it may need to be tweaked s/30/60/ .
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribe
** Description changed:
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 k
** Description changed:
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 k
Scratch that. We started testing on arale, and it seems that on arale at
least the delay workaround is not enough. It also seems 30 reboot is noy
enough to reliably reproduce the hang, as once it happened after 54
reboots.
** Changed in: lxc-android-config (Ubuntu)
Assignee: Timo Jyrinki (tim
** Changed in: lxc-android-config (Ubuntu)
Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)
** Changed in: lxc-android-config (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetri
It seems I've found a workaround for the original unity8 hang on boot,
which we can include in lxc-android-config without touching Qt while the
upstream fixing of QDBus is not 100% complete.
** Also affects: lxc-android-config (Ubuntu)
Importance: Undecided
Status: New
--
You received
Note that the activity indicator itself might be the CPU hogger - see
bug #1431957.
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetrics in Ubuntu.
https://bugs.launchpad.net/bugs/1421009
Title:
unity8 sometimes hangs on boot
With latest silo 18 on mako #183 I still got the account deleted after
reboot.
And the spinner is still shown many times after clicking on "Sign In" in
the online accounts screen, both when started from system-
settings->account and from the apps scope "Install" button. Then it
takes more than 10
https://code.launchpad.net/~mardy/ubuntu-system-settings-online-
accounts/lp1421009/+merge/257267 got added to the PPA now. It seems to
move the problem so that it never happens anymore during reboot - after
reboot, the account is always still there.
But it'd seem possible that a similar fix to a
** Branch linked: lp:~mardy/ubuntu-system-settings-online-
accounts/lp1421009
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetrics in Ubuntu.
https://bugs.launchpad.net/bugs/1421009
Title:
unity8 sometimes hangs on boot
Status
** Description changed:
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 k
** Description changed:
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 k
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
** Attachment added: "relevant logs that cover usage both with and without the
silo"
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1421009/+attachment/4382081/+files/logs.tar.gz
--
You received this bug notification because you are a member of Unity API
bugs, which is
As an update ~test3 updated ppc64el symbols and "ubuntu7" is a no-change
rebuild of ~test3 with a saner version number. Putting forward to QA for
further testing and signoff.
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetrics in
Weekend's test results at
http://people.canonical.com/~tjyrinki/qt5/ap-2015-04-18-mako-175-silo-018/
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetrics in Ubuntu.
https://bugs.launchpad.net/bugs/1421009
Title:
unity8 sometime
With the current build 5.4.1+dfsg-2ubuntu6~rtm~test2 the KDE legacy app
situation looks unchanged. Now the phone PPA is enabled so I will start
evaluating if the current build would be suitable to there.
--
You received this bug notification because you are a member of Unity API
bugs, which is su
This is still pending on an upstream fix that doesn't break certain KDE
apps using deprecated functions. Meanwhile, I can (and will) prepare a
landing to vivid-rtm PPA if it seems a fix that can be landed to Ubuntu
proper continues to take time.
--
You received this bug notification because you a
** Changed in: autopilot (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetrics in Ubuntu.
https://bugs.launchpad.net/bugs/1421009
Title:
unity8 sometimes hangs on boot
Status in
Seems the updated patch indeed fixes the crashes in Plasma 5 startup,
but applications using KUniqueApplication like konsole or kfontview fail
to start, these applications got a warning before (i.e. without the
patchset) that they were misusing qdbus and i think that Qt changing to
make them fail
Yesterday ubuntu7~test1 was done with http://paste.ubuntu.com/10759851/
- unfortunately no changes in Plasma 5 despite upstream thinking those
would address the problem.
Now building ubuntu7~test2 with https://codereview.qt-
project.org/#/c/109632/ updated to the latest patch set which was missed
Indeed the testing was finished only on the phone + Unity 7 desktop (Qt
5 apps only). QA signoff is now put on hold once again because of the
Plasma 5 regression.
The phone Autopilot results are at
http://people.canonical.com/~tjyrinki/qt5/ap-2015-04-02-mako-156-silo-018/
--
You received this bu
Bad news, tried to start Plasma 5 with the patches to be greated by a
zillion of crashing processes, here a backtrace of one of them
Thread 1 (Thread 0x7f658362a780 (LWP 10972)):
[KCrash Handler]
#6 0x7f6583662168 in QDBusConnectionPrivate::shouldWatchService(QString
const&) (this=this@entry
The bug is now finally confirmed as fixed without regressions in
autopilot tests, in the silo 018 (qtbase version ending ubuntu6). The
silo is now handed off to QA.
** Changed in: qtbase-opensource-src (Ubuntu)
Status: Incomplete => In Progress
** Changed in: libusermetrics (Ubuntu)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: autopilot (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetrics in Ubuntu.
https://bugs.launchpad.net/bu
As per Albert's instructions I took three updated patches and five new
patches from upstream. Four of them needed rebasing for Qt 5.4, but a
local build now finished and a PPA build with version number
ubuntu6~vivid1~test1 is now building in 018 PPA.
--
You received this bug notification because
Ok, got one thread deadlock in the calculator app that seems dbus
related, investigating a bit more
** Attachment added: "thread_stacktrace"
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1421009/+attachment/4361070/+files/thread_stacktrace
--
You received this bug notification becaus
And one more addition to anyone not constantly running autopilot and
aware of the pre-requirements:
phablet-config autopilot --dbus-probe enable
is needed before running tests. This is documented at
https://wiki.ubuntu.com/Touch/Testing#Running_Click_tests and also done
automatically for me as I
Addition to my previous comment, for weather + calculator apps you need to run
phablet-click-test-setup from the host or one at a time:
phablet-click-test-setup --click com.ubuntu.calculator
phablet-click-test-setup --click com.ubuntu.weather
The other tests come from the mentioned deb packages.
A boottest failure with image 167 (krillin):
https://jenkins.qa.ubuntu.com/job/vivid-boottest-dialer-app/3/console
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetrics in Ubuntu.
https://bugs.launchpad.net/bugs/1421009
Title:
My opinion is that all those failures where probably there already since
the ones i've been able to find/replicate don't seem qdbus related
Now why is this happening with these patches? These patches make qdbus
serialize much less on the main thread, i.e. things are executed more in
different thre
** Branch linked: lp:~aacid/autopilot/dbus_search_no_seen_connections
** Branch linked: lp:~timo-
jyrinki/autopilot/ap1.5_dbus_search_no_seen_connections
** Description changed:
The following gdbus call is failing with a "Error: Timeout was reached"
message:
gdbus call --session --dest
The earlier simplified test case does not fail anymore or at least not
easily. Whether on stock image or using the PPA, the problem with
running the same test over and over is that Unity8 crashes or restarts
sooner or later when running the command, for example that crasher bug
noticed.
I ran a ne
** Tags added: lt-blocker lt-category-visible
--
You received this bug notification because you are a member of Unity API
bugs, 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:
https://bugs.launchpad.net/qtmir/+bug/1437357 is that crash
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetrics in Ubuntu.
https://bugs.launchpad.net/bugs/1421009
Title:
unity8 sometimes hangs on boot
Status in autopilot pack
The crash in
http://people.canonical.com/~tjyrinki/qt5/fail/mako151_plus_018/_usr_bin_unity8.32011.crash
is mir/unity8 crashing because they disagree on touch event delivery,
nothing to do with dbus patches.
--
You received this bug notification because you are a member of Unity API
bugs, which i
Looking in more detail, it seems the new Mir may have helped mako in the
address-book-app "hang" case, even though for example UITK and
webbrowser-app still have more failures. The address-book-app that
failed reliably several times earlier, now in the comment #33 linked
results failed only 1 test
krillin.
--
You received this bug notification because you are a member of Unity API
bugs, 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 packa
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
A boottest failure with image 160:
http://d-jenkins.ubuntu-ci:8080/view/Vivid/view/BootTest/job/vivid-
boottest-ofono/1/console
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetrics in Ubuntu.
https://bugs.launchpad.net/bugs/14210
So i tried with silo 13 two times in a row and all the SDK autopilot
tests passed fine.
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetrics in Ubuntu.
https://bugs.launchpad.net/bugs/1421009
Title:
unity8 sometimes hangs on bo
webbrowser-app with the new qtbase + AP
http://people.canonical.com/~tjyrinki/qt5/fail/qtbase_ubuntu5/ap-
2015_03_26-15_57_41-webbrowser_app-1-018.tests (3 failures, between 1-2
without 018 and 5-7 with 018 before AP was updated)
--
You received this bug notification because you are a member of U
running phablet-test-run ubuntuuitoolkit hanged for me with
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1436860 not sure it's
caused by these patches or just happens now more becuase things are
faster, trying silo 13 as per mir guys suggetsion
--
You received this bug notification because
I tried again to reproduce the issue, using #150 + silo 18 (including
autopilot update). I've not been able to reproduce it again after many
retries.
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetrics in Ubuntu.
https://bugs.lau
I've reflashed the device so this is with vivid #150 + 018. The MP in
#23 (just adjusted for AP 1.5 branch) is now in the 018 PPA.
The simplified test case seems fixed for me too, but unfortunately it'd
look like running a whole suite like phablet-test-run ubuntuuitoolkit
simply hangs at some poin
I was using mako devel-proposed image #148 with the silo installed.
I'll try and reproduce again and get some more info.
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to libusermetrics in Ubuntu.
https://bugs.launchpad.net/bugs/1421009
Tit
Richard, which hardware are you using?
Can you try reproducing the issue again and then gdb'ing in to the
frozen app and posting a backtrace? I've been running it in a loop for
minutes and had nothing.
--
You received this bug notification because you are a member of Unity API
bugs, which is sub
I tried reproducing this issue on silo 18 using
address_book_app.tests.test_add_contact.TestAddContact.test_go_to_add_contact.
The test failed on the 10th attempt in the same way as in the logs:
http://people.canonical.com/~tjyrinki/qt5/fail/qtbase_ubuntu5/ap-
2015_03_24-21_48_11-address_book_app-
Timo, can you try running the tests again with
https://code.launchpad.net/~aacid/autopilot/dbus_search_no_seen_connections/+merge/254109
? I've been running
while [ 1 ] ; do phablet-test-run
ubuntuuitoolkit.tests.custom_proxy_objects.test_header.SectionsTestCase.test_select_sections_with_sections_
** Description changed:
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 o
All the failure traces seem to be stating that autopilot wouldn't be
able to launch the application. In case of eg address-book-app once a
test fails, all subsequent tests fail too. In case of eg UITK, it's just
that random tests fail.
Here's a simplified test case:
while [ 1 ] ; do phablet-test-
I ran some Autopilot testing last night and continuing a bit now . The
two new patches do not fix the AP problems. As examples:
- Archive image (#145):
* UITK: 1-2 AP failures
* webbrowser-app: 1-2 AP failures
* calculator: 0 AP failures
* ubuntu-system-settings: 0 AP failures
- Image (#147) adde
And some more with 158:
https://jenkins.qa.ubuntu.com/job/vivid-boottest-language-pack-touch-ca/4/console
https://jenkins.qa.ubuntu.com/job/vivid-boottest-language-pack-touch-nl/5/console
https://jenkins.qa.ubuntu.com/job/vivid-boottest-language-pack-touch-sk/4/console
https://jenkins.qa.ubuntu.co
Some more boottest failures, these with krillin image 158
https://jenkins.qa.ubuntu.com/job/vivid-boottest-language-pack-touch-zh-hant/3/console
https://jenkins.qa.ubuntu.com/job/vivid-boottest-language-pack-touch-ru/3/console
--
You received this bug notification because you are a member of Uni
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
89 matches
Mail list logo