[00:15] Ursinha: LOL ^ ;-) [00:15] I think it's working ;-) [00:18] robru: \o/ awesome! [00:24] hey, rtm silo 007 needs the new apparmor 2.8.96~2652-0ubuntu5 that is in utopic. so, I need a resync. is that self-serve? if not, how do I do that? [00:27] jdstrand: well, your landing request just says 'apparmor' which implied you are responsible for uploading that to the silo yourself. you probably wanna change that to 'sync:ubuntu,utopic apparmor' and then you can just run the build job and it'll sync in the new apparmor for you [00:28] robru: ok, thanks. at the time, I did upload it. I could just upload it again, but wasn't sure if there was a better way [00:28] thanks [00:32] jdstrand: you're welcome. whether or not you consider the heaping pile of untested citrain code "a better way" is up to you. [00:32] jdstrand: also you need to reconfig after changing that landing request [00:39] sigh [00:40] watch-ppa is still busted. [00:42] jdstrand: hm seems like the upload failed. the ppa only has 0ubuntu4 [00:42] I love how the utter lack of the uploaded package in the PPA qualifies as a successful build. [00:45] jdstrand: i guess try rebuilding, if it fails again you'll have to manually upload to the PPA then do a WATCH_ONLY build. I'm off for dinner, may check back in later. [00:46] plars: still here? my gallery run didn't save the subunit file https://jenkins.qa.ubuntu.com/job/generic-click-autopilot-runner-mako/581/? [00:47] maybe the run command is generating only the xml, not the subunit. [00:54] robru: so, I tried the sync, but it gave me a new version that was lower than what is currently in the rtm, so I did just 'apparmor', then reconfigure then watch only. it failed cause ubuntu4 was in there, so I deleted it, prepared the ppa, reconfigured then watch only. it seems to all be working now [00:54] I forgot to mention I uploaded ubuntu5 to it somewhere along the way [01:23] jdstrand: right. One day ci train will be replaced with something that works. One day. [02:10] === trainguards: IMAGE 252 building (started: 20140923 02:10) === [02:21] robru: Any chance we can get rtm/landing-002 (UITK) into the next RTM build? [02:21] IIRC, that starts in about 40 minutes. [02:29] robru: I'm not sure how long that process takes. [02:29] elopio: hmm, the one I thought you were pointing at before was the one under generic-mediumtests-utopic [02:29] ToyKeeper: depends on the autopkgtests in the proposed migration [02:30] ToyKeeper: well you can just forget about that because ci train just decided to delete the silo. [02:32] elopio: so you would see them here for instance: https://jenkins.qa.ubuntu.com/job/generic-mediumtests-utopic/3702/? [02:32] elopio: what's the distinction between those two jobs? do you know offhand? [02:32] ToyKeeper: https://ci-train.ubuntu.com/job/ubuntu-landing-009-2-publish/19/console also the MPs aren't even approved. jeez [02:33] A wise old wizard once said, "Nothing is ever easy." [02:43] ToyKeeper: so I'm EOD, but get bzoltan1 to approve the merges, then get Mirv to publish in utopic, and then once that's done we can rebuild & retest & publish the RTM packages. [02:44] robru: Thanks. I'm just sending a summary to QA, since we were kinda planning on doing promotion testing on this image and that's not going to happen. [03:09] === trainguards: RTM IMAGE 56 building (started: 20140923 03:10) === [03:11] oh holy god [03:13] oh, it seems queuebot restarted, thankfully i dont see anything wrong with the spreadsheet [03:42] [03:44] robru: ToyKeeper: I hold back the approval to have a sencond run of the RTM silo002 tests. The first run was OK and I have shared th eresults with brendand-nexus5. Here you go with the latest results -> http://people.canonical.com/~bzoltan/ap-2014_09_22-RTM-SILO2-KRILLIN/ [03:44] Mirv: ^ [03:55] === trainguards: IMAGE 252 DONE (finished: 20140923 03:55) === [03:55] === changelog: http://people.canonical.com/~ogra/touch-image-stats/252.changes === [04:01] Mirv: robru: bregma: ToyKeeper: and here is the first half of the Ubuntu tests -> http://people.canonical.com/~bzoltan/ap-2014_09_22-UBUNTU-SILO9-MAKO/ For some reason the calculator tests hanged, so I had to restart in the morning. [04:03] ToyKeeper: brendand-nexus5: robru: Mirv: I see lots of hanging, crashing AP tests. The adb connection can get unstable and some of the tests just do not work. So i trust only the fully OK tests. I would suggest heavy manual and visual tests before releasing the new UITK. With more autopilot we can not get any further from this point. [04:06] :( I'm not looking forward to validating my qtbase patch release then [04:09] bzoltan1: any idea where the hangs/crashes originate? (i.e. autopilot, the tests, adb) [04:15] === trainguards: RTM IMAGE 56 DONE (finished: 20140923 04:15) === [04:15] === changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/56.changes === [04:24] bzoltan1: so, what's the situation with rtm 002? QA says it has signed it off, but you say it's not? and for some reason you've just kicked a no-change rebuild of it? [04:30] bzoltan1: reading the backlog further, it seems robru says ci train deleted the packages. ok then. robru btw: they could have been salvaged by going to Copy Packages and doing binary copy of the deleted packages to the PPA itself. [04:31] it's obviously the same version that QA signed off, but I'm unsure how to proceed now [04:31] veebers: yes, there ... tests, adb, autopilot. In short, no idea. [04:32] bzoltan1: heh ack [04:32] Mirv: I have not kicked off anything right now. I rebuilt both silos yesterday evening and run the AP tests overnight. [04:33] bzoltan1: oh, right, it was robru who kicked the rebuild [04:33] Mirv: From my point the RTM silo2 and the Ubuntu silo9 are good to go. If QA has signed them than it is a shared responsibility to release. [04:33] bzoltan1: anyhow, it was no-change rebuild that finished an hour ago [04:33] bzoltan1: I published silo9. robru just mentioned "we can rebuild & retest & publish the RTM packages". I think traditionally for no-change rebuilds smoke-testing has been enough, could you do that? [04:34] Mirv: What I mean is that the last two regressions (icon in gallery and messed header in dialer) were both _visual_ regression and not functional. So there are things we can not capture with 900+ tests. [04:34] bzoltan1: ah, right, now I get the context :) [04:35] Mirv: the rtm silo2 has been rebuilt and retested -> http://people.canonical.com/~bzoltan/ap-2014_09_22-RTM-SILO2-KRILLIN/ [04:36] bzoltan1: but it was rebuilt again 1h ago because train destroyed the packages. no changes though, but I was wondering if you could install them on your rtm device and just 5min smoketest. [04:36] (I assume robru needed to do a reconfigure and at that point train removed them) [04:37] Mirv: I know :) it sounds suspicious, but I just wish to be honest and open about the risks. [04:37] Mirv: bzoltan1 yes there's a bug in the train that makes it delete ppa packages during a reconfigure. I neutered that bit of code just now as it had bit me one too many times, so this issue shouldn't pop up again, but still i needed to rebuild the packages [04:37] Mirv: The RTM silo2 has exactly the same version as the Ubuntu silo9 and the version I have run 4 full round tests. [04:38] bzoltan1: yes but that package was deleted and rebuilt despite being the same version, so it's not really "the same" package [04:39] Mirv: didn't know you could copy deleted packages back into a PPA, thanks for that [04:39] robru: heh, thanks for the fix, it has bitten me too enough times [04:39] robru: do you want me to re-run the tests again? I have no problem with that. Only it would add 4-6 hours. [04:40] bzoltan1: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-002/+packages <- 58 minutes ago <- it's the same as built 10h ago <- but we have tradition that even after no-change rebuild the new packages are still installed on device and the device is at least rebooted [04:41] robru: in the past we've done just smoke-testing if the source hasn't changed but a packages has been rebuilt [04:41] Mirv: I go and do that right now. Plus I wil run few tests... the UITK and the browser for example [04:42] * bzoltan1 is flashing version 56 [04:43] bzoltan1: ok then [04:43] bzoltan1: sorry for the trouble, blame the train, but take consolation in the knowledge that this bug won't bite again ;-) [04:44] robru: this is absolutely no problem :) [04:45] robru: I am eating my morning oatmeal and drink my tea ... all the same what I do in the meantime :) [06:45] Mirv: congrats [06:48] Mirv: the rtm silo2 with the #56 boots and looks identical to the previous version. [06:49] rsalveti: thanks :) MOTU makes lifes a bit more easy [06:50] bzoltan: cool, publishing [06:50] yeah :-) [06:51] good morning :) can I get a silo assigned for line 75? [06:52] Mirv: thank you. [06:53] tvoss: landing-019 [06:53] Mirv, excellent,thank you [06:53] Mirv: how about the silo9 for Ubuntu? [06:54] Mirv: it is as good and as tested as the RTM. [06:55] bzoltan: already pubished when I woke up [07:05] Mirv: that is cool [07:10] bzoltan, some problems with the uitk landing? [07:10] brendand: not as I know [07:11] anyone updated their nexus 4 beyond ubuntu-touch/devel-proposed 251 this morning? [07:11] bzoltan, ok it's published. i read in the morning there were some issues [07:11] brendand: Mirv: I am not sure if we need to ping somebody on #ubuntu-release [07:19] bzoltan: beta freeze is in effect until Thursday [07:20] not sure if pinging would help [07:22] popey: latest image is dead here for me it seems [07:23] rsalveti: which one? [07:23] wonder if apparmor related [07:23] a bunch of packages got dropped as well [07:23] trying to flash 48 on krillin (utopic) [07:23] can't get out of the boot logo [07:26] Mirv: you mean that there is no chance to land the UITK on our trunk before Thursday? [07:29] bzoltan: well, feel free to try on the release channel. alternatively, it is possible to force merge&clean if you want to eg start preparing the next one. the uitk has landed anyway where it matters to us. [07:29] Mirv: for me the trunk matters the most [07:31] bzoltan: I meant rtm/14.09, so no reason not to clean [07:34] rsalveti, remove lightdm from the upstart stanza in the adbd job via recovery [07:35] ogra_: hm, why? [07:35] to debug why it hangs ? [07:35] how this got broken? [07:35] oh, indeed [07:35] o/ [07:35] testing my landing with 47 now, will retest 48 later [07:35] rsalveti, it broke with the last media-hub landing [07:35] but we can trigger 49 already, new kernel and new android [07:35] Damn, I hope I didn't catch a cold yesterday, brrr [07:36] how could, not even booting [07:36] http://people.canonical.com/~ogra/touch-image-stats/252.changes [07:36] this is the changes file [07:36] rsalveti, yeah, thats a bit weird, we know unity8 tests han hard with that package [07:36] oh [07:36] you are talking about utopic [07:36] * ogra_ was talking rtm :P [07:37] rsalveti, hmm, what was the customization hooks chnage ? [07:37] utopic because I need it for my landing :-) [07:37] Mirv: so it is possible to merge from the RTM silo2? [07:37] looks like one package that could intercept the boot [07:37] ogra_: I think related with apparmor [07:37] yes [07:38] precompiled profiles [07:38] surprised by the amount of dropped packages [07:38] and wonder why that [07:38] yeah, some deps seem to have been dropped [07:39] nothing should break the boot though [07:40] yeah [07:40] ogra_: I have question :) How can I tell from adb shell that the device is booted up to the welcome wizard? [07:41] sil2100: ogra_ new uitk now in rtm... image build? [07:41] bzoltan, should be checkable via initctl (if not via something like pgrep) [07:41] bzoltan: utopic can be m&c:d before it's in release pocket, if needed for next preparations [07:41] Mirv, sure, if sil2100 agrees ... trhough i wonder if we shouldnt roll back media-hub first [07:43] Mirv: thanks, now I understand it. Cool [07:45] ogra_: I have no idea what to look for with initctl [07:47] ogra_: let me take a look at that roll-back [07:59] hey there [08:00] is there a known issue with CI runs on merge requests failing with "I: Unlock failed" [08:00] rsalveti, would you mind top approving https://code.launchpad.net/~ogra/phablet-tools/phablet-tools-fix-edge-intro/+merge/235440 ? seems sergiusens forgot about it and i need to land it today [08:01] seb128, i know that mterry and plars discussed unlocking flakiness in unity8 a few times over the last week [08:01] ogra_, do you know if there is a bug recording the discussion? [08:01] *in unity8 unlocking (sorry) [08:01] not sure [08:04] seb128, bug 1370644 [08:04] bug 1370644 in unity8 (Ubuntu) "unity8-autopilot device unlock seems racy" [Undecided,New] https://launchpad.net/bugs/1370644 [08:04] ogra_, danke [08:04] :) [08:05] ogra_: I'll revert the 3 packages that landed for RTM [08:05] sil2100, +1 [08:05] sil2100, do we want to wait with an image build ? [08:08] ogra_: yeah, I guess it would be best [08:08] ogra_: I'll need your help with uploading dbus-cpp though [08:08] (since it's in main) [08:10] Feels like: -6'C... I can feel it [08:10] ...winter is coming? ;) [08:11] I wish :) [08:11] ogra_: can you fetch dbus-cpp from http://people.canonical.com/~lzemczak/packaging/ and upload to RTM? [08:11] ogra_: I'll upload the two others then [08:13] sil2100: was utopic mir 0.7.3 all fine, or do we want to wait for the next image build before publishing it to rtm? [08:13] (QA has signed it off now) [08:13] I think it was fine, but let's wait with the publishing for us to kick a new image [08:14] Just in case ;) [08:14] sounds good [08:14] I hope davmor2 is not back, since I don't have cats today either [08:14] sil2100, bah, i 'll need to re-pack it ... (teh direct upload will be rejected if the sseries isnt 14.09) [08:15] It's not 14.09? Damn, then the revert script still has issues [08:15] grrr [08:15] * sil2100 repacks the others too [08:15] Changes: [08:15] dbus-cpp (4.0.0+14.10.20140909~rtm.is.4.0.0+14.10.20140808-0ubuntu1) utopic; urgency=medium [08:17] * sil2100 fixes the script too [08:17] Anyway, uploading the rest now [08:19] ogra_: to make sure qtubuntu-media builds against the right media-hub, I'll have to wait for media-hub to build first in the archive [08:19] So it will take a moment I guess [08:20] sil2100, ok, then after the meeting [08:22] Mirv: you'd better have cats, that or we really need popey to have salem in the room [08:23] \o/ cats [08:26] Morning all [08:31] ogra_, davmor2, Mirv: be there in a minute [08:32] thanks popey for saving the day [08:34] * popey stabs chrome [08:34] also firefox [08:38] popey: stick with the webbrowser app :D [08:40] all browsers suck [08:40] [FACT] [08:49] popey: maybe you just use them wrong :P [08:49] mandel, tickle [08:49] not possible [08:50] popey: inconceivable, you mean surely :) [09:00] psivaa, hmm, looking at the console log of the 252 test ... do you actually have adbd runnin on the device after it failed ? [09:01] ogra_: let me check [09:01] (it seems like it can adb shell but no upstart user session is running ... that indicates that the adbd emergency shell started ... which it only does if lightdm crashes or the container doesnt come up) [09:02] can someone ( psivaa ?) tell me what the latest comment on this means? https://code.launchpad.net/~zeller-benjamin/reminders-app/sdkcompat/+merge/233743 - I tried re-running, same error. [09:02] ogra_, yes? [09:02] mandel, two things ... [09:02] mandel, i need top approval on https://code.launchpad.net/~ogra/phablet-tools/phablet-tools-fix-edge-intro/+merge/235440 [09:02] ok [09:02] mandel: hey! [09:02] mandel, and the other issue is that tvoss obvously ybroke media-hub when he ported it to dbus-ccp ... [09:03] mandel, and then went on holiday ... [09:03] mandel: right, can you help us fixing that? Do you know the dbus-cpp code-base well? [09:03] mandel, we look for someone who understands that stuff :) [09:03] la puta de oros (do not look for that in a dictionary) [09:03] ogra_, sil2100 on it! [09:03] * ogra_ hugs mandel [09:03] * sil2100 hugs mandel as well [09:04] sil2100, ogra_ can you let me know the issues/symptoms ? [09:04] one sec [09:04] we have a bug for that [09:04] ogra_: adbd is running with 252 [09:04] mandel: so, the media-hub that's in utopic seems to be broken now (due to the mentioned porting to dbus-cpp) and it's causing the unity8 autopilot tests to hang [09:04] https://bugs.launchpad.net/bugs/1371454 [09:04] Launchpad bug 1371454 in Media Hub "unity8.indicators.tests.test_indicators.IndicatorExistsTestCase.test_indicator_exists hangs on mako #245 #246" [Critical,New] [09:04] mandel: this is the main bug I guess ^ [09:05] sil2100, ogra_ ok, and do we know the MR that broke this? [09:05] mandel: let me find those, one moment [09:05] psivaa, can you log in and do: sudo lxc-info --name android [09:05] ogra_: btw. did we try only downgrading dbus-cpp to fix this bug? [09:06] psivaa, as well as: sudo initctl status lightdm [09:06] sil2100, i doubt that would work, since a bunch of hard dependencies were added [09:07] mandel: so, it got broken somewhere in these merges: [09:07] mandel: http://paste.ubuntu.com/8409382/ [09:08] ok [09:08] ogra_: since with the media-hub landing, there was also a dbus-cpp landing which didn't change the ABI or anything (was only some quick bugfix) [09:08] sil2100, ogra_ I'll investigate and will ping you with info [09:08] ogra_: maybe that one small change actually causes havoc? [09:08] mandel: you're our hero! [09:09] ogra_: 'lightdm stop/waiting' and http://pastebin.ubuntu.com/8409388/ [09:10] psivaa, thanks ! [09:10] so lightdm definitely crashes on start [09:10] (and the adb emergency shell works as expected, yay !) [09:12] popey: i'll take a look [09:12] popey: Also, could you please ping 'cihelp' for the queries like this in the future if there is no specific vanguard is available. [09:12] thanks [09:12] * ev hugs psivaa [09:12] :D [09:12] ok [09:21] sil2100, ogra_ did you see that downgrading gstreamer seems to fix the issue? [09:21] mandel, oh ? i thought it doesnt [09:21] ogra_, https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1371454/comments/13 [09:21] Launchpad bug 1371454 in Media Hub "unity8.indicators.tests.test_indicators.IndicatorExistsTestCase.test_indicator_exists hangs on mako #245 #246" [Critical,New] [09:21] mandel, hmm, right [09:21] Wait, it does? But we don't have the new gstreamer in RTM and it's reproducible there [09:22] Or do we? [09:22] my last knowledge was comment 12 [09:23] popey: for that MP, continuous-integration -> approved and it's the Autolanding that failed. This could be due to a review still being in 'needs fixing' fro mzanetti. that needs to be 'approved' before landing [09:23] sil2100, ogra_ is going back a number of revs.. I'll take a look at what has changed, maybe it will give us a clue [09:23] mandel, only two ubuntu versions though [09:23] psivaa: oh, interesting. thanks. [09:23] mzanetti: ^ [09:24] mandel, but if it is really gstreamer, probabaly involving Laney would make sense [09:24] ogra_, yes [09:24] popey: ? [09:24] popey: what branch [09:24] mzanetti: https://code.launchpad.net/~zeller-benjamin/reminders-app/sdkcompat/+merge/233743 [09:29] thanks mzanetti [09:30] ogra_: but how come it's reproducible on RTM if gstreamer hasn't been updated? [09:30] ogra_: I mean, I don't remember us updating gstreamer at all in RTM [09:30] sil2100, it has ... kgunn was going back two versions [09:30] you guys are still discussing gstreamer issues? [09:31] seb128, see bug 1371454 [09:31] bug 1371454 in Media Hub "unity8.indicators.tests.test_indicators.IndicatorExistsTestCase.test_indicator_exists hangs on mako #245 #246" [Critical,New] https://launchpad.net/bugs/1371454 === zbenjamin_ is now known as zbenjamin [09:37] sil2100, sorry, got distracted ... the new gstreamer landed around the day we did the initial rtm sync ... thats why you never saw an upload [09:46] ogra_, approved [09:46] * ogra_ hugs mandel again [09:47] damn ... i cant get an adb shell on 252 [09:47] * ogra_ wonders whats different with the smoke test devices [09:47] psivaa, that adb shell you did, was that on mako ? [09:47] oh [09:47] ogra_: yes [09:48] seems i'm just to impatient ... now the screen blanked [09:48] i guess it was just busy with apparmor and now respanwns lightdm til it fails [09:48] * ogra_ leans back and waits a bit more [09:50] ogra_, small question, I just updated my devices and they do not longer boot, have you guys seen that? [09:51] ogra_, it was via system image updates (not ubuntu-device-flash) [09:51] mandel, yes [09:51] investigating (see a few lines above) [09:51] ogra_, any pointers on how to fix it? [09:51] well, or trying to [09:51] while sivaa can get in via adb in the lab, i cant hre [09:52] mandel, ubuntu-device-flash ... and use the --revision option [09:52] to go back to 251 [09:53] ogra_, Device initctl: unable to determine sessions [09:53] mandel, thats fine, since there is no session running :) [09:54] why the heck does everyone else get in and i dont ! [09:56] ogra_, same as why I got the maps working ;) [09:56] golden hands ? [09:57] ogra_, no, we are just too good looking to have broken software [09:59] * ogra_ is stroking his fingers through his hair ... [09:59] hmm ... that might be true [09:59] :) [09:59] * sil2100 wonders why media-hub doesn't want to migrate [09:59] deps ? [10:00] All are pushed, both qtubuntu-media and media-hub are in -proposed as valid candidates [10:00] Maybe we just need a publisher run? [10:01] https://launchpad.net/ubuntu-rtm/+source/media-hub/+publishinghistory [10:01] it did [10:01] Although the update_output.txt does have something strange [10:01] where's proposed-migration for rtm, ooi? [10:01] sil2100, it migrated https://launchpad.net/ubuntu-rtm/+source/media-hub [10:01] Laney, http://people.canonical.com/~ubuntu-archive/proposed-migration/ubuntu-rtm/update_output.txt [10:01] oh, I see it [10:01] you can see "accepted: media-hub" there [10:01] that means it did go [10:03] sil2100: this is a problem https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1370064 [10:03] Launchpad bug 1370064 in unity8 (Ubuntu) "Empty dash when pressing Ubuntu button in launcher while in the overview" [High,Triaged] [10:06] * sil2100 sighs [10:06] davmor2: is that confirmed? [10:07] sil2100: yeap jibel me and brendand can all reproduce it both ways [10:07] sil2100: it also happens from all 3rd party, unfavourited scopes too [10:09] davmor2, i'm not sure it should be a blocker. it only happens in that view [10:09] davmor2, and it is recoverable. although it is a regression [10:09] brendand: no I didn't say blocker I said issue [10:09] sil2100: add it to user visible [10:10] sil2100: especially as it seems to be being, worked on already [10:12] sil2100, bug 1332538 is what breaks 252 [10:12] bug 1332538 in livecd-rootfs (Ubuntu) "No UID checks on rootfs updates" [High,Confirmed] https://launchpad.net/bugs/1332538 [10:12] * ogra_ tries a fresh flash of 252 to confirm ... [10:20] ah, wait, the lab uses freshly flashed images [10:20] so that might just be a coincidence [10:22] ogra_: 252 on a fresh flash here didn't even start the wizard [10:23] root@ubuntu-phablet:~# ls -l /var/lib/|grep lightdm [10:23] drwxr-x--- 6 111 lxc-dnsmasq 4096 Jun 6 14:12 lightdm [10:23] well, all lightdm owned bits are now owned by the non existing user with the UID 111 [10:25] ogra_: anyway, can you kick a new image for RTM? [10:25] :) [10:25] All should be migrated [10:25] davmor2: will do! [10:25] sil2100, oh, the roll-back too ? [10:27] ogra_: ofcourse I blame developer mode and that oliver bloke, he's always breaking the images for fun......oh wait that's you right ;) [10:27] :P [10:28] davmor2, can you get in anyhow ? [10:29] (flashing will still take ~30min for me) [10:30] ogra_: having a look give me 2 seconds [10:30] thx [10:31] davmor2, oh, and did you flash with --wipe ? (or --bootstrap) [10:32] ogra_: bootstrap [10:32] k, that should definitely get you a virgin system with the right UIDs [10:33] ogra_: bugger forgot to enable developer-mode reflashing back in about 10 minutes [10:33] ah, crap [10:34] ogra_: won't be a minute only need to flash the image is on my system [10:35] sil2100, Mirv: can silo 17 (utopic) be published? [10:36] ogra_: I blame Mirv's lack of cats jinxing the day ;) [10:36] haha, yeah [10:36] sil2100, image triggered [10:37] \o/ [10:37] oSoMoN: let me take a look [10:38] sil2100, so all roll backs are in ? [10:38] * ogra_ thought he'd need to dput dbus-cpp still [10:38] ogra_: oh, you didn't do that yet ;p? [10:38] no [10:38] I thought you did [10:39] Please push, it didn't require anything else, it just had some isolated bugfix [10:39] sil2100, hmm, k, did you re-pack already ? [10:39] sorry about that :( [10:42] sil2100, the dbus-cpp package still says "utopic" [10:45] === trainguards: RTM IMAGE 57 building (started: 20140923 10:45) === [10:48] ogra_: right I'm back with an adb-able system what do you want me to try? [10:48] Ah, I thought you would re-pack ;) Ok, let me do that [10:49] ogra_: uploaded to the same place [10:49] sil2100, thanks [10:50] davmor2, well, not sure, check syslog or so :) [10:55] ogra_: so is that #57 going to be alright regardless of dbus-cpp? [10:55] Mirv, no idea [10:56] hmm [10:58] sil2100, uploaded [10:58] i doubt it will make thhis image buuild though [11:00] ogra_: I see a bunch of issues http://paste.ubuntu.com/8409857/ [11:01] davmor2, i dont ... well, at least not the root cause [11:01] i see that lightdm restarts over and over [11:01] but tthats something we know already [11:03] ogra_: I guess it is linked to the issue as lightdm is never displayed. [11:03] sure [11:03] the prob is that we dont know why [11:04] ogra_: let me check my working rtm image against it and see what we cet from that [11:04] i see mtp-server crashing like crazy [11:05] and apport is collecting something new [11:05] ogra_: no crash report though [11:06] ogra_: there is nothing in /var/crash at least [11:06] right [11:06] i stopped it here [11:07] ogra_: does it matter that userdata is owned by root on rtm and system on utopic? [11:07] ogra_: thanks! [11:08] davmor2, it shouldnt [11:09] davmor2, is that on the same device ? [11:09] note that krillin is indeed different (using native partitions) [11:09] ogra_: no krillin for rtm, mako for utopic [11:10] right [11:12] what are the ffe/release rules for touch? [11:13] I'm asking because of https://launchpad.net/bugs/1352142 [11:13] Launchpad bug 1352142 in ubuntu-touch-meta (Ubuntu) "Doesn't load Japanese font on Ubuntu Touch" [Medium,In progress] [11:14] * ogra_ disables apparmor ... lets see [11:14] dholbach, we dont have ffe's [11:14] there's a standing exception [11:14] bug #1371635 [11:15] bug 1371635 in Ubuntu "[FFe] standing freeze exception in utopic for Ubuntu Touch-specific packages" [Undecided,Triaged] https://launchpad.net/bugs/1371635 [11:16] Laney, well, who cares... its a meta update anyway [11:16] in this case, but the general statement wasn't accurate [11:20] we dont have FFes in RTM i should have said :) [11:22] http://paste.ubuntu.com/8410032/ [11:22] hmpf [11:22] ogra_: http://paste.ubuntu.com/8410033/ [11:22] davmor2, yeah, i'm one step further already :) [11:23] ogra_: I'm just look through everything in /var/log currently. I'll keep pasting though then it gives you a confirmation on what you are seeing :) [11:24] uh, oh [11:24] new android ? [11:24] hmm [11:25] but a trivial change that shouldnt do any harm [11:25] ogra_: http://paste.ubuntu.com/8410071/ [11:25] right [11:26]