[06:09] bzoltan_: strange. my last full test run was I think on Wed, and all I experienced was some test essentially stalling so I needed to kill a process to continue. some other runs completed without interaction [07:26] Mirv: For me it is Vivid exclusive ... like vivid image + vivid desktop [07:26] Mirv: do you know anybody around who could ack the UITK landing? [07:45] bzoltan_: sure I could find, but I'm looking at the gles package first for it [07:54] bzoltan_: test build went fine, I'm now doing the real build [08:07] hmm [08:08] very weird, it's as if it would pick bzoltan_'s other MP (completely different, rtm) watch file or something.. [08:09] oh, no, I had wrong MP myself [08:39] Mirv: Ohh man, I did indeed forget about the gles package. Sorry. [08:43] ricmm: hey, hm, where did silo 8 for rtm go? [08:43] ricmm: ah, I see, Ricardo pushed it without landing the silo [08:48] bzoltan_: both built and published. synced the packaging changes too. [08:55] john-mcaleely: hey, can you please be on the morning landing meeting? Since those changing factory requirements are starting to get confusing [09:19] Mirv: I just simple love you man :) Thanks a bunch [09:27] sil2100, ack [09:53] oSoMoN: do we have a bug to track the "download android app" popup we get in the HERE webapp? [09:53] I couldn't find one. [09:54] popey, I thought we did, but a quick search didn’t yield any results [09:55] oSoMoN: I'll file one. lp:webbrowser-app ? [09:56] popey, yes please [09:56] k [09:57] ogra_, john-mcaleely: binaries copied, but I had to copy them to -proposed in 14.09-factory since it didn't permit me to upload directly ;p [10:05] i updated my krillin this morning and now adb shell refuses to connect - i just get "error: device not found" [10:05] tried rebooting and unplug/replug [10:06] oSoMoN: found it. https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1414029 [10:06] Launchpad bug 1414029 in webbrowser-app (Ubuntu) "HERE asks to download the Android app on first launch" [Low,Confirmed] [10:07] low seems inappropriate to me [10:07] popey, ha, thanks. lp bug search sucks, I did a search for webbrowser-app project with "here" keyword, and it didn’t find it [10:07] :) [10:09] popey, do you happen to know who our POC at here is? this is something that should be fixed on their side, really [10:09] oSoMoN: I don't. victor p probably does. [10:10] yeah, I’ll ask him [10:10] k [10:11] ogra_: is there some udev nonsense that hasn't made its way to vivid (on my laptop) which prevents my adb from working? [10:13] popey, with what device ? [10:13] krillin [10:13] no, we havent changed anything around this in a while [10:13] hm [10:13] wonder why I suddenly can't adb in [10:13] kinda blocks me doing anything. [10:14] did you unlock the screen ? [10:14] popey, is your screen locked? [10:14] no [10:14] yes/no [10:14] :) [10:14] heh, do that then [10:14] yes, you to, no to john-mcaleely [10:14] ah [10:14] hmm [10:14] adbd is running (checked in terminal) [10:15] ogra@anubis:~/datengrab$ adb shell [10:15] phablet@ubuntu-phablet:~$ logout [10:15] ogra@anubis:~/datengrab$ [10:15] works here [10:15] adb devices shows nothing [10:15] (and i just upgraded 20min ago or so) [10:15] running 230 from 1409-proposed [10:15] tried disabling / re-enabling developer mode [10:16] * ogra_ is on 230 too [10:16] did you try restarting the adb server on the PC ? [10:16] yes [10:16] just done again [10:17] do you see USB connect events in syslog or dmesg when you connect it ? [10:17] yes [10:18] very strange [10:18] mtp works fine [10:18] if you: adb kill-server ; sudo adb devices ... [10:18] does it show then ? [10:19] yes :( [10:19] yeah, sounds like udev [10:19] i wonder if anything in udev iself changed on vivid [10:19] popey: Hey [10:19] ask pitti perhaps [10:19] rvr: hey, will look at your music thing once I get past this adb issue [10:19] thanks ogra_ [10:20] popey: Ok [10:20] sil2100: john-mcaleely: I will be testing the hot fix. Ping me when the channel is ready, please. [10:20] sil2100: Do you have any ETA? [10:25] rvr: hey! [10:25] rvr: we should have the channel finalized soon, which means we'll be able to build a new image with the 2 fixes in the rootfs [10:25] hmmm [10:26] ogra_: I think we didn't have an ubuntu-rtm image with the 2 hot-fix packages, right? Or is it only my commitlogs lying? [10:26] sil2100: Ack [10:27] ogra_: maybe it would be good to kick a new ubuntu-rtm image to have a standard 14.09 image to test against with the new device and custom bits? [10:27] yeah, let me check [10:27] Since we anyway need to land those 2 tarballs for 14.09 as well, not only for the new 14.09-factory [10:28] imgbot, status 230 [10:28] Status: succeeded, Started: 2015-02-09 03:02:17 UTC, Finished: 2015-02-09 03:53:45 UTC [10:28] Build URL: https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu-rtm/14.09/ubuntu-touch/+build/19536 [10:28] Changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/230.changes [10:28] hmm [10:29] aha [10:29] sil2100, 229 had it [10:29] imgbot, status 229 [10:29] rvr: confirmed url-dispatcher crash [10:29] Status: succeeded, Started: 2015-02-07 20:09:02 UTC, Finished: 2015-02-07 21:01:00 UTC [10:29] Build URL: https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu-rtm/14.09/ubuntu-touch/+build/19484 [10:29] Changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/229.changes [10:29] 229? [10:29] rvr: will file a bug. [10:29] Aaaaah! [10:29] Crap, right! [10:30] ogra_: yeah, indeed, didn't see it as it wasn't noted as a CI Train landing [10:30] popey: Ok, I will mark the card as failed in trello. [10:30] ok [10:30] thanks rvr [10:30] ogra_: thanks for double-checking [10:30] sil2100, yeah, i think rsalveti had to dput [10:30] (seeing the packlog) [10:30] *back [10:45] FYI folks, the URLs for proposed-migration output have changed a bit - for ubuntu-rtm, they now have the series prepended. see http://people.canonical.com/~ubuntu-archive/proposed-migration/ubuntu-rtm/ [10:45] needed to do that in order to support 14.09 and 14.09-factory both being live in parallel [10:48] trainguards, could I have a silo for row #83? sil2100 this includes the merge from rtm and a fix to the FTBFS in vivid. [10:51] Chipaca: let me take a look [11:08] john-mcaleely, ogra_, jibel: I'm building the first 14.09-factory image right now [11:09] ack [11:09] sil2100, k [11:09] My first build job ever started, a bit rough but I think next time I'll just use screen for it ;) [11:09] As recommended by Colin [11:09] :-) [11:11] sil2100, haha, he recommends that to me too since years ... [11:12] (and i havent managed til today to use screen for more than serial terminals in my workflow ... ) [11:12] I use screen most of the time locally, I put my irssi clients in those out of habit [11:12] Was very useful when I was testing new unity/compiz packages back in the old days [11:12] ;) [11:13] Of course, it's better to have an IRC shell, which I also use sometimes [11:13] yeah, many do ... i never got into that and just plaster my desktop with terminal windows :) [11:15] (i guess thats just the gamer in me needing a reason for three monitors) [11:15] hoho [11:16] Only working on a dual-screen here [11:21] http://people.canonical.com/~jhm/barajas/ubuntu-rtm-14.09/device_krillin-20150209-094615f.tar.xz [11:21] http://people.canonical.com/~jhm/barajas/ubuntu-rtm-14.09/device_krillin-20150209-094615f.changes [11:21] http://people.canonical.com/~jhm/barajas/ubuntu-rtm-14.09/device_krillin-testresults-20150209-094615f.ods [11:22] sil2100, device tarball, as discussed ^ [11:26] john-mcaleely: passed your QA \o/ ? [11:26] sil2100, yes [11:26] john-mcaleely: ok, then let's get those 2 device tarball changes + the custom tarball into QA [11:27] jibel, rvr: hey guys, so the plan is: [11:27] jibel, rvr: we have a 14.09-factory-proposed image building (the snapshot-based image + the rootfs fixes for the hot-fix) [11:27] jibel, rvr: we need the device and custom tarballs tested for both the 14.09-proposed and 14.09-factory-proposed images [11:28] jibel, rvr: 14.09-factory-proposed is still building, but in the meantime you coudl already start testing the change on standard 14.09 [11:28] 14.09-proposed [11:29] jibel, rvr: once the 14.09-factory-proposed first build finishes, then you could double-confirm it's all alright on that one as well [11:29] So you still want the first factory image to be with the older device/custom tarballs? [11:29] After we get those 2 +1's from you, we'll push the tarballs [11:30] cjwatson: with the ones that are currently available - it's what's happening now, right? [11:30] sil2100: Ok, so I need the instructions to test with 14.09-proposed. [11:30] Since the new tarballs didn't get published anywhere in public right now [11:31] Well, I haven't saved the new system-image configuration yet [11:31] cjwatson: ah, ok :) [11:31] But it was what I previously understood the plan to be, so was checking [11:31] sil2100, build one with the old tarballs we have time [11:31] cjwatson: ^ [11:32] cjwatson: well, it doesn't matter anyway as we will be only testing 14.09-factory-proposed with the new tarballs [11:32] But yeah [11:32] Best if first it fetches the old ones, it will make testing easier [11:32] We won't be publishing anything in blind then [11:32] OK [11:32] cjwatson: thanks! [11:33] Separately FYI, there'll be rolling LP builder downtime in a bit since we're doing a launchpad-buildd upgrade [11:33] Please let us know if there are any super-urgent builds that mustn't be interrupted [11:35] john-mcaleely: sil2100: To test with 14.09-proposed, what do I need to do? [11:35] rvr do you want to test the custom & device together, or separately? [11:36] sil2100, ^ [11:37] john-mcaleely: What are the changes in the custom and in the device? [11:38] rvr are you on qa-team mailing list? [11:38] john-mcaleely: Yes, reading the emails [11:39] rvr: so first you upgrade to the 14.09-proposed latest image on you krillin - the actual upgrade of the tarballs I guess john-mcaleely can help you with [11:39] rvr: thanks! [11:43] john-mcaleely: Ok, so device tarball enables factory wipe, and custom tarball allows to reboot, wipe (I suppose this needs device tarball) and power off. [11:44] rvr yup [11:45] john-mcaleely: I'll test device+custom at the same time. [11:55] rvr, I've emailed you [11:55] john-mcaleely: Received === MacSlow is now known as MacSlow|lunch [11:57] sil2100, The device tarball above ^ is the one to land in #17, and is the one rvr has a pointer to :-) [11:57] \o/ [11:58] john-mcaleely: got the e-mail, thanks for forwarding all communication :) Let's get this tested and released [12:05] Flashing [12:06] trainguards, silo 8 (row 83) ready to go [12:09] Chipaca: ok [12:10] sil2100: fyi the bug seems to be a bug in go 1.3's c-stack garbage collector. Still digging some more, and will file a bug with go when we've got it pared down a bit more. [12:10] Chipaca: MP not top-approved [12:11] Mirv: 'tis now :) [12:11] sil2100: ubuntu-touch/ubuntu-rtm/14.09-factory-proposed krillin #2 exists now [12:12] cjwatson: \o/ Thanks for confirming [12:13] rvr: so, once you're done with testing 14.09-proposed, you can flash to ubuntu-touch/ubuntu-rtm/14.09-factory-proposed and sanity-check if all is ok as well? [12:13] * sil2100 needs to jump out for lunch [12:13] I'll be reading this IRC if anything urgent pops up [12:14] Chipaca: thanks! :) [12:25] MIRV: I'm not here today you might want to recommend someone else [12:27] sure thing dave [12:37] trainguards: Halp! I can't install rtm silo 7. Basically, u-s-s says it depends on >= 0.70 of a package and the candidate is 0.70-ppa-etc. [12:42] jgdx: the u-s-s dependency is wrong, instead of "qtdeclarative5-ofono0.2 (>=0.70)," it should be "qtdeclarative5-ofono0.2 (>=0.70~)," [12:42] so, it needs a rebuild with that [12:42] Mirv, ah, k. Thanks [12:52] Mirv, and that change is picked up automatically… [13:02] john-mcaleely: I installed 14.09-proposed with device tarball (alone), and did touch /data/.factory_wipe. How is it triggered? Rebooting didn't reset the system. === alan_g is now known as alan_g|lunch [13:08] jgdx: hm? I see you update the MP, so yes now you should try a rebuild [13:08] Mirv, k [13:08] thanks [13:09] sil2100: Should we switch over to the new URLs in order to get an updated build in parallel with QA? [13:10] jgdx: ubuntu-system-settings in PACKAGES_TO_REBUILD [13:11] Mirv, right === MacSlow|lunch is now known as MacSlow === chunsang is now known as chunsang-away [13:41] rvr, *#0704#* in the dialler === alan_g|lunch is now known as alan_g === chunsang-away is now known as chunsang [14:04] cjwatson: what do you mean? [14:09] sil2100: Well, AIUI QA is currently testing 14.09-factory-proposed krillin #2, which uses the old device and custom tarballs, but we want to deliver an image using the new device and custom tarballs by end of day Spain [14:09] sil2100: Shouldn't we be building such an image kind of NOW, even if QA is still testing the old one? [14:13] bzoltan_, is silo5 ready now ? [14:13] om26er: yes, it is [14:14] bzoltan_, do you have the latest testing results [14:14] om26er: duuude :) it takes 8-10 hours ... for vivid landing it took 48 because of the reboot loops [14:15] cjwatson: QA is testing the new tarballs as well, they usually do it by installing the old image and manually getting the tarballs on top of it [14:15] cjwatson: that way they can test if it's good to land without us having to revert the tarball uploads in case of any problems [14:15] OK [14:16] cjwatson: so let's wait for their test results and then built it once it's all ok :) [14:16] sil2100: Can I assume that this is all in your hands now and I don't need to mangle configuration, then? [14:16] om26er: unless if you agree that this change -> http://bazaar.launchpad.net/~zsombi/ubuntu-ui-toolkit/haptics-feedback-singleton/revision/1148 wil not effect the test results and accept my previous tests [14:16] cjwatson: all is ok so far, thanks :) [14:17] COol [14:17] With sensible capitalisation [14:17] bzoltan_, the change looks simple enough, though I am not the expert there. [14:18] bzoltan_, i'll just go ahead with my verification and cross my fingers. [14:18] om26er: if you want i can run the test plan... it will just take time. Earliest by tomorrow morning... with some luck [14:20] sil2100: john-mcaleely: Sanity tests pass on 14.09-proposed + device tarball (not proposed-customized + device + tarball). [14:20] \o/ [14:21] bzoltan_, I think the risk here is probably we could see a crash with that change in some case. So perhaps running the test plan again will help us be sure. [14:21] thanks rvr [14:21] john-mcaleely: I asked about how to check device tarball with proposed, since I understand it doesn't have the MMI fix. [14:21] rvr, ah, I see. sorry, I don't know a wau [14:21] way [14:22] john-mcaleely: I touched /data/.factory_wipe and rebooted hoping it will do something, but it didn't. [14:22] ricmm: ping [14:25] john-mcaleely: And ricmm must be resting... Ok. I am flashing custom-proposed with device tarball. [14:25] proposed-customized [14:31] rvr, sounds good [14:32] rvr: could you also repeat the same tests for 14.09-factory-proposed? [14:33] sil2100: What's the difference between that and proposed-customized? [14:35] rvr: proposed-customized? I mean, now you took the tarballs and installed them on top of an image from the ubuntu-rtm/14.09-proposed channel, right? [14:35] rvr: we would need the same tarballs tested against an image from ubuntu-rtm/14.09-factory-proposed, which is has basically everything as the last image we promoted [14:36] rvr: we need it tested on that as this will be what will be sent out to the client essentially [14:36] sil2100: I installed the device tarball + ubuntu-rtm/14.09-proposed, but the custom tarball is only available as an image in 14.09-proposed-customized. [14:36] hm [14:37] john-mcaleely, cwayne: is there any way to install the custom tarball on an image from a different channel? [14:37] device tarball contains only a couple of changes to allow factory wipe, the other fixes are in the custom tarball. [14:38] sil2100, no [14:38] that's why we suggested to test device + custom in one go :) [14:38] (well, not in any sane way) [14:38] yeah, there's some hacky ways to do it, but i'd feel more comfortable having it tested from the channel [14:38] So basically we cannot test the custom tarball on top of the last promoted image, right? [14:40] Ok, then it's a bit sad, but I guess we can assume it's ok, get the tarballs published and then just test the new ubuntu-rtm/14.09-factory-proposed image [14:40] Which will have both tarballs in place [14:40] sil2100, yeah, I think so [14:41] rvr: did you finish all the tests regarding custom and device already, or is there still something left to do? [14:41] version device: 20150129-c75dcfb [14:41] version custom: 20150207-538-29-183 [14:42] john-mcaleely: The version doesn't match, device is 20150209-094615f [14:42] rvr, yes, that's the behaviour with --device-tarball [14:42] john-mcaleely: Ok [14:42] the UI doesn't see the updated version, sadly - it believes the server [14:43] you can look at /etc/device-build to be sure [14:43] rvr, ^ [14:43] Checking [14:44] sil2100: I only checked the device part with proposed, now checking the whole thing in proposed-customized [14:44] john-mcaleely: That file reports the correct version [14:45] rvr, :-) [14:47] "Do you want to reset your phone?" Not translated, but not a big deal, I guess ;D [14:49] Ok, I can see the wizard. Now waiting 2 minutes. [14:49] Hmm [14:49] This was faster [14:50] john-mcaleely: It did power off, but I see the red light [14:50] Is that right? [14:50] rvr are you plugged in? [14:50] Yes [14:50] rvr, then yes, it goes to charge mode automatically === marcusto_ is now known as marcustomlinson [14:56] Wipe also worked [14:57] john-mcaleely: sil2100: So, features do work as expected. Running sanity suite on proposed-customized + device tarball. [14:57] \o/ [15:03] is someone already validating the pay-ui fix [15:04] pmcgowan: In the qa team, not that I know. I am pinging them to check. [15:05] rvr, thanks as thats also high priority [15:06] rvr: \o/ [15:07] pmcgowan: om26er will check it. [15:07] thanks [15:07] rvr: then waiting on your final +1 - once we have that, we get both tarballs in place and then we would again need to get this validated for the -factory image... ;( [15:07] sil2100: Ok [15:09] oh ok. was just going to ask if all the qa people were away on national holiday or something today, as the "under testing" column of trello is empty :) [15:09] dobey, for pay-ui fix do I need to buy an app using paypal ? [15:11] om26er: just going up to the point of needing to ender the username/password on the paypal page is enough to verify the specific fix, but yes, an app would need to be purchased to test the full flow (that it exits and the app starts installing after a succesful purchase) [15:13] dobey, I don't have paypal, I'll make sure to test the plan to the point where I don't need to buy anything with paypal, probably you can help me with that part ? [15:14] om26er: there is a link at the bottom of the paypal page that says "Cancel and Return to 'Canonical Store'" or something like that [15:14] om26er: tapping that should cancel the purcahse [15:14] purchase [15:14] dobey, right, what I want to say is that if we need to test a real purchase perhaps you could do that. [15:14] and back arrow in the toolbar will return to the payment methods page of pay-ui [15:16] * dobey can't wait to get refunds implemented [15:22] dobey, can you name a few paid apps in the store [15:23] om26er, wallet lightener pro [15:24] om26er: search for "price:2.99" (capitalization important there) [15:24] bzoltan_: approval needed https://code.launchpad.net/~zeller-benjamin/qtcreator-plugin-ubuntu/small-templ-fix/+merge/249056 ! [15:24] maybe i should update the testplan to just say to search for price:foo [15:26] and done [15:45] zbenjamin: https://code.launchpad.net/~zeller-benjamin/qtcreator-plugin-ubuntu/small-templ-fix/+merge/249056 <- can you get this approved? [15:45] bzoltan_: ^^^ [15:55] kenvandine, "testing only" in rtm silo 7, what's the plan? [15:56] jgdx, have you been able to test all the pieces? [15:56] kenvandine, oui [15:56] i think it was hard to do that before, because we needed all the packages [15:57] it was [15:59] rvr: how far are you with testing? [16:08] john-mcaleely: how much more time do we have for the image to be released? [16:08] sil2100, not long [16:09] Then I suppose on 14.09-factory we'll only ask rvr to perform tests checking if the new functionality works [16:09] I'm finishing with proposed-customized [16:10] sil2100, makes sense [16:10] It took longer because I had a problem with video recording, that cannot reproduce [16:10] Reflashing takes time [16:10] I'll flash my krillin to 14.09-factory to see if all looks ok with those images on first glance [16:17] sil2100: john-mcaleely: Sanity tests passes on proposed-customized [16:17] rvr, sil2100 \o/ [16:18] Yaay! [16:18] john-mcaleely, cwayne: could you please upload your tarballs? [16:18] sil2100, I guess it's time for me and cwayne to do some pushing [16:18] sil2100, ack [16:18] IIUC those should be also found and imported to the 14.09-factory-proposed channel [16:18] john-mcaleely: sil2100: I had a problem with video recording, playing them showed a black screen. But I reflashed with and witouth the tarball and couldn't reproduce. [16:19] rvr, noted. can you raise a barajas bug - probably a one-off, but worth checking [16:20] sil2100, device tarball pushed [16:20] custom pushed [16:21] john-mcaleely: 14.09-factory-proposed needs also --device-tarball, right? [16:21] cjwatson: to double confirm, the tarballs that have been pushed to 14.09-proposed will be also visible now and picked up in 14.09-factory-proposed, right? [16:23] rvr, now or once there's been one more build? [16:23] rvr if you wait ~10 mins, I think there will be a build with the right tarball in place [16:24] john-mcaleely: Ok [16:24] * sil2100 just hopes that the importer is enabled [16:25] sil2100, looks like it's dopne [16:26] build #3 in factory-proposed is looking good. agreed cwayne ? [16:26] $ ubuntu-device-flash query --show-image --channel ubuntu-touch/ubuntu-rtm/14.09-factory --device krillin [16:26] ubuntu-device-flash query --show-image --channel ubuntu-touch/ubuntu-rtm/14.09-factory-proposed --device krillin [16:26] even [16:26] sil2100: should do yes, the URLs matched [16:26] john-mcaleely: sil2100: jibel has been able to reproduce the problem with the videos [16:26] looks right to me [16:27] rvr, ok, so lets see if it's in build #3 of factory-proposed [16:27] sil2100, #3 looks like the promotion candidate, right? [16:30] rvr, we can hope the video issue is just in current RTM [16:33] I only happened with proposed-customized [16:34] rvr, I'm bootstrapping rtm/16, it seems to happen only on first boot [16:34] there's *nothing* in the tarball that could even possibly affect video recording [16:34] so it may be intermittent [16:35] cwayne, could the factory reset trigger such a bug? [16:35] jibel, no, I don't believe so [16:35] cwayne, it's only on first boot after a reset [16:35] weird [16:35] jibel, fwiw, I record and play a video with every device tarball [16:36] jibel, and does the type of reset matter? (through the UI, or through the dialler short code?) [16:37] john-mcaleely, no idea, I'm trying on rtm/16 and will compare with factory/3 [16:37] jibel, makes sense [16:41] jibel: I did a factory reset, and video plays fine this time. [16:42] john-mcaleely: hm, #4 should be the candidate I suppose? [16:43] sil2100, er why? [16:43] john-mcaleely: since the image I built in the morning was #2 from what cjwatson said, and we had 2 tarball uploads [16:43] rvr, john-mcaleely same problem on #16, I cannot record/play a video on first boot, so not a regression but something to fix ASAP. [16:43] sil2100, #3 has both tarballs [16:43] So I suppose it should trigger 2 builds? [16:43] Oh, nice [16:43] sil2100, I guess it optimised [16:43] Maybe because it got in on one importer run [16:44] rvr, can you file a bug if not done already? [16:44] or maybe #4 will arrive shortly as a dupe... [16:44] Anyway, yeah, then #3 is the candidate ;) [16:44] jibel: Yup [16:44] jibel, ack. bug please :-) [16:44] rvr, nice catch :-) [16:45] jibel, rvr: thanks for finding and confirming ;) [16:48] rvr: then if you could simply check if the modifications still work on the 14.09-factory-proposed image number #3 it would be awesome :) [16:48] We could then promote it basically [16:48] sil2100: Is the image already available? [16:49] rvr: it seems it's there, john-mcaleely says that #3 has both the tarballs [16:49] So it's the promotion candidate for today [16:49] ok [16:49] https://bugs.launchpad.net/camera-app/+bug/1419875 [16:49] Launchpad bug 1419875 in camera-app "Recorded video in black" [Undecided,New] [16:51] Flashing [16:53] Kaleo, ^ on first boot on rtm/16 [16:54] the generation of the thumbnails fails too [16:57] jibel, aha. I never record more than 5 sec or so in my testing [17:00] sil2100: no landing call? [17:01] jibel, thanks [17:01] popey: I'll be there in a minute [17:01] fscking hangouts [17:01] crashed [17:01] GAHHGAGHAKtfigyzsueeafwe [17:11] crashed again, I give up [17:12] popey: we just finished :) [17:12] popey: you published the music-app, right? [17:12] i did [17:12] sil2100, no landing meeitngs? [17:12] meeting [17:13] jibel, we had it [17:13] ogra_, ah, I was that late, sorry. [17:36] Factory reset via dialer app works [17:42] yay [17:45] Scopes are there, apps are there, phone works, camera works... [17:45] john-mcaleely: Looks good to me. [17:46]