Ok, this should fix it:
https://code.launchpad.net/~albaguirre/media-hub/fix-1371454/+merge/235893
On Wed, Sep 24, 2014 at 12:37 PM, Oliver Grawert 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
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 endless
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 t
It should be easily reproducible by running the unity8 autopilot tests.
On Sep 24, 2014 1:16 PM, "Jim Hodapp" 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 some
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 e
Hey!
W dniu 24.09.2014 o 18:44, Alberto Aguirre pisze:
> Is there a bug number for the dbus-cpp issue?
>
> Is there a specific smoketest that was failing due to dbus-cpp?
>
https://bugs.launchpad.net/bugs/1371454
This is the bug number, it's in the list in the 'non-user visible'
issues category.
Is there a bug number for the dbus-cpp issue?
Is there a specific smoketest that was failing due to dbus-cpp?
On Tue, Sep 23, 2014 at 1:44 PM, Łukasz 'sil2100' Zemczak <
lukasz.zemc...@canonical.com> wrote:
> Hi everyone,
>
> We almost had an image promoted today for the ubuntu-rtm channel. Sadl
On Wed, Sep 24, 2014 at 4:31 AM, Łukasz 'sil2100' Zemczak <
lukasz.zemc...@canonical.com> wrote:
> So regarding this issue: It is a blocker because it passed the time
> period of 7 business days after reporting. This policy was invented so
> that smaller non-blocking issues don't get forgotten and
Hey!
First of all: Dave just mentioned to me that the twitter issue he had
was some false positive. Don't have too much information about that as I
was also waiting for a bug filled, but it seems it's a no-issue in overall.
W dniu 24.09.2014 o 09:09, Olivier Tilloy pisze:
>> * Blocking issues:
>>
On Tue, Sep 23, 2014 at 8:44 PM, Łukasz 'sil2100' Zemczak
wrote:
> Hi everyone,
>
> We almost had an image promoted today for the ubuntu-rtm channel. Sadly
> only 'almost'. Everything seemed to be ok but in the end QA noticed 2
> blocking issues and decided not to give a +1 on the image. One probl
On Tue, Sep 23, 2014 at 8:44 PM, Łukasz 'sil2100' Zemczak
wrote:
> Hi everyone,
>
> We almost had an image promoted today for the ubuntu-rtm channel. Sadly
> only 'almost'. Everything seemed to be ok but in the end QA noticed 2
> blocking issues and decided not to give a +1 on the image. One probl
Hi everyone,
We almost had an image promoted today for the ubuntu-rtm channel. Sadly
only 'almost'. Everything seemed to be ok but in the end QA noticed 2
blocking issues and decided not to give a +1 on the image. One problem
seems to be related to the video scope acting flaky, the other -
problem
12 matches
Mail list logo
