[Touch-packages] [Bug 1261338] Re: lxc-stop and even lxc-stop -k can hang
It never happened again (and may have been a misuse involving immortal sudo subprocesses but I'm blurry on the details), marking invalid but fixed released may be correct as well. ** Changed in: lxc (Ubuntu) Status: Expired => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1261338 Title: lxc-stop and even lxc-stop -k can hang Status in lxc package in Ubuntu: Invalid Bug description: and even 'lxc-stop -k -t ' can hang :-/ The context is an automated test run with otto using a lxc-container trigerring a kernel crash on the host. The host is still alive and so is the container but trying to implement a catch-all to stop a container left running is blocked because there is no way in this particular case to stop the container. The only alternative so far is to reboot the host :-/ http://q-jenkins.ubuntu-ci:8080/job/autopilot-trusty- daily_release/label=qa-intel-4000/951/console is one occurrence where the kernel crashed and 'lxc-stop -k -t 120 -n trusty-i386-20131216-0008' hanged requiring the job to be aborted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1261338/+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 1451448] Re: bzr fails to build on vivid (release) and trusty (test-rebuild only)
** Changed in: bzr Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1451448 Title: bzr fails to build on vivid (release) and trusty (test-rebuild only) Status in Bazaar: Fix Released Status in bzr package in Ubuntu: Confirmed Status in python2.7 package in Ubuntu: Invalid Status in bzr source package in Trusty: Fix Committed Status in python2.7 source package in Trusty: New Status in bzr source package in Vivid: Fix Released Status in python2.7 source package in Vivid: Invalid Status in bzr package in Debian: Fix Released Bug description: bzr fails to build on vivid (release) and trusty (test-rebuild only) various test failures seen, likely exposed by python 2.7.10. release: https://launchpad.net/ubuntu/+archive/test-rebuild-20150402/+build/7133674 test rebuild: https://launchpad.net/ubuntu/+archive/test-rebuild-20150501-updates/+build/7375272 how to validate: successful build. the testsuite is run during the build To manage notifications about this bug go to: https://bugs.launchpad.net/bzr/+bug/1451448/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
@Chris: Thanks ! I had to implement a different scheme not using nested containers but still requiring lxc-1.1.2. I'll give nested containers another shot asap. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid Status in lxc package in Ubuntu: Confirmed Bug description: The nested LXC functionality seems to be broken on Vivid, at least with the following setup: Vivid (Host) - Trusty (Outer LXC) - Trusty (Inner LXC) What happens: The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/ ( 631 cgroup error? 100 cgroups with this name already running seems to be the revelant error message). What is expected to happen: The inner LXC start command is expected to succeed and result in a running nested container. Steps to reproduce: - Install vivid server daily, update. - sudo apt-get install lxc - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo su - echo 'lxc.aa_profile = lxc-container-default-with-nesting' /var/lib/lxc/outer/config - exit - sudo lxc-start -n outer - (SSH to outer) - sudo apt-get update sudo apt-get dist-upgrade - sudo apt-get install lxc - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo lxc-start -n inner Fails with: http://pastebin.ubuntu.com/10682639/ Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/ Control: The exact same scenario works on trusty and utopic. Tested by spinning up server installs (from isos) in KVMs and verifying manually. Any further log or information available on request, including KVM images demonstrating the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 08:43:56 2015 InstallationDate: Installed on 2015-03-12 (13 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
I run into the same issue on a vivid host while trying to start a trusty nested container from inside a trusty container. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid Status in lxc package in Ubuntu: Confirmed Bug description: The nested LXC functionality seems to be broken on Vivid, at least with the following setup: Vivid (Host) - Trusty (Outer LXC) - Trusty (Inner LXC) What happens: The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/ ( 631 cgroup error? 100 cgroups with this name already running seems to be the revelant error message). What is expected to happen: The inner LXC start command is expected to succeed and result in a running nested container. Steps to reproduce: - Install vivid server daily, update. - sudo apt-get install lxc - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo su - echo 'lxc.aa_profile = lxc-container-default-with-nesting' /var/lib/lxc/outer/config - exit - sudo lxc-start -n outer - (SSH to outer) - sudo apt-get update sudo apt-get dist-upgrade - sudo apt-get install lxc - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo lxc-start -n inner Fails with: http://pastebin.ubuntu.com/10682639/ Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/ Control: The exact same scenario works on trusty and utopic. Tested by spinning up server installs (from isos) in KVMs and verifying manually. Any further log or information available on request, including KVM images demonstrating the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 08:43:56 2015 InstallationDate: Installed on 2015-03-12 (13 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
@Chris: Where do you add the ubuntu-lxc/daily ppa ? On the host or on the outer container ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid Status in lxc package in Ubuntu: Confirmed Bug description: The nested LXC functionality seems to be broken on Vivid, at least with the following setup: Vivid (Host) - Trusty (Outer LXC) - Trusty (Inner LXC) What happens: The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/ ( 631 cgroup error? 100 cgroups with this name already running seems to be the revelant error message). What is expected to happen: The inner LXC start command is expected to succeed and result in a running nested container. Steps to reproduce: - Install vivid server daily, update. - sudo apt-get install lxc - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo su - echo 'lxc.aa_profile = lxc-container-default-with-nesting' /var/lib/lxc/outer/config - exit - sudo lxc-start -n outer - (SSH to outer) - sudo apt-get update sudo apt-get dist-upgrade - sudo apt-get install lxc - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo lxc-start -n inner Fails with: http://pastebin.ubuntu.com/10682639/ Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/ Control: The exact same scenario works on trusty and utopic. Tested by spinning up server installs (from isos) in KVMs and verifying manually. Any further log or information available on request, including KVM images demonstrating the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 08:43:56 2015 InstallationDate: Installed on 2015-03-12 (13 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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
@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
@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
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
** 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
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 1430675] Re: fails to set up a bridged network interface
Re-creating the symlink with the command above was enough to fix the issue for me. Thanks ! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1430675 Title: fails to set up a bridged network interface Status in systemd package in Ubuntu: Incomplete Bug description: I have a simple bridge set up in /etc/network/interfaces so that the virtual machines running on that machine can use it and be on the same subnet. But with systemd it's not started on boot. The bridge is configured as follows auto br0 iface br0 inet dhcp bridge_ports eth0 bridge_stp off bridge_maxwait 5 reproduced now on a fresh vm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1430675/+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 1414992] [NEW] Generating /boot/initrd.img-touch = dpkg: warning: version 'touch' has bad syntax: version number does not start with digit
Public bug reported: Encountered when trying to test that a phone image upgraded with -proposed still boots. According to pitti: naming it initrd.img-touch is broken, that's not what initramfs-tools and other tools expect so at the very least, i-t-ubuntu-touch needs to disable the trigger somehow http://dev-jenkins.ubuntu-ci:8080/job/vila-bootesting/23/console is an example using adt-run --apt-upgrade to test libpng. The base phone image is ubuntu-touch/devel- proposed/krillin/version-87.tar.xz ** Affects: initramfs-tools-ubuntu-touch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools-ubuntu- touch in Ubuntu. https://bugs.launchpad.net/bugs/1414992 Title: Generating /boot/initrd.img-touch = dpkg: warning: version 'touch' has bad syntax: version number does not start with digit Status in initramfs-tools-ubuntu-touch package in Ubuntu: New Bug description: Encountered when trying to test that a phone image upgraded with -proposed still boots. According to pitti: naming it initrd.img-touch is broken, that's not what initramfs-tools and other tools expect so at the very least, i-t-ubuntu-touch needs to disable the trigger somehow http://dev-jenkins.ubuntu-ci:8080/job/vila-bootesting/23/console is an example using adt-run --apt-upgrade to test libpng. The base phone image is ubuntu-touch/devel- proposed/krillin/version-87.tar.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools-ubuntu-touch/+bug/1414992/+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