this may have already been said on IRC. Reproducing locally.. 1) make image writable, connect to network 2) adb shell powerd-cli display on bright 3) then on the device shell sudo apt-get install unity8-autopilot stop unity8 autopilot run -v unity8 ....you'll eventually see the spinner spin endlessly & a lot of dbus whining on the terminal
On Wed, Sep 24, 2014 at 1:26 PM, Paul Larson <paul.lar...@canonical.com> wrote: > It should be easily reproducible by running the unity8 autopilot tests. > On Sep 24, 2014 1:16 PM, "Jim Hodapp" <jim.hod...@canonical.com> wrote: > >> Oliver, >> >> So it's not so much that anything really needs porting to GStreamer 1.4, >> as I had been testing general media playback (audio, video) with it for a >> while, but something about it causes the Unity8 AP tests to crash. I don't >> believe that the fix would be a big effort code-wise, but it might take a >> bit of time to identify what the exact offending code is. Has anybody been >> able to reproduce this locally and not only on the Jenkins server? >> >> Jim >> >> On Wed, Sep 24, 2014 at 1:37 PM, Oliver Grawert <o...@ubuntu.com> wrote: >> >>> hi, >>> Am Mittwoch, den 24.09.2014, 11:44 -0500 schrieb Alberto Aguirre: >>> > Is there a bug number for the dbus-cpp issue? >>> >>> yes, this is bug 1371454 >>> >>> > Is there a specific smoketest that was failing due to dbus-cpp? >>> >>> unity8's AP test is clearly hanging hard (killing the lab devices), we >>> see a lot more errors that only show in utopic which may or may not be >>> related ... >>> >>> >>> in the offending landing we have thee packages involved: dbus-dpp. >>> qtubuntu-media and media-hub ... >>> >>> * as you will see in the bug, reverting gstreamer to the 1.2 release >>> seems to fix the issue ... >>> >>> * in utopic there are already other fixes landed on top of the offending >>> media-hub version, which makes rolling back the change there pretty >>> hard. >>> >>> * to my knowledge debian is not planning to support gstreamer 1.2 in the >>> long term, so if we would actually go the easiest path and turn all of >>> gstreamer in rtm back to 1.2 we would lose our upstream and i doubt the >>> security team would like to support an unsupported gstreamer version. >>> >>> we will need a wider discussion that involves the ubuntu gstreamer >>> package maintainer and the security team to make a proper decision >>> here ... >>> the other alternative would be to simply port everything to gst. 1.4 but >>> i have no idea what code changes that involves, if you have any bright >>> idea, please drop it in :) >>> >>> ciao >>> oli >>> >>> -- >>> Mailing list: https://launchpad.net/~ubuntu-phone >>> Post to : ubuntu-phone@lists.launchpad.net >>> Unsubscribe : https://launchpad.net/~ubuntu-phone >>> More help : https://help.launchpad.net/ListHelp >>> >>> >> >> -- >> Mailing list: https://launchpad.net/~ubuntu-phone >> Post to : ubuntu-phone@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~ubuntu-phone >> More help : https://help.launchpad.net/ListHelp >> >> > -- > Mailing list: https://launchpad.net/~ubuntu-phone > Post to : ubuntu-phone@lists.launchpad.net > Unsubscribe : https://launchpad.net/~ubuntu-phone > More help : https://help.launchpad.net/ListHelp > >
-- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
