[04:15] <aki237> Guys I am porting ubuntu-touch to a new device. But the port guide shwed me to a link which is dead.https://wiki.ubuntu.com/Touch/Building <-
[04:55] <aki237> Anyone?
[05:05] <cedarctic> aki237 Hello
[05:06] <cedarctic> which link did you click?
[05:06] <aki237> https://wiki.ubuntu.com/Touch/Building
[05:06] <cedarctic> Which is supposed to link to what?
[05:23] <aki237> When I did phablet-bootstrap phablet ... It didn't clone the kernel source for my device(for that any device).
[06:48] <mike00> Hi all
[06:49] <mike00> Why on my bqE4.5 the remote display doesn't work
[06:49] <mike00> ?
[06:53] <mike00> I can't activate it: The switch is gray....
[06:55] <duflu> mike00: I read that it's only available for one device or so, probably not the E4.5
[07:10] <mike00> Ok thanks
[07:39] <zetheroo> I am trying to update my phone but it's not finding any of the sources
[07:39] <zetheroo> I tried via the GUI (and it just says "Checking for updates" for forever) and then with the terminal ...
[07:41] <zetheroo> sorry, nevermind - rebooted the phone and it's working now. Maybe the wireless connection got messed up :P
[08:42] <jdhoek> Hello, is there any way to install command line utils on a Ubuntu Touch device in OTA mode?
[08:44] <nhaines> No, unless you make a chroot.
[08:45] <jdhoek> nhaines: Where can I find more information on that approach?
[08:48] <nhaines> jdhoek: I do not have the typical Ubuntu Touch-specific guides available, as I don't really do that sort of thing outside of libertine, but it's no different than any other chroot.
[08:50] <jdhoek> How does Libertine fit in all this? Should I see that as a way to install .deb packages in a container?
[08:58] <nhaines> jdhoek: it's a really easy way to install .deb packages in a container, at least.
[08:59] <nhaines> But focused on legacy X apps.
[09:00] <MCMic> It’s so sad that ubuntu touch does not give access to apt
[09:01] <jdhoek> Am I correct in assuming the Libertine will become available as a click package?
[09:03] <jdhoek> What I am looking for is a way to install tools to experiment and test things on my device, but without leaving the OTA cycle.
[09:03] <jdhoek> It is fine if tools installed by me don't survive an OTA update.
[09:06] <nhaines> MCMic: it is one of Ubuntu's best benefits that it does not give access to apt.
[09:06] <nhaines> jdhoek: OTA-13 (if not 12) will include libertine.
[09:06] <nhaines> It will be part of the base system, so I understand.
[09:07] <MCMic> nhaines: oO
[09:07] <MCMic> How is that a benefit? It removes possibilities
[09:07] <jdhoek> Ah good, that will help a lot.
[09:07] <nhaines> MCMic: 'apt' requires root access to the entire system.  Snappy allows for secure apps without compromise to the base system or other apps.
[09:08] <ogra_> jdhoek, no. libertine wont be a click package, it is an integral part of the system itself (but as nhaines said, it will be in all images with OTA12 or 13 or so)
[09:10] <jdhoek> ogra_: Understood. So if I want to install some tools along the line of lsusb etc. to poke around USB devices connected to my device, Libertine would be the way to achieve that?
[09:10] <ogra_> well, for commandline stuff you could just use a chroot :)
[09:10] <ogra_> libertine comes into play if it gets graphical
[09:11] <ogra_> it is the "extension" of a chroot that adds XMir support to it so you can run X11 apps under Mir
[09:12] <jdhoek> ogra_: So do I understand correctly that with a chroot I can install (temporarily) apt-getabble packages on my device in OTA-mode?
[09:13] <ogra_> sure, you can create a chroot in your homedir and use the chroot command to enter it as a work environment at any time
[09:13] <ogra_> read: no need to ever touch the readonly side of the system
[09:14] <jdhoek> ogra_: Alright, I'll have a go at that. Thanks.
[09:14] <ogra_> and regarding libertine: https://docs.google.com/document/d/1yJepibh68YaQijWO3Z3dWTtTTmzXnMmEE8eswhUXzw4
[09:14] <ogra_> this is how you can use it today already without making anything writable
[09:14] <nhaines> And by 'temporary' I suspect you mean 'permanent'.  :)
[09:15] <ogra_> yeah, unless you apt-get remove them or wipe the chroot they stay :)
[09:16] <jdhoek> nhaines: I'll probably end up using a chroot most of the time. :)
[09:16] <nhaines> jdhoek: until snappy takes over, probably the best route.  :)
[09:17] <jdhoek> nhaines: What still confuses me about this way of packaging is how to integrate with the basic Linux userspace. For example, if I want to create a password manager app that uses the PasswordStore way of storing data, but with a UI suitable for touch. I would need access to my GPG keychain and the Gnupg libraries. How would something like that work with sandboxed packages?
[09:19] <ogra_> you would ship all you need in your package
[09:20] <jdhoek> ogra_: So each package that uses Gnupg would ship its own copy of the library?
[09:20] <ogra_> in click it is like that, yeah
[09:21] <ogra_> snaps will allow you to have a GPG package that provides an interface for other packages to use
[09:21] <ogra_> (or the core system would simply provide such an interface)
[09:23] <jdhoek> With the latter route (Gnupg interface provided by core system) would it be possible to implement 'access my GPG keychain' as a permission?
[09:24] <ogra_> something like that, yeah
[09:24] <jdhoek> Interesting. Thanks for explaining.
[09:37] <jouke> I have an aquaris M10 and I was wondering if I could use the miracast that was added to OPA-11 as well?
[09:37] <jouke> What does "OTA" stand for btw?
[09:41] <ogra_> jouke, "over the air (update)"
[09:41] <jouke> OTA means update?
[09:41] <ogra_> jouke, yes
[09:42] <jouke> Right.
[09:42] <ogra_> all ubuntu phones (and tablets) get system updates every 6 weeks ... we are at the 11th of these :)
[09:42] <jouke> But not all features are available for all systems?
[09:43] <ogra_> wrt miracast, i think it is not yet wired up in the UI on the M10 ... but you should be able to enable it from commandline using aethercastctl
[09:43] <jouke> Right
[09:44] <crs___> there is a ?bug? in the browser. i can no longer use slither.io while it worked some weeks ago.
[09:45] <ogra_> works fine here
[09:46] <jouke> Failed to scan:GDBus.Error:org.aethercast.Error.NotReady: Not Ready
[09:46] <crs___> when i hit 'play' the browser shows me an error page and offers me to reload
[09:47] <ogra_> that is what you get running aethercastctl in the terminal app ?
[09:47] <jouke> ogra_: yes
[09:47] <jouke> And issueing the scan command
[09:48] <ogra_> weird, works here ... i get the prompt and can call enable ... scan doesnt do anything though
[09:48] <ogra_> popey, ^^^ do you know what we need to do on the M10 to get aethercast up ?
[09:49] <jouke> Oh, didn't enable it at first
[09:49] <jouke> scan doesn't output anything for me either
[09:50] <crs___> ogra_: did you try on pro5 ? i am trying on pro5 with rc-proposed
[09:50] <ogra_> crs___, there it works fine ...
[09:53] <popey> ogra_: nope, not tried
[10:05] <jouke> If I look at this: https://wiki.ubuntu.com/Touch/DisplayCasting I would expect to see the scanning setting to be changed
[10:05] <jouke> But "show" displays: Scanning: false
[10:05] <ogra_> yeah
[10:05] <ogra_> check the log, perhaps it says something valuable
[10:07] <ogra_> aha
[10:07] <ogra_> sudo service aethercast restart
[10:08] <ogra_> then aethercastctl ... call enable ... call scan
[10:08] <ogra_> works here
[10:09] <nhaines> sneaky! :)
[10:09] <mariogrip> What android apis does aethercast?
[10:09] <mariogrip> use
[10:11] <jouke> Ah, it is scanning
[10:11] <mariogrip> morphis: ^
[10:11] <jouke> Didn't find my TV though.
[10:12] <morphis> mariogrip: its using the MediaCodecSource class from libstagefright
[10:12] <morphis> jouke: is that on a Pro5?
[10:12] <mariogrip> morphis: thanks
[10:12] <morphis> mariogrip: see https://code-review.phablet.ubuntu.com/#/c/444/ https://code-review.phablet.ubuntu.com/#/c/445/ https://code-review.phablet.ubuntu.com/#/c/446/
[10:13] <morphis> mariogrip: and the latest changes we did on the media parts on https://git.launchpad.net/~libhybris-maintainers/libhybris/+git/libhybris/log/
[10:14] <mariogrip> morphis: is it plans for backporting it to 4.4?
[10:15] <morphis> mariogrip: not officially
[10:15] <mariogrip> ack
[10:15] <morphis> mariogrip: some time back I played with a backport to 4.4 for Nexus4
[10:15] <morphis> the result are those three changes above
[10:15] <morphis> which gets video encoding working
[10:15] <morphis> but on Nexus4 the real problem is a broken WiFi driver
[10:16] <ogra_> morphis, jouke is on an M10 ... tyring it here too, but cant get it to connect
[10:16] <popey> trying on M10 here... dongle says "Connecting to ubuntu-phablet" but never completes
[10:16] <popey> and I get "Timeout was reached"
[10:16] <popey> ooh, i think i had this before
[10:16] <ogra_> popey, thats more than i get
[10:16] <popey> i suspect i know what this is :)
[10:16] <morphis> ogra_, popey: it could be that we're missing a few fixes still
[10:16] <mariogrip> i was thinking backporting to e4.5, e5 and mx4
[10:16]  * popey tries again
[10:16] <morphis> mariogrip: you simply can't without having access to the android source tree of those
[10:17] <mariogrip> morphis: are they not open?
[10:17] <morphis> they are not
[10:17] <popey> aethercastctl should support cursor keys btw :)
[10:17] <mariogrip> oh? i did not know that
[10:18] <morphis> mariogrip: basically for no commercial device we have an open tree
[10:18] <morphis> popey: feel free to send a fix for that :-)
[10:18] <jouke> morphis: aquaris M10
[10:18] <popey> \o/ it works
[10:18] <morphis> jouke: rc-proposed or stable?
[10:19] <jouke> Euh, haven't done anything on the tablet, so I suppose stable
[10:19] <ogra_> morphis, isnt that the same atm ?
[10:19] <popey> http://imgur.com/cUlHUWt success \o/
[10:19] <ogra_> with the realease yesterday channels should be largely in sync
[10:19] <morphis> ogra_: not necessary
[10:20] <ogra_> well, "largely" :)
[10:20] <morphis> we already landed fixes for post ota 11
[10:20] <morphis> especially for aethercast :-)
[10:20] <jouke> Ah. I am willing to run rc-proposed :)
[10:20] <ogra_> popey, are you on proposed ?
[10:21] <morphis> jouke: I don't give any gurantee that things are working yet
[10:21] <morphis> we're still in the process of make it solid on the M10
[10:21] <morphis> and don't expect that to be done before OTA 12 comes
[10:24] <morphis> mariogrip: however there might be the possiblity that we import those patches I linked above into the tree for krillin and arale and you fix anything from the Ubuntu side
[10:25] <mariogrip> morphis: yeah, that would be great
[10:25] <MCMic> morphis: Who has the decision of opening those tree or not? Is it BQ?
[10:25] <morphis> MCMic: yes, BQ or Meizu but even for them it depends on a lot other stakeholders like MTK, ARM, ...
[10:26] <MCMic> :-/
[10:26] <MCMic> This is so stupid…
[10:27] <MCMic> I hope we’ll some day be able to use this on the E4.5 some way or another.
[10:27] <jouke> How do I change to rc-proposed?
[10:28] <MCMic> BTW, why is there two names aethercast and miracast? Is it not the same thing?
[10:28] <morphis> no
[10:28] <morphis> MCMic: aethercast is simply the name of our management service which is meant to cover other streaming protocols too
[10:28] <MCMic> ok
[10:28] <morphis> and miracast is the actual display streaming std we're using
[10:29] <MCMic> So aethercast is a software/library on the ubuntu side, and miracast is one streaming protocol that it supports?
[10:29] <mariogrip> jouke: http://askubuntu.com/questions/764554/how-to-change-from-ubuntu-touch-stable-channel-to-rc-proposed
[10:29] <jouke> Thanks!
[10:29] <morphis> MCMic: yes
[10:29] <MCMic> Ok thanks
[10:30] <morphis> MCMic: https://launchpad.net/aethercast
[10:36] <popey> morphis: nice work :) https://twitter.com/popey/status/738318147955089408 / https://plus.google.com/u/0/+AlanPope/posts/d8PCVidDww1
[10:36] <morphis> popey: performing well for you?
[10:37] <ogra_> popey, is that on stable or rc-proposed  ?
[10:37] <popey> rc-proposed
[10:37] <ogra_> ah, thats why
[10:37] <morphis> popey: thank abeato for the M10 enablement :-)
[10:37] <popey> morphis: yeah, the scaling makes the fonts hard to read, same as on pro 5
[10:37] <popey> 1080p->720p->1080p doesn't do the fonts justice
[10:38] <morphis> popey: we don't do the first scale step
[10:38] <ogra_> yeah
[10:38] <morphis> we don't scale down from 1080p to 720p
[10:38] <popey> do you have a recommended hdmi dongle?
[10:38] <popey> (i mean, real hdmi, not wireless)
[10:38] <morphis> we render on a virtual display which has 720p
[10:38] <popey> ah
[10:38] <ogra_> i wonder if the app for the dongle could help somewhat here
[10:38] <morphis> don't know
[10:38] <popey> either way, it doens't look great
[10:39] <ogra_> might become slightly better if it renders at 720p
[10:39] <morphis> popey: we may add an option to enable 1080p but that will always be a performance thing
[10:39] <ogra_> instead of doing internal upscaling
[10:42] <morphis> ogra_: maybe
[10:44] <ogra_> (not sure if the app allows you to set the output resolution though)
[11:14] <DSMcGuire> Hello all! I have the Pro 5 and i can't install the lastest OTA
[11:15] <DSMcGuire> These are my log files for .cache and .upstart:
[11:16] <DSMcGuire> https://imgur.com/a/gcnj9
[11:25] <DSMcGuire> hello? :D
[11:26] <popey> sil2100: ^ have you seen other reports of this?
[11:26] <DS-McGuire> Logged into my xchat, this is my new name!
[11:27] <sil2100> DS-McGuire: hey! Does it download the update and then reboot your phone for installation?
[11:30] <DS-McGuire> sil2100, Nope, it gets to around 25% and then claims it cannot install.
[11:31] <popey> seeing Alan bell talking about update failures on the mailing list too
[11:32] <DS-McGuire> popey, which mailing list?
[11:34] <popey> the phone list
[11:35] <popey> DS-McGuire: anything in /var/log/ubuntu-download-manager most recent logs?
[11:38] <sil2100> It's a different failure
[11:39] <sil2100> That's why I asked if it tries to isntall it - Alan's problem was that it wasn't installing the update after download
[11:39] <sil2100> So at least it's a different issue, no one reported something like that yet
[11:40] <DS-McGuire> popey, http://imgur.com/CIxXeg9
[11:40] <DS-McGuire> sil2100, ^
[11:41] <DS-McGuire> My phone is an hour behind of the correct time
[11:43] <sil2100> hmm
[11:56] <DS-McGuire> So what would be the best course of action right now?
[12:00] <DS-McGuire> sil2100, ^
[12:02] <ogra_> is that an unmodified pro5 ? not made writable or anything ?
[12:04] <DS-McGuire> ogra_, I haven't done anything to it yet at all.
[12:17] <DS-McGuire> Should I flash the new ota to my phone?
[12:18] <ogra_> DS-McGuire, try cleaning up /cache/recovery and then try again
[12:18] <DS-McGuire> ogra_, What would be the best way to do that?
[12:19] <XaRz> Hello, I was checking the html5 app tutorials from ubuntu dev portal. They are made from 14.04 plattform isn't it? I'm finding some discrepances like the inspector and oxide support. Any hints?
[12:19] <ogra_> use the terminal app ...
[12:19] <ogra_> sudo rm -rf /cache/recovery/*
[12:19] <DS-McGuire> I ssh into my phone, but thanks!
[12:20] <ogra_> then reboot and try the update via the GUI again
[12:23]  * DS-McGuire download now
[12:23] <DS-McGuire> ing*
[12:25] <DS-McGuire> ogra_, Still fails
[12:25] <ogra_> well, was worth a try
[12:26] <DS-McGuire> it was, thanks
[12:26] <ogra_> where/how exactly does it fail tghough
[12:26] <ogra_> *though
[12:26] <DS-McGuire> around 19%
[12:26] <ogra_> does it reboot into recovery ?
[12:26] <DS-McGuire> Think it might be a network thing?
[12:26] <ogra_> and fail when applying ...
[12:26] <ogra_> or does it fail before
[12:26] <DS-McGuire> It fails as it's downloading.
[12:27] <ogra_> oh
[12:27] <ogra_> are you behind a proxy in your WLAN or some such ?
[12:28] <DS-McGuire> Nope
[12:28] <DS-McGuire> All others updates for apps and such work though
[12:28] <DS-McGuire> Plus, an MX4 on my network updated to OTA11.
[12:28] <DS-McGuire> Would it be that I'm going from OTA9 > OTA11?
[12:29] <ogra_> well, if apps work that kind of rules out the download manager
[12:29] <DS-McGuire> Yeah that makes sense
[12:29] <DS-McGuire> After it fails if I try to run it again it fails straight away.
[12:30] <ogra_> well, try to pastebin the logs somewhere
[12:30] <sil2100> hm
[12:31] <ogra_> (/var7log/download-manager and /var/log/system-image should be the interesting dirs to pick the logs from)
[12:31] <sil2100> I'm starting to wonder if the problem isn't that the image is OTA-9
[12:31] <sil2100> We did a key rotation and only re-signed the latest images from each channel with the new key
[12:31] <ogra_> well, there should be an error logged *somewhere*
[12:31] <ogra_> which should tell you :)
[12:32] <sil2100> Might be that the image for OTA-10 is signed with the old key, and since from OTA-9 to OTA-11 there are OTA-10 and OTA-10.1 which need to be downloaded
[12:32] <ogra_> would indeed be bad if you cant update a factory device
[12:32] <sil2100> Yeah, I'd have to re-sign the old images too
[12:32] <sil2100> Anyway, we need more logs
[12:32] <DS-McGuire> sil2100, I got the device early yesterday and never got any OTAs until OTA11.
[12:32] <sil2100> If that's the case, I'll have to sweep through all the stable channels and re-sign more images
[12:33] <sil2100> DS-McGuire: you didn't get an update notification about OTA-10.1?
[12:33] <sil2100> That's really weird, hm
[12:33] <DS-McGuire> Nope, I got nothing.
[12:34] <ogra_> sil2100, well, if 11 was already phasing ... why would he get a former OTA
[12:34] <DS-McGuire> I knew about OTA11 and just assumed I would get that when it hits my phone
[12:34] <sil2100> Anyway, if you could pastebin the logs ogra_ mentioned (like, download them from the device and use pastebinit or something to get us the contents)
[12:34] <sil2100> ogra_: we started phasing in the afternoon, DS-McGuire said he got it early yesterday, but maybe indeed
[12:35] <ogra_> sil2100, well, it is morning in the US now ;)
[12:35] <DS-McGuire> sil2100, Just be exact, I checked for an update around 1pm GMT
[12:35] <ogra_> "morning" is a very flexible term :)
[12:35] <DS-McGuire> Phone came eariler than that.
[12:35] <DS-McGuire> Sorry that wasn't very accurate.
[12:35] <DS-McGuire> Right, I'll try and get these logs
[12:36] <sil2100> Ah, ok, so it might be that :) Anyway, we want you to get the update as soon as possible
[12:36] <sil2100> Thanks!
[12:36] <DS-McGuire> I would love the update asap too haha!
[12:36] <DS-McGuire> What would be the easiest way? I'm not the best with the terminal, can I use a GUI?
[12:37] <ogra_> you said you use ssh
[12:37] <DS-McGuire> Yeah, still pretty bad though haha
[12:37] <ogra_> so just use scp to pull the files
[12:37] <sil2100> For log fetching we sadly don't have too many GUI tools :)
[12:38] <DS-McGuire> No worries
[12:38] <sil2100> DS-McGuire: does your device have adb enabled? e.g. is it set to developer mode? Then you could connect it through cable to your PC and use adb pull to get the contents
[12:38]  * ogra_ actually uses the "connect to server" thing in nautilus with an sftp url .. that way you can drag/drop 
[12:38] <sil2100> Although ssh could be used as well
[12:39] <sil2100> ogra_: hah, right, that's also a good way
[12:39] <DS-McGuire> Yeah I can do that
[12:39] <DS-McGuire> device is in dev  mode npw
[12:39] <ogra_> sftp://phablet@$ip_of_phone/home/phablet
[12:39] <DS-McGuire> now
[12:39] <ogra_> use that for the connect to server address
[12:40] <ogra_> (with the right IP indeed)
[12:41] <DS-McGuire> What would the adb command be?
[12:44] <ogra_> adb pull /path/to/files
[12:45] <ogra_> but i think at least system-image requires root access and adb runs as phablet user, so you will likely have probs pulling these logs
[12:45] <popey> you can scp them off the device  if you have ssh access
[12:46] <popey> scp phablet@<ip>:/foo/bar/baz .
[12:47] <DS-McGuire> sorry, bad time for a phone call,
[12:49] <DS-McGuire> Im getting Usage: adb devices [-l]
[12:49] <popey> its not adb devices
[12:49] <popey> it's adb pull
[12:50] <popey> scp is easier though
[12:50] <DS-McGuire> sweet jesus sorry
[12:50] <ogra_> well, but both run as phablet after all
[12:50] <ogra_> /var/log/system-image wont let you access
[12:51] <metasequoia> hello, does anybody know when canonical will add a character counter to the text messaging app so I can stop sending double messages accidentally? :)
[12:52] <DS-McGuire> for system-image and everything else i get 0 files pulled. 0 files skipped.
[12:52] <ogra_> metasequoia, probably after you filed a bug about it :)
[12:53] <metasequoia> I figured it would be planned or already noted... seems basic functionality
[12:53] <pmcgowan> metasequoia, why would you get double messages sent?
[12:53] <metasequoia> because there is no character count...
[12:53] <dobey> pmcgowan: because SMS has a character limit
[12:53] <dobey> pmcgowan: so long messages get split up
[12:53] <pmcgowan> but thats old news
[12:53] <pmcgowan> they get split and reassembled transparently
[12:54] <pmcgowan> on some networks they just get sent
[12:54] <dobey> right, unless the other phone doesn't support it
[12:54] <metasequoia> yeah but they still use twice as many of your free messages
[12:55] <metasequoia> I just find it annoying and every phone I have ever owned had a char counter
[12:55] <dobey> metasequoia: please file a bug against messaging-app stating your use case
[12:55] <pmcgowan> interesting but still seems a throwback to me, I have never used one
[12:56] <dobey> pmcgowan: well yeah, we don't much care about message length over here, because we have unlimited messages
[12:56] <pmcgowan> right, hence my lack of sensitivity
[12:57] <JanC> well, not unlimited here, but it's unlikely I'll ever send 5000 or whatever free messages I got  :)
[12:57] <metasequoia> yeah a lot of people 'here' have them too
[12:57] <metasequoia> but pay as you go still limited
[12:57] <DS-McGuire> sil2100, ogra_ popey I have pulled all files from /log, i'll sort it out now, where should I put it?
[12:57] <popey> pastebin
[12:57] <popey> or email them to sil2100 :)
[12:57] <JanC> also, it often depends on who you send them to
[12:58] <ogra_> http://paste.ubuntu.com
[12:58] <dobey> and lunar position
[12:58] <ogra_> if you are using an ubuntu desktop ... install the pastebinit package
[12:59] <sil2100> pastebinit is a really useful tool
[12:59] <ogra_> then you can just use the pastebinit command (i.e: pastebinit /path/to/file)
[12:59] <pmcgowan> you know the logviewer app in the store can push them direct to pastebin
[12:59] <ogra_> it will return an url for you
[12:59] <sil2100> oh
[12:59] <ogra_> pmcgowan, and you say that *now* !
[12:59] <sil2100> pmcgowan: all logs?
[13:00] <pmcgowan> well I never tried it personanlly
[13:00] <DS-McGuire> haha!
[13:00] <pmcgowan> a subset
[13:00] <ogra_> well, probably not the ones the pahblet user can not open :)
[13:00] <pmcgowan> true
[13:00] <ogra_> so wouldnt help for system-image logs
[13:00] <sil2100> I mean, even those in /var/log/ ? Since the ones we needed are root-owned
[13:00] <pmcgowan> hmm not syslog
[13:00] <sil2100> Ok ;)
[13:00] <sil2100> Well, anyway, good to know, I'll install that app myself in a moment
[13:00] <ogra_> not syslog ?
[13:00] <pmcgowan> yeah we should fix it up
[13:01] <ogra_> syslog should work, the pahblet user shjould be in the adm group
[13:01] <pmcgowan> yeah, I blame victorp
[13:01] <ogra_> yeah, he is a good target for blame here :)
[13:01] <sil2100> DS-McGuire: for now, please try to put those files on paste.ubuntu.com or e-mail me or ogra_, so lukasz.zemczak@ubuntu.com
[13:02] <DS-McGuire> sil2100, I think it will be easier to zip them up and send it to you, pastebin as far as I can tell wont allow me to upload multiple files
[13:02] <sil2100> DS-McGuire: yeah, you'd have to upload each separately - send it over by e-mail and we'll check what's up with that
[13:03] <JanC> metasequoia: what you want is probably not a character counter but a byte counter
[13:03] <metasequoia> it is up to canonical how they want to handle it
[13:03] <metasequoia> I just want the phone to tell me how many chars are left before a second text will be needed
[13:03] <metasequoia> logging it now anyway
[13:04] <ogra_> +1
[13:04] <JanC> the limit for SMS is per byte AFAIK
[13:05] <DS-McGuire> sil2100, sent in an  email to the address provided.
[13:05] <JanC> (not sure it's 8-bit clean even?)
[13:06] <sil2100> DS-McGuire: thanks! Waiting for it to arrive
[13:07] <metasequoia> okay, I logged it, thanks anyway guys
[13:07] <metasequoia> cya
[13:07] <ogra_> whats the bug number
[13:07] <DS-McGuire> sil2100, Let me know when you have it. Geary said it it sent but couldn't save it in my sent folder.
[13:07] <sil2100> DS-McGuire: got those, let me look at that in a minute, need to finish something up quickly
[13:10] <DS-McGuire> No problem
[13:14] <sil2100> DS-McGuire: ok, so I would need one more log from your device, since it seems to be missing
[13:14] <DS-McGuire> sil2100, Which one? I might have missed it when I packaged it up.
[13:14] <sil2100> DS-McGuire: so /var/log/system-image/client.log I would need - to access it you need root permissions
[13:15] <DS-McGuire> oh
[13:15] <popey> DS-McGuire: sudo cat /var/log/system-image/client.log | nc termbin.com 9999
[13:16] <popey> is a good way to get the file off the device, to a pastebin directly
[13:16] <DS-McGuire> cat: /var/log/system-image/client.log: No such file or directory
[13:16] <sil2100> oh
[13:16] <sil2100> hm
[13:16] <DS-McGuire> Very odd
[13:16] <sil2100> Wow, ok
[13:16] <DS-McGuire> thanks popey though
[13:17] <popey> it may have log-rotated
[13:17] <popey> sudo ls /var/log/system-image/
[13:17] <popey> is there a client.log.1.gz or some other file there?
[13:17] <sil2100> DS-McGuire, popey: maybe let's try running the updater from the console and see what it results in?
[13:18] <DS-McGuire> there is only a client.log file
[13:18] <sil2100> Oh, ok, so the file is there?
[13:19] <DS-McGuire> right
[13:19] <DS-McGuire> I have it
[13:19] <DS-McGuire> I used the wrong terminal
[13:19] <sil2100> :)
[13:19] <DS-McGuire> http://termbin.com/v3bx
[13:19] <sil2100> Ok, if you could send it over as well all will be clear (hopefully)
[13:19] <DS-McGuire> My bad
[13:20] <DS-McGuire> sil2100, Is that okay^
[13:21] <sil2100> DS-McGuire: perfect, let me look into that in a moment
[13:21] <DS-McGuire> Not a problem
[13:22] <pmcgowan> sil2100, the download is jut failing
[13:22] <sil2100> Yeah, it looks like it fails downloading one of the deltas
[13:23] <sil2100> But the files are present, wait, might be something else
[13:24] <sil2100> FileNotFoundError: http://system-image.ubuntu.com/pool/custom-f635fa450d07a4abb036ae386ccf4f73055910e8cf411c04ea31cf545ba99fd0.delta-custom-83eb19e343f9a712bf666557a84676a34ba83613c22ef1e34bbee01f5cd93cbd.tar.xz.asc <- this is worrying, since the file is available on the remote location
[13:24] <pmcgowan> this sounds familiar
[13:25] <sil2100> FileNotFoundError: https://system-image.ubuntu.com/channels.json
[13:25] <sil2100> There's a lot of those, looks like download issues all the way
[13:25] <sil2100> Doesn't look like system-image is at fault here
[13:27] <ogra_> which is weird, since app updates work
[13:28] <pmcgowan> there are also reactor error
[13:29] <sil2100> Ok, it won't be that easy, let me fill in a bug for this DS-McGuire and we'll try to get some more eyeballs on tit
[13:29] <sil2100> I'll report it for ubuntu-download-manager and system-image just in case
[13:29] <DS-McGuire> sil2100, Sure thing. One last question? What should I do now? Sit on my OTA9?
[13:31] <sil2100> DS-McGuire: you could re-flash your device to the latest version through your Ubuntu desktop easily, but not sure if we wouldn't need your device in this state to find the cause of this bug
[13:31] <sil2100> We would need barry around
[13:32] <sil2100> He should be up pretty soon I suppose
[13:32] <DS-McGuire> Well if I'm the only person with this problem and it would help a lot then I would feel bad if I did update.
[13:32] <popey> i imagine you're one of a few people who managed to get a pro 5
[13:32] <popey> and are still on ota 9
[13:32] <popey> timing :)
[13:32] <DS-McGuire> One of things is that my camera doesn't work yet so that's kinda annoying.
[13:32] <popey> i suspect most people got theirs and went 9->10.1->11
[13:32] <sil2100> DS-McGuire: if you could stay in this 'broken' state for at least a little bit more today it would be great, I want barry to comment
[13:32] <sil2100> Maybe he needs some more logs
[13:32] <DS-McGuire> popey, Very true.
[13:33] <popey> appreciate you helping us DS-McGuire
[13:33] <sil2100> DS-McGuire: thank you for your patience ;)
[13:33] <DS-McGuire> sil2100, Oh the rest of today is fine. I just would like it updated for the weekend :)
[13:33] <DS-McGuire> At least now I know I can stop trying to update it.
[13:33] <popey> sil2100: want me to revert my pro 5 back to 9?
[13:33] <popey> is that worth doing?
[13:33] <DS-McGuire> popey, Not a problem, thanks for helping out :)
[13:33] <sil2100> hmmmm
[13:34] <sil2100> popey: would be nice to have something like this tested - is that a testing device or your main phone?
[13:34] <popey> DS-McGuire: can you "system-image-cli --info | nc termbin.com 9999" please?
[13:34] <popey> it's my own personal phone and I don't care what happens to it
[13:35] <DS-McGuire> popey, http://termbin.com/bype
[13:36]  * popey backs up device first
[13:36] <popey> ok, ta DS-McGuire
[13:36] <DS-McGuire> NP
[13:38] <sil2100> DS-McGuire, popey: reported this to track the issue: https://bugs.launchpad.net/ubuntu-system-image/+bug/1588370
[13:38] <DS-McGuire> For what it's worth, my phone has a problem with the screen and I'm talking to Joybuy about getting it replaced so if my next phone comes back with OTA9 I'll be able to try again haha!
[13:39] <sil2100> ;)
[13:39] <popey> hah
[13:39] <DS-McGuire> Marked as affecting me.
[13:42] <dobey> i thought turbo came with 10.2
[13:43] <ogra_> DS-McGuire, what kind of issues ?
[13:43] <popey> light bleed from one side
[13:43] <ogra_> same here
[13:43] <popey> ooh
[13:43] <dobey> mardy: is it not possible to do migration from one signon plug-in to another, in the existing migration script where we deal with the ACL?
[13:43] <pmcgowan> the log says Upgrade path is 2:3 but his info says current build number: 1
[13:44] <ogra_> a greenish glow if there is a black bg
[13:44] <pmcgowan> that seems wrong
[13:44] <ogra_> on the right side of the display
[13:44] <DS-McGuire> ogra_, Really!?
[13:44] <ogra_> yes
[13:45] <DS-McGuire> ogra_, These are the images I have sent to joybuy: https://www.dropbox.com/sh/zv9uva1m1ky53tv/AACrZgdvWFiXWiM-ImXrPPa7a?dl=0
[13:45] <ogra_> not bad enough that it bothers me (and i also assume i will crack the display during the phones lifetime, so i will eventually replace it anyway )
[13:45] <DS-McGuire> I can only see it at low light with the dark backgrounds.
[13:45] <ogra_> DS-McGuire, yep, i see something similar ... a bit less for me though
[13:46] <DS-McGuire> This is weird. Is this a hardware or a software problem since we both have it?
[13:48] <popey> i would imagine they were made in a fairly small batch
[13:48] <popey> so plausible it's a hardware issue
[13:49] <ogra_> yeah, likely a HW issue
[13:50] <ogra_> (like they sell you a gold phone and you get an antique pink one instead :P )
[13:50] <DS-McGuire> Hmm, don't know if I can be bothered to send it all the way back with the chance of my new one having the same problem.
[13:50] <DS-McGuire> Very true, phone is not even gold. It's copper!
[13:51] <ogra_> FSVO copper :P
[13:51] <ogra_> it is somewhere between pink and copper IMHO :)
[13:52] <DS-McGuire> Might slap a case on it so I can't see it anyway.
[13:52]  * ogra_ was thinking about a paintjob :) 
[13:55] <DS-McGuire> Pimp my Pro 5.
[13:55] <pmcgowan> DS-McGuire, what does system-image-cli -n tell you?
[13:56] <dobey> champagne
[13:56] <DS-McGuire> pmcgowan, Exception occurred during update; see log file for details
[13:56] <pmcgowan> DS-McGuire, maybe it needs sudo
[13:56] <dobey> to be fair, when i hear "small batch" it isn't phones that come to mind ;)
[13:58] <DS-McGuire> pmcgowan, Nothing seems to happen
[13:58] <pmcgowan> hmm
[13:58] <pmcgowan> it should say Upgrade path is foo
[13:59] <DS-McGuire> Just leaves me with a blinking cursor
[14:00] <pmcgowan> hmm ok thanks
[14:00] <DS-McGuire> Let me try on the terminal app on the phone and get back to you
[14:01] <ogra_> dobey, it is to red for champagne (the photos make it look champagne though ... it s more copper in real life)
[14:04] <DS-McGuire> pmcgowan, On the phone app with sudo it gives Exception occurred during update; see log file for details again
[14:04] <pmcgowan> DS-McGuire, with sudo?
[14:04] <DS-McGuire> yep
[14:04] <pmcgowan> let me try here
[14:05] <DS-McGuire> okie doke
[14:05] <dobey> ogra_: copper would be more blue/green i think. :)
[14:05] <dobey> ogra_: but it's not kentucky small batch bourbon, either way.
[14:05] <ogra_> yeah ... it is really more $undefined ... kind of old pink copperish ...
[14:06] <pmcgowan> DS-McGuire, same here, doesnt run in terminal for some reason
[14:06] <ogra_> definitely far from "gold" :)
[14:06] <pmcgowan> guess we cant do sudo from the app
[14:06] <DS-McGuire> Well, I'm glad it's not just me :P
[14:07] <dobey> pmcgowan: sudo works fine in terminal app
[14:08] <pmcgowan> dobey, for some reason system-image-cli doesnt
[14:08] <dobey> pmcgowan, DS-McGuire: try "sudo system-image-cli -vvvv -n"
[14:08] <dobey> pmcgowan: it should. i've used it plenty to switch channels
[14:08] <popey> okay, sil2100 I am now on the same revisoin as DS-McGuire on my pro 5
[14:09] <sil2100> popey: do you have the same issues with upgrading?
[14:09] <pmcgowan> dobey, it blew up with an exception
[14:09] <dobey> pmcgowan: what exception?
[14:09] <popey> http://popey.com/~alan/screenshots/device-2016-06-02-150915.png thats what i see in os build details
[14:09] <dobey> pastebinit :)
[14:10] <pmcgowan> dobey, just says check the log file for details
[14:10] <sil2100> popey: love the device build description ;) So pro with that aletu and test-keys
[14:10] <pmcgowan> but its the same as what happens when you dont sudo
[14:10] <popey> it's downloading version 3
[14:10] <dobey> pmcgowan: weird
[14:11] <popey> http://popey.com/~alan/screenshots/device-2016-06-02-151049.png
[14:11] <dobey> pmcgowan: i blame barry then
[14:11] <popey> 371.9MB seems awfully big, from OTA9 to OTA11
[14:11] <pmcgowan> anyway seems its trying to do the right thing, no idea why it fails
[14:11] <dobey> pmcgowan: what is the full output from system-image-cli though? just the exception and nothing else?
[14:12] <pmcgowan> dobey, no bunches of other things with -vvvv
[14:12] <dobey> popey: it's because you're having to download the full image
[14:12] <pmcgowan> but they all seem like it just doesnt have access
[14:12] <popey> ah
[14:12] <dobey> pmcgowan: can you pastebin the full output?
[14:13] <pmcgowan> dobey, not sure I never use terminal app
[14:14] <dobey> pmcgowan: can you run the same command via phablet-shell or ssh then? should give the same result
[14:15] <DS-McGuire> dobey, That works. Want the output?
[14:15] <pmcgowan> dobey, thats just it works fine in phablet-shell
[14:15] <DS-McGuire> popey, How's yours doing?
[14:16] <pmcgowan> let me try again
[14:16] <popey> 93%
[14:16] <DS-McGuire> .... -___-
[14:16] <dobey> pmcgowan: oh, weird
[14:16] <DS-McGuire> Mine never got that far.
[14:16] <pmcgowan> dobey, must be some sort of cockpit error
[14:16] <popey> http://popey.com/~alan/screenshots/device-2016-06-02-151626.png
[14:16] <DS-McGuire> This is unfair haha!
[14:17] <popey> well, I didn't wipe, maybe i should have?
[14:17] <pmcgowan> jibel, what else should we grab from his system?
[14:17] <popey> sil2100: ^
[14:17] <sil2100> popey: hm, no, I guess it looks ok
[14:17] <popey> does my device already have the necessary gpg keys though?
[14:18] <popey> which would not be there if I --wiped back to #1
[14:18] <sil2100> popey: I guess it doesn't really matter, hm, since u-s-i anyway downloads the latest ones from system-image if it finds a mis-match
[14:19] <popey> sil2100: so is there anything else you want me to do? Want me to press 'install' on this? http://popey.com/~alan/screenshots/device-2016-06-02-151911.png ?
[14:19] <sil2100> popey: in both your and a fresh-flash case both of you would get the new keys
[14:19] <pmcgowan> sil2100, popey his log starts with No valid image master key found, downloading
[14:19] <jibel> DS-McGuire, hi, so apparently download fails for some reason, could you attach all the log files from /var/log/ubuntu-download-manager/ ?
[14:19] <popey> ah
[14:19] <sil2100> popey: could you just pastebin the client.log?
[14:19] <popey> sure
[14:20] <sil2100> jibel: we have those, let me upload
[14:20] <sil2100> jibel: DS-McGuire sent me the logs, I can pastebin those and attach to the bug
[14:20] <pmcgowan> popey, sil2100 but then it never really works when it tries to update
[14:20] <jibel> sil2100, great
[14:20] <jibel> sil2100, all of them?
[14:20] <jibel> including hidden ones?
[14:20] <sil2100> pmcgowan: yeah, that can happen, it just downloads the latest keys from the server then
[14:21] <sil2100> jibel: not sure, I got a ubuntu-download-manager directory with two logs being quite detailed
[14:21] <popey> sil2100: http://termbin.com/g2uh my current client.log
[14:21] <sil2100> popey: ok, thanks
[14:21] <sil2100> popey: guess you can upgrade now ;)
[14:21] <pmcgowan> sil2100, it wouldnt need a restart would it?
[14:21] <sil2100> No
[14:21] <pmcgowan> DS-McGuire, have you rebooted since the updates failed?
[14:22] <sil2100> jibel: maybe I'll just tar it up and attach the whole thing to the bug report
[14:23] <DS-McGuire> pmcgowan, Yes several times, even reset the phone.
[14:23] <popey> btw does anyone else get insane flickering on the pro 5 while updating?
[14:23] <DS-McGuire> Since it was quite new I didn't need to do much.
[14:23] <popey> the white screen with the blue bouncer
[14:24] <pmcgowan> ok
[14:24] <ogra_> popey, yep
[14:24] <popey> ok
[14:59] <sil2100> DS-McGuire: ok, so far, as already mentioned above, this does seem like networking issues - is your connection stable? Could you see if you have issues accessing system-image.ubuntu.com from your network?
[14:59] <DS-McGuire> sil2100, On the same network accessing system-image.ubuntu.com seems fine.
[14:59] <DS-McGuire> want me to try on the phone
[14:59] <DS-McGuire> ?
[15:00] <DS-McGuire> The phone can access it.
[15:00] <sil2100> It seems that it's not failing every time, just from time to time certain files cannot be downloaded
[15:00] <sil2100> DS-McGuire: anyway, for now I guess it doesn't make sense to keep your device out-of-date - did you upgrade an ubuntu-touch device before with ubuntu-device-flash?
[15:01] <DS-McGuire> sil2100, FWIW My nan has the MX4 and she downloaded and installed OTA11 fine.
[15:01] <DS-McGuire> sil2100, I have done in the past, but not for a while. Is there any commands I can use?
[15:02] <sil2100> popey: do we have some adb-enabled recovery available somewhere for the turbo? What do you use during flashing?
[15:02]  * sil2100 doesn't have a turbo
[15:03] <davmor2> sil2100: yes the devices wiki page along with the rest
[15:04] <sil2100> DS-McGuire: ok, so first download http://people.canonical.com/~plars/touch/recovery-turbo.img on your desktop
[15:04]  * DS-McGuire downloading
[15:05] <DS-McGuire> Done
[15:06] <DS-McGuire> sil2100, ^ sorry
[15:07] <sil2100> Ok, sorry, in a meeting right now
[15:09] <DS-McGuire> No worries, I don't know the etiquette of pinging people on IRC.
[15:10] <ogra_> just ping at any time :)
[15:10] <ogra_> IRC is asyncronous ... he will answer when he gets to it :)
[15:10] <sil2100> DS-McGuire: no worries, just saying I'm in a meeting so I will be slowly responding ;)
[15:11] <sil2100> DS-McGuire: ok, not sure how turbo flashing works, but try this for starters: ubuntu-device-flash touch --channel ubuntu-touch/stable/meizu.en --recovery-image /full/path/to/recovery-turbo.img
[15:11] <sil2100> I always use --bootstrap but I'm not sure if that wipes your userdata or not (I only re-flash with u-d-f my testing device)
[15:12] <pmcgowan> it does wipe
[15:12] <DS-McGuire> userdata isn't a problem for me.
[15:12] <DS-McGuire> Phones a day old
[15:12] <sil2100> Anyway, for starters that should be good, right ^ ? Be sure to have the latest ubuntu-device-flash
[15:12] <dobey> we should rename it to --obliterate
[15:13] <popey> --nuke
[15:32] <DS-McGuire> sil2100, Seems like that's working,
[15:33] <sil2100> DS-McGuire: woo!
[15:47] <DS-McGuire> Hmm, I'm getting error pushing:
[15:50] <robinhero> hey guys, I filled a bug report a few days ago, if you think this feature would be useful please +1 it: https://bugs.launchpad.net/ubuntu-ux/+bug/1585353 Thanks :)
[16:06] <DS-McGuire> Seems to be updating now!
[16:06] <sil2100> DS-McGuire: phew! Sometimes the device can fail pushing when the download takes too long, usually a re-run of the command helps
[16:07] <DS-McGuire> That's what I did. Thanks :)
[16:07] <DS-McGuire> Brilliant British Internet speeds.
[16:07] <DS-McGuire> sil2100, It failed to enter recovery.
[16:07] <DS-McGuire> try again?
[16:08] <DS-McGuire> Oh wait. It has updated.
[16:08] <DS-McGuire> Terminal claims that but phone is clearly updated.
[16:09] <sil2100> Yeah, don't worry about it, check if you have OTA-11 :)
[16:09] <DS-McGuire> Yep. I have it.
[16:09] <DS-McGuire> Thanks so much for all your help today.
[16:09] <DS-McGuire> Hope my logs have helped.
[16:09] <sil2100> Apologies for the rough ride, usually OTA is a no-problematic thing, we'll keep on looking into what happened there
[16:10] <DS-McGuire> It's not a problem. I've had the MX4 for a year and no problems updating that. :)
[16:53] <zzarr> is it possible to show a display on a Google cast device from an MX4?
[16:53] <zzarr> with aethercast or what it's called?
[16:58] <kenvandine> tedg, is there a way to pass an env variable with dbus-test-runner
[16:58] <kenvandine> ?
[16:59] <kenvandine> zzarr, you mean a chromecast?
[17:00] <kenvandine> zzarr, i don't think the chromecast speaks miracast
[17:02] <zzarr> it's a chromebook
[17:03] <zzarr> a normal Ubuntu desktop?
[17:05] <kenvandine> zzarr, oh, not sure about that
[17:07] <zzarr> I meant connecting a phone to a normal Ubuntu desktop (I realized my question was implicit)
[17:26] <effbiai> hi, has ubuntu for phone been ported to the meizu pro 6 or only pro 5?
[17:27] <ogra_> only pro5
[17:28] <effbiai> is it possible to buy the normal pro 5 and install ubuntu on it, or do i have to buy the ubuntu version?
[17:31] <dobey> you would have to get the tools from meizu to repartition the device, and would need a device with unlocked bootloader
[17:31] <effbiai> so buy the ubuntu edition? :)
[17:32] <dobey> when it's not out of stock, yes :)
[17:32] <effbiai> let's hope they produce more of those then :)
[19:04] <artur_scholz> Hello! I have the BQ Aquaris E5 now since more than half a year. And well, almost nothing is really working well. Is it only me?
[19:04] <artur_scholz> For example, the music player crashes regularly, after having played 3 or so songs
[19:05] <davmor2> artur_scholz: never had that happen here on any of the devices I have
[19:05] <davmor2> popey, john-mcaleely: either of you guys seen that ^
[19:07] <artur_scholz> My assumption is that it is hanging when trying to play a wav file
[19:08] <artur_scholz> There are actually much more issues. For example, GPS is working sometimes, except when I need it. Also, the gallery for pictures is crashing at times.
[19:09] <popey> not had music app crashing, no
[19:09] <artur_scholz> There are many more of those little annoying things on the phone that left me with the impression that it is still in a kind of pre-development status
[19:10] <popey> oh sure, there's a bunch of little issues, i agree with that
[19:11] <artur_scholz> Problem is: for any those things, where to file a bug report? Normally I would expect a pop-up after a crash that asks me whether to send a crash report.
[19:11] <davmor2> popey: but not crashes all the time right
[19:12] <popey> no
[19:12] <popey> artur_scholz: crashes get captured
[19:12] <dobey> artur_scholz: there's a setting under privacy settings for automatic crash reporting
[19:12] <popey> you can see the ones that you have sent to us in system settings -> privacy
[19:13] <artur_scholz> Thanks for the hint. It's now enabled!
[19:14] <popey> we have a wiki page which links to all the projects on the phone, if you feel inclined to manually file bugs, that's welcome
[19:14] <dobey> though if it's an OOM issue where the app is just getting killed, i'm not sure those get reported
[19:14] <popey> http://wiki.ubuntu.com/Avenger
[19:14] <popey> no,they dont
[19:18] <tedg> kenvandine: Not a formal way, but if you just setenv on your own process it'll inherit that.
[19:21] <dobey> i kenvandine "env FOO=bar dbus-test-runner ..." ?
[19:22] <kenvandine> dobey, i don't think so
[19:23] <dobey> why not? wfm
[19:23] <kenvandine> oh... it does work!
[19:24]  * kenvandine is confused, i thought dbus-test-running cleaned the env
[19:24] <dobey> no. only real dbus activation does i think
[19:32] <effbiai> how to manually install ubuntu on nexus 5 with fastboot?
[20:38] <mardy> dobey: yes, it's possible -- brilliant idea!
[20:39] <mardy> dobey: so I will create such a script, and simplify the plugin a bit, alright?
[20:40] <dobey> mardy: is it doable with just account-console and/or sqlite?
[20:41] <dobey> mardy: i've been trying to simplify things in a branch i have here, so i can understand all this better, but so much of what's going on just doesn't make sense to me when i think about it :-/
[20:42] <dobey> also, isn't it like 23:00 for you?
[20:43] <JanC> almost midnight probably
[20:44] <JanC> (assuming he's in Finland)