[01:32] <ahoneybun> mariogrip: sticers = stickers
[11:57] <popey> Just OTA updated my rc-proposed turbo and it's been sat at the meizu logo for some considerable time (relatively)
[11:58] <popey> mzanetti: you have a turbo on rc-proposed? Updated to latest image just released about 30 mins ago?
[12:02] <popey> seems to be bug 1595933
[12:26] <jibel> popey, it's all devices
[12:56] <jgdx> jibel, not mako
[12:56] <jgdx> … at 470 anyway
[12:56] <jibel> jgdx, interesting. mako on which channel?
[12:57] <jgdx> jibel, rc proposed
[12:57] <jibel> jgdx, ubuntu or bq-aquaris.en?
[12:57] <jgdx> jibel, ubuntu
[12:58] <jgdx> but my turbo is busted
[12:58] <jibel> ChrisTownsend, ^ the libertine stuff is not on ubuntu only custom tarballs?
[12:59] <ChrisTownsend> jibel: libertine is in the base image now
[13:00] <jibel> ChrisTownsend, right but is there anything related in the custom tarball that could affect the boot?
[13:01] <ChrisTownsend> jibel: Umm, not that I know of, but I really don't have anything to do with the custom tarball other than the puritine click and libertine-scope are there and those are unchanged.
[13:02] <bregma> ChrisTownsend, is it at all possible the puritine click hook is causing the restart hang after the libertine upgrade?
[13:02] <jibel> bregma, it also happens during a fresh flash
[13:03] <ChrisTownsend> bregma: It wasn't hanging before and the only change this affects is making a missing directory and that was in libertine-tools.
[13:04] <ChrisTownsend> bregma: biometry-d to me seems more like a culprit
[13:04] <ChrisTownsend> Being a brand new package and all.
[13:04] <bregma> right, I reviewd the libertine MP and that's all it does, but I just want to be sure creating that directory does not trigger some untoward behaviour in the puritine click
[13:05] <ChrisTownsend> bregma: I don't see how at all.
[13:05] <bregma> I'm more than pleased to point my finger at someone else's package as the culprit if it's true
[13:05] <ChrisTownsend> bregma: Well, all I'm basing my opinion on is what I know about what changed in Libertine and a gut feeling, so no, not real proof:)
[13:06] <popey> fwiw my /var/log/upstart/biometryd.log is full of "Failed to instantiate device"
[13:06] <dobey> mardy: ok, so with your branch, i'm just not getting any UI opened at all for Setup::exec() when an account already exists.
[13:06] <ChrisTownsend> That looks quite suspicious.
[13:07] <jgdx> jibel, as soon as I install a silo, mako does not boot. Not sure what that signifies. So maybe disregard above comment for now.
[13:08] <jibel> jgdx, ack
[13:24] <chris___> hi, i would like some advice please
[13:25] <chris___> anyone?
[13:25] <k1l_> just ask
[13:26] <chris___> i am considering intalling ububtu touch to nexus 7
[13:26] <chris___> i have read tutorial
[13:27] <chris___> question is, i am running linux mint on my laptop do i really need ubuntu on my laptop to install touch to nexus?
[13:33] <bozit> h
[13:33] <dobey> oh i guess he didn't want an answer
[13:59] <tuttle955i> Hiya, my bq e5 works great, but my meizu pro5 cannot connect to mobile network, also cannt get mobile data to work =( is this a known bug?
[14:00] <tuttle955i> Have tried full reset, no change
[14:01] <tuttle955i> Seems to have a very low radio signal strength?
[14:13] <ahoneybun> who has control of the topic?
[14:13] <ahoneybun> https://wiki.ubuntu.com/Avengers should be up there
[14:14] <dobey> ahoneybun: it is there
[14:14] <dobey> ahoneybun: "Bug filing: ..."
[14:15] <ahoneybun> oh using a tinyurl
[14:15] <ahoneybun> sorry dobey
[14:15] <ahoneybun> is there a command to share that link?
[14:15] <ahoneybun> !info
[14:15] <ahoneybun> or something
[14:15] <dobey> i don't know, i guess the bot probably doesn't have one
[14:15] <dobey> !avengers
[14:16] <dobey> ubot5: don't message me that you don't know, it's a public channel
[15:54] <brunch875> Installed last update on rc-proposed
[15:54] <brunch875> phone stuck at bq splash
[15:55] <brunch875> bricked e4.5 :C
[15:56] <ogra_> brunch875, see above ...
[15:56] <jibel> brunch875, this is bug 1595933, long press the power button until it reboots and second boot should be fine
[15:56] <brunch875> neato
[15:56] <ogra_> (was just discussed a while ago) ... just do a hard reset (hold power button) and it will boot fine
[15:57] <brunch875> kudos for non-brick!
[15:57] <brunch875> to be honest I was expecting it to brick some time since not on stable channel
[15:57] <ogra_> well, even on rc-proposed this is very rare
[15:57] <ogra_> but yeah it happens at times ... the fun of living on the edge
[18:28] <pleia2> hi there! I have a few questions, if someone could point me in the right direction
[18:29] <pleia2> I have the touch image installed on my Nexus 7 2013 and have been upgrading it along for over a year now, it's now at version 20160222-020405
[18:29] <popey> yo
[18:29] <pleia2> and says r8 in some places
[18:30] <pleia2> so I'm wondering 1) is this the newest version I can get for the N7? if not, how do I upgrade/reflash it?
[18:30] <pleia2> the flashing instructions all seem to be for android + debug mode, and I can't get adb to see my tablet when it's plugged in and running ubuntu
[18:30] <popey> hm, I think 9 should be latest
[18:30] <popey> https://wiki.ubuntu.com/Touch/ReleaseNotes/OTA-11 according to that, nexus 7 (flo) is #9
[18:31] <pleia2> ah, it won't upgrade any further in the UI
[18:31] <pleia2> keep checking for updates in the hopes of something coming, the apps update, but not the OS
[18:31] <popey> do you have the terminal installed, or can you "adb shell" into the device?
[18:32] <popey> so we can run commands
[18:33] <pleia2> I have a terminal on the tablet, but 'adb devices' doesn't show it when I try to get to it from my desktop
[18:33] <popey> ok, on the device can you do this:-
[18:33] <popey> system-image-cli --info | nc termbin.com 9999
[18:33] <popey> and post the url here pls?
[18:33] <pleia2> k
[18:36] <pleia2> sigh, launching a terminal is just giving me a big white screen
[18:36] <popey> well thats not expected
[18:36] <pleia2> tried rebooting, now just going to let it sit for a few minutes to see if it resolves itself
[18:37] <popey> ok, we can try from your pc.
[18:37] <popey> system settings on the tablet has an about -> developer mode
[18:37] <popey> switch that on to enable "adb" from your pc
[18:37] <popey> then you can run the above command from inside adb
[18:37] <popey> i have a nexus 7 2013 here, so can compare
[18:38] <pleia2> hooray, adb sees it now, thanks
[18:39] <popey> for reference, this is what mine shows http://termbin.com/uegx
[18:41] <pleia2> meh Configuration directory not found: /etc/system-image/config.d
[18:41] <popey> waat
[18:42] <pleia2> maybe a relic from the ancient version of system-image-cli I'm using?
[18:42] <popey> hm
[18:42] <popey> i have never seen that message before
[18:42] <popey> i mean, if system-image-cli can't run, that says something is a bit busted
[18:43] <pleia2> looking at https://bugs.launchpad.net/ubuntu-system-image/+bug/1460262 now
[18:43] <popey> you're certain you're running the command on the device, and not been booted out of adb (which sometimes happens)
[18:43] <popey> that very old
[18:43] <popey> ooh, do you have a root prompt or phablet@ prompt?
[18:44] <popey> the quick/easy way out of this is a re-flash tbh
[18:44] <popey> ubuntu-device-flash touch --channel=ubuntu-touch/stable/ubuntu --device=flo
[18:44] <popey> (from your pc)
[18:45] <pleia2> welp, now it's just closing my shell on me with error: closed
[18:45] <pleia2> I think it's time to reflash, it's getting crusty anyway
[18:46] <popey> heh
[18:46] <popey> if it has no valuable data, you can add --wipe to ^ that command
[18:46] <popey> or leave it off and it will keep data/apps
[18:46] <pleia2> 2016/06/24 11:46:52 Target device cannot be reached over adb
[18:47] <pleia2> /o\
[18:47] <popey> ok, probably time for a wipe, nuke from orbit
[18:47] <popey> if you "adb reboot recovery" and then do "ubuntu-device-flash touch --channel=ubuntu-touch/stable/ubuntu --device=flo --wipe"
[18:48] <pleia2> ok, rebooting
[18:48] <popey> if the adb reboot recovery doesn't work you can reboot, hold power and vol- (or vol+, I forget) to get into recovery mode
[18:48] <pleia2> it listened to that command!
[18:48] <popey> \o/
[18:48] <popey> its in recovery?
[18:48] <pleia2> yeah, giving me a menu of options
[18:48] <popey> sweet
[18:48] <pleia2> wipe data/factory reset, wipe cache partition, etc
[18:48] <popey> so the u-d-f may work now :)
[18:49] <popey> (with --wipe) (which will wipe the entire device - note)
[18:49] <pleia2> can run while on this menu screen?
[18:49] <popey> i think so, yes
[18:49] <pleia2> yes, be gone with it!
[18:49] <pleia2> ok, that seems to be working :)
[18:49] <pleia2> thank you
[18:49] <popey> \o/
[18:50] <popey> huzzah
[18:50] <popey> somewhere near the top of the command output it might mention that it's image #9
[18:51] <pleia2> yeah, it did
[18:51] <pleia2> "Flashing version 9" :)
[18:52] <pleia2> so what's the difference between this and what I have on my m10? (can point me to docs if you want)
[18:52] <pleia2> m10 has ota11
[18:52] <popey> same url as before
[18:52] <popey> https://wiki.ubuntu.com/Touch/ReleaseNotes/OTA-11
[18:53] <popey> they'll be identical
[18:53] <popey> #9 _is_ OTA 11 on flo
[18:53] <popey> unfortunately all the image numbers don't line up
[18:53] <pleia2> ah, neat
[18:53] <popey> because sometimes we have to crank a new image just for one device
[18:53]  * pleia2 nods
[18:53] <popey> we don't crank a new image for every device
[18:53] <popey> also older ones like bq e4.5 have many images due to time
[18:54] <pleia2> I see
[18:54] <popey> i think that's why we now expose the OTA number in the UI - we didn't used to
[18:54] <popey> which made it even harder, we had to have a magic decoder ring to figure out what you're on
[18:55] <pleia2> yeah :)
[19:00] <pleia2> booted into the new version, thanks popey :)
[19:02] <peat-psuwit> Have anyone ever encountered this: When trying to select a photo (in Gallary or something) for browser, the Browser is killed and the photo isn't transferred.
[19:03] <pleia2> woo, I can copy/paste my wifi password now (it's 64 characters, paaaaaainful to type)
[19:13] <popey> pleia2: yay
[19:14] <dobey> peat-psuwit: what device? and by "Browser is killed" do you mean the content picker, or the actual webbrowser app?
[19:15] <peat-psuwit> dobey: It's LG L90 Dual (my port) with 1 GB of RAM.
[19:16] <peat-psuwit> dobey: For what's being killed, It's browser itself, because I'm presented with a blurry screenshot of Browser when it comes back.
[19:18] <peat-psuwit> dobey: Actually, I have a bug report with full reproduction process here: https://bugs.launchpad.net/ubuntu-application-lifecycle/+bug/1596059
[19:18] <dobey> no, can't say i've seen that
[21:06] <lars_> Hey guys, I'm thinking about buying an Aquaris E4.5 and concluding my decision. I just read that Facebook blogged the messenger function of the web-app. Is that true?
[21:07] <popey> Some people have found it blocked, yes. Looks like fb are slowly rolling out the block
[21:07] <lars_> I see
[21:08] <lars_> on my laptop I'm using pidgin... can I install such packages (as purple) on the Ubuntuphone? (with some effort)
[21:09] <lars_> ha, and more importantly, can I manage the Ubuntuphone nicely while running Arch on my laptop?
[21:16] <lars_> Someone using the Aquaris E4.5 currently?