[01:56] <nerdcore> I'm trying to follow these instructions https://devices.ubports.com/#/hammerhead and the files seem to have downloaded OK now but all I get is this: http://nerdcore.net/mike/ubtouch-error-1480902949.txt
[01:57] <nerdcore> it's been stalled there for over an hour and does not appear to be doing anything more
[03:34] <nerdcore> Does my device need to be in a specific state (recovery / bootloader) to complete `ubuntu-device-flash`?
[03:37] <duflu> nerdcore: I have never tried Ubuntu on a hammerhead but being a Nexus device you should not need any preparation other than the normal rooting
[03:41] <duflu> nerdcore: A Nexus device should only require unlocking before flashing:  https://developer.ubuntu.com/en/phone/devices/installing-ubuntu-for-devices/#unlock-device
[03:59] <nerdcore> duflu: It's quite unlocked I'm sure. I just replaced CM on it yesterday
[04:00] <nerdcore> i've replaced recovery a few times as well with clockwork and twrp
[04:00] <nerdcore> but ubuntu-device-flash just seemed to stall here: http://nerdcore.net/mike/ubtouch-error-1480902949.txt
[04:03] <nerdcore> I've also just tried building AOSP from source which appears to have worked and now I'm looking to flash it. Should I have the device in the state described here before running ubuntu-device-flash? http://source.android.com/source/running.html#flashing-a-device
[04:06] <nerdcore> oh i missed that step somehow. Stupid user error. my apologies
[04:18] <nerdcore> hmm, ubuntu appears to have booted but is asking me a question in a font so small I cannot possibly read it :(
[04:22] <nerdcore> what does "Boot access possibly lost. Fix?" mean?
[04:27] <nerdcore> maybe "Root" not "Boot"? really hard to read
[04:33] <duflu> nerdcore: Don't know sorry
[04:34] <nerdcore> I selected "Go back" and it rebooted and loaded the OS :)
[04:35] <nerdcore> Is there a way to import the contacts I dumped from adnroid in VCF format? The Contacts app only offers "import from google" or "import from SIM card"
[04:49] <nerdcore> oh and Browser seems to crash every time. I'm guessing that's not supposed to happen :/
[10:18] <Jobo> Hi! It seems like my phone won't turn back on after installing update 35. It started installing and was at the "powered by ubuntu" progress bar screen when I put it in my pocket, and now it won't turn on. iirc if it's run out of battery it would still flash the screen
[10:18] <Jobo> And I don't recall it being low on battery
[10:58] <Jobo> Anyone from the company here that saw my message?
[11:24] <harirama> I dropped my BQ4.5, glass is broken ....
[11:25] <harirama> grrrrrrrrrrrrrrrrrrrr
[11:25] <harirama> where would i get a new ubuntu phone?
[11:25] <harirama> what model would it be?
[11:51] <Acou_Bass> can you not just repair it?
[11:59] <harirama> tried to repair it. Got a new glass, had it installed, was the wrong type.
[12:00] <harirama> so found another bq4.5 secondhand, also dropped that one, glass broken.
[12:00] <harirama> now i have 2 broken phones.
[14:39] <mterry> tedg: libertine in the silo doesn't build on any platform.  I guess it's trunk that doesn't build, since the one branch we had is merged already
[14:39] <mterry> Just a heads up
[14:50] <dobey> hmm, i guess mesa is still broken :-/
[14:50] <tedg> mterry: Hmm, we should mention that to ChrisTownsend :-P
[14:52] <ChrisTownsend> tedg: mterry:  Which silo?
[14:55] <mterry> ChrisTownsend: silo 2129
[14:55] <ChrisTownsend> mterry: Ok, thanks
[14:55] <tedg> ChrisTownsend: 2129, I have my LD_LIBRARY_PATH patch in there, but nothing else.
[14:55] <mterry> But that's already merged
[14:56] <mterry> So we're just building trunk
[14:56] <larryprice> re: libertine - seems there was an update to cmake-extras this weekend that has hidden our `translations` target causing builddeb to fail... i'm looking at it now
[14:57] <mterry> larryprice, ChrisTownsend: yup, that's the build failure
[14:58] <ChrisTownsend> mterry: tedg: Ok, it's in the very capable hands of larryprice:)
[14:58] <tedg> Woot! Larry! Larry! Larry!
[15:26] <larryprice> mterry, is this libertine from the archives or from a source branch?
[15:26]  * larryprice has a fix ready, needs to figure out where to put it
[15:26] <mterry> larryprice: source branch (trunk)
[15:27] <mterry> larryprice: oh like a silo?  You could put it in our silo (2129) to help our builds, but don't land it from there -- that silo will never land, just for testing
[15:28] <larryprice> mterry, well if you're just pulling from our source branches, it makes things easier
[15:28] <mterry> larryprice: what is the schedule for libertine releases to archive?  I was surprised to see things land in trunk but not archive, so you must do manual landings?
[15:29] <larryprice> mterry, we do dev work on lp:libertine and then manually release lp:libertine/trunk when we have enough changes in place or someone needs something
[15:29] <mterry> k
[15:53] <ChrisTownsend> mterry: tedg: Ok, fix has landed in lp:libertine, so you should be able to rebuild libertine now in your silo.
[15:54] <mterry> ChrisTownsend, larryprice: such quick turnaround without an archive-trunk.  :)  Nice selling point
[15:54] <ChrisTownsend> mterry: Yep, we have to do some songs and dances, but it makes development agile:)
[15:55] <dobey> eh, more a sign that we have process problems we need to fix
[15:55] <ChrisTownsend> mterry: It also helps shake out any regressions before we release into the archive.
[15:55] <ChrisTownsend> dobey: We have beaten that dead horse into the ground.  It is what it is.
[15:57] <dobey> sure; just saying that "subverting the process by ignoring it" isn't a good solution to "we have X/Y/Z problems with the process"
[15:59] <ChrisTownsend> dobey: We don't ignore the process.  We just do it differently than many other projects.  We still use the ci-train and QA for landing releases.  Our development model is just different.  And I think it's a good thing to have the freedom to choose one way or the other.
[16:01] <taiebot> mm am i the only one experiencing regressions on the telephony side due to the landing of the group chat support?
[16:01] <pmcgowan> taiebot, I lost some history in a test I just did, guys are looking at it now
[16:03] <taiebot> pmcgowan: i have just seen you confirming.
[16:03] <taiebot> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1647024
[16:03] <pmcgowan> my symptoms are a bit different so will need to dig
[16:05] <taiebot> pmcgowan: i am roaming in a foreign country at the moment maybe that's why initialisation is slow.
[16:05] <dobey> ChrisTownsend: not quite what i was saying (or trying to say), but eh, not fussed to argue about it either :)
[16:10] <taiebot> pmcgowan: whaouh did not realise everything is back now... Weird!! i swear i had lost everything just re-opened now app launches fine and i have my messages and my call history back. Wonder what happened, the only stuff i think is i received a phone call last night maybe this re-triggered everything?
[16:11] <pmcgowan> taiebot, interesting, there was some sort of db schema change, maybe the script finally finsihed? add to the bug
[16:11] <pmcgowan> bfiller, ^
[16:12] <bfiller> salem_, ^^^
[16:16] <taiebot> pmcgowan, bfiller and salem, my messages app was like a first launch, 20 sec to boot and the intro set up displayed. No messages at all and calls history was also blank.
[16:16] <salem_> taiebot, could you check your $HOME/.cache/upstart/dbus.log  ?
[16:17] <salem_> taiebot, looks like history-daemon is somehow stuck.
[16:25] <taiebot> salem_ i have lots of oFonoConnection::inspectHandles contact (2)
[16:25] <taiebot> i suppose it's normal
[16:26] <boiko> taiebot: usually it is normal
[16:30] <taiebot> salem_ i have the debug of saturday which is a little bit more useful i suppose.
[16:31] <salem_> taiebot, the inspectHandles() is expected. I saw the ones in the bug report. Do you have any other debug?
[16:32] <salem_> taiebot, can you look into dbus.log for some text like "SQLite" or "database" ?
[16:39] <mterry> pete-woods: does your silo 2224's libqtdbusmock build if you rebuilt it?  I tried that branch in a separate silo and got a build error around GMock not being found...
[16:40] <taiebot> salem_ https://paste.ubuntu.com/23584095/
[16:41] <pete-woods> mterry: it does, yes. there were some changes in cmake-extras recently that means you have to totally rebuild if you have a dirty build tree?
[16:41] <pete-woods> could possibly be that
[16:42] <pete-woods> the MR itself only adds two new methods to a dbus stub, shouldn't make gmock dissappear..
[16:42] <pete-woods> (I hope)
[16:42] <mterry> pete-woods: yeah I agree it's not your branch, just saying there seems to be a problem with libqtdbusmock trunk
[16:42] <pete-woods> mterry: oh, trunk doesn't build?
[16:43] <pete-woods> that does surprise me
[16:43] <mterry> pete-woods: well it doesn't build with your MP.  And I don't think it's your MP.  So must be trunk
[16:43] <pete-woods> hmm
[16:43] <pete-woods> that's not completely true
[16:43] <salem_> taiebot, thanks. it looks correct. Are you still able to reproduce the issue?
[16:43] <pete-woods> as that assumes nothing else changed
[16:44] <mterry> pete-woods: no I'm assuming something else changed
[16:44] <pete-woods> pretty sure in ubuntu-land the sands shift regularly
[16:44] <mterry> pete-woods: but they broke your trunk is the point
[16:44] <pete-woods> right
[16:44] <pete-woods> yeah, I think gmock broke a lot of trunks recently
[16:44] <mterry> yup
[16:44] <pete-woods> but we made a workaround in cmake-extras
[16:44] <pete-woods> that *should* have fixed it?
[16:44]  * pete-woods double-checks that it's being used in libqtdbusmock
[16:45] <taiebot> salem_ my database could have been big i have been using my device for 3 years
[16:45] <mterry> pete-woods: I'm just saying, try rebuilding your silo package.  I did in a separate silo and it broke
[16:45] <pete-woods> mterry: I'm being dense here
[16:45] <pete-woods> it turns out my MR *does* fix the FTBFS
[16:45] <taiebot> salem_ i am not able to reproduce anymore.
[16:45] <pete-woods> but I just forgot :$
[16:45] <pete-woods> you need to make sure cmake-extras is up to date, though
[16:46] <mterry> pete-woods: I just now, like 30m ago took your silo MP and built in another silo and it broke
[16:46] <pete-woods> oh
[16:46] <mterry> Maybe my silo messed it up?  But my first guess is that archive broke you
[16:46] <pete-woods> then I really don't know what's going on
[16:46] <pete-woods> ahh
[16:47] <pete-woods> the cmake-extras fix is only in the stable-overlay for xenial
[16:47] <pete-woods> maybe that's it?
[16:47] <mterry> pete-woods: I was seeing ftbfs in xenial and zesty
[16:47] <mterry> All arches
[16:48] <mterry> Just try rebuilding the package and see what happens?
[16:48] <pete-woods> mterry: really don't know what's going on there then
[16:48] <pete-woods> mterry: yeah, will try and and see
[16:48] <pete-woods> thanks for the heads up!
[16:49] <mterry> yw!
[16:49] <salem_> taiebot, ahh, so you were able to reproduce it only once?
[16:49] <taiebot> Well  i could downgrade and re-upgrade to see if i can reproduce on upgrade
[16:50] <taiebot> salem_  I had no messages on saturday and sunday even after reboots
[16:51] <taiebot> salem_ while i was talking to pmcgowan realised that everything was back.
[16:51] <taiebot> salwm_ I can downgrade/upgrade to see if i reproduce on upgrade.
[16:57] <salem_> taiebot, thank you. I don't know if you will be able to downgrade, since the database got already upgraded to work with the most recent version. downgrading the packages may cause some other troubles.
[16:58] <salem_> taiebot, in case you face this issue again, could you grab dbus.log so we can check?
[16:59] <salem_> taiebot, also, could you run a command line via adb so I can confirm something?
[16:59] <taiebot> no problem
[17:02] <salem_> taiebot, sqlite3 $HOME/.local/share/history-service/history.sqlite "select * from schema_version"
[17:03] <taiebot> salem_  17 is the ouput
[17:06] <salem_> taiebot, ok, thanks! so your database got upgraded successfully.
[18:27] <zeu5> Hi. I'm trying to port to Xiaomi redmi 1s. I build the project for nexus as a part of the guide but can't find the boot.img or recovery.img
[18:28] <zeu5> Where do i look for what went wrong?
[18:29] <zeu5> I'm a noob to this so help me out