subject:"\[Touch\-packages\] \[Bug 1421009\] Re\: unity8 sometimes hangs on boot"

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 the revert I've pushed to https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/landing-007/+packages

I've improved the test case in the description several times to get fuller 
backtraces. With the latest version I was able to see that both in case of the 
current libusermetrics and the reverted one the backtrace leads back to 
usermetrics's DBus usage. Which is not to say there's anything wrong with 
libusermetrics, as the bug is in multi-threaded handling of DBus inside Qt. The 
DBus call being called is:
#17 0x in dbus_bus_add_match (connection=0xe9d140, rule=0x11ba818 
type='signal',sender='com.canonical.UserMetrics',path='/com/canonical/UserMetrics/DataSource/2',interface='com.canonical.usermetrics.DataSource',member='emptyDataStringChanged',
 error=0x0) at ../../dbus/dbus-bus.c:1553
msg = 0xf76058
__FUNCTION__ = dbus_bus_add_match

-- 
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 lxc-android-config package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
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.

  == Test Case ==

  # Prepare debugging
  adb shell
  sudo apt install qtbase5-dbg libc6-dbg libdbus-glib-1-2-dbg dbus-1-dbg 
libglib2.0-0-dbg
  echo deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe 
multiverse | sudo tee -a /etc/apt/sources.list.d/ddebs.list
  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 428D7C01
  sudo apt-get update
  sudo apt install libusermetricsoutput1-dbgsym=1.1.1+15.04.20150219-0ubuntu1

  # Start the reboot loop
  # This reboots the device in a loop, and if this bug is not fixed by whatever 
proposed solution, it will hang eventually. Current highest amount of reboots 
without errors is 54, so it's probable a 100 reboots is needed for testing.

  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done

  # When it fails
  adb shell
  sudo gdb -p $(pidof unity8)
  bt

  --
  At this point, the backtrace should show:
  #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  #1  0xb6301e12 in _q_futex (op=0, val=3, timeout=0x0, addr=optimized out)
  at thread/qmutex_linux.cpp:146
  #2  lockInternal_helperfalse (timeout=-1, elapsedTimer=0x0, d_ptr=...)
  at thread/qmutex_linux.cpp:187
  #3  QBasicMutex::lockInternal (this=this@entry=0x1523b44)
  at thread/qmutex_linux.cpp:203
  #4  0xb6301eb6 in lock (this=0x1523b44) at thread/qmutex.h:59
  #5  lock (timeout=-1, this=0x1523b38) at thread/qmutex.cpp:620
  #6  QMutex::lock (this=this@entry=0x1523d6c) at thread/qmutex.cpp:215
  #7  0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48,
  a=ToggleWatchAction, this=synthetic pointer) at qdbusthreaddebug_p.h:183
  #8  QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction,
  this=synthetic pointer) at qdbusthreaddebug_p.h:198
  #9  qDBusRealToggleWatch (d=0x1523d48, watch=0x1524dd0, fd=46)
  at qdbusintegrator.cpp:346
  #10 0xb5ae18f6 in ?? ()

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

** 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 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 lxc-android-config package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
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.

  == Test Case ==

  # Prepare debugging
  adb shell
  sudo apt install qtbase5-dbg libc6-dbg libdbus-glib-1-2-dbg dbus-1-dbg 
libglib2.0-0-dbg
  echo deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe 
multiverse | sudo tee -a /etc/apt/sources.list.d/ddebs.list
  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 428D7C01
  sudo apt-get update
  sudo apt install libusermetricsoutput1-dbgsym=1.1.1+15.04.20150219-0ubuntu1

  # Start the reboot loop
  # This reboots the device in a loop, and if this bug is not fixed by whatever 
proposed solution, it will hang eventually. Current highest amount of reboots 
without errors is 54, so it's probable a 100 reboots is needed for testing.

  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done

  # When it fails
  adb shell
  sudo gdb -p $(pidof unity8)
  bt

  --
  At this point, the backtrace should show:
  #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  #1  0xb6301e12 in _q_futex (op=0, val=3, timeout=0x0, addr=optimized out)
  at thread/qmutex_linux.cpp:146
  #2  lockInternal_helperfalse (timeout=-1, elapsedTimer=0x0, d_ptr=...)
  at thread/qmutex_linux.cpp:187
  #3  QBasicMutex::lockInternal (this=this@entry=0x1523b44)
  at thread/qmutex_linux.cpp:203
  #4  0xb6301eb6 in lock (this=0x1523b44) at thread/qmutex.h:59
  #5  lock (timeout=-1, this=0x1523b38) at thread/qmutex.cpp:620
  #6  QMutex::lock (this=this@entry=0x1523d6c) at thread/qmutex.cpp:215
  #7  0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48,
  a=ToggleWatchAction, this=synthetic pointer) at qdbusthreaddebug_p.h:183
  #8  QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction,
  this=synthetic pointer) at qdbusthreaddebug_p.h:198
  #9  qDBusRealToggleWatch (d=0x1523d48, watch=0x1524dd0, fd=46)
  at qdbusintegrator.cpp:346
  #10 0xb5ae18f6 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3

  With this, it's know that it was a QDBus locking related problem.
  --

  ---

  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
  2015-04-10: Further patches from upstream fix all AP tests.
  2015-04-23:

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

(note that the path and member may be different on each hang)

-- 
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 lxc-android-config package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
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.

  == Test Case ==

  # Prepare debugging
  adb shell
  sudo apt install qtbase5-dbg libc6-dbg libdbus-glib-1-2-dbg dbus-1-dbg 
libglib2.0-0-dbg
  echo deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe 
multiverse | sudo tee -a /etc/apt/sources.list.d/ddebs.list
  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 428D7C01
  sudo apt-get update
  sudo apt install libusermetricsoutput1-dbgsym=1.1.1+15.04.20150219-0ubuntu1

  # Start the reboot loop
  # This reboots the device in a loop, and if this bug is not fixed by whatever 
proposed solution, it will hang eventually. Current highest amount of reboots 
without errors is 54, so it's probable a 100 reboots is needed for testing.

  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done

  # When it fails
  adb shell
  sudo gdb -p $(pidof unity8)
  bt

  --
  At this point, the backtrace should show:
  #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  #1  0xb6301e12 in _q_futex (op=0, val=3, timeout=0x0, addr=optimized out)
  at thread/qmutex_linux.cpp:146
  #2  lockInternal_helperfalse (timeout=-1, elapsedTimer=0x0, d_ptr=...)
  at thread/qmutex_linux.cpp:187
  #3  QBasicMutex::lockInternal (this=this@entry=0x1523b44)
  at thread/qmutex_linux.cpp:203
  #4  0xb6301eb6 in lock (this=0x1523b44) at thread/qmutex.h:59
  #5  lock (timeout=-1, this=0x1523b38) at thread/qmutex.cpp:620
  #6  QMutex::lock (this=this@entry=0x1523d6c) at thread/qmutex.cpp:215
  #7  0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48,
  a=ToggleWatchAction, this=synthetic pointer) at qdbusthreaddebug_p.h:183
  #8  QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction,
  this=synthetic pointer) at qdbusthreaddebug_p.h:198
  #9  qDBusRealToggleWatch (d=0x1523d48, watch=0x1524dd0, fd=46)
  at qdbusintegrator.cpp:346
  #10 0xb5ae18f6 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3

  With this, it's know that it was a QDBus locking related problem.
  --

  ---

  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
  2015-04-10: Further patches from upstream fix all AP tests.
  2015-04-23: Upstream continues to work on the patches but they have not yet 
been merged. AP:s pass, but U1 account gets

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

2015-04-27 Thread Albert Astals Cid

** Branch linked: lp:~aacid/unity8/useOwnDbusConnections

-- 
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 lxc-android-config package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
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.

  == Test Case ==

  # Prepare debugging
  adb shell
  sudo apt install qtbase5-dbg libc6-dbg libdbus-glib-1-2-dbg dbus-1-dbg 
libglib2.0-0-dbg
  echo deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe 
multiverse | sudo tee -a /etc/apt/sources.list.d/ddebs.list
  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 428D7C01
  sudo apt-get update
  sudo apt install libusermetricsoutput1-dbgsym=1.1.1+15.04.20150219-0ubuntu1

  # Start the reboot loop
  # This reboots the device in a loop, and if this bug is not fixed by whatever 
proposed solution, it will hang eventually. Current highest amount of reboots 
without errors is 54, so it's probable a 100 reboots is needed for testing.

  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done

  # When it fails
  adb shell
  sudo gdb -p $(pidof unity8)
  bt

  --
  At this point, the backtrace should show:
  #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  #1  0xb6301e12 in _q_futex (op=0, val=3, timeout=0x0, addr=optimized out)
  at thread/qmutex_linux.cpp:146
  #2  lockInternal_helperfalse (timeout=-1, elapsedTimer=0x0, d_ptr=...)
  at thread/qmutex_linux.cpp:187
  #3  QBasicMutex::lockInternal (this=this@entry=0x1523b44)
  at thread/qmutex_linux.cpp:203
  #4  0xb6301eb6 in lock (this=0x1523b44) at thread/qmutex.h:59
  #5  lock (timeout=-1, this=0x1523b38) at thread/qmutex.cpp:620
  #6  QMutex::lock (this=this@entry=0x1523d6c) at thread/qmutex.cpp:215
  #7  0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48,
  a=ToggleWatchAction, this=synthetic pointer) at qdbusthreaddebug_p.h:183
  #8  QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction,
  this=synthetic pointer) at qdbusthreaddebug_p.h:198
  #9  qDBusRealToggleWatch (d=0x1523d48, watch=0x1524dd0, fd=46)
  at qdbusintegrator.cpp:346
  #10 0xb5ae18f6 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3

  With this, it's know that it was a QDBus locking related problem.
  --

  ---

  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
  2015-04-10: Further patches from upstream fix all AP tests.
  2015-04-23: Upstream continues to work on the patches but they have not yet 
been merged. AP:s pass, but U1 account gets removed

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

** 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 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.
  
  == Test Case ==
  
  # Prepare debugging
  adb shell
- sudo apt install qtbase5-dbg libc6-dbg
+ sudo apt install qtbase5-dbg libc6-dbg libdbus-glib-1-2-dbg dbus-1-dbg
  
  # Start the reboot loop
  # This reboots the device in a loop, and if this bug is not fixed by whatever 
proposed solution, it will hang eventually. Current highest amount of reboots 
without errors is 54, so it's probable a 100 reboots is needed for testing.
  
  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done
  
  # When it fails
  adb shell
  sudo gdb -p $(pidof unity8)
  bt
  
  --
  At this point, the backtrace should show:
  #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  #1  0xb6301e12 in _q_futex (op=0, val=3, timeout=0x0, addr=optimized out)
- at thread/qmutex_linux.cpp:146
+ at thread/qmutex_linux.cpp:146
  #2  lockInternal_helperfalse (timeout=-1, elapsedTimer=0x0, d_ptr=...)
- at thread/qmutex_linux.cpp:187
+ at thread/qmutex_linux.cpp:187
  #3  QBasicMutex::lockInternal (this=this@entry=0x1523b44)
- at thread/qmutex_linux.cpp:203
+ at thread/qmutex_linux.cpp:203
  #4  0xb6301eb6 in lock (this=0x1523b44) at thread/qmutex.h:59
  #5  lock (timeout=-1, this=0x1523b38) at thread/qmutex.cpp:620
  #6  QMutex::lock (this=this@entry=0x1523d6c) at thread/qmutex.cpp:215
- #7  0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48, 
- a=ToggleWatchAction, this=synthetic pointer) at qdbusthreaddebug_p.h:183
- #8  QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction, 
- this=synthetic pointer) at qdbusthreaddebug_p.h:198
+ #7  0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48,
+ a=ToggleWatchAction, this=synthetic pointer) at qdbusthreaddebug_p.h:183
+ #8  QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction,
+ this=synthetic pointer) at qdbusthreaddebug_p.h:198
  #9  qDBusRealToggleWatch (d=0x1523d48, watch=0x1524dd0, fd=46)
- at qdbusintegrator.cpp:346
+ at qdbusintegrator.cpp:346
  #10 0xb5ae18f6 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3
  
  With this, it's know that it was a QDBus locking related problem.
  --
  
  ---
  
  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
  2015-04-10: Further patches from upstream fix all AP tests.
  2015-04-23: Upstream continues to work on the patches but they have not yet 
been merged. AP:s pass, but U1 account gets removed usually after a reboot, 
even though apps can be installed after adding U1 account flawlessly for the 
duration of that boot.

** 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 krillin devices starting with image 106 from
  ubuntu-touch/devel-proposed. It doesn't happen every time, so far today,

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

** 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 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.
  
  == Test Case ==
  
  # Prepare debugging
  adb shell
  sudo apt install qtbase5-dbg libc6-dbg libdbus-glib-1-2-dbg dbus-1-dbg 
libglib2.0-0-dbg
+ echo deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe 
multiverse | sudo tee -a /etc/apt/sources.list.d/ddebs.list
+ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 428D7C01
+ sudo apt-get update
+ sudo apt install libusermetricsoutput1-dbgsym=1.1.1+15.04.20150219-0ubuntu1
  
  # Start the reboot loop
  # This reboots the device in a loop, and if this bug is not fixed by whatever 
proposed solution, it will hang eventually. Current highest amount of reboots 
without errors is 54, so it's probable a 100 reboots is needed for testing.
  
  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done
  
  # When it fails
  adb shell
  sudo gdb -p $(pidof unity8)
  bt
  
  --
  At this point, the backtrace should show:
  #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  #1  0xb6301e12 in _q_futex (op=0, val=3, timeout=0x0, addr=optimized out)
  at thread/qmutex_linux.cpp:146
  #2  lockInternal_helperfalse (timeout=-1, elapsedTimer=0x0, d_ptr=...)
  at thread/qmutex_linux.cpp:187
  #3  QBasicMutex::lockInternal (this=this@entry=0x1523b44)
  at thread/qmutex_linux.cpp:203
  #4  0xb6301eb6 in lock (this=0x1523b44) at thread/qmutex.h:59
  #5  lock (timeout=-1, this=0x1523b38) at thread/qmutex.cpp:620
  #6  QMutex::lock (this=this@entry=0x1523d6c) at thread/qmutex.cpp:215
  #7  0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48,
  a=ToggleWatchAction, this=synthetic pointer) at qdbusthreaddebug_p.h:183
  #8  QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction,
  this=synthetic pointer) at qdbusthreaddebug_p.h:198
  #9  qDBusRealToggleWatch (d=0x1523d48, watch=0x1524dd0, fd=46)
  at qdbusintegrator.cpp:346
  #10 0xb5ae18f6 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3
  
  With this, it's know that it was a QDBus locking related problem.
  --
  
  ---
  
  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
  2015-04-10: Further patches from upstream fix all AP tests.
  2015-04-23: Upstream continues to work on the patches but they have not yet 
been merged. AP:s pass, but U1 account gets removed usually after a reboot, 
even though apps can be installed after adding U1 account flawlessly for the 
duration of that boot.

-- 
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 lxc-android-config package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

** Branch linked: lp:~timo-jyrinki/libusermetrics/dont-share-dbus-
sessionbus-connections

-- 
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 lxc-android-config package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
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.

  == Test Case ==

  # Prepare debugging
  adb shell
  sudo apt install qtbase5-dbg libc6-dbg libdbus-glib-1-2-dbg dbus-1-dbg 
libglib2.0-0-dbg
  echo deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe 
multiverse | sudo tee -a /etc/apt/sources.list.d/ddebs.list
  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 428D7C01
  sudo apt-get update
  sudo apt install libusermetricsoutput1-dbgsym=1.1.1+15.04.20150219-0ubuntu1

  # Start the reboot loop
  # This reboots the device in a loop, and if this bug is not fixed by whatever 
proposed solution, it will hang eventually. Current highest amount of reboots 
without errors is 54, so it's probable a 100 reboots is needed for testing.

  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done

  # When it fails
  adb shell
  sudo gdb -p $(pidof unity8)
  bt

  --
  At this point, the backtrace should show:
  #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  #1  0xb6301e12 in _q_futex (op=0, val=3, timeout=0x0, addr=optimized out)
  at thread/qmutex_linux.cpp:146
  #2  lockInternal_helperfalse (timeout=-1, elapsedTimer=0x0, d_ptr=...)
  at thread/qmutex_linux.cpp:187
  #3  QBasicMutex::lockInternal (this=this@entry=0x1523b44)
  at thread/qmutex_linux.cpp:203
  #4  0xb6301eb6 in lock (this=0x1523b44) at thread/qmutex.h:59
  #5  lock (timeout=-1, this=0x1523b38) at thread/qmutex.cpp:620
  #6  QMutex::lock (this=this@entry=0x1523d6c) at thread/qmutex.cpp:215
  #7  0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48,
  a=ToggleWatchAction, this=synthetic pointer) at qdbusthreaddebug_p.h:183
  #8  QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction,
  this=synthetic pointer) at qdbusthreaddebug_p.h:198
  #9  qDBusRealToggleWatch (d=0x1523d48, watch=0x1524dd0, fd=46)
  at qdbusintegrator.cpp:346
  #10 0xb5ae18f6 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3

  With this, it's know that it was a QDBus locking related problem.
  --

  ---

  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
  2015-04-10: Further patches from upstream fix all AP tests.
  2015-04-23: Upstream continues to work on the patches but they have not yet 
been merged. AP:s

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

** 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 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.
  
  == Test Case ==
  
  # Prepare debugging
  adb shell
  sudo apt install qtbase5-dbg libc6-dbg libdbus-glib-1-2-dbg dbus-1-dbg 
libglib2.0-0-dbg
  echo deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe 
multiverse | sudo tee -a /etc/apt/sources.list.d/ddebs.list
  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 428D7C01
  sudo apt-get update
  sudo apt install libusermetricsoutput1-dbgsym=1.1.1+15.04.20150219-0ubuntu1
  
  # Start the reboot loop
  # This reboots the device in a loop, and if this bug is not fixed by whatever 
proposed solution, it will hang eventually. Current highest amount of reboots 
without errors is 54, so it's probable a 100 reboots is needed for testing.
  
  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done
  
  # When it fails
  adb shell
  sudo gdb -p $(pidof unity8)
- bt
+ bt full
  
  --
  At this point, the backtrace should show:
  #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  #1  0xb6301e12 in _q_futex (op=0, val=3, timeout=0x0, addr=optimized out)
  at thread/qmutex_linux.cpp:146
  #2  lockInternal_helperfalse (timeout=-1, elapsedTimer=0x0, d_ptr=...)
  at thread/qmutex_linux.cpp:187
  #3  QBasicMutex::lockInternal (this=this@entry=0x1523b44)
  at thread/qmutex_linux.cpp:203
  #4  0xb6301eb6 in lock (this=0x1523b44) at thread/qmutex.h:59
  #5  lock (timeout=-1, this=0x1523b38) at thread/qmutex.cpp:620
  #6  QMutex::lock (this=this@entry=0x1523d6c) at thread/qmutex.cpp:215
  #7  0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48,
  a=ToggleWatchAction, this=synthetic pointer) at qdbusthreaddebug_p.h:183
  #8  QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction,
  this=synthetic pointer) at qdbusthreaddebug_p.h:198
  #9  qDBusRealToggleWatch (d=0x1523d48, watch=0x1524dd0, fd=46)
  at qdbusintegrator.cpp:346
  #10 0xb5ae18f6 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3
  
  With this, it's know that it was a QDBus locking related problem.
  --
  
  ---
  
  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
  2015-04-10: Further patches from upstream fix all AP tests.
  2015-04-23: Upstream continues to work on the patches but they have not yet 
been merged. AP:s pass, but U1 account gets removed usually after a reboot, 
even though apps can be installed after adding U1 account flawlessly for the 
duration of that boot.

-- 
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 lxc-android-config package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

** 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 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.
  
  == Test Case ==
  
  # Prepare debugging
  adb shell
+ sudo apt-get clean # so that you wouldn't run out of disk space
  sudo apt install qtbase5-dbg libc6-dbg libdbus-glib-1-2-dbg dbus-1-dbg 
libglib2.0-0-dbg
  
  # Add also libusermetrics debug symbols, unless you're testing a PPA version
  echo deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe 
multiverse | sudo tee -a /etc/apt/sources.list.d/ddebs.list
  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 428D7C01
  sudo apt-get update
  sudo apt install libusermetricsoutput1-dbgsym=1.1.1+15.04.20150219-0ubuntu1
  
  # Start the reboot loop
  # This reboots the device in a loop, and if this bug is not fixed by whatever 
proposed solution, it will hang eventually. Current highest amount of reboots 
without errors is 54, so it's probable a 100 reboots is needed for testing.
  
  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done
  
  # When it fails
  adb shell
  sudo gdb -p $(pidof unity8)
  bt full
  
  --
  At this point, the backtrace should show:
  #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  #1  0xb6301e12 in _q_futex (op=0, val=3, timeout=0x0, addr=optimized out)
  at thread/qmutex_linux.cpp:146
  #2  lockInternal_helperfalse (timeout=-1, elapsedTimer=0x0, d_ptr=...)
  at thread/qmutex_linux.cpp:187
  #3  QBasicMutex::lockInternal (this=this@entry=0x1523b44)
  at thread/qmutex_linux.cpp:203
  #4  0xb6301eb6 in lock (this=0x1523b44) at thread/qmutex.h:59
  #5  lock (timeout=-1, this=0x1523b38) at thread/qmutex.cpp:620
  #6  QMutex::lock (this=this@entry=0x1523d6c) at thread/qmutex.cpp:215
  #7  0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48,
  a=ToggleWatchAction, this=synthetic pointer) at qdbusthreaddebug_p.h:183
  #8  QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction,
  this=synthetic pointer) at qdbusthreaddebug_p.h:198
  #9  qDBusRealToggleWatch (d=0x1523d48, watch=0x1524dd0, fd=46)
  at qdbusintegrator.cpp:346
  #10 0xb5ae18f6 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3
  
  With this, it's know that it was a QDBus locking related problem.
  --
  
  ---
  
  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
  2015-04-10: Further patches from upstream fix all AP tests.
  2015-04-23: Upstream continues to work on the patches but they have not yet 
been merged. AP:s pass, but U1 account gets removed usually after a reboot, 
even though apps can be installed after adding U1 account flawlessly for the 
duration of that boot.

-- 
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:

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

+ similar changes to unity8 from Albert, the 010 description was meant
to be.

-- 
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:
  In Progress
Status in lxc-android-config package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
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.

  == Test Case ==

  # Prepare debugging
  adb shell
  sudo apt-get clean # so that you wouldn't run out of disk space
  sudo apt install qtbase5-dbg libc6-dbg libdbus-glib-1-2-dbg dbus-1-dbg 
libglib2.0-0-dbg

  # Add also libusermetrics debug symbols, unless you're testing a PPA version
  echo deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe 
multiverse | sudo tee -a /etc/apt/sources.list.d/ddebs.list
  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 428D7C01
  sudo apt-get update
  sudo apt install libusermetricsoutput1-dbgsym=1.1.1+15.04.20150219-0ubuntu1

  # Start the reboot loop
  # This reboots the device in a loop, and if this bug is not fixed by whatever 
proposed solution, it will hang eventually. Current highest amount of reboots 
without errors is 54, so it's probable a 100 reboots is needed for testing.

  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done

  # When it fails
  adb shell
  sudo gdb -p $(pidof unity8)
  bt full

  --
  At this point, the backtrace should show:
  #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  #1  0xb6301e12 in _q_futex (op=0, val=3, timeout=0x0, addr=optimized out)
  at thread/qmutex_linux.cpp:146
  #2  lockInternal_helperfalse (timeout=-1, elapsedTimer=0x0, d_ptr=...)
  at thread/qmutex_linux.cpp:187
  #3  QBasicMutex::lockInternal (this=this@entry=0x1523b44)
  at thread/qmutex_linux.cpp:203
  #4  0xb6301eb6 in lock (this=0x1523b44) at thread/qmutex.h:59
  #5  lock (timeout=-1, this=0x1523b38) at thread/qmutex.cpp:620
  #6  QMutex::lock (this=this@entry=0x1523d6c) at thread/qmutex.cpp:215
  #7  0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48,
  a=ToggleWatchAction, this=synthetic pointer) at qdbusthreaddebug_p.h:183
  #8  QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction,
  this=synthetic pointer) at qdbusthreaddebug_p.h:198
  #9  qDBusRealToggleWatch (d=0x1523d48, watch=0x1524dd0, fd=46)
  at qdbusintegrator.cpp:346
  #10 0xb5ae18f6 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3

  With this, it's know that it was a QDBus locking related problem.
  --

  ---

  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
  2015-04-10:

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

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 changes to libusermetrics only (note, Pete is updating his branch but 
the current build is from his first revision that only updated systemBus calls)
- https://launchpad.net/~canonical-qt5-edgers/+archive/qt5-proper/ - Pete's and 
my changes to libusermetrics
- https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-010/ - 
Pete's and my changes to libusermetrics + similar 

Using 007, my mako is now at 105 reboots and counting.

-- 
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:
  In Progress
Status in lxc-android-config package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
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.

  == Test Case ==

  # Prepare debugging
  adb shell
  sudo apt-get clean # so that you wouldn't run out of disk space
  sudo apt install qtbase5-dbg libc6-dbg libdbus-glib-1-2-dbg dbus-1-dbg 
libglib2.0-0-dbg

  # Add also libusermetrics debug symbols, unless you're testing a PPA version
  echo deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe 
multiverse | sudo tee -a /etc/apt/sources.list.d/ddebs.list
  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 428D7C01
  sudo apt-get update
  sudo apt install libusermetricsoutput1-dbgsym=1.1.1+15.04.20150219-0ubuntu1

  # Start the reboot loop
  # This reboots the device in a loop, and if this bug is not fixed by whatever 
proposed solution, it will hang eventually. Current highest amount of reboots 
without errors is 54, so it's probable a 100 reboots is needed for testing.

  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done

  # When it fails
  adb shell
  sudo gdb -p $(pidof unity8)
  bt full

  --
  At this point, the backtrace should show:
  #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  #1  0xb6301e12 in _q_futex (op=0, val=3, timeout=0x0, addr=optimized out)
  at thread/qmutex_linux.cpp:146
  #2  lockInternal_helperfalse (timeout=-1, elapsedTimer=0x0, d_ptr=...)
  at thread/qmutex_linux.cpp:187
  #3  QBasicMutex::lockInternal (this=this@entry=0x1523b44)
  at thread/qmutex_linux.cpp:203
  #4  0xb6301eb6 in lock (this=0x1523b44) at thread/qmutex.h:59
  #5  lock (timeout=-1, this=0x1523b38) at thread/qmutex.cpp:620
  #6  QMutex::lock (this=this@entry=0x1523d6c) at thread/qmutex.cpp:215
  #7  0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48,
  a=ToggleWatchAction, this=synthetic pointer) at qdbusthreaddebug_p.h:183
  #8  QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction,
  this=synthetic pointer) at qdbusthreaddebug_p.h:198
  #9  qDBusRealToggleWatch (d=0x1523d48, watch=0x1524dd0, fd=46)
  at qdbusintegrator.cpp:346
  #10 0xb5ae18f6 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3

  With this, it's know that it was a QDBus locking related problem.
  --

  ---

  Timeline/Updates:
  2015-02-20: libusermetrics lands, causing (apparently) this boot problem to 
start happening rarely.

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

2015-04-27 Thread Pete Woods

** 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 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:
  In Progress
Status in lxc-android-config package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
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.

  == Test Case ==

  # Prepare debugging
  adb shell
  sudo apt-get clean # so that you wouldn't run out of disk space
  sudo apt install qtbase5-dbg libc6-dbg libdbus-glib-1-2-dbg dbus-1-dbg 
libglib2.0-0-dbg

  # Add also libusermetrics debug symbols, unless you're testing a PPA version
  echo deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe 
multiverse | sudo tee -a /etc/apt/sources.list.d/ddebs.list
  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 428D7C01
  sudo apt-get update
  sudo apt install libusermetricsoutput1-dbgsym=1.1.1+15.04.20150219-0ubuntu1

  # Start the reboot loop
  # This reboots the device in a loop, and if this bug is not fixed by whatever 
proposed solution, it will hang eventually. Current highest amount of reboots 
without errors is 54, so it's probable a 100 reboots is needed for testing.

  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done

  # When it fails
  adb shell
  sudo gdb -p $(pidof unity8)
  bt full

  --
  At this point, the backtrace should show:
  #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  #1  0xb6301e12 in _q_futex (op=0, val=3, timeout=0x0, addr=optimized out)
  at thread/qmutex_linux.cpp:146
  #2  lockInternal_helperfalse (timeout=-1, elapsedTimer=0x0, d_ptr=...)
  at thread/qmutex_linux.cpp:187
  #3  QBasicMutex::lockInternal (this=this@entry=0x1523b44)
  at thread/qmutex_linux.cpp:203
  #4  0xb6301eb6 in lock (this=0x1523b44) at thread/qmutex.h:59
  #5  lock (timeout=-1, this=0x1523b38) at thread/qmutex.cpp:620
  #6  QMutex::lock (this=this@entry=0x1523d6c) at thread/qmutex.cpp:215
  #7  0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48,
  a=ToggleWatchAction, this=synthetic pointer) at qdbusthreaddebug_p.h:183
  #8  QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction,
  this=synthetic pointer) at qdbusthreaddebug_p.h:198
  #9  qDBusRealToggleWatch (d=0x1523d48, watch=0x1524dd0, fd=46)
  at qdbusintegrator.cpp:346
  #10 0xb5ae18f6 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3

  With this, it's know that it was a QDBus locking related problem.
  --

  ---

  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

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

** 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 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.
  
  == Test Case ==
  
  # Prepare debugging
  adb shell
  sudo apt install qtbase5-dbg libc6-dbg libdbus-glib-1-2-dbg dbus-1-dbg 
libglib2.0-0-dbg
+ 
+ # Add also libusermetrics debug symbols, unless you're testing a PPA version
  echo deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe 
multiverse | sudo tee -a /etc/apt/sources.list.d/ddebs.list
  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 428D7C01
  sudo apt-get update
  sudo apt install libusermetricsoutput1-dbgsym=1.1.1+15.04.20150219-0ubuntu1
  
  # Start the reboot loop
  # This reboots the device in a loop, and if this bug is not fixed by whatever 
proposed solution, it will hang eventually. Current highest amount of reboots 
without errors is 54, so it's probable a 100 reboots is needed for testing.
  
  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done
  
  # When it fails
  adb shell
  sudo gdb -p $(pidof unity8)
  bt full
  
  --
  At this point, the backtrace should show:
  #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  #1  0xb6301e12 in _q_futex (op=0, val=3, timeout=0x0, addr=optimized out)
  at thread/qmutex_linux.cpp:146
  #2  lockInternal_helperfalse (timeout=-1, elapsedTimer=0x0, d_ptr=...)
  at thread/qmutex_linux.cpp:187
  #3  QBasicMutex::lockInternal (this=this@entry=0x1523b44)
  at thread/qmutex_linux.cpp:203
  #4  0xb6301eb6 in lock (this=0x1523b44) at thread/qmutex.h:59
  #5  lock (timeout=-1, this=0x1523b38) at thread/qmutex.cpp:620
  #6  QMutex::lock (this=this@entry=0x1523d6c) at thread/qmutex.cpp:215
  #7  0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48,
  a=ToggleWatchAction, this=synthetic pointer) at qdbusthreaddebug_p.h:183
  #8  QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction,
  this=synthetic pointer) at qdbusthreaddebug_p.h:198
  #9  qDBusRealToggleWatch (d=0x1523d48, watch=0x1524dd0, fd=46)
  at qdbusintegrator.cpp:346
  #10 0xb5ae18f6 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3
  
  With this, it's know that it was a QDBus locking related problem.
  --
  
  ---
  
  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
  2015-04-10: Further patches from upstream fix all AP tests.
  2015-04-23: Upstream continues to work on the patches but they have not yet 
been merged. AP:s pass, but U1 account gets removed usually after a reboot, 
even though apps can be installed after adding U1 account flawlessly for the 
duration of that boot.

-- 
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 lxc-android-config package in Ubuntu:

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

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
to revalidate that and if that's good, put it to QA for sign-off. Unity
8 changes would not be needed at this point.

So, testing should be done with https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/landing-017 once it has finished building.

-- 
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:
  In Progress
Status in lxc-android-config package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
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.

  == Test Case ==

  # Prepare debugging
  adb shell
  sudo apt-get clean # so that you wouldn't run out of disk space
  sudo apt install qtbase5-dbg libc6-dbg libdbus-glib-1-2-dbg dbus-1-dbg 
libglib2.0-0-dbg

  # Add also libusermetrics debug symbols, unless you're testing a PPA version
  echo deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe 
multiverse | sudo tee -a /etc/apt/sources.list.d/ddebs.list
  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 428D7C01
  sudo apt-get update
  sudo apt install libusermetricsoutput1-dbgsym=1.1.1+15.04.20150219-0ubuntu1

  # Start the reboot loop
  # This reboots the device in a loop, and if this bug is not fixed by whatever 
proposed solution, it will hang eventually. Current highest amount of reboots 
without errors is 54, so it's probable a 100 reboots is needed for testing.

  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done

  # When it fails
  adb shell
  sudo gdb -p $(pidof unity8)
  bt full

  --
  At this point, the backtrace should show:
  #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  #1  0xb6301e12 in _q_futex (op=0, val=3, timeout=0x0, addr=optimized out)
  at thread/qmutex_linux.cpp:146
  #2  lockInternal_helperfalse (timeout=-1, elapsedTimer=0x0, d_ptr=...)
  at thread/qmutex_linux.cpp:187
  #3  QBasicMutex::lockInternal (this=this@entry=0x1523b44)
  at thread/qmutex_linux.cpp:203
  #4  0xb6301eb6 in lock (this=0x1523b44) at thread/qmutex.h:59
  #5  lock (timeout=-1, this=0x1523b38) at thread/qmutex.cpp:620
  #6  QMutex::lock (this=this@entry=0x1523d6c) at thread/qmutex.cpp:215
  #7  0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48,
  a=ToggleWatchAction, this=synthetic pointer) at qdbusthreaddebug_p.h:183
  #8  QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction,
  this=synthetic pointer) at qdbusthreaddebug_p.h:198
  #9  qDBusRealToggleWatch (d=0x1523d48, watch=0x1524dd0, fd=46)
  at qdbusintegrator.cpp:346
  #10 0xb5ae18f6 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3

  With this, it's know that it was a QDBus locking related problem.
  --

  ---

  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

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

2015-04-27 Thread Launchpad Bug Tracker

** Branch linked: lp:~mardy/ubuntu-system-settings-online-
accounts/lp1447175

-- 
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:
  In Progress
Status in lxc-android-config package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
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.

  == Test Case ==

  # Prepare debugging
  adb shell
  sudo apt-get clean # so that you wouldn't run out of disk space
  sudo apt install qtbase5-dbg libc6-dbg libdbus-glib-1-2-dbg dbus-1-dbg 
libglib2.0-0-dbg

  # Add also libusermetrics debug symbols, unless you're testing a PPA version
  echo deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe 
multiverse | sudo tee -a /etc/apt/sources.list.d/ddebs.list
  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 428D7C01
  sudo apt-get update
  sudo apt install libusermetricsoutput1-dbgsym=1.1.1+15.04.20150219-0ubuntu1

  # Start the reboot loop
  # This reboots the device in a loop, and if this bug is not fixed by whatever 
proposed solution, it will hang eventually. Current highest amount of reboots 
without errors is 54, so it's probable a 100 reboots is needed for testing.

  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done

  # When it fails
  adb shell
  sudo gdb -p $(pidof unity8)
  bt full

  --
  At this point, the backtrace should show:
  #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  #1  0xb6301e12 in _q_futex (op=0, val=3, timeout=0x0, addr=optimized out)
  at thread/qmutex_linux.cpp:146
  #2  lockInternal_helperfalse (timeout=-1, elapsedTimer=0x0, d_ptr=...)
  at thread/qmutex_linux.cpp:187
  #3  QBasicMutex::lockInternal (this=this@entry=0x1523b44)
  at thread/qmutex_linux.cpp:203
  #4  0xb6301eb6 in lock (this=0x1523b44) at thread/qmutex.h:59
  #5  lock (timeout=-1, this=0x1523b38) at thread/qmutex.cpp:620
  #6  QMutex::lock (this=this@entry=0x1523d6c) at thread/qmutex.cpp:215
  #7  0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48,
  a=ToggleWatchAction, this=synthetic pointer) at qdbusthreaddebug_p.h:183
  #8  QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction,
  this=synthetic pointer) at qdbusthreaddebug_p.h:198
  #9  qDBusRealToggleWatch (d=0x1523d48, watch=0x1524dd0, fd=46)
  at qdbusintegrator.cpp:346
  #10 0xb5ae18f6 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3

  With this, it's know that it was a QDBus locking related problem.
  --

  ---

  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
  2015-04-10:

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

2015-04-27 Thread Alberto Mardegan

** Branch unlinked: lp:~mardy/ubuntu-system-settings-online-
accounts/lp1421009

-- 
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:
  In Progress
Status in lxc-android-config package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
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.

  == Test Case ==

  # Prepare debugging
  adb shell
  sudo apt-get clean # so that you wouldn't run out of disk space
  sudo apt install qtbase5-dbg libc6-dbg libdbus-glib-1-2-dbg dbus-1-dbg 
libglib2.0-0-dbg

  # Add also libusermetrics debug symbols, unless you're testing a PPA version
  echo deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe 
multiverse | sudo tee -a /etc/apt/sources.list.d/ddebs.list
  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 428D7C01
  sudo apt-get update
  sudo apt install libusermetricsoutput1-dbgsym=1.1.1+15.04.20150219-0ubuntu1

  # Start the reboot loop
  # This reboots the device in a loop, and if this bug is not fixed by whatever 
proposed solution, it will hang eventually. Current highest amount of reboots 
without errors is 54, so it's probable a 100 reboots is needed for testing.

  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done

  # When it fails
  adb shell
  sudo gdb -p $(pidof unity8)
  bt full

  --
  At this point, the backtrace should show:
  #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  #1  0xb6301e12 in _q_futex (op=0, val=3, timeout=0x0, addr=optimized out)
  at thread/qmutex_linux.cpp:146
  #2  lockInternal_helperfalse (timeout=-1, elapsedTimer=0x0, d_ptr=...)
  at thread/qmutex_linux.cpp:187
  #3  QBasicMutex::lockInternal (this=this@entry=0x1523b44)
  at thread/qmutex_linux.cpp:203
  #4  0xb6301eb6 in lock (this=0x1523b44) at thread/qmutex.h:59
  #5  lock (timeout=-1, this=0x1523b38) at thread/qmutex.cpp:620
  #6  QMutex::lock (this=this@entry=0x1523d6c) at thread/qmutex.cpp:215
  #7  0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48,
  a=ToggleWatchAction, this=synthetic pointer) at qdbusthreaddebug_p.h:183
  #8  QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction,
  this=synthetic pointer) at qdbusthreaddebug_p.h:198
  #9  qDBusRealToggleWatch (d=0x1523d48, watch=0x1524dd0, fd=46)
  at qdbusintegrator.cpp:346
  #10 0xb5ae18f6 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3

  With this, it's know that it was a QDBus locking related problem.
  --

  ---

  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
  2015-04-10:

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

** 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 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.
  
  == Test Case ==
  
  # Prepare debugging
  adb shell
  sudo apt-get clean # so that you wouldn't run out of disk space
  sudo apt install qtbase5-dbg libc6-dbg libdbus-glib-1-2-dbg dbus-1-dbg 
libglib2.0-0-dbg
  
  # Add also libusermetrics debug symbols, unless you're testing a PPA version
  echo deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe 
multiverse | sudo tee -a /etc/apt/sources.list.d/ddebs.list
  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 428D7C01
  sudo apt-get update
  sudo apt install libusermetricsoutput1-dbgsym=1.1.1+15.04.20150219-0ubuntu1
  
  # Start the reboot loop
- # This reboots the device in a loop, and if this bug is not fixed by whatever 
proposed solution, it will hang eventually. Current highest amount of reboots 
without errors is 54, so it's probable a 100 reboots is needed for testing.
+ # This reboots the device in a loop, and if this bug is not fixed by whatever 
proposed solution, it will hang eventually with Unity 8 having a black 
background. Other kind of hangs (like just Google logo showing, no adb) are not 
related to this bug. Current highest amount of reboots without errors is 54, so 
it's probable a 100 reboots is needed for testing.
  
  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done
  
  # When it fails
  adb shell
  sudo gdb -p $(pidof unity8)
  bt full
  
  --
  At this point, the backtrace should show:
  #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  #1  0xb6301e12 in _q_futex (op=0, val=3, timeout=0x0, addr=optimized out)
  at thread/qmutex_linux.cpp:146
  #2  lockInternal_helperfalse (timeout=-1, elapsedTimer=0x0, d_ptr=...)
  at thread/qmutex_linux.cpp:187
  #3  QBasicMutex::lockInternal (this=this@entry=0x1523b44)
  at thread/qmutex_linux.cpp:203
  #4  0xb6301eb6 in lock (this=0x1523b44) at thread/qmutex.h:59
  #5  lock (timeout=-1, this=0x1523b38) at thread/qmutex.cpp:620
  #6  QMutex::lock (this=this@entry=0x1523d6c) at thread/qmutex.cpp:215
  #7  0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48,
  a=ToggleWatchAction, this=synthetic pointer) at qdbusthreaddebug_p.h:183
  #8  QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction,
  this=synthetic pointer) at qdbusthreaddebug_p.h:198
  #9  qDBusRealToggleWatch (d=0x1523d48, watch=0x1524dd0, fd=46)
  at qdbusintegrator.cpp:346
  #10 0xb5ae18f6 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3
  
  With this, it's know that it was a QDBus locking related problem.
  --
  
  ---
  
  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
  2015-04-10: Further patches from upstream fix all AP tests.
  2015-04-23: Upstream continues to work on the patches but they have not yet 
been merged. AP:s pass, but U1 account gets removed usually after a reboot, 
even though apps can be installed after adding U1 account flawlessly for the 
duration of that boot.

-- 
You received

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

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 ci-train-...@canonical.com  Mon, 27 Apr 2015 15:38:43
+

The bug will stay open for the possibility of getting the reworked QDBus
from upstream at some point.

** Changed in: libusermetrics (Ubuntu)
   Status: In Progress = Fix Released

** Changed in: canonical-devices-system-image
   Status: In Progress = Fix Committed

** Changed in: lxc-android-config (Ubuntu)
   Status: Incomplete = Invalid

** Changed in: qtbase-opensource-src (Ubuntu)
   Importance: Critical = High

-- 
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:
  Fix Committed
Status in autopilot package in Ubuntu:
  Fix Released
Status in libusermetrics package in Ubuntu:
  Fix Released
Status in lxc-android-config package in Ubuntu:
  Invalid
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
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.

  == Test Case ==

  # Prepare debugging
  adb shell
  sudo apt-get clean # so that you wouldn't run out of disk space
  sudo apt install qtbase5-dbg libc6-dbg libdbus-glib-1-2-dbg dbus-1-dbg 
libglib2.0-0-dbg

  # Add also libusermetrics debug symbols, unless you're testing a PPA version
  echo deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe 
multiverse | sudo tee -a /etc/apt/sources.list.d/ddebs.list
  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 428D7C01
  sudo apt-get update
  sudo apt install libusermetricsoutput1-dbgsym=1.1.1+15.04.20150219-0ubuntu1

  # Start the reboot loop
  # This reboots the device in a loop, and if this bug is not fixed by whatever 
proposed solution, it will hang eventually with Unity 8 having a black 
background. Other kind of hangs (like just Google logo showing, no adb) are not 
related to this bug. Current highest amount of reboots without errors is 54, so 
it's probable a 100 reboots is needed for testing.

  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done

  # When it fails
  adb shell
  sudo gdb -p $(pidof unity8)
  bt full

  --
  At this point, the backtrace should show:
  #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  #1  0xb6301e12 in _q_futex (op=0, val=3, timeout=0x0, addr=optimized out)
  at thread/qmutex_linux.cpp:146
  #2  lockInternal_helperfalse (timeout=-1, elapsedTimer=0x0, d_ptr=...)
  at thread/qmutex_linux.cpp:187
  #3  QBasicMutex::lockInternal (this=this@entry=0x1523b44)
  at thread/qmutex_linux.cpp:203
  #4  0xb6301eb6 in lock (this=0x1523b44) at thread/qmutex.h:59
  #5  lock (timeout=-1, this=0x1523b38) at thread/qmutex.cpp:620
  #6  QMutex::lock (this=this@entry=0x1523d6c) at thread/qmutex.cpp:215
  #7  0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48,
  a=ToggleWatchAction, this=synthetic pointer) at qdbusthreaddebug_p.h:183
  #8  QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction,
  this=synthetic pointer) at qdbusthreaddebug_p.h:198
  #9  qDBusRealToggleWatch (d=0x1523d48, watch=0x1524dd0, fd=46)
  at qdbusintegrator.cpp:346
  #10 0xb5ae18f6 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3

  With this, it's know that it was a QDBus locking related problem.
  --

  ---

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

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 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:
  In Progress
Status in lxc-android-config package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
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.

  == Test Case ==

  # Prepare debugging
  adb shell
  sudo apt-get clean # so that you wouldn't run out of disk space
  sudo apt install qtbase5-dbg libc6-dbg libdbus-glib-1-2-dbg dbus-1-dbg 
libglib2.0-0-dbg

  # Add also libusermetrics debug symbols, unless you're testing a PPA version
  echo deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe 
multiverse | sudo tee -a /etc/apt/sources.list.d/ddebs.list
  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 428D7C01
  sudo apt-get update
  sudo apt install libusermetricsoutput1-dbgsym=1.1.1+15.04.20150219-0ubuntu1

  # Start the reboot loop
  # This reboots the device in a loop, and if this bug is not fixed by whatever 
proposed solution, it will hang eventually. Current highest amount of reboots 
without errors is 54, so it's probable a 100 reboots is needed for testing.

  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done

  # When it fails
  adb shell
  sudo gdb -p $(pidof unity8)
  bt full

  --
  At this point, the backtrace should show:
  #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  #1  0xb6301e12 in _q_futex (op=0, val=3, timeout=0x0, addr=optimized out)
  at thread/qmutex_linux.cpp:146
  #2  lockInternal_helperfalse (timeout=-1, elapsedTimer=0x0, d_ptr=...)
  at thread/qmutex_linux.cpp:187
  #3  QBasicMutex::lockInternal (this=this@entry=0x1523b44)
  at thread/qmutex_linux.cpp:203
  #4  0xb6301eb6 in lock (this=0x1523b44) at thread/qmutex.h:59
  #5  lock (timeout=-1, this=0x1523b38) at thread/qmutex.cpp:620
  #6  QMutex::lock (this=this@entry=0x1523d6c) at thread/qmutex.cpp:215
  #7  0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48,
  a=ToggleWatchAction, this=synthetic pointer) at qdbusthreaddebug_p.h:183
  #8  QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction,
  this=synthetic pointer) at qdbusthreaddebug_p.h:198
  #9  qDBusRealToggleWatch (d=0x1523d48, watch=0x1524dd0, fd=46)
  at qdbusintegrator.cpp:346
  #10 0xb5ae18f6 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3

  With this, it's know that it was a QDBus locking related problem.
  --

  ---

  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
  2015-04-10:

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

2015-04-25 Thread Vincent Ladeuil

@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 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 lxc-android-config package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
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.

  == Test Case ==

  # Prepare debugging
  adb shell
  sudo apt install qtbase5-dbg libc6-dbg

  # Start the reboot loop
  # This reboots the device in a loop, and if this bug is not fixed by whatever 
proposed solution, it will hang eventually. Current highest amount of reboots 
without errors is 54, so it's probable a 100 reboots is needed for testing.

  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done

  # When it fails
  adb shell
  sudo gdb -p $(pidof unity8)
  bt

  --
  At this point, the backtrace should show:
  #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  #1  0xb6301e12 in _q_futex (op=0, val=3, timeout=0x0, addr=optimized out)
  at thread/qmutex_linux.cpp:146
  #2  lockInternal_helperfalse (timeout=-1, elapsedTimer=0x0, d_ptr=...)
  at thread/qmutex_linux.cpp:187
  #3  QBasicMutex::lockInternal (this=this@entry=0x1523b44)
  at thread/qmutex_linux.cpp:203
  #4  0xb6301eb6 in lock (this=0x1523b44) at thread/qmutex.h:59
  #5  lock (timeout=-1, this=0x1523b38) at thread/qmutex.cpp:620
  #6  QMutex::lock (this=this@entry=0x1523d6c) at thread/qmutex.cpp:215
  #7  0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48, 
  a=ToggleWatchAction, this=synthetic pointer) at qdbusthreaddebug_p.h:183
  #8  QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction, 
  this=synthetic pointer) at qdbusthreaddebug_p.h:198
  #9  qDBusRealToggleWatch (d=0x1523d48, watch=0x1524dd0, fd=46)
  at qdbusintegrator.cpp:346
  #10 0xb5ae18f6 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3

  With this, it's know that it was a QDBus locking related problem.
  --

  ---

  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
  2015-04-10: Further patches from upstream fix all AP tests.
  2015-04-23: Upstream continues to work on the patches but they have not yet 
been merged. AP:s pass, but U1 account gets removed usually after a reboot, 
even though apps can be installed after adding U1 account flawlessly for the 
duration of that boot.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

2015-04-25 Thread Vincent Ladeuil

@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 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 lxc-android-config package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
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.

  == Test Case ==

  # Prepare debugging
  adb shell
  sudo apt install qtbase5-dbg libc6-dbg

  # Start the reboot loop
  # This reboots the device in a loop, and if this bug is not fixed by whatever 
proposed solution, it will hang eventually. Current highest amount of reboots 
without errors is 54, so it's probable a 100 reboots is needed for testing.

  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done

  # When it fails
  adb shell
  sudo gdb -p $(pidof unity8)
  bt

  --
  At this point, the backtrace should show:
  #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  #1  0xb6301e12 in _q_futex (op=0, val=3, timeout=0x0, addr=optimized out)
  at thread/qmutex_linux.cpp:146
  #2  lockInternal_helperfalse (timeout=-1, elapsedTimer=0x0, d_ptr=...)
  at thread/qmutex_linux.cpp:187
  #3  QBasicMutex::lockInternal (this=this@entry=0x1523b44)
  at thread/qmutex_linux.cpp:203
  #4  0xb6301eb6 in lock (this=0x1523b44) at thread/qmutex.h:59
  #5  lock (timeout=-1, this=0x1523b38) at thread/qmutex.cpp:620
  #6  QMutex::lock (this=this@entry=0x1523d6c) at thread/qmutex.cpp:215
  #7  0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48, 
  a=ToggleWatchAction, this=synthetic pointer) at qdbusthreaddebug_p.h:183
  #8  QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction, 
  this=synthetic pointer) at qdbusthreaddebug_p.h:198
  #9  qDBusRealToggleWatch (d=0x1523d48, watch=0x1524dd0, fd=46)
  at qdbusintegrator.cpp:346
  #10 0xb5ae18f6 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3

  With this, it's know that it was a QDBus locking related problem.
  --

  ---

  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
  2015-04-10: Further patches from upstream fix all AP tests.
  2015-04-23: Upstream continues to work on the patches but they have not yet 
been merged. AP:s pass, but U1 account gets removed usually after a reboot, 
even though apps can be installed after adding U1 account flawlessly for the 
duration of that boot.

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] [Bug 1421009] Re: unity8 sometimes hangs on boot

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 this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-system-settings-
online-accounts 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 lxc-android-config package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
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.

  == Test Case ==

  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done

  This reboots the device in a loop, and if this bug is not fixed by
  whatever proposed solution, it will hang at 30 boots.

  ---

  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
  2015-04-10: Further patches from upstream fix all AP tests.
  2015-04-23: Upstream continues to work on the patches but they have not yet 
been merged. AP:s pass, but U1 account gets removed usually after a reboot, 
even though apps can be installed after adding U1 account flawlessly for the 
duration of that boot.

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

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

** 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 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 lxc-android-config package in Ubuntu:
  In Progress
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
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.

  == Test Case ==

  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done

  This reboots the device in a loop, and if this bug is not fixed by
  whatever proposed solution, it will hang at 30 boots.

  ---

  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
  2015-04-10: Further patches from upstream fix all AP tests.
  2015-04-23: Upstream continues to work on the patches but they have not yet 
been merged. AP:s pass, but U1 account gets removed usually after a reboot, 
even though apps can be installed after adding U1 account flawlessly for the 
duration of that boot.

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

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

** 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 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.
  
  == Test Case ==
  
  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done
  
  This reboots the device in a loop, and if this bug is not fixed by
- whatever proposed solution, it will hang at 30 boots.
+ whatever proposed solution, it will hang eventually. Current highest
+ amount of reboots without errors is 54, so it's probable a 100 reboots
+ is needed for testing.
  
  ---
  
  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
  2015-04-10: Further patches from upstream fix all AP tests.
  2015-04-23: Upstream continues to work on the patches but they have not yet 
been merged. AP:s pass, but U1 account gets removed usually after a reboot, 
even though apps can be installed after adding U1 account flawlessly for the 
duration of that boot.

-- 
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 lxc-android-config package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
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.

  == Test Case ==

  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done

  This reboots the device in a loop, and if this bug is not fixed by
  whatever proposed solution, it will hang eventually.

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

** 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 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.
  
  == Test Case ==
  
+ # Prepare debugging
+ adb shell
+ sudo apt install qtbase5-dbg libc6-dbg
+ 
+ # Start the reboot loop
+ # This reboots the device in a loop, and if this bug is not fixed by whatever 
proposed solution, it will hang eventually. Current highest amount of reboots 
without errors is 54, so it's probable a 100 reboots is needed for testing.
+ 
  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done
  
- This reboots the device in a loop, and if this bug is not fixed by
- whatever proposed solution, it will hang eventually. Current highest
- amount of reboots without errors is 54, so it's probable a 100 reboots
- is needed for testing.
+ # When it fails
+ adb shell
+ sudo gdb -p $(pidof unity8)
+ bt
+ 
+ --
+ At this point, the backtrace should show:
+ #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
+ #1  0xb6301e12 in _q_futex (op=0, val=3, timeout=0x0, addr=optimized out)
+ at thread/qmutex_linux.cpp:146
+ #2  lockInternal_helperfalse (timeout=-1, elapsedTimer=0x0, d_ptr=...)
+ at thread/qmutex_linux.cpp:187
+ #3  QBasicMutex::lockInternal (this=this@entry=0x1523b44)
+ at thread/qmutex_linux.cpp:203
+ #4  0xb6301eb6 in lock (this=0x1523b44) at thread/qmutex.h:59
+ #5  lock (timeout=-1, this=0x1523b38) at thread/qmutex.cpp:620
+ #6  QMutex::lock (this=this@entry=0x1523d6c) at thread/qmutex.cpp:215
+ #7  0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48, 
+ a=ToggleWatchAction, this=synthetic pointer) at qdbusthreaddebug_p.h:183
+ #8  QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction, 
+ this=synthetic pointer) at qdbusthreaddebug_p.h:198
+ #9  qDBusRealToggleWatch (d=0x1523d48, watch=0x1524dd0, fd=46)
+ at qdbusintegrator.cpp:346
+ #10 0xb5ae18f6 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3
+ 
+ With this, it's know that it was a QDBus locking related problem.
+ --
  
  ---
  
  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
  2015-04-10: Further patches from upstream fix all AP tests.
  2015-04-23: Upstream continues to work on the patches but they have not yet 
been merged. AP:s pass, but U1 account gets removed usually after a reboot, 
even though apps can be installed after adding U1 account flawlessly for the 
duration of that boot.

-- 
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 lxc-android-config package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

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 (timo-jyrinki) = (unassigned)

** Changed in: lxc-android-config (Ubuntu)
   Status: In Progress = Incomplete

-- 
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 lxc-android-config package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
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.

  == Test Case ==

  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done

  This reboots the device in a loop, and if this bug is not fixed by
  whatever proposed solution, it will hang at 30 boots.

  ---

  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
  2015-04-10: Further patches from upstream fix all AP tests.
  2015-04-23: Upstream continues to work on the patches but they have not yet 
been merged. AP:s pass, but U1 account gets removed usually after a reboot, 
even though apps can be installed after adding U1 account flawlessly for the 
duration of that boot.

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

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

2015-04-24 Thread Vincent Ladeuil

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 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 lxc-android-config package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
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.

  == Test Case ==

  # Prepare debugging
  adb shell
  sudo apt install qtbase5-dbg libc6-dbg

  # Start the reboot loop
  # This reboots the device in a loop, and if this bug is not fixed by whatever 
proposed solution, it will hang eventually. Current highest amount of reboots 
without errors is 54, so it's probable a 100 reboots is needed for testing.

  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done

  # When it fails
  adb shell
  sudo gdb -p $(pidof unity8)
  bt

  --
  At this point, the backtrace should show:
  #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  #1  0xb6301e12 in _q_futex (op=0, val=3, timeout=0x0, addr=optimized out)
  at thread/qmutex_linux.cpp:146
  #2  lockInternal_helperfalse (timeout=-1, elapsedTimer=0x0, d_ptr=...)
  at thread/qmutex_linux.cpp:187
  #3  QBasicMutex::lockInternal (this=this@entry=0x1523b44)
  at thread/qmutex_linux.cpp:203
  #4  0xb6301eb6 in lock (this=0x1523b44) at thread/qmutex.h:59
  #5  lock (timeout=-1, this=0x1523b38) at thread/qmutex.cpp:620
  #6  QMutex::lock (this=this@entry=0x1523d6c) at thread/qmutex.cpp:215
  #7  0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48, 
  a=ToggleWatchAction, this=synthetic pointer) at qdbusthreaddebug_p.h:183
  #8  QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction, 
  this=synthetic pointer) at qdbusthreaddebug_p.h:198
  #9  qDBusRealToggleWatch (d=0x1523d48, watch=0x1524dd0, fd=46)
  at qdbusintegrator.cpp:346
  #10 0xb5ae18f6 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3

  With this, it's know that it was a QDBus locking related problem.
  --

  ---

  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
  2015-04-10: Further patches from upstream fix all AP tests.
  2015-04-23: Upstream continues to work on the patches but they have not yet 
been merged. AP:s pass, but U1 account gets removed usually after a reboot, 
even though apps can be installed after adding U1 account flawlessly for the 
duration of that boot.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

2015-04-24 Thread Vincent Ladeuil

** Branch linked: lp:~canonical-platform-qa/unity8/1421009-hangs-on-boot

-- 
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 lxc-android-config package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
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.

  == Test Case ==

  # Prepare debugging
  adb shell
  sudo apt install qtbase5-dbg libc6-dbg

  # Start the reboot loop
  # This reboots the device in a loop, and if this bug is not fixed by whatever 
proposed solution, it will hang eventually. Current highest amount of reboots 
without errors is 54, so it's probable a 100 reboots is needed for testing.

  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done

  # When it fails
  adb shell
  sudo gdb -p $(pidof unity8)
  bt

  --
  At this point, the backtrace should show:
  #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  #1  0xb6301e12 in _q_futex (op=0, val=3, timeout=0x0, addr=optimized out)
  at thread/qmutex_linux.cpp:146
  #2  lockInternal_helperfalse (timeout=-1, elapsedTimer=0x0, d_ptr=...)
  at thread/qmutex_linux.cpp:187
  #3  QBasicMutex::lockInternal (this=this@entry=0x1523b44)
  at thread/qmutex_linux.cpp:203
  #4  0xb6301eb6 in lock (this=0x1523b44) at thread/qmutex.h:59
  #5  lock (timeout=-1, this=0x1523b38) at thread/qmutex.cpp:620
  #6  QMutex::lock (this=this@entry=0x1523d6c) at thread/qmutex.cpp:215
  #7  0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48, 
  a=ToggleWatchAction, this=synthetic pointer) at qdbusthreaddebug_p.h:183
  #8  QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction, 
  this=synthetic pointer) at qdbusthreaddebug_p.h:198
  #9  qDBusRealToggleWatch (d=0x1523d48, watch=0x1524dd0, fd=46)
  at qdbusintegrator.cpp:346
  #10 0xb5ae18f6 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3

  With this, it's know that it was a QDBus locking related problem.
  --

  ---

  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
  2015-04-10: Further patches from upstream fix all AP tests.
  2015-04-23: Upstream continues to work on the patches but they have not yet 
been merged. AP:s pass, but U1 account gets removed usually after a reboot, 
even though apps can be installed after adding U1 account flawlessly for the 
duration of that boot.

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] [Bug 1421009] Re: unity8 sometimes hangs on boot

2015-04-24 Thread Vincent Ladeuil

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: 30e975dd988b3be7886017b6d46b2821da187d7b8e5e4c7a30b953114b50bb15
version device: 998baf0435d37e42421b39c34a27ed5f872c145f1d2016e08f477d9ad6b8a654
version custom: 76da72854bde96be6e9d546a607550a952b75ca9c3143e0002f457f826056e87

In addition, the first time I ran this test I ended up with a black screen with 
only the tiny ubuntu logo after two reboots only.
Rebooting the phone from the power button was enough to recover it though.

Looks like this test can reproduce more than one bug ;)

-- 
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 lxc-android-config package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
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.

  == Test Case ==

  # Prepare debugging
  adb shell
  sudo apt install qtbase5-dbg libc6-dbg

  # Start the reboot loop
  # This reboots the device in a loop, and if this bug is not fixed by whatever 
proposed solution, it will hang eventually. Current highest amount of reboots 
without errors is 54, so it's probable a 100 reboots is needed for testing.

  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done

  # When it fails
  adb shell
  sudo gdb -p $(pidof unity8)
  bt

  --
  At this point, the backtrace should show:
  #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  #1  0xb6301e12 in _q_futex (op=0, val=3, timeout=0x0, addr=optimized out)
  at thread/qmutex_linux.cpp:146
  #2  lockInternal_helperfalse (timeout=-1, elapsedTimer=0x0, d_ptr=...)
  at thread/qmutex_linux.cpp:187
  #3  QBasicMutex::lockInternal (this=this@entry=0x1523b44)
  at thread/qmutex_linux.cpp:203
  #4  0xb6301eb6 in lock (this=0x1523b44) at thread/qmutex.h:59
  #5  lock (timeout=-1, this=0x1523b38) at thread/qmutex.cpp:620
  #6  QMutex::lock (this=this@entry=0x1523d6c) at thread/qmutex.cpp:215
  #7  0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48, 
  a=ToggleWatchAction, this=synthetic pointer) at qdbusthreaddebug_p.h:183
  #8  QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction, 
  this=synthetic pointer) at qdbusthreaddebug_p.h:198
  #9  qDBusRealToggleWatch (d=0x1523d48, watch=0x1524dd0, fd=46)
  at qdbusintegrator.cpp:346
  #10 0xb5ae18f6 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3

  With this, it's know that it was a QDBus locking related problem.
  --

  ---

  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

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

2015-04-24 Thread Pat McGowan

Tried running the new test but I get  /tmp/autopkgtest-reboot: not found

-- 
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 lxc-android-config package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
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.

  == Test Case ==

  # Prepare debugging
  adb shell
  sudo apt install qtbase5-dbg libc6-dbg

  # Start the reboot loop
  # This reboots the device in a loop, and if this bug is not fixed by whatever 
proposed solution, it will hang eventually. Current highest amount of reboots 
without errors is 54, so it's probable a 100 reboots is needed for testing.

  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done

  # When it fails
  adb shell
  sudo gdb -p $(pidof unity8)
  bt

  --
  At this point, the backtrace should show:
  #0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
  #1  0xb6301e12 in _q_futex (op=0, val=3, timeout=0x0, addr=optimized out)
  at thread/qmutex_linux.cpp:146
  #2  lockInternal_helperfalse (timeout=-1, elapsedTimer=0x0, d_ptr=...)
  at thread/qmutex_linux.cpp:187
  #3  QBasicMutex::lockInternal (this=this@entry=0x1523b44)
  at thread/qmutex_linux.cpp:203
  #4  0xb6301eb6 in lock (this=0x1523b44) at thread/qmutex.h:59
  #5  lock (timeout=-1, this=0x1523b38) at thread/qmutex.cpp:620
  #6  QMutex::lock (this=this@entry=0x1523d6c) at thread/qmutex.cpp:215
  #7  0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48, 
  a=ToggleWatchAction, this=synthetic pointer) at qdbusthreaddebug_p.h:183
  #8  QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction, 
  this=synthetic pointer) at qdbusthreaddebug_p.h:198
  #9  qDBusRealToggleWatch (d=0x1523d48, watch=0x1524dd0, fd=46)
  at qdbusintegrator.cpp:346
  #10 0xb5ae18f6 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3

  With this, it's know that it was a QDBus locking related problem.
  --

  ---

  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
  2015-04-10: Further patches from upstream fix all AP tests.
  2015-04-23: Upstream continues to work on the patches but they have not yet 
been merged. AP:s pass, but U1 account gets removed usually after a reboot, 
even though apps can be installed after adding U1 account flawlessly for the 
duration of that boot.

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] [Bug 1421009] Re: unity8 sometimes hangs on boot

** 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 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.
  
+ == Test Case ==
+ 
+ bzr branch lp:unity8
+ cd unity8
+ while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done
+ 
+ This reboots the device in a loop, and if this bug is not fixed by
+ whatever proposed solution, it will hang at 30 boots.
+ 
  ---
  
  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
  2015-04-10: Further patches from upstream fix all AP tests.
  2015-04-23: Upstream continues to work on the patches but they have not yet 
been merged. AP:s pass, but U1 account gets removed usually after a reboot, 
even though apps can be installed after adding U1 account flawlessly for the 
duration of that boot.

-- 
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.

  == Test Case ==

  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done

  This reboots the device in a loop, and if this bug is not fixed by
  whatever proposed solution, it will hang at 30 boots.

  ---

  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 /

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

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 racy code would be needed
somewhere that gets called when Install button gets pressed for the
first time after a reboot. It now often removes the account when it's
pressed, although sometimes you can do a full add U1 account, reboot,
install app cycle without problems.

-- 
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 ubuntu-system-settings-online-accounts package in Ubuntu:
  New
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.

  == Test Case ==

  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done

  This reboots the device in a loop, and if this bug is not fixed by
  whatever proposed solution, it will hang at 30 boots.

  ---

  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
  2015-04-10: Further patches from upstream fix all AP tests.
  2015-04-23: Upstream continues to work on the patches but they have not yet 
been merged. AP:s pass, but U1 account gets removed usually after a reboot, 
even though apps can be installed after adding U1 account flawlessly for the 
duration of that boot.

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

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

2015-04-23 Thread Launchpad Bug Tracker

** Branch linked: lp:~mardy/ubuntu-system-settings-online-
accounts/lp1421009

-- 
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.

  == Test Case ==

  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done

  This reboots the device in a loop, and if this bug is not fixed by
  whatever proposed solution, it will hang at 30 boots.

  ---

  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
  2015-04-10: Further patches from upstream fix all AP tests.
  2015-04-23: Upstream continues to work on the patches but they have not yet 
been merged. AP:s pass, but U1 account gets removed usually after a reboot, 
even though apps can be installed after adding U1 account flawlessly for the 
duration of that boot.

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

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

2015-04-23 Thread Alejandro J. Cura

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 minutes for the user to regain back control, after
what looks like a unity8 crash.

While the spinner is shown, both online-accounts-ui and unity8 seem to
go on a merry dance while chewing at the cpu. (perhaps it's online-
accounts-lib the one inside the unity8 process, or it's qtdbus)

The top that alesage sees on arale looks similar to what I see on mako:
http://pasteboard.co/2MKR1ed7.png

But, starting dbus-monitor doesn't show any unusual traffic that might
explain the high cpu usage.

-- 
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 ubuntu-system-settings-online-accounts package in Ubuntu:
  New
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.

  == Test Case ==

  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done

  This reboots the device in a loop, and if this bug is not fixed by
  whatever proposed solution, it will hang at 30 boots.

  ---

  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
  2015-04-10: Further patches from upstream fix all AP tests.
  2015-04-23: Upstream continues to work on the patches but they have not yet 
been merged. AP:s pass, but U1 account gets removed usually after a reboot, 
even though apps can be installed after adding U1 account flawlessly for the 
duration of that boot.

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

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

2015-04-23 Thread Michał Sawicz

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 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 ubuntu-system-settings-online-accounts package in Ubuntu:
  New
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.

  == Test Case ==

  bzr branch lp:unity8
  cd unity8
  while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device 
|| break; done

  This reboots the device in a loop, and if this bug is not fixed by
  whatever proposed solution, it will hang at 30 boots.

  ---

  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
  2015-04-10: Further patches from upstream fix all AP tests.
  2015-04-23: Upstream continues to work on the patches but they have not yet 
been merged. AP:s pass, but U1 account gets removed usually after a reboot, 
even though apps can be installed after adding U1 account flawlessly for the 
duration of that boot.

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

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

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.

---

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:

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

** 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 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

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

** 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 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).
+ 2015-04-10: Further patches from upstream fix all AP tests.
+ 2015-04-23: Upstream continues to work on the patches but they have not yet
been merged. AP:s pass, but U1 account gets removed usually after a reboot,
even though apps can be installed after adding U1 account flawlessly for the
duration of that boot.

--
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

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

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

---

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

2015-04-22 Thread Timo Jyrinki

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 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

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

2015-04-20 Thread Timo Jyrinki

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 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

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

2015-04-18 Thread Timo Jyrinki

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 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

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

2015-04-15 Thread Michał Sawicz

** Changed in: autopilot (Ubuntu)
   Status: Confirmed = Fix Released

-- 
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

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

2015-04-09 Thread Albert Astals Cid

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 to start is ok but the problem is us introducing this
before Qt does (qt 5.4 vs qt 5.5) and so suddenly/close to the vivid
release.

Maybe this patchset could be applied either only to armhf or only to
vivid-rtm (if we end up with that solution for this release) so the
desktop apps using Qt5 have time to adapt?

-- 
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 autopilot package in Ubuntu:
  Confirmed
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/ubuntu/+source/autopilot/+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

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

2015-04-08 Thread Timo Jyrinki

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
earlier.

-- 
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 autopilot package in Ubuntu:
  Confirmed
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/ubuntu/+source/autopilot/+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

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

2015-04-02 Thread Timo Jyrinki

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 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 autopilot package in Ubuntu:
  Confirmed
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/ubuntu/+source/autopilot/+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

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

2015-04-02 Thread Timo Jyrinki

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: Incomplete = Invalid

-- 
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 autopilot package in Ubuntu:
  Confirmed
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/ubuntu/+source/autopilot/+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

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

2015-04-02 Thread Albert Astals Cid

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=0x0, service=...) at qdbusintegrator.cpp:2310
#7  0x7f6583662ce2 in QDBusConnectionPrivate::watchService(QString const, 
QFlagsQDBusServiceWatcher::WatchModeFlag, QObject*, char const*) (this=0x0, 
service=..., mode=..., obj=0xb226b8, member=member@entry=0x7f65836ac300 
1_q_serviceOwnerChanged(QString,QString,QString)) at qdbusintegrator.cpp:2315
#8  0x7f65836a8695 in QDBusServiceWatcher::addWatchedService(QString 
const) (service=..., this=optimized out) at qdbusservicewatcher.cpp:103
#9  0x7f65836a8695 in QDBusServiceWatcher::addWatchedService(QString 
const) (this=optimized out, newService=...) at qdbusservicewatcher.cpp:283
#10 0x7f653fde3254 in  () at 
/usr/lib/x86_64-linux-gnu/qt5/plugins/kded_touchpad.so
#11 0x7f653fdcbd38 in  () at 
/usr/lib/x86_64-linux-gnu/qt5/plugins/kded_touchpad.so
#12 0x7f65823bd608 in KPluginFactory::create(char const*, QWidget*, 
QObject*, QListQVariant const, QString const) () at 
/usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#13 0x7f65832ece7d in  () at /usr/lib/x86_64-linux-gnu/libkdeinit5_kded5.so
#14 0x7f65832ed45f in  () at /usr/lib/x86_64-linux-gnu/libkdeinit5_kded5.so
#15 0x7f65832edc88 in  () at /usr/lib/x86_64-linux-gnu/libkdeinit5_kded5.so
#16 0x7f65832eec53 in  () at /usr/lib/x86_64-linux-gnu/libkdeinit5_kded5.so
#17 0x7f65832ef03a in kdemain () at 
/usr/lib/x86_64-linux-gnu/libkdeinit5_kded5.so
#18 0x7f6582f38a40 in __libc_start_main (main=0x400720 main, argc=1, 
argv=0x7fff13734958, init=optimized out, fini=optimized out, 
rtld_fini=optimized out, stack_end=0x7fff13734948) at libc-start.c:289
#19 0x0040074e in _start ()

Also konsole is now failing to start (this may be a misuse of api on
KUniqueApplication) but still not good to regress like that

-- 
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 autopilot package in Ubuntu:
  Confirmed
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/ubuntu/+source/autopilot/+bug/1421009/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

2015-03-31 Thread Timo Jyrinki

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 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 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.

  ---

  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/ubuntu/+source/autopilot/+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

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

2015-03-31 Thread Launchpad Bug Tracker

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 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 autopilot package in Ubuntu:
  Confirmed
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.

  ---

  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/ubuntu/+source/autopilot/+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

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

2015-03-30 Thread Łukasz Zemczak

** Tags added: lt-blocker lt-category-visible

-- 
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 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

-- 
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

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

** 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 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
+ ---
+ 
+ Timeline/Updates:
+ 2015-02-20: libusermetrics using DBus lands, causing this boot problem to 
start happening rarely
+ 2015-03-25: qtbase dbus update to support threads (instead of one main 
threads) in PPA 018 fixes the boot issue
+ 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).

** 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 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 using DBus lands, causing this boot problem to 
start happening rarely
+ 2015-02-20: libusermetrics using DBus lands, causing this boot problem to 
start happening rarely. 
http://people.canonical.com/~ogra/touch-image-stats/106.changes
  2015-03-25: qtbase dbus update to support threads (instead of one main 
threads) in PPA 018 fixes the boot issue
  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).

** 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 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

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

2015-03-30 Thread Francis Ginther

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 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 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.

  ---

  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/ubuntu/+source/autopilot/+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

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

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.

-- 
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 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.

  ---

  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/ubuntu/+source/autopilot/+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

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

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 use UI Toolkit's test script to run my AP
Testing: http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-
toolkit/trunk/view/head:/tests/uitk_test_plan.sh

-- 
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 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.

  ---

  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/ubuntu/+source/autopilot/+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

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot