=== nkf1 is now known as NKF1 === salem_ is now known as _salem [01:32] mariogrip: sticers = stickers === Coolguy42 is now known as ATDT911 === NKF1 is now known as nkf1 === davidcalle_afk is now known as davidcalle === _salem is now known as salem_ [11:57] Just OTA updated my rc-proposed turbo and it's been sat at the meizu logo for some considerable time (relatively) [11:58] mzanetti: you have a turbo on rc-proposed? Updated to latest image just released about 30 mins ago? [12:02] seems to be bug 1595933 [12:02] bug 1595933 in Canonical System Image "devices don't boot on first boot after upgrade" [Undecided,Confirmed] https://launchpad.net/bugs/1595933 [12:26] popey, it's all devices [12:56] jibel, not mako [12:56] … at 470 anyway [12:56] jgdx, interesting. mako on which channel? [12:57] jibel, rc proposed [12:57] jgdx, ubuntu or bq-aquaris.en? [12:57] jibel, ubuntu [12:58] but my turbo is busted [12:58] ChrisTownsend, ^ the libertine stuff is not on ubuntu only custom tarballs? [12:59] jibel: libertine is in the base image now [13:00] ChrisTownsend, right but is there anything related in the custom tarball that could affect the boot? [13:01] 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] ChrisTownsend, is it at all possible the puritine click hook is causing the restart hang after the libertine upgrade? [13:02] bregma, it also happens during a fresh flash [13:03] 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] bregma: biometry-d to me seems more like a culprit [13:04] Being a brand new package and all. [13:04] 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] bregma: I don't see how at all. [13:05] I'm more than pleased to point my finger at someone else's package as the culprit if it's true [13:05] 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] fwiw my /var/log/upstart/biometryd.log is full of "Failed to instantiate device" [13:06] 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] That looks quite suspicious. [13:07] 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] jgdx, ack === barry` is now known as barry [13:24] hi, i would like some advice please [13:25] anyone? [13:25] just ask [13:26] i am considering intalling ububtu touch to nexus 7 [13:26] i have read tutorial [13:27] 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] h [13:33] oh i guess he didn't want an answer === allizom1 is now known as allizom [13:59] 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] Have tried full reset, no change [14:01] Seems to have a very low radio signal strength? === zulucloud1 is now known as zulucloud [14:13] who has control of the topic? [14:13] https://wiki.ubuntu.com/Avengers should be up there [14:14] ahoneybun: it is there [14:14] ahoneybun: "Bug filing: ..." [14:15] oh using a tinyurl [14:15] sorry dobey [14:15] is there a command to share that link? [14:15] !info [14:15] or something [14:15] i don't know, i guess the bot probably doesn't have one [14:15] !avengers [14:16] ubot5: don't message me that you don't know, it's a public channel [14:16] dobey: I am only a bot, please don't think I'm intelligent :) === dandrader is now known as dandrader|afk === chihchun is now known as chihchun_afk [15:54] Installed last update on rc-proposed [15:54] phone stuck at bq splash [15:55] bricked e4.5 :C [15:56] brunch875, see above ... [15:56] brunch875, this is bug 1595933, long press the power button until it reboots and second boot should be fine [15:56] bug 1595933 in Canonical System Image "devices don't boot on first boot after upgrade or fresh flash" [Critical,Confirmed] https://launchpad.net/bugs/1595933 [15:56] neato [15:56] (was just discussed a while ago) ... just do a hard reset (hold power button) and it will boot fine [15:57] kudos for non-brick! [15:57] to be honest I was expecting it to brick some time since not on stable channel [15:57] well, even on rc-proposed this is very rare [15:57] but yeah it happens at times ... the fun of living on the edge === dandrader|afk is now known as dandrader [18:28] hi there! I have a few questions, if someone could point me in the right direction [18:29] 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] yo [18:29] and says r8 in some places [18:30] 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] 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] hm, I think 9 should be latest [18:30] https://wiki.ubuntu.com/Touch/ReleaseNotes/OTA-11 according to that, nexus 7 (flo) is #9 [18:31] ah, it won't upgrade any further in the UI [18:31] keep checking for updates in the hopes of something coming, the apps update, but not the OS [18:31] do you have the terminal installed, or can you "adb shell" into the device? [18:32] so we can run commands [18:33] 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] ok, on the device can you do this:- [18:33] system-image-cli --info | nc termbin.com 9999 [18:33] and post the url here pls? [18:33] k [18:36] sigh, launching a terminal is just giving me a big white screen [18:36] well thats not expected [18:36] tried rebooting, now just going to let it sit for a few minutes to see if it resolves itself [18:37] ok, we can try from your pc. [18:37] system settings on the tablet has an about -> developer mode [18:37] switch that on to enable "adb" from your pc [18:37] then you can run the above command from inside adb [18:37] i have a nexus 7 2013 here, so can compare [18:38] hooray, adb sees it now, thanks [18:39] for reference, this is what mine shows http://termbin.com/uegx [18:41] meh Configuration directory not found: /etc/system-image/config.d [18:41] waat [18:42] maybe a relic from the ancient version of system-image-cli I'm using? [18:42] hm [18:42] i have never seen that message before [18:42] i mean, if system-image-cli can't run, that says something is a bit busted [18:43] looking at https://bugs.launchpad.net/ubuntu-system-image/+bug/1460262 now [18:43] Launchpad bug 1460262 in Ubuntu system image "system-image Exception occurred during dry-run" [Undecided,Invalid] [18:43] you're certain you're running the command on the device, and not been booted out of adb (which sometimes happens) [18:43] that very old [18:43] ooh, do you have a root prompt or phablet@ prompt? [18:44] the quick/easy way out of this is a re-flash tbh [18:44] ubuntu-device-flash touch --channel=ubuntu-touch/stable/ubuntu --device=flo [18:44] (from your pc) [18:45] welp, now it's just closing my shell on me with error: closed [18:45] I think it's time to reflash, it's getting crusty anyway [18:46] heh [18:46] if it has no valuable data, you can add --wipe to ^ that command [18:46] or leave it off and it will keep data/apps [18:46] 2016/06/24 11:46:52 Target device cannot be reached over adb [18:47] /o\ [18:47] ok, probably time for a wipe, nuke from orbit [18:47] if you "adb reboot recovery" and then do "ubuntu-device-flash touch --channel=ubuntu-touch/stable/ubuntu --device=flo --wipe" [18:48] ok, rebooting [18:48] 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] it listened to that command! [18:48] \o/ [18:48] its in recovery? [18:48] yeah, giving me a menu of options [18:48] sweet [18:48] wipe data/factory reset, wipe cache partition, etc [18:48] so the u-d-f may work now :) [18:49] (with --wipe) (which will wipe the entire device - note) [18:49] can run while on this menu screen? [18:49] i think so, yes [18:49] yes, be gone with it! [18:49] ok, that seems to be working :) [18:49] thank you [18:49] \o/ [18:50] huzzah [18:50] somewhere near the top of the command output it might mention that it's image #9 [18:51] yeah, it did [18:51] "Flashing version 9" :) [18:52] so what's the difference between this and what I have on my m10? (can point me to docs if you want) [18:52] m10 has ota11 [18:52] same url as before [18:52] https://wiki.ubuntu.com/Touch/ReleaseNotes/OTA-11 [18:53] they'll be identical [18:53] #9 _is_ OTA 11 on flo [18:53] unfortunately all the image numbers don't line up [18:53] ah, neat [18:53] because sometimes we have to crank a new image just for one device [18:53] * pleia2 nods [18:53] we don't crank a new image for every device [18:53] also older ones like bq e4.5 have many images due to time [18:54] I see [18:54] i think that's why we now expose the OTA number in the UI - we didn't used to [18:54] which made it even harder, we had to have a magic decoder ring to figure out what you're on [18:55] yeah :) [19:00] booted into the new version, thanks popey :) [19:02] 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] woo, I can copy/paste my wifi password now (it's 64 characters, paaaaaainful to type) === dandrader is now known as dandrader|afk [19:13] pleia2: yay [19:14] peat-psuwit: what device? and by "Browser is killed" do you mean the content picker, or the actual webbrowser app? [19:15] dobey: It's LG L90 Dual (my port) with 1 GB of RAM. [19:16] 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] dobey: Actually, I have a bug report with full reproduction process here: https://bugs.launchpad.net/ubuntu-application-lifecycle/+bug/1596059 [19:18] Launchpad bug 1596059 in ubuntu-application-lifecycle "An application waiting for content from other application should not be killed" [Undecided,New] [19:18] no, can't say i've seen that === dandrader|afk is now known as dandrader [21:06] 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] Some people have found it blocked, yes. Looks like fb are slowly rolling out the block [21:07] I see [21:08] on my laptop I'm using pidgin... can I install such packages (as purple) on the Ubuntuphone? (with some effort) [21:09] ha, and more importantly, can I manage the Ubuntuphone nicely while running Arch on my laptop? [21:16] Someone using the Aquaris E4.5 currently? === boiko_ is now known as boiko