[08:04] <dholbach> good morning
[09:46] <tvoss> mardy, mind giving https://requests.ci-train.ubuntu.com/#/ticket/678 a spin
[09:47] <mardy> tvoss: on it!
[09:47] <tvoss> mardy, thx
[10:12] <mardy> tvoss: damn, I cannot open the HERE apps if I'm in flight mode :-)
[10:12] <tvoss> mardy, oh yeah, I see :)
[10:12] <tvoss> mardy, you probably want to try the simple example client from location service then
[10:12] <mardy> tvoss: I guess OSMtouch is good enough
[10:12] <tvoss> mardy, yeah, should do the job
[10:19] <ogra_`> hmpf
[10:19] <ogra_`> after todays update my scopes dont have any images anymore
[10:20]  * ogra_` reloaded ten times already but nothing chaanges
[10:20] <robin-hero> Hey, is there a bug report for this: I set up an event in the calendar and indicator-datetime shows this in UTC, instead of the correct time?
[10:23] <JamesTait> Good morning all; happy Thursday and happy Cake Day! 😃  http://goo.gl/oKyw2t
[10:29] <mardy> tvoss: mmm... it works a bit too well
[10:29] <tvoss> mardy, ?
[10:29] <mardy> tvoss: the position keeps being updated apparently
[10:29] <mardy> tvoss: isn't the GPS switched off, when we enter flight mode?
[10:29] <tvoss> mardy, hmmm, maybe not
[10:29] <tvoss> morphis, ^
[10:30] <tvoss> morphis, do you know if urfkill disables the gps?
[10:30] <tvoss> morphis, would be kinda pointless as a gps receiver is not emitting any signal, but not sure about regulations
[10:30] <mardy> tvoss: what's the name of the location command line client? Just want to make sure that OSMtouch is not messing up
[10:31] <davmor2> tvoss: not that I am aware of as I wrote a bug asking about it and was told it was not needed
[10:32] <tvoss> mardy, ^
[10:32] <tvoss> mardy, probably best to explicitly switch off gps then
[10:32] <davmor2> mardy, tvoss: you would lose the instant fix that you get from agps
[10:33] <tvoss> davmor2, that's a confusing statement :)
[10:34] <davmor2> tvoss: without cell and internet info agps would have no way to get an initial fix right, so you would be limited to gps only which can take a while to get a fix right
[10:34] <tvoss> davmor2, I get that, not sure what you are arguing for or against :)
[10:35] <davmor2> tvoss: no just a statement I thought it wasn't working for someone or something, not read the rest of the context :)
[10:35] <tvoss> davmor2, okay, that makes a little more sense then :)
[10:38] <morphis> tvoss: I know there is not specific urfkill for GPS
[10:38] <morphis> s/urfkill/rfkill/
[10:38] <morphis> but not sure what urfkill does for GPS
[10:39] <tvoss> morphis, I would be surprised if it ties in to the android gps layer
[10:40] <morphis> abeato: you know?
[10:40] <morphis> tvoss: I know urfkill has some hybris* stuff in it
[10:40] <morphis> but if I remember well that was only for WiFi
[10:41] <abeato> morphis, tvoss not really sure what urfkill does for gps, as morphis says it enables/disables wifi
[10:43] <davmor2> tvoss, morphis: Flight mode (urfkill) does wifi/telephony/bluetooth and nothing else as far as I am aware
[10:48] <tvoss> mpt, o/
[10:48] <mpt> \o
[10:48] <tvoss> mpt, updated trust prompt shot: http://pasteboard.co/2qgdLJ0R.png
[10:49] <mpt> tvoss, cool!
[10:49] <tvoss> mpt, the elliding of the name behaves as in the app scope, elliding of the app id ellides from the center to stay readable
[10:50] <mpt> tvoss, what do you think of making the id grey instead of putting it in brackets?
[10:51] <tvoss> mpt, that's fine with me, I selected the font size as small and replaced _ in the app id with / to make it a little more friendly
[10:51] <tvoss> what do you think?
[10:51] <tvoss> _ somewhat looks like "error"
[10:51] <mpt> agreed
[10:51] <seb128> tvoss, can you fix https://bugs.launchpad.net/trust-store/+bug/1382610 while you are changing that dialog? I can provide a patch if needed, but it's only  switching the order of the buttons and changing a label
[10:51] <tvoss> seb128, sure
[10:51] <seb128> thanks
[10:51] <mpt> I was just going to say, yes
[10:52] <mpt> I didn’t know seb128 had reported a bug about it :-)
[10:52] <tvoss> mpt, http://pasteboard.co/2qguqwvi.png
[10:53] <tvoss> mpt, the description never elides, but wraps
[10:53] <mpt> “description” = “wants to access X”?
[10:54] <tvoss> mpt, yup
[10:57] <tvoss> mpt, http://pasteboard.co/2qgPK55k.png
[10:57] <tvoss> mpt, secondary text with UbuntuColors.lightGrey
[10:58] <tvoss> mpt, parenthesis removed
[10:59] <mpt> tvoss, great. Is now a good time to change “Deny” to “Don’t Allow” as well (as seb128 also mentioned in that bug report)? In my MP comment I forgot that detail for a moment.
[10:59] <tvoss> mpt, sure, it's a string change though, which has implications for translations
[10:59] <mpt> right, that’s what I mean by “a good time” :-)
[11:00] <tvoss> mpt, but we have to adjust the translations anyway, as the description is no longer in the format "%1% wants to access %2%"
[11:00] <tvoss> seb128, ^ what do you think?
[11:00] <seb128> tvoss, ota-8 just went out, translation freeze for ota-9 is not before a while
[11:00]  * tvoss thinks having a watermark on the trust prompt would be really helpful
[11:00] <seb128> so +1
[11:01] <tvoss> seb128, ack
[11:01] <seb128> now seems like the perfect time to do it
[11:01] <tvoss> seb128, mpt mind filing a bug for the change?
[11:01] <seb128> what change?
[11:01] <seb128> the Deny -> Don't Allow?
[11:01] <tvoss> seb128, Deny -> Don't allow
[11:01] <tvoss> yup
[11:01] <seb128> I mentioned it on the bug you just assigned to yourself
[11:01] <seb128> the one about the buttons order
[11:01] <tvoss> ah okay
[11:01] <seb128> but I can open another one if you prefer
[11:02] <tvoss> seb128, ah no, that's fine with me
[11:02] <seb128> great
[11:02] <tvoss> mpt, it's "Don't Allow" with a capital "A", correct?
[11:02] <mpt> yep
[11:03] <mpt> tvoss, what do you mean by a watermark?
[11:04] <tvoss> mpt, so let's assume our oobe requests the user to specify a unique image (probably taken with the camera during the oobe wizard) that was only accessible to the trust-store
[11:04] <tvoss> mpt, if we had that, we could "mark" the trust prompt with the unique watermark image, thereby ensuring that it wasn't faked by an app
[11:04] <mpt> tvoss, ah, like I specced for the PolicyKit dialogs https://wiki.ubuntu.com/AccountPrivileges#icon
[11:06] <tvoss> mpt, something along those lines, yes
[11:06] <tvoss> mpt, are you fine with the eliding I described before?
[11:07] <mpt> tvoss, yep
[11:07] <tvoss> okay, cool
[11:08] <mpt> tvoss, actually, English has this weird thing where ellipsis at start/finish doesn’t have a space after/before it
[11:08] <mpt> tvoss, so in your screenshot it should be “long name for…”, not “long name for …”
[11:08] <tvoss> mpt, hmmm, you would have to talk the qml guys then, I'm just selecting a value from an enumeration
[11:08] <mpt> oh, ok
[11:09] <mardy> tvoss: what's the name of the location command line client? Just want to make sure that OSMtouch is not messing up
[11:09] <tvoss> mardy, oh sorry, let me find it :)
[11:10] <tvoss> mardy, package is *location-service*examples* :) executable should be in /usr/lib/{ARCH}/ubuntu-location-service/examples/client --bus system
[11:10] <tvoss> mardy, use tab for good measure to fix my typos :)
[11:11] <mardy> tvoss: thanks!
[11:14] <mardy> tvoss: yep, it works. I immediately get the same location, same timestamp
[11:15] <mardy> tvoss: if this has to go through QA, better change the steps to use this cli app, instead of here
[11:16] <tvoss> mardy, yup, mind adjusting the silo description?
[11:16] <tvoss> mardy, perfect
[11:17] <mardy> tvoss: sure
[14:05] <samsruti> Hi
[14:26] <shadeslayer> ogra_: hi, I was reverse engineering the scripts to build the ubuntu touch rootfs and came up with this so far http://paste.ubuntu.com/13514952/
[14:26] <ogra_> shadeslayer, apt-get source livecd-rootfs ?
[14:26] <shadeslayer> ogra_: but it doesn't seem to be particularly happy
[14:26] <shadeslayer> ogra_: why source?
[14:27] <shadeslayer> I just install the livecd-rootfs package
[14:27] <ogra_> did you try to use rootstock-ng instead ?
[14:27] <shadeslayer> I have not
[14:27] <ogra_> it does all the necessary wrapping needed for livecd-rootfs
[14:27] <shadeslayer> ogra_: log http://paste.ubuntu.com/13514963/
[14:27] <ogra_> (you need a stacked build chroot for it)
[14:27] <shadeslayer> ogra_: oh, but I need to modify some stuff like package-lists
[14:27] <ogra_> https://launchpad.net/project-rootstock-ng
[14:27] <shadeslayer> ( see http://people.ubuntu.com/~rohangarg/customizations.tar.gz )
[14:28] <shadeslayer> right, http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/current/trusty-preinstalled-touch-armhf.tar.gz is something I need to modify then right, because rootstock-ng doesn't do that
[14:28] <ogra_> rootstock-touch is what you want ...
[14:29] <shadeslayer> oh
[14:29] <ogra_> it allows you to add PPAs
[14:29] <ogra_> (it hasnt been maintained since i stopped working on the phone so it might need some adjustments)
[14:29] <shadeslayer> ok
[14:30] <ogra_> so i guess you could set up a PPA and upload a modified metapackage to that to get your different package set
[14:30] <shadeslayer> ogra_: all of that's already setup, the meta package is called differently though
[14:30] <shadeslayer> and I'm mostly having issues with the live build hooks really
[14:31] <ogra_> well,. they are rather specific for the particular target indeed
[14:31] <shadeslayer> right, except they don't seem to work even with no modifications for me :)
[14:32] <shadeslayer> but seem to work just fine on launchpad
[14:32] <ogra_> why dont you just integrate it properly instead and get a system-image people can just switch to
[14:32] <shadeslayer> yeah, that'd be the correct way of doing it, yes
[14:33] <ogra_> (it could be a channel... then you can just switch channels with a single command on any ubuntu phone out there and our UI will just work )
[14:33] <tvoss> mpt, seb128 so what would be sensible behavior if we cannot find an icon?
[14:33] <ogra_> shadeslayer, well, i dont care about correct/incorrect ... but it would get you immediately a ton of devices out there without you having to care at all
[14:33] <shadeslayer> mmhm
[14:34] <ogra_> like ... every ubuntu phone
[14:34]  * shadeslayer will poke someone
[14:34] <shadeslayer> ogra_: right
[14:34] <ogra_> sudo system-image-cli --switch=plasma-phone-channel ....
[14:34] <ogra_> ;)
[14:34] <mpt> tvoss, that question should be answered by the “give me the icon for this app” API that is also responsible for rounding the corners etc
[14:35] <mpt> tvoss, I’m guessing that API doesn’t currently exist? :-]
[14:35] <tvoss> mpt, well, that api shouldn't handle corner rounding at any rate :)
[14:35] <mpt> What should, then?
[14:35] <Elleo> sil2100: heya; having a bit of trouble getting silo 17 working after switching it to vivid only; changed a few of the MRs to new vivid specific ones but getting odd "not a branch" bzr errors show up, does it need cleaning again in some way? or am I doing something else wrong?
[14:35] <tvoss> mpt, well, the component responsible for actually rendering the icon obviously
[14:36] <tvoss> mpt, but that's a different question
[14:36] <ogra_> shadeslayer, in any case, i'd recommend using rootstock-touch to get the right build env setup
[14:36] <sil2100> Elleo: let me take a look, uno momento
[14:36] <ogra_> if you do it out of archive
[14:37] <mpt> tvoss, ok, so I should have said “component” rather than “API” … Anyway, I’d expect that component to display a placeholder of some sort if it still hasn’t loaded the real icon after ~1 second
[14:38] <shadeslayer> ogra_: ack, I'm looking into it
[14:38] <shadeslayer> and seeing what's blocking us from uploading to launchpad and using the livefs builds
[14:38] <tvoss> mpt, that's not how our ui framework operates. anyway: I will ask the u8 guys
[14:39] <Elleo> sil2100: thanks
[14:41] <mpt> tvoss, I’d expect it to be exactly the same placeholder regardless of whether it’s showing (or trying to show) an app icon in the Dash, in a System Settings screen, in a trust prompt, or anywhere else
[14:44] <shadeslayer> ogra_: I've been told that we would at the very least need a PPA with actual real arm hw
[14:44] <shadeslayer> because qemu'd builds won't cut it
[14:44] <shadeslayer> which is why we build the packages from our own CI at the moment
[14:44] <shadeslayer> ogra_: is there a way to make that happen?
[15:08] <popey> shadeslayer, you can request a real hardware armhf builder, but in launchpad I believe they're restricted (for security reasons) to Canonical employees only.
[15:09] <popey> shadeslayer, the other option being buy a few cheap chromebook / raspberry pi / beaglebone / odroid .. ;)
[15:10] <shadeslayer> popey: I have arm builders from my company, but then we can't leverage lp for the livefs builds ;)
[15:10] <popey> Right, bummer
[15:10] <k1l> iirc you can request PPAs to be build for arm too.
[15:10] <shadeslayer> qemu'd
[15:11] <shadeslayer> won't work for some of the KDE packages
[15:11] <k1l> ah ok
[15:11]  * shadeslayer has a idea
[15:13] <sil2100> Elleo: still looking, but it looks like an internal issue, so not something you did wrong
[15:15] <Elleo> sil2100: okay, thanks
[15:16] <Elleo> sil2100: not sure if I might need to ask people for other MRs targetting their respective vivid branches as well now that it's vivid only?
[15:24] <shadeslayer> ogra_: isn't there a way to specify the ubuntu rootfs via ubuntu-device-flash :(
[15:24] <ogra_> nope
[15:24] <shadeslayer> damn :(
[15:25] <shadeslayer> I guess I can reuse the rootstock stuff to convert it into a image and fastboot flash that instead
[15:37] <sil2100> Elleo: hmmm, ok, silo building... I actually tried building with 'indicator-transfer' mentioned explicitly and it worked
[15:38] <sil2100> Elleo: I suppose it might be also a leftover from one of the transitions Robert was doing in the train, so not related even to your switch from dual to vivid
[15:38] <sil2100> Elleo: most probably once this finishes, there should be no further problems as I see it re-created the indicator-transfer directories
[15:49] <shadeslayer> ogra_: so, I ran rootstock-touch-install on a tarball I have, and then ... nothing
[15:50] <shadeslayer> do I have to reboot into recovery again?
[15:52] <ogra_> shadeslayer, there is a README, in the tree ...
[15:52] <ogra_> i'm not sure it still works ... as i said it has been unmaintained quite a while
[15:52] <ogra_> (the -install script)
[15:52] <shadeslayer> mhmm
[15:52] <ogra_> also it can only work on nexus devices ...
[15:53] <shadeslayer> ah
[15:53] <shadeslayer> I'm using a E5
[15:53] <shadeslayer> readme has a typo btw :P
[15:53] <shadeslayer> ./rootsotck-touch-install
[15:53] <ogra_> ah, yeah, the production phones use actual partitions where the nexus devices use loop mounted images
[15:54] <ogra_> (so the partitioning doesnt need to be changed on developer devices)
[15:54] <ogra_> the install script only handles the loop case
[15:54] <shadeslayer> okay, is it possible to manually untar the tarball onto the right partition then?
[15:55] <ogra_> you can try ;) no idea
[15:58] <shadeslayer> ogra_: oh and the custom tarball is unpacked ontop of the rootfs right?
[15:58] <ogra_> yeah ... but the bits use specific dirs iirc
[15:59] <shadeslayer> yeah :/
[15:59] <ogra_> ypou have to check the code
[16:00] <Elleo> sil2100: cool, thanks
[16:00] <Elleo> sil2100: erk, it's showing a similar error for ubuntu-system-settings now
[16:01] <Elleo> sil2100: do I just ask it to build ubuntu-system-settings on its own?
[16:01] <Elleo> sil2100: ah yeah, that seems to be working
[16:02] <sil2100> Elleo: yeah...
[16:02] <Elleo> sil2100: guess I might have to do that for the others too
[16:02] <sil2100> I think this might need repeating ;/
[16:02] <sil2100> It looks like a train bug to me
[16:02] <Elleo> sil2100: it's entirely possible it's something I messed up, as I've been adding and removing MRs a bit after the switch from dual to vivid
[16:17] <tvoss> mardy, updated to account for security request and design guidelines: https://code.launchpad.net/~thomas-voss/trust-store/fix-1504022/+merge/278418
[16:19] <mardy> tvoss: mmm... I might need to do something similar in OA...
[16:19] <tvoss> mardy, please elaborate
[16:20] <mardy> mpt: I guess we need to update the OA permission request screen in a similar way?
[16:20] <mardy> tvoss: in Online Accounts we also have a permission request screen, which is a bit more complex that this
[16:20] <mpt> mardy, hmm, yes
[16:21] <mardy> mpt: I wonder if space might be a problem there
[16:21] <mardy> well, I guess not
[16:23] <tvoss> mardy, ah okay
[16:28] <mardy> tvoss: that screeenshot is coming from that QML file?
[16:28] <tvoss> mardy, yup
[16:29] <mardy> tvoss: I thought that one had to set the anchors on Column in order to make it use the full width of the parent
[16:29] <mardy> tvoss: but if it's smarter than I thought, all the better :-)
[16:30] <mardy> tvoss: reapproved :-)
[16:50] <tvoss> mardy, would you mind giving https://requests.ci-train.ubuntu.com/#/ticket/657 a spin?
[17:06] <shadeslayer> ogra_: hurray, I hacked up ubuntu_command to flash my image after flashing ubuntu on the E5 :P
[17:09] <shadeslayer> still not happy though [  111.076811]systemd-logind[5359]: Failed to start user service: Unknown unit: user@32011.service
[17:21] <Elleo> sil2100: heya, any idea what causes the "Not in PPA" errors?
[17:21] <Elleo> sil2100: (still with silo 17)
[17:22] <ogra_> shadeslayer, weird, given the phone does not use systemd at all
[17:23] <ogra_> oh, wait, thats only logind
[17:26] <shadeslayer> ogra_: mmh, well, presumably there's other stuff going on as well on account of it being plasma and not unity :)
[17:27] <ogra_> yeah, llikely
[17:27]  * shadeslayer tries flashing without formatting /system
[18:55] <slash> Hello, do you know a way to mount folder at every boot ?