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 0x00007f6583662168 in QDBusConnectionPrivate::shouldWatchService(QString const&) (this=this@entry=0x0, service=...) at qdbusintegrator.cpp:2310 #7 0x00007f6583662ce2 in QDBusConnectionPrivate::watchService(QString const&, QFlags<QDBusServiceWatcher::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 0x00007f65836a8695 in QDBusServiceWatcher::addWatchedService(QString const&) (service=..., this=<optimized out>) at qdbusservicewatcher.cpp:103 #9 0x00007f65836a8695 in QDBusServiceWatcher::addWatchedService(QString const&) (this=<optimized out>, newService=...) at qdbusservicewatcher.cpp:283 #10 0x00007f653fde3254 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/kded_touchpad.so #11 0x00007f653fdcbd38 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/kded_touchpad.so #12 0x00007f65823bd608 in KPluginFactory::create(char const*, QWidget*, QObject*, QList<QVariant> const&, QString const&) () at /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #13 0x00007f65832ece7d in () at /usr/lib/x86_64-linux-gnu/libkdeinit5_kded5.so #14 0x00007f65832ed45f in () at /usr/lib/x86_64-linux-gnu/libkdeinit5_kded5.so #15 0x00007f65832edc88 in () at /usr/lib/x86_64-linux-gnu/libkdeinit5_kded5.so #16 0x00007f65832eec53 in () at /usr/lib/x86_64-linux-gnu/libkdeinit5_kded5.so #17 0x00007f65832ef03a in kdemain () at /usr/lib/x86_64-linux-gnu/libkdeinit5_kded5.so #18 0x00007f6582f38a40 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 0x000000000040074e 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 More help : https://help.launchpad.net/ListHelp
