El día Friday, May 20, 2016 a las 07:28:31AM +0100, Barry Drake escribió:
> Hi ... I can't remember who I was talking to a while back, as I've been
> out of the country a while, and had only a netbook with me. Now I have
> access to my archives again, I see that I had success with Twinkle, as
On 20-05-16 08:59, Matthias Apitz wrote:
El día Friday, May 20, 2016 a las 07:28:31AM +0100, Barry Drake escribió:
Hi ... I can't remember who I was talking to a while back, as I've been
out of the country a while, and had only a netbook with me. Now I have
access to my archives again, I see
On 19/05/2016 23:27, Rutger Hendriks wrote:
> Well, as you might have guessed, my app will be the only one to use the
> account. Now what is the preferred way to store my account settings? I
> guess it needs to be somewhat secure... Wouldn't want anyone to read
> it... but then again, that might be
El día Friday, May 20, 2016 a las 08:59:34AM +0200, Matthias Apitz escribió:
> Just for the records, there is also a C-written, highly portable SIP
> client 'baresip', details: https://github.com/alfredh/baresip/wiki
> It would be interesting to get to know if it could run in a chroot or
> liberti
Hi folks,
Today I applied the latest system update on my krillin running on
rc-proposed. This triggered a reboot, and then I got the screen
prompting my SIM pin number. So far so good.
Then by accident instead of entering the pin I swiped leftwards and
the pin screen was dismissed, replaced by th
On Fri, May 20, 2016 at 9:40 AM, Olivier Tilloy
wrote:
> Hi folks,
>
> Today I applied the latest system update on my krillin running on
> rc-proposed. This triggered a reboot, and then I got the screen
> prompting my SIM pin number. So far so good.
>
> Then by accident instead of entering the pin
W dniu 20.05.2016 o 09:40, Olivier Tilloy pisze:
> Is that a known issue? If not I’ll see if I can reliably reproduce,
> and will file a bug.
I don't think that's known, no - likely a bug with indicator-network
(that still thinks there's a SIM dialog open) and unity8 (that shouldn't
allow you to d
On Fri, May 20, 2016 at 9:52 AM, Michał Sawicz
wrote:
> W dniu 20.05.2016 o 09:40, Olivier Tilloy pisze:
>> Is that a known issue? If not I’ll see if I can reliably reproduce,
>> and will file a bug.
>
> I don't think that's known, no - likely a bug with indicator-network
> (that still thinks ther
W dniu 20.05.2016 o 10:08, Olivier Tilloy pisze:
> Thanks Michał!
> Not sure whether that’s by design, but being allowed to swipe the SIM
> dialog away doesn’t sound that bad to me, it still allows the user to
> use their device without connectivity (although it’s not very
> discoverable, I found o
On Fri, May 20, 2016 at 10:14 AM, Michał Sawicz
wrote:
> W dniu 20.05.2016 o 10:08, Olivier Tilloy pisze:
>> Thanks Michał!
>> Not sure whether that’s by design, but being allowed to swipe the SIM
>> dialog away doesn’t sound that bad to me, it still allows the user to
>> use their device without
Hi Zsombor,
On 20/05/2016 08:33, Zsombor Egri wrote:
[...]
> Second, frameworks do guard you from API breaks, indeed. What I am
> surprised a bit is you guys immediately thought this change will be an
> API break. Which is not. Again, this wasn't clear from the original
> mail.
[...]
You yourself
Hello Alberto
On Fri, May 20, 2016 at 11:29 AM, Alberto Mardegan <
alberto.marde...@canonical.com> wrote:
> Hi Zsombor,
>
> On 20/05/2016 08:33, Zsombor Egri wrote:
> [...]
> > Second, frameworks do guard you from API breaks, indeed. What I am
> > surprised a bit is you guys immediately thought t
It may work. From your message I assume you already have a container and
understand the current situation with desktop files, etc. Easiest way
would be to do $ libertine-container-manager install-package -i
containername -p /home/phablet/Downloads/logmein-etcetc.deb
If you need shell access use $
On 05/20/2016 01:14 PM, Tim Peeters wrote:
The stable release is 1.2, which does not break API or behavior.
OK. This should be somehow communicated to developers.
Now if one goes to
https://developer.ubuntu.com/api/qml/
and wants to develop using a stable version, one would see that 15.04.5
On 20.05.2016 12:14, Tim Peeters wrote:
> Hello Alberto
>
> On Fri, May 20, 2016 at 11:29 AM, Alberto Mardegan
> mailto:alberto.marde...@canonical.com>>
> wrote:
>
> Hi Zsombor,
>
> On 20/05/2016 08:33, Zsombor Egri wrote:
> [...]
> > Second, frameworks do guard you from API br
Hi all,
Just to let you know, we have now published a blog post about the new
palette: https://design.canonical.com/2016/05/colour-palette-updates/
On Wed, Apr 27, 2016 at 4:49 PM, Filip Dorosz wrote:
> Hi.
>
> I'm reading your conversation and I wondering: why?
>
> I do like the change, and
Hey Rae,
The new NearBy scope on the right image is just a design concept or is it
"real"? It looks awesome :)
2016-05-20 14:37 GMT+02:00 Rae Shambrook :
> Hi all,
>
> Just to let you know, we have now published a blog post about the new
> palette: https://design.canonical.com/2016/05/colour-pal
I basically copped out because of shortage of time and needed a quick
working solution so i setup guacamole and that accesses a couple of
computers, one has team viewer on so can access that from my tablet
when im working away just through the browser and then get to the tools
i need the tablet for
Hi Rae,
thanks for posting this, I have a couple of questions
What is the yellow for?
Will all the colours have functional names so that things can be
consistent between QML and HTML based applications and people can change
the definition of the colours in once place and expect that to update
It is by design which is why the other interfaces to unlock exist. The bug
is that those did not work whereas they certainly used to.
On Fri, May 20, 2016 at 4:18 AM, Olivier Tilloy <
olivier.til...@canonical.com> wrote:
> On Fri, May 20, 2016 at 10:14 AM, Michał Sawicz
> wrote:
> > W dniu 20.05
Hi Richard,
Yes, it's real :) Development for the new scopes UI will be very soon under
way.
On Fri, May 20, 2016 at 2:05 PM, Richard Somlói
wrote:
> Hey Rae,
>
> The new NearBy scope on the right image is just a design concept or is it
> "real"? It looks awesome :)
>
> 2016-05-20 14:37 GMT+02:
Hello,
Just to make sure everything is clear, this is the proposal:
- The Page.head property will *NOT* be touched. It will stay as deprecated
(as it was) and no Page API will change.
- From OTA13, the deprecated Page.head (and also Page.title) property will
be ignored *only* if it is used inside
Hi,
I can't make an ubuntu-sdk-15.04 armhf chroot (on xenial).
...
The following packages have unmet dependencies:
ubuntu-sdk-libs:armhf : Depends: ubuntu-html5-container:armhf
Cheers
On 02/17/2016 01:56 PM, Zoltán Balogh wrote:
Hi,
Just for your information, this case was tracked by the
htt
Hey Kyle:
Some time ago I had problems creating click chroot for armhf in xenial.
I don't remember if the error was the same you describe but I think it
is. Zoltan provided me the solution described below. Maybe it helps you.
Cheers.
On 29/04/16 15:37, Zoltán Balogh wrote:
> Hi,
>
> I have a su
Hi Roberto,
I did (previously) try that, and chroot create failed with a dependency
error.
It seems that the xenial ubutu-sdk-team tools-development ppa [1] does
not contain a click package: indeed it only has (that I can see)
go-get-ubunut-touch.
[1]
https://launchpad.net/~ubuntu-sdk-tea
Hello everyone,
Apologies for the missed yesterday e-mail. We were doing a mass copy of
xenial-overlay to yakkety for all our touch packages (as part of
triple-landing enablement) and there was simply not enough time for a
status update. Not much movement in the landing world yesterday anyway.
To
Hi,
The SDK Release PPA [1] has the 0.4.43+16.04.20160203-0ubuntu3 version
of the click packages.
Please check with `apt-cache policy python3-click-package` that you have
that one installed.
The backup solution for the unfortunate case when the click chroot
creation is not possible is to
27 matches
Mail list logo
