[01:35] anyone around to provide some silo love ?...so we can start building for mir. [01:36] maybe Mirv when you come on? ^ [02:10] === trainguard: IMAGE 62 building (started: 20140603 02:10) === [03:35] === trainguard: IMAGE 62 DONE (finished: 20140603 03:35) === [03:36] === changelog: http://people.canonical.com/~ogra/touch-image-stats/62.changes === [04:24] kgunn: assigned and kicked a build: https://ci-train.ubuntu.com/job/landing-008-1-build/83/console [04:41] ogra_: 61 and 62 still have dbus-x11 installed it seems, so they are still going to be broken. I guess from the suggests in dbus? That's the only rdepends I can find for it that we have installed [04:49] plars: I can see there's a new line for reverting the split greeter, I'm not sure if that's because this previous fix failed to work or if it's just in case it's needed [04:49] plars: Suggests: does not bring a package in, Recommends would [04:50] so, weird [04:56] oh, right, so it's in case the dbus split wouldn't be done [06:02] it does not seem that at least simply again installing dbus-x11 and removing /etc/X11/Xsession.d/75dbus_dbus-launch would make #62 show more than a black screen for me [06:04] it might be of course also because of my 5.3 experiments so I could need a fresh wipe [06:21] I'll assign a silo and kick a build of the revert anyhow, better to have it ready [06:36] Nice. Image 62 crashed four times after flashing, before I even turned the screen on to try it... and all the indicators are missing. [06:39] interestingly, now that I upgraded my #62 + dbus-x11 - 75dbus_dbus-launch to the Qt 5.3 PPA, everything seems working correctly including indicators [06:40] so maybe it was that my black screen was because of non-clean wipe (I've seen it before), but that restoring dbus-launch binary makes things work. or alternatively Qt 5.3 is simply that much better :) [06:40] note that the unity8 rebuild does have the split greeter etc anyhow, everything's up-to-date. [06:45] This was a fresh flash. Maybe it was a boot fluke, but it's not a good sign when the phone tries to melt itself on first boot. [06:46] It was getting hot enough that I worry it could cause damage... so I shut it off completely for now. [06:55] Er, and one of the crashed processes was /sbin/init ... which really worries me. [06:58] I seem to have /sbin/init .crash file from last Wednesday, so nothing totally new apparently [07:10] * sil2100 sighs [07:17] cihelp: can anyone help me figure out what happened to the packages in silo #009? https://ci-train.ubuntu.com/job/check-publication-migration/17381/console [07:17] "WARNING hud (14.04+14.04.20140528-0ubuntu1) is in no known space (and time). We didn't find it anywhere. It could have been rejected, or you run it too quickly and it's not published in proposed yet, or a network issue happened. If this persistent some time after the publication, you need to ping a landing team member to get more informations." [07:17] ogra_: ok, I understand from the e-mails that the current unity8 and such are causing indicators not appearing, but I wonder why some application tests still fail completely [07:18] pete-woods: I will try looking at this, wanted to do it yesterday already but there was too much chaos [07:18] pete-woods: since the package is in -proposed now when ai last checked [07:19] pete-woods: actually, wait, no [07:19] sil2100: that one was a failed SRU [07:19] pete-woods: ok, this needs some intervention [07:20] sil2100: just let me know if I need to change anything [07:22] sil2100: read the backlog from #ubuntu-touch if you didn't yet, regarding pete's landing [07:22] it was probably filtered out ie never copied to archives [07:22] Mirv: will do that and poke some archive admins for help here [07:23] sil2100: poking was also done, so if you combine the #ci-eng and #touch discussion you should have the whole picture I think [07:24] so probably you'll need to let didrocks know if you want that filter changed or something else, and then probably republish is needed [07:25] sil2100: http://irclogs.ubuntu.com/2014/06/02/%23ubuntu-ci-eng.html#t10:42 + aha we don't have #ubuntu-touch logs?? [07:26] + http://pastebin.ubuntu.com/7578497/ then [07:28] Mirv: thanks! I have this in my logs at least... but hm, why did it suddenly use the sru-staging PPA? [07:29] I didn't configure it to do so [07:29] I'll check the code and see what's going on [07:32] Mirv: so, I'll have to chat with didrocks again, since it seems to be the default behavior so it should have done the same the first time the SRU was published [07:33] Mirv: we don't have logs of that though since it was long ago [07:34] Mirv: so not sure why suddenly now it would get 'filtered out' [07:34] sil2100: ok, sounds good (to have a chat). I thought the abandoning of sru-staging was something you had agreed to last week or such. [07:35] so I didn't have much idea what should be the case [07:35] It was nothing that has been discussed with me around at least === iahmad is now known as iahmad|afk [07:51] sil2100, ugh ... that looked totally different last night, 61 was mostly green [07:53] ogra_: looking at 61 now it's similar though, makes me feel a bit uneasy [07:54] sil2100, yeah, dropping dbus-x11 didnt help at all it seems [07:54] sil2100, see the mail discussions though [07:55] sil2100, it seems we need 50% of dbus-x11 [07:55] Yeah, saw that discussion more or less [07:55] (dbus-launch, but not the Xsession.d part) [07:56] and pitti seems to have a good suggestion for a fix by dropping a config option [07:59] ogra_: right, I see that now - need to read up about that option though [07:59] ogra_: ah, so this way the dbus session won't launch even with dbus-x11 installed? [08:00] o/ [08:00] sil2100, can you kick https://launchpad.net/~ci-train-ppa-service/+archive/landing-019/+build/6064416 ? I hope for a flaky test - only failed on amd64 [08:01] sil2100, gdbus uses dbus-launch to fire up a dbus when it first tries to connect and finds one [08:02] sil2100, the first gdbus call seems to happen before the Xsession script is processed [08:02] this then starts another dbus-daemon [08:06] Saviq: sure [08:08] hmm, no answer from bfiller at all ... so we have to roll back i guess [08:08] :( [08:09] He'll be like in around 5 hours [08:09] Which is quite long... [08:10] It's really a shame though, such a big landing reverted [08:10] sil2100, well, pitti just proposed a fix for which we need to roll back the dep dropping and he needs to upload a fix to dbus ... [08:11] ogra_: remember on Friday when I was saying about getting ready for this big thing landing and you were like "it's nothing risky, it was in testing for months!" ;) ? [08:11] but we will have the same prob as yesterday [08:11] I've #62 working just fine with Qt 5.3, after installing dbus-x11 back in and removing the X related script :) [08:11] needs to be tested in the lab [08:11] Mirv, right [08:11] Mirv, and thats what we tested with plars yesterday [08:11] Right [08:12] i didnt think of the fact that dbus-launch could play any role by being called directly [08:12] which means we need exactly 50% of dbus-x11 [08:12] But what is the cause of all the current failures we have in smoketesting? [08:13] but pitti agrees its a dbus bug that the Xsession part gets processed at all [08:13] sil2100, that we completely dropped dbus-x11 [08:13] we need to keep half of it [08:13] ogra_: wasn't is mentioned that 'smoketesting is fine after dropping dbus-x11' on the ML? [08:13] or in other words, make the Xsession script a no-op if gdbus fired one up already [08:14] Ok, so it's like, everything has one cause [08:14] sil2100, yes, before i went to bed mako was all green (not all tests had run) [08:14] http://paste.ubuntu.com/7578684/ [08:14] thats the proposed fix ... i will test that in a minute and pitti will upload it [08:15] Let's wait for this to happen, the big revert silo might build itself in the meantime [08:15] but we still have to make a decision if we want to risk it or complketely roll back [08:15] So that we have a fallback in case of nothing helping [08:15] the prob is that we tested with dbus-launch installed ... where it worked fine ... my change dropped that alongside [08:15] * ogra_ gets his flo and fresh coffee ... [08:16] I would try risking it, really, as such a big revert is never 100% sure as well [08:16] then i'll test [08:16] sil2100, i agree [08:21] cihelp - can someone help me understand these jenkins failures? https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-mako/1027/console [08:23] pete-woods: so, I need to change something in our CI Train code to get this moving [08:23] pete-woods: will try to finish it up today, but there's a lot going on [08:23] sil2100: okay, thanks for the update :) [08:24] brendand: RO file system despite phablet-config writable-image, that's beyond my understanding, you want plars or doanac [08:25] brendand: is this a recent failure ? [08:26] sil2100, I forgot the channel of the train, can you telll it to me? [08:26] mandel: #ubuntu-ci-choo-choo ? :) [08:26] sil2100, thx! [08:27] sil2100, malta has drained my brain [08:27] vila, semi recent. a specific mr keeps failing for that reason [08:28] vila, since the end of last week i think [08:29] brendand: add fginther to your ping then since it's a s-jenkins job [08:29] brendand: they are all in US [08:29] vila, i'll take one more try and see if it happens again [08:30] sil2100: ogra_ landing meeting? [08:30] popey: yep [08:31] yeah, sorry, still in debug mode ... on my way [08:32] * ogra_ cant connect ... [08:34] sil2100, ogra_, train is happy with revert silo, what do we do? [08:34] Saviq, we have the landing meeting right now ... discussing that ... wanna join ? [08:34] Saviq: come over, let's have a chat [08:35] https://plus.google.com/hangouts/_/canonical.com/landing-meeting [09:16] cihelp - i have my vpn up but can't reach s-jenkins [09:17] brendand: interesting. Having a look now [09:17] brendand, ev: bfiller had a similar issue yesterday already [09:17] It seems after relogging 10 times it started working... [09:17] ev, some people mentioned similar yesterday [09:18] being able to reach it and being able to log in are different problems, no? [09:19] brendand: funny you mention that, I just had to fix my laptop and desktop configs following instructions from https://wiki.canonical.com/UbuntuEngineering/CI/VPN [09:19] brendand: I was using a config that didn't followed the updated instructions [09:20] vila, but i used this yesterday [09:20] vila, did it change in that time? [09:20] brendand: yeah, I used mine for months [09:20] vila, ok i'll check the config [09:21] brendand: I suspect that some pieces were left in place to let people update to the new (long term supported) bits so nobody realized they had to change the relevant bits [09:21] brendand: for NM based config I had to change to 10.99.244.1 for the ubuntu-ci DNS server (I was using an old IP) [09:22] brendand: for the openvpn based I had to stop using my hand-crafted scripts and switch to /etc/openvpn/update-resolv-conf for 'up' and 'down' [09:22] vila, so that seems to have done the trick [09:23] vila, but all i did was remove some whitespace for the up and down lines [09:23] vila, not even sure how the whitespace got there [09:23] bad copy and paste i guess [09:24] brendand: and you did 'service openvpn restart' ? [09:24] vila, no i just run openvpn from the command line [09:25] brendand: and you had a previous running but not giving you the right infos correct ? [09:25] vila, well yes [09:25] brendand: so may be it was relying on some old IP that got cleaned up recently [09:26] vila, perhaps [09:27] brendand: anyway, if it works now, I would keep that explanation in mind and ask retoaded for some confirming bits [09:56] thanks vila [09:57] ev: you didn't have any issues with your vpn I suspect ? [10:18] not at present [10:19] ev: right, so you probably had an up-to-date config already [10:33] pete-woods: ok, let's hope that now HUD goes forward [10:33] * sil2100 did some hacks to push it without a rebuild [10:35] pete-woods: yesss! hud re-appeared in the unapproved queue :) [10:36] sil2100: :D [11:49] * Mirv gone for a while, will check irc etc still today [12:02] Mirv: o/ === fginther` is now known as fginther === tedg is now known as ted [13:08] sil2100: was there not going to be another catch up? [13:08] popey: yeah, let's wait for the image first though [13:08] k [13:10] imgbot, stunt [13:10] * imgbot rolls on its back and purrs [13:10] :) [13:10] hah [13:11] publisher has both packages in proposed now ... [13:11] * pmcgowan waits for 62 [13:11] next publisher run is ours [13:11] then we can start a build [13:11] * sil2100 spams rmadison [13:12] popey, i guess we wont have the image before the evening meeting ... at least not much ... and we all worked together over the last few hours anyway [13:12] (in #ubuntu-devel mostly) [13:12] so i dont think we need another meeting right now [13:12] ok === mhr3__ is now known as mhr3 [13:30] * ogra_ is afk for a moment [13:34] * Mirv back [13:40] ogra_: it's in! [13:40] ogra_: or wait [13:40] hmmm [13:40] ogra_: ok, so actually rmadison says it's still in -propsoed, but citrain thinks otherwise [13:43] sil2100: citrain is too fast afaik [13:43] I thought that with the latest changes it should work similar to how rmadison works [13:43] it requires the usual 10-15min more so that rmadison agrees [13:44] ah, I don't know if it has changed recently [13:45] I remember it always being accurate since some time [13:45] But hm, dunno [13:47] Mirv, all set for that webkit landing? I just wanted to be sure it got properly tested [13:50] pmcgowan: oSoMoN is reviewing the webbrowser branch still (or maybe done now), I can start builds and testing as soon as traincon-0 is over. [13:51] Mirv, webbrowser-app branch reviewed and approved [13:52] oSoMoN: thanks! [13:52] Mirv, whats the webbrowser branch for? [13:54] === image triggered === [13:55] o/ [13:55] ogra_: thanks! [13:55] bot shoulld announce it soon [13:57] sil2100, reconf of 010 pls? [13:58] mhr3: done [13:59] ty [13:59] np [14:00] === trainguard: IMAGE 63 building (started: 20140603 14:00) === [14:01] there we go [14:01] with luck we should have the first smoke results when the meeting starts [14:03] pmcgowan: https://code.launchpad.net/~dbarth/webbrowser-app/webapp-container.remove-qtwebkit-support/+merge/221773 <- oSoMoN can probably elaborate (or dbarth). I'm not 100% sure if it'd be required, since we do continue to have qtwebkit (just a newer version). [14:03] Mirv, we need some sort of test plan to validate that webkit is still working properly independent of our not using it anymore [14:04] Mirv, we didnt include it originally for a reason, to do with bad dpr, not sure thats an issue or not [14:05] pmcgowan: I think the DPR got fixed, the only issue we had with 5.2 (as we were going to ship it originally) at the end was that WebGL sites didn't work properly with it [14:06] but yes, I added now a tab to create a test plan at https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AjuCdq68GSyVdFI4QzNQdWpfME5aMEV2VXo0cUpOMkE#gid=23 [14:08] Mirv, thanks [14:09] ogra_: as with every Tuesday, I might not be able to attend the meeting [14:09] ok [14:09] ogra_: but I will be back around 20 if anything [14:09] dbarth: can you check ^ url (it's editable). I'd mostly want at least one line for every theoretical webkit user, and status if it's something that is needed to be retested with 5.2 or has already switched to oxide [14:09] yeah, thats fine [14:09] * sil2100 is battling the bot [14:09] Mirv: yup [14:10] sil2100, since the AP tests wont be done anyway we should probably skip ... unless people feel an urge to talk [14:10] Mirv: there is an additional apparmor change required to do a transparent switch though [14:10] i assume we'll be somewhere in the middle [14:10] trying to set that up properly [14:13] thanks, it's starting to look good. I wasn't sure if OA switched, but indeed it did. [14:47] Mirv, can you look at https://bugs.launchpad.net/qt/+bug/1318584, I cannot seem to assign it to you [14:47] Ubuntu bug 1318584 in Next Generation Checkbox (GUI) "checkbox-gui crashed when switching video out mode to external only mode" [Medium,Confirmed] [14:56] sil2100, could you click the rebuild button on https://launchpad.net/~ci-train-ppa-service/+archive/landing-010/+build/6065421 pls? [14:56] i was too quick to build it, the ppc -api pkg wasn't published yet [14:57] Mirv, or you ^? [14:57] mhr3: after my meeting [15:00] mhr3: click [15:01] thx === retoaded changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp - sprinting this week, slow to respond | CI Train support - US: robru, rsalveti - EU: sil2100, Mirv | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Known issues: TRAINCON-0; QA Lab VPN connection issues [15:07] kgunn, Saviq: how do I initiate a new silo request? Ask here? [15:07] mterry, added to the spreadsheet? [15:07] Saviq, no not yet, I'm new to "adding new silos to spreadsheet" -- wasn't sure of order of operations [15:07] mterry, so just add your data at the end of https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dFVHQ3FuMDJGLUZCamJfSjYzbWh3Wnc#gid=0 [15:16] mterry, now you want to set the "Ready" column to Yes [15:16] mterry, and start begging sil2100 to get us the last silo available ;) [15:16] Saviq, well... I'll have to poke tiagosh about getting the checklist right for his MP [15:16] If I'm going by book [15:17] mterry, we'll probably have to wait until image 63 results are in, so there's time [15:17] ;p [15:17] I like the description! [15:18] sil2100, see! [15:19] Saviq, mterry: assigned! Silo 020 for you [15:19] sil2100, we'll be quick, promise [15:19] heh, that's a bit confusing but makes sense since it was just cleared by us [15:19] indeed ;) [15:19] Saviq, tiagosh is going to add a checklist to his merge [15:20] mterry, sure, we can build in the mean time [15:20] mterry, as that doesn't affect the process [15:20] Saviq, yup, just saying [15:20] kk [15:20] mterry, you pushing the button on this? [15:21] Saviq, the build button? I guess the fact that landing-020 sheet has content means its configured with those 3 branches already? [15:23] mterry, when sil2100 says it's ready, that's when it's ready ;) [15:23] hm, should be safe to do operations [15:23] But the spreadsheet is behaving strangely [15:24] Could anyone of you press the build button? [15:25] === trainguard: IMAGE 63 DONE (finished: 20140603 15:25) === [15:25] o/ [15:26] === changelog: http://people.canonical.com/~ogra/touch-image-stats/63.changes === [15:26] yippie ! [15:26] Image testing begiiin! [15:26] \o\ /o/ [15:26] now the anxious waiting til the smoke infra picks it up [15:29] updated to #63 and i have no wifi ☹ [15:30] Reboot [15:30] Oh [15:30] On the other hand [15:30] bah [15:30] just did [15:31] My landing might have kicked us in the balls [15:31] * ogra_ watches the update animation idly [15:31] popey: still no internet? [15:31] works after reboot [15:32] Ah, phew [15:32] Still, let's see if ogra_ will have the same [15:32] wlan oon flo is fine here [15:32] right after upgrade ... no extra reboot [15:33] mtp also behaves [15:33] Indicators present? [15:33] yep [15:33] yes [15:33] all like it should here [15:34] Ossum [15:35] hmm, going back after adding a U1 account is weird [15:35] you see system settings for s split second ... then it slides away and shows you systme settings [15:37] on first sight it looks all fine [15:37] so lets hope the AP tests confirm that [15:52] popey, do you feel the need to have a landing meeting now ? would be only us two and i think we know what we wait for now to drop traincon-0 [15:52] i do not [15:53] great, then lets skip [15:53] and just watch smoke tests to chug along [15:53] mediaplayer had no failures ! [15:53] that hasnt happened in a while === retoaded changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp - sprinting this week, slow to respond | CI Train support - US: robru, rsalveti - EU: sil2100, Mirv | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Known issues: TRAINCON-0 [16:04] ogra_, 63 looks better then [16:04] nice job cross fingers [16:04] pmcgowan, from a user POV it looks ok [16:04] hah [16:04] implying not from an engineers I suppose [16:04] cant say much about the AP tests yet [16:04] sil2100: no landing meeting? [16:05] plars, we decided to skip ... all we wait for is anyway that the AP tests finish [16:05] plars, to drop TRAINCON-0 [16:06] (i didnt know you are back today) [16:06] ah [16:06] ogra_: I am [16:06] ok [16:06] ogra_: fyi, I'm gone all next week though [16:06] well, we hpefull have all fixes proper now [16:06] so waiting for #63 to finish testing [16:07] if that looks okayish we'll drop TRAINCON-0 [16:07] plars, why does mako look so much different while the tests are running ... i.e. the tablets both list all tests, mako seems to be missing 1/3 [16:08] ogra_: so I didn't really look into or understand the fix for this yesterday, but I do see that dbus-x11 is still installed. is that expected? [16:08] it isnt installed [16:08] ogra_: could be part haven't started yet, I'll take a look [16:08] ogra_: it is installed, I'm looking at it right now on 63 [16:08] http://people.canonical.com/~ogra/touch-image-stats/61.changes [16:08] root@ubuntu-phablet:~# apt-cache policy dbus-x11 [16:08] dbus-x11: [16:08] Installed: 1.6.18-0ubuntu6 [16:09] i definitely dont have it on a fresh flash on 63 [16:09] that's running in the lab right now [16:09] ugh [16:09] so something is bringing it in then [16:09] thats evil [16:09] ogra_: that's what I was trying to say last night [16:09] yeah, my #63 has it [16:09] So I don't expect 63 to look any more green [16:10] root@ubuntu-phablet:~# dpkg -l |grep dbus-x11 [16:10] root@ubuntu-phablet:~# [16:10] root@ubuntu-phablet:~# system-image-cli -i|grep "version version" [16:10] version version: 63 [16:10] how can you have it ... i dont get that [16:10] popey, ? [16:11] did you install any AP tests ? [16:11] nope [16:11] oh hang on [16:11] it's possibly I'm an idiot [16:11] Installed: (none) [16:11] PHEW ! [16:11] sorry ☻ [16:11] ah, found it [16:11] carry on taking the pills [16:11] messaging-app-autopilot brought it in [16:12] plars, well, if that got pulled in by any AP this is super evil [16:12] it will cause all sorts of dbus flakyness [16:12] i hipe the autoremove at least purges it after testing ? [16:12] ogra_: http://paste.ubuntu.com/7581296/ [16:12] there is a fixed dbus-x11 too, that shouldnt spawn any dbuses anymore [16:13] oh [16:13] ofono-phonesim [16:13] will find out, that's the one its on now [16:13] i think ofono-phonesim-autostart depends on it for whatever reason [16:14] if we get dbus-x11 1.6.18-0ubuntu8 in that shouldnt be an issue anymore though [16:14] but i see you are on ubuntu6 in the lab [16:14] so lets cross fingers [16:15] anyway, the trigger that made it start random dbus-daemons is gone so it shouldnt break [16:15] we re-ordered the greeter session startup so that you have a dbus before anything wants to talk to it [16:15] ogra_: well, we don't apt-get update [16:16] which hopefully makes dbus-x11 less harmful [16:16] i dont think ubunt8 has migrated yet anyway [16:16] likely still in proposed ... it has a gazillion of deps for which it runs all tests [16:17] https://launchpad.net/ubuntu/utopic/+source/dbus/1.6.18-0ubuntu8 [16:17] hah [16:17] Published 13 minutes ago [16:17] bad timing [16:18] ogra_: autoremove didn't take it out :( [16:18] crap [16:18] i wonder fi thats not responsible for flaky tests we saw in the past then [16:18] ogra_: quite possibly [16:18] well, messaging-app at least passed fine [16:26] ARGH! [16:26] dialer-app failed all tests [16:27] :(((( [16:28] ogra_, also, no indicators on #62 [16:28] robru, 62 is dead and buried [16:28] it was horribly broken [16:29] ogra_, is there a new one? I just flashed and got 62... [16:29] root@ubuntu-phablet:~# system-image-cli -i|grep "version version" [16:29] version version: 63 [16:29] ogra_, [16:30] ogra_, ha! [16:30] robru, 63 is fine from locally running tests and from a few mins usage testing [16:30] but it seems dbus-x11 is still causing issues in the lab [16:33] sigh calendar is also failing [16:33] mterry, ^^^ [16:33] http://ci.ubuntu.com/smokeng/utopic/touch/mako/63:20140603.1:20140530/8381/ [16:34] plars, for a test, can you re-run any of the failing ones after manually purging dbus-x11 again ? [16:34] we definitely had them pass in local tests [16:38] ogra_, so what happened in 63? did that have the greeter revert? [16:38] nope [16:38] that would have been a gigantic revert [16:38] we didnt want to do that [16:38] we fixed it instead [16:38] ogra_, yeah, i don't want that either ;-) [16:38] great [16:38] apparently not enough though [16:38] ah [16:39] looking at the currently running AP tests [16:39] but thats seemingly caused by a leftover dbus-x11 package that should not be on the device at all [16:40] ogra_: sure, of course. I could do it locally right now, or I could do it in the lab after the runs are done [16:40] plars, in the lab please, i want to be sure you use the same env and setup [16:41] plars, we need to find a way to purge dbus-x11 though ... i dont get why teardown doesnt pull it out [16:42] ogra_: 'sudo apt-get autoremove --purge -y messaging-app-autopilot' was what got run, I suppose maybe because it didn't follow the dep chain far enough down [16:43] well, autoremove should actually follow the chain [16:53] plars, could we somehow ass dbus-x11 as a permanent entry to the teardown packageset ? [16:54] *add [16:54] :) [16:54] heh [16:54] probably, let me take a look - it would be a temporary hack I guess right? [16:54] ogra_: is it even worth it though? from what you said, in the version of dbus-x11 we pull in next it shouldn't have this problem [16:54] well, we definitely dont want that package ever installed ... except for ofono-phonesim tests ... [16:55] well, the new version will only make sure that the Xsession script wont run if there is already a dbus running [16:56] but if you have any code that calls gdbus this will spawn a session dbus via the dbus-launch binary which dbus-x11 ships [16:56]