On 02/03/2014 10:10 PM, Michał Sawicz wrote:
> That said, having upstart manage those would definitely help, having to
> track the PID is not something we'd like to do. I don't think you'll
> need more than one instance of the plugin? In that case a simple
> .desktop file with NoShow=True (or whate
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/03/2014 11:50 PM, Ted Gould wrote:
> The feature that Content Hub is using I've called "untrusted
> helpers" and it has a lot more flexibility than applications do as
> we're expecting that the helper managers to do a lot of the
> lifecycle manag
On 04.02.2014 09:07, Alberto Mardegan wrote:
We actually need to support the case where multiple instances of the
plugin are running, in different trusted sessions.
I'm not sure what is the matter of PID tracking; what are the
requirements there? My idea was to just start the plugin process, and
On Fri, Jan 31, 2014 at 7:55 PM, Michał Sawicz
wrote:
> On 31.01.2014 18:37, Łukasz 'sil2100' Zemczak wrote:
>>
>> I have tried looking
>> into one of the unity8 crashes on install-and-boot tests, but it seems
>> the crash file is corrupt.
>
>
> Please whenever you see a unity8 crash, make sure to
On 02/03/2014 06:42 PM, Michał Sawicz wrote:
> On 03.02.2014 22:51, Jamie Strandboge wrote:
>> Is this true? Doesn't the untrusted app call out to the trusted online
>> accounts
>> which is not part of this lifecycle group, and then online accounts calls the
>> plugin? The unconfined app talks to
On 04.02.2014 14:33, Jamie Strandboge wrote:
Is this part of LP: #1230091 (the window reparenting bug)? If so, I wonder what
the status of that bug is-- I've not seen any progress in the bug for some time,
yet its needed for a number of other things too.
Maybe not part of it, but related for su
On Tue, 2014-02-04 at 10:05 +0200, Alberto Mardegan wrote:
> I had a quick look at the untrusted helper branch, but I couldn't
> understand if it's suitable for my case:
>
> " * Start an untrusted helper for a specific @type on a given
> * @appid. We don't know how that is done specifically, as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Ted,
On 02/04/2014 04:13 PM, Ted Gould wrote:
> On Tue, 2014-02-04 at 10:05 +0200, Alberto Mardegan wrote:
>> I had a quick look at the untrusted helper branch, but I
>> couldn't understand if it's suitable for my case:
>>
>> " * Start an untruste
Hello,
I tried to restore my backup image using "adb restore backup.ab" and it did
not work.
I could make my device work by flashing the Google image:
https://dl.google.com/dl/android/aosp/nakasi-jdq39-factory-c317339e.tgz
I can try to install phablet on it again but I'd prefer using dualBoot
On Tue, Feb 4, 2014 at 4:50 AM, Alexander Sack wrote:
> On Fri, Jan 31, 2014 at 7:55 PM, Michał Sawicz
> wrote:
> > On 31.01.2014 18:37, Łukasz 'sil2100' Zemczak wrote:
> >>
> >> I have tried looking
> >> into one of the unity8 crashes on install-and-boot tests, but it seems
> >> the crash file
On 04.02.2014 18:23, Didier Roche wrote:
After that and some protobuf transition (in image #162), we don't see
any regression compared to usual crashes and flakyness. The new AP test
failure on unity 8 is a test that was ignored recently but failing again
by the revert.
Ignored? I'd venture to
Hey,
We were able to get back to a promotable state. Image #161 is now the
latest and greatest of ubuntu touch.
This image contains all the changes and the reverts discussed in
yesterday's email. We dogfooded the image ourself on both mako and
maguro and everything seems green.
After that an
On Tue, Feb 4, 2014 at 5:23 PM, Didier Roche wrote:
> - ubuntu-html5-theme will be in tomorrow's image
Just published.
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help : https://hel
On 04.02.2014 18:23, Didier Roche wrote:
- unity8 is now fixed
Published and landed.
--
Michał (Saviq) Sawicz
Canonical Services Ltd.
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More hel
Le 04/02/2014 17:37, Michał Sawicz a écrit :
On 04.02.2014 18:23, Didier Roche wrote:
After that and some protobuf transition (in image #162), we don't see
any regression compared to usual crashes and flakyness. The new AP test
failure on unity 8 is a test that was ignored recently but failing a
On 04.02.2014 18:53, Didier Roche wrote:
I saw on the CI train, part of this landing description:
"- skip broken test"
I was thinking it was that test, but maybe it was another one?
A different one:
https://code.launchpad.net/~mterry/unity8/disable-nm-test/+merge/203980
The otto setup does n
MultiROM indeed supports these testing images. Make sure you have the
latest MultiROM and recovery (I've just released new one) and follow
instructions in the XDA thread[1], under "Adding ROMs" -> "3. Ubuntu Touch".
[1]: http://forum.xda-developers.com/showthread.php?t=2457063
PS: Sorry to Davide
On 02/04/2014 12:23 PM, Didier Roche wrote:
> Hey,
>
> We were able to get back to a promotable state. Image #161 is now the
> latest and greatest of ubuntu touch.
> This image contains all the changes and the reverts discussed in
> yesterday's email. We dogfooded the image ourself on both mako and
Yeah, adding support for sideload might be a good idea. It's just alias for
adb push file.zip /sdcard/sideload.zip though, that's all, so it won't be
faster or anything just a tiny bit more user friendly.
You should be able to update these testing images quite safely if you set
FLASH_KERNEL_SKIP=1
19 matches
Mail list logo
