=== salem_ is now known as _salem [03:18] Good morning [06:56] good morning [07:01] bonjour jibel [07:01] bonjour pitti [10:02] gema: any way i can see whats going on with mako? [10:02] the logs dont show a bootlog etc. [10:14] asac: what is going on with what? smoke testing? [10:14] gema: yeah. wonder if there is a way i can see more details [10:14] guess i need VPN for that? [10:15] https://jenkins.qa.ubuntu.com/job/raring-touch-mako-smoke-default/56/console [10:15] this is the console of that job [10:15] right [10:15] problems with resolving ports [10:15] asac: if the job finished, anything that is inside is also outside [10:15] having a look, gimme a sec [10:15] so i would see the bootlog of the device there if it would get to that? [10:15] cool [10:15] i think its a network issue [10:16] asac: it is [10:16] i dont think i see the device booting [10:16] even though we push to it in adb [10:16] using adb [10:17] those network issues are on the device? or is that on a server? [10:17] on the device [10:18] ok... so we dont have a bootlog? [10:18] it's when it tries to install ssh that I see the first problem [10:18] after that it's all happening on the device if I am reading the log correctly [10:18] is phoenix the name of the device? [10:19] no, phoenix is the server to which all the phones are connnected [10:19] uhmm, maybe it's on the server [10:19] I will talk to paul whenever he's online and we'll look at this together so that I can learn about it [10:21] asac: I am going to try today's build on my mako [10:22] asac: I will let you know if I see any problem [10:24] it needs some battery first, it went dry over the weekend [10:24] it'll take me 20 mins or so [10:24] yeah. sowhat i really want is to get the boot log of the device in there [10:25] ttyl [10:25] have problems with machine here [10:25] asac: np, my first priority now is to verify if today's image is good [10:25] will work with paul on fixing that job later [11:20] asac: image from May 26th works fine on mako, network works fine also [11:48] when running autopilot launch gnome-screenshot it automatically takes a whole screen shot and asks if you want to save. Is this a bug or is this the intended behaviour?..... actually even running 'gnome-screenshot' in terminal does the same. === _salem is now known as salem_ === mzanetti is now known as mzanetti|lunch === mzanetti|lunch is now known as mzanetti === francisco is now known as Guest51059 [14:09] hi is there anyone [14:09] ? [14:10] hi Skini151 [14:10] i have a question [14:11] I found a little bug during testcase on VM and don't know how exactly to report it [14:11] what testcase are you following? [14:11] ubuntu saucy daily amd64 (install entire disk) [14:14] the bug is: mouse cursor disappaered after reboot [14:14] http://iso.qa.ubuntu.com/qatracker/testcases/1300/info this testcase? [14:15] yeah [14:15] At the bottom of that test is the link to file a bug :) [14:15] i still can click but cursor is invisible [14:16] oh ok [14:16] thanks [14:17] i think you need to submit a failed result aswell [14:23] "file a bug" link get me to home directory of testing tracker [14:29] nope all ok now [14:31] cursor is Xorg stuff? [14:34] Skini151, im not familiar with packages if you ask in #ubuntu-bugs im sure they can help :D [14:34] ok [14:34] thanks [14:47] hello everyone [14:48] balloons, hello, how are you? [14:48] DanChapman, good.. I'm almost finished going through the backlog of things :-) Long weekend in the US here, and it was nice to be off the pc for a day :-p [14:50] ballons, Yeah we had a long weekend here aswell. :D I have been keeping etherpad updated with status of porting autopilot, and have been fleshing out an email to send to the mailing list for everyone to see where its at. [14:52] balloons, do you still use the trello board or is that no more? [14:52] DanChapman, hmm.. We should chat about that [14:53] balloons, did you already get to my tut-tut message about invalid html? :) [14:53] we had used it last cycle, but I wonder if people would rather use something else [14:53] just using bugs has worked well for us on the manual test project [14:53] knome, I saw that :-) Leave it to me to produce more bad html.. thanks for noticing! [14:53] np [14:53] do you need help with getting it right? [14:53] (i could do a push with a few testcases formatted correctly if you want) [14:54] What alternatives are there? I think its needed as LP can be hard to follow where/what everyone is doing [14:54] Umm, we can clean up the existing stuff by script I hope, then update the tidy script and format wiki page to point out not to do it ;-) [14:54] oki! [14:54] knome, I certainly would not refuse a merge request fixing it.. That would be nice if you can do it [14:55] i'll look if i get to do that [14:55] DanChapman, alternatives.. hmm, well, that's how we ended up there to begin with [14:55] not today, i have already had too much adults' juice :P [14:55] it's been used all cycle, we simply used the pad for the hackfest [14:55] knome, :-p [14:56] So using bugs would it be that you assign it to yourself rather than leave a comment saying 'I'm doing this' [14:56] DanChapman, yes [14:57] cool I can work with that :D [14:57] It's worth bringing up with the list and then updating our project to reflect it [15:01] balloons when i run autopilot launch gnome-screenshot it instantly takes a screenshot of the whole screen and goes straight to the save dialog window. I wasnt sure if this is a bug or intended behaviour. I get the same running just gnome-screenshot in terminal [15:02] DanChapman, wild.. heh, I seem to remember getting a dialog before [15:02] but it happens to me too. Check the manual testcase for it; it probably contains the old behavior and needs to be updated too [15:04] Yeah launching it from dash though brings up a dialog to select grab whole screen or grab window or grab area. Thats what i found weird. Will go check the man-test now [15:05] DanChapman, I tried from the dash and it took a screenshot automatically too [15:05] I'm on saucy tho [15:05] ah ok, i'll look into it :D === cjohnston_ is now known as cjohnston [16:13] balloons: when you've got 5 minutes - that'd be cool :) [16:31] elfy, shoot [16:33] I'm just diving into the code reviews :-) [16:34] balloons: it's a simple one - I did some testcases - BUT should I be doing something like bzr push lp:~elfy/ubuntu-manual-tests/foo/testcase1 and then bzr push lp:~elfy/ubuntu-manual-tests/foo/testcase2 [16:34] or what I've been doing bzr push lp:~elfy/ubuntu-manual-tests/testcase1 bzr push lp:~elfy/ubuntu-manual-tests/testcase2 [16:34] or does it not matter at all :) [16:35] and have I even been doing the whole thing right in the first place :p [16:38] elfy, heh.. let's take a look [16:39] so I'm not seeing what your saying above in the branches you linked [16:39] they aren't real :p [16:39] ~elfy/ubuntu-manual-tests/Mousepad looks good [16:39] basically submitting a merge proposal for each testcase [16:39] right - so I can carry on like that - elfy/ubuntu-manual-tests/testcase [16:39] yes, that should be just fine [16:40] k - thanks [16:40] basically people don't want lots of extras in the merge request in general.. but if things should be lumped together do it [16:40] for instance, we try and avoid things like updating 20 testcases at once, but it has been done. When that happened we did it as one merge request [16:40] ok - don't understand what you mean by that [16:41] well these ones are all completely new [16:41] most of the time your updating/editing one testcase [16:41] so having only those changes in the merge proposal works nicely [16:42] are you saying that now I've done these ones - if things need to be changed I would be notified because I wrote the original? [16:42] no, I think I've confused you [16:42] yep :) [16:42] :-) Let's just say what your doing is perfect [16:42] keep doing it [16:42] ok lol [16:44] got to say trying to get to grips with bzr was not very easy and as I suspected trying to follow a video didn't work too well for me :) [16:45] elfy, looks like your up and running though. Is there anything that would make it easier? [16:45] not now :) [16:45] you still have fresh perspective ;-) [16:45] I mean easier for others to learn it [16:46] I will put together a 'wiki' section perhaps [16:46] manana :p [16:46] so did this page help? https://wiki.ubuntu.com/QATeam/ContributingTestcases/Launchpad [16:47] my crib sheet has 9 lines - from bzr add to propose for merging [16:47] only as far as getting bzr to work - I will expand https://wiki.ubuntu.com/QATeam/ContributingTestcases/Manual#Contribute_your_new_test.21 [16:47] elfy, hmm.. so it sounds like the issue wasn't so much setting things up, as on that wiki page, but actually doing the work to commit, push and stage for review [16:48] yep - danchapman was great :) [16:49] elfy, I would appreciate any additions to the page.. I wrote the original pages, but I already was familiar with bzr and in general, version control [16:49] yeah, I always forget how to do it too, I just go to http://developer.ubuntu.com/packaging/html/fixing-a-bug.html#committing-the-fix [16:49] so adding detail where you got stuck should help others [16:49] balloons: there is nothing on that contribute page to tell you you need to add and commit for instance [16:49] and without that it was all failing here :) [16:50] but it's on my pad to do that for the wiki [16:50] thanks! Yes, little assumptions like that sneak into things [16:50] * balloons waves @ chilicuil [16:50] I tried to follow the video and it sort of worked a bit - but with a cat and a kid in the house ... ;) [16:50] n_n/ [16:51] chilicuil: ta - I'll look at that page - if the synatx etc is already writtent then I'll just make sure the qa page makes sense in one place [16:52] today you won't get my bug reporting storm balloons, I left my computer downloading lubuntu, which is the only one I've still not seen =P [16:52] chilicuil, :-) amazing work, really [16:52] * elfy is working through the xubuntu testcases slowly [16:53] elfy: yeah, I'll at the qa wiki too, so we all see the same cheatsheet =) [16:55] elfy, since I'm reading it, I'm typing something onto that page to expand it.. Don't let that stop you from editing though :-) [16:59] it won't be today anyway - just got in from work - dinner to sort out :) [17:01] this is handy; I [17:01] http://doc.bazaar.canonical.com/bzr.1.0/en/quick-reference/quick-start-summary.svg [17:05] balloons: possibly - but to be honest if you've never used bzr - it's just a not very pretty picture with words on it :) [17:07] elfy, :-) [17:07] I'm linking here also: http://doc.bazaar.canonical.com/latest/en/mini-tutorial/ [17:07] afternoon elfy :D [17:07] the chat is meant for once you've learned everything [17:08] :) [17:08] hi DanChapman :) [17:08] elfy, can you do one thing quickly before you go? [17:08] yep [17:08] So, I'm looking at your merge for https://code.launchpad.net/~elfy/ubuntu-manual-tests/Mousepad/+merge/165798.. but you've got xchat in that branch also [17:08] do you see it? [17:09] I assume since you have an xchat merge proposal that's the version you want reviewed and merged ;-0 [17:09] yea - I saw that yesterday - again - maent nothing to me [17:09] confusing [17:10] ok, so we'll leave the confusion for now.. dinner is soon :-) [17:10] but yea - there are 3 of them that I've done [17:10] however, I will drop xchat from that merge then [17:10] hardly - not got into the kitchen yet lol [17:10] ok - there is one for it [17:18] balloons, what are the plans for autopilot tests are they purely just for running on jenkins or is it planned for them to be used elsewhere aswell? [17:19] elfy, ok new version of https://wiki.ubuntu.com/QATeam/ContributingTestcases/Manual is up [17:19] DanChapman, it's intended for them to be run on jenkins everyday [17:19] however, in the past we did manually run then as part of cadence weeks [17:20] ok, so with tests like for shotwell, connecting a camera isnt really going to be possible? [17:21] DanChapman, a-hah! But it will be possible thanks to pitti.. and Carla who wrote the test proving it out [17:21] pitti, has a cool tool called umockdev that lets use mock real hardware and do things to it [17:22] I already tried that with umockdev, and shotwell was happily importing :) [17:22] DanChapman, https://github.com/martinpitt/umockdev [17:22] Oooooo. that sounds cool :D [17:22] indeed :-) so don't let needing a device stop you from writing a test [17:23] elfy, basically this is the section that I updated in light of your comments: https://wiki.ubuntu.com/QATeam/ContributingTestcases/Manual#Using_Bzr [17:25] that looks better - though I get an error with the status one bzr: ERROR: Not a branch: "/home/hob/" [17:25] which logically makes sense as there isn't :) [17:25] elfy, excellent .. should we mention you need to run bzr commands inside the directory? [17:25] the directory that contains the repository that is [17:26] I'd say so [17:26] k, adding it ;-) [17:27] makes senses to me now in the right place - terminal echoes nothing at all - which is as it should be [17:29] balloons: if you need a guinea pig to check through new things - I'm your man :p [17:29] ok, modified a bit more [17:29] elfy, it's really helpful to have, so yes, thank you [17:31] balloons: bzr add /path/to/testcase if you're in the right path already do you need to do that? because I didn't lol [17:31] elfy, the path is relative [17:31] balloons: that all looks much better, actually what you need to do [17:31] so if you're there already bzr add works [17:32] yes.. you can use absolute or relative path name [17:32] so if your in the directory.. hehe bzr add testcase works [17:32] if I'd have had that on saturday then I'd have been ok and so would DanChapman :p [17:33] elfy, good.. one more thing for you. [17:33] best be quick I could eat a scabby dog ;) [17:33] do we need to explain version control anymore, or can we leave that to the links on bzr? [17:34] meaning, can I say, here's how to commit you work without talking about what a commit is? [17:34] I've not even looked at that - so I couldn't really comment [17:34] unless I have and didn't know that's what I was doing [17:34] ok, well if it makes sense to you now and looks good let's leave it. Thanks for your help [17:35] and enjoy dinner! [17:35] where is the information relating to version control? [17:35] beacuse I will look at it in a while [17:36] random question: do you use supper at all? or perhaps you supper what would be lunch? [17:36] as a word? [17:36] elfy, well I mean in general the idea of having files versioned and being able to manage them.. [17:37] I mean something like: http://en.wikipedia.org/wiki/Revision_control [17:37] elfy, yes as a word [17:37] supper is a late evening meal - or in my case the bit's I eat to fill in the gaps :p [17:37] lol.. random though popped in [17:37] just thought I would see if it's use differed across the pond or not [17:38] sounds like a little bit. I would use supper and dinner interchangeably and supper wouldn't have any special meaning or context [17:38] back to your merge now :-) [17:38] yes - if version control is not specifically mentioned you need to talk about version control - especially because peppered everywhere are 'you don't need to be a coder to help' comments - thosepeople like me will need to know the things that other people who might be used to working with bzr would know [17:39] biab [17:40] balloons: lunch is lunch, breakfast is breakfast even if I've not eaten till 3pm :) lunch would be after breakfast as would tea/dinner and supper [18:37] balloons: " add a close step and check to make sure it doesn't prompt this time" prompt for what? to save settings and the like? [18:37] and I'm back so now would be a good time to talk about version control perhaps [18:37] prompt on close.. your previous step unchecked that box [18:37] I found this: http://chronicle.com/blogs/profhacker/a-gentle-introduction-to-version-control/23064 [18:38] it was the closest thing to version control for non-technical people.. even the stuff on version control mean to introduce it would be over people's head I'd imagine [18:39] I'm with it enough to work with version control - I did a lot of iso9001 work back in the day - which is a quality control system [18:40] balloons: aaah - got what you mean about the xchat thing now [18:41] elfy, yea, you don't have to learn everything about bzr or version control.. just enough to be able to contribute, so perhaps it's enough [18:42] balloons: ok - so I've changed it here - now what do I do as far as bzr is concerned? [18:43] bzr add and commit and then push it? [18:44] and how do I make it work with bzr and version control ? [18:45] hello Letozaf [18:46] elfy, ok so you made a change to your local repository to fix the issue [18:46] hello balloons [18:46] once the change is committed, simply use the bzr push command to send it to the remote repository on launchpad so it's all synced up [18:46] if your wondering how to change and committ locally I can help with that too [18:47] do the bzr add step or just bzr commit before I push it [18:47] if you didn't make a new file, you don't need to use bzr add [18:47] k - so commit and push [18:47] if your confused, bzr status helps out :-) [18:47] yep - got a modified and unknown [18:47] which is logical [18:48] bzrso I'm going to bzr commit xchat - that right? [18:48] balloons: even ... ^^ [18:49] amd then I bzr push bzr push lp:~elfy/ubuntu-manual-tests/xchat [18:50] elfy, let's fix one thing at a time ;-) [18:50] :p [18:50] ok, so for the xchat content change, you all committed and pushed? [18:51] no [18:51] ok, so let's do that [18:51] cos I'm not sure I'm doing the right thing :) [18:51] so what does bzr status say/ [18:51] modified - xchat , unknown - thunar [18:52] ok, so if you commit at this point the only changes that will be committed are to xchat [18:52] k [18:52] bzr diff will show you the exact changes [18:53] not as pretty as in launchpad, but they will be there [18:53] a + in front of a line means it was added.. a - means it was removed on the diff print [18:53] before commit? because I've got the nano window open after commit now :) [18:53] right, that + and - makes sense and I'd get that [18:53] you can cancel a commit by just exiting without leaving a message [18:53] if you wish [18:54] but you don't need to [18:54] and yes bzr diff only shows the pending changes [18:54] once committed, it will be blank [18:54] yep - diff makes sense to me [18:55] ok, so once that's done you can push it to lp and your merge proposal will have the new changes :-_) [18:55] right - so I can see what I have changed, commiting now - what to put in the nano window - changed after comment or something ? or something specific [18:55] you can't go wrong on a commit message [18:55] just say what you did, very briefly [18:56] add check for 'quit verification' window [18:56] k done that - pushing now [18:57] k - pushed to revision 111 [18:58] ok great [18:59] now if your ready, let's talk about why everything is showing up inside all of your branches [18:59] Letozaf, how's things for you today? have a nice weekend? [18:59] spy anymore salamanders? :-) [18:59] balloons: 2 secs and yea that would be good :p [19:00] DanChapman, Letozaf gonna start on the autopilot reviews now [19:00] Letozaf, I'll try yours now since your here :-) [19:01] so I'm looking at gedit: https://code.launchpad.net/~carla-sella/ubuntu-autopilot-tests/gedit-a1.3/+merge/165936 [19:02] balloons, ok fine [19:03] balloons: when you're ready [19:05] Letozaf, cool, it runs :-) I did get the MismatchError: None == None error.. I wonder if I need to pull down a newer autopilot version [19:07] balloons, I do not know why but that INS label is not being seen it's like it's not there, I tried "INS" " INS" " INS" but nothing :( [19:07] Letozaf, :-( Did you try using the "in" command [19:07] it searches the string.. so "INS" in result [19:08] Ok balloons :D [19:08] balloons, never used it, I must check how it's used the "in" command I mean [19:09] DanChapman, hey [19:09] Hey Letozaf :) [19:10] so elfy, and perhaps DanChapman can fill in here to, the issue with your merge proposals is that the branch your proposing for merging contains work other than your intended testcase [19:11] what I'm trying to say is you appear to be working out of the same directory for all the testcases your adding [19:11] yep [19:11] so what's happening is you push a branch up, then do some more work, and push another branch up, et, etc [19:11] balloons: can you answer someone's question in -bugs? I think it's an ISO test case bug thing... you might be more qualified to answer than bugsquad/bugcontrol [19:12] but your branch has changed from the target branch, that is trunk, in more than one way [19:12] right - so each branch should have only the one thing in it? [19:12] balloons: thanks :) [19:12] * TheLordOfTime gives balloons a gold star [19:13] like /foo/bar/xchat and /foo/bar/catfish ? [19:13] to be completely frank - it is all as clear as mud [19:14] TheLordOfTime, you can push people to that page also [19:14] it links to bugsquad stuff :-) [19:15] elfy, yes only change what you want to show up in each branch [19:15] balloons: see, i didn't know that page :P [19:15] * TheLordOfTime handles standard bug triage, not ISO testcase stuff :P [19:15] so for example if your merge proposal wants to include only mousepad changes, branch trunk, change mousepad, submit the branch [19:15] all straightforward and you know how to do that now [19:16] next, if you want to change catfish, re-branch trunk and make the changes, and submit the branch [19:16] elfy what i do is create a folder say called manual-tests, then for each manual test i do i would create a folder for it so xchat - folder. then in that folder pull down the main branch from launchpad. and only change xchat stuff in this folder then push up only xchat changes from that branch/folder. This way when you create you xchat branch on launchpad you will only be merging changes to xchat. [19:16] do it in a different directory.. starting fresh from branching lp:ubuntu-manual-tests [19:16] make sense? [19:16] DanChapman: aah right - I see [19:16] DanChapman, perfect.. glad your able to explain :-) [19:17] :) no probs. [19:17] so you'd end up with the whole main bracnh for each testcase you want to write? [19:17] is that right? [19:17] yeah thats correct [19:17] and then in 'that' one the only thing different would be that testcase [19:18] yep [19:18] right [19:18] got that :) [19:19] balloons: see - you get some connectors and some wire, then you wire up a whole plane - now I can do that from those instructions because I did it - could you :) [19:19] that is what I was fighting on saturday when trying to do this stuff :) [19:19] I rewired my car once. Never again!! :D [19:19] :) [19:20] elfy, :-) probably not a whole plane [19:20] balloons DanChapman - thanks that has watered down the mud somewhat - it's just a little bit opaque now :) [19:20] :) [19:20] also note once your branch is merged you can delete that folder.. that branch isn't needed anymore [19:20] does that make sense? [19:20] so - then as far as changes to testcases goes - do the change, commit and push [19:21] might need DanChapman's help again :-) [19:21] brb [19:21] yep - because that work is now in the main thing for everyone [19:21] I get that [19:22] once I see one of the things I've done it'll probably go 'ping' light on :) [19:24] balloons, I cannot find docs on that "in" command ...:p [19:31] balloons DanChapman - yep completely understand that logic now - just done it for the thunar test - got the branch and the mousepad one is there amongst the paackages [19:36] elfy, yeah do the change, commit, push, but keep committing and pushing up to your branch until you think it is ready to be merged. When it gets merged to the trunk only the difference between your branch and trunk gets merged. For example say you changed xchat and mousepad on the same branch and it got merged. If for some reason there was a need to go back to a revision before xchat was added but mousepad is not part of the pr [19:36] because they were merged together. Does that make sense? [19:37] yea - which is what I ended up doing - sending them all instead of the one that I wanted to - if I was in different folders for each - that wouldn't have happened [19:38] k, back [19:39] Letozaf, it's a python thing [19:39] http://kracekumar.com/post/22512660850/python-in-operator-use-cases [19:39] balloons, aaah! was looking in autopilot docs :p [19:39] myString = "Hello Carla" [19:39] "Carla" in myString [19:40] True [19:40] DanChapman: so I could bzr add my /manualtests/Thunar/ branch now and it would just get added to my https://code.launchpad.net/~elfy [19:40] balloons, thanks :D [19:40] then when I'm ready I push it to the main branch and propose for review [19:46] elfy here is my kind of work flow for bzr http://paste.ubuntu.com/5711310/ [19:47] yep - that is what I'd got from the last 30 minutes or so :) [19:48] autopilot updated, trying gedit test again [19:48] thats all you really need to know :D [19:48] I've got that now - then when I was done to at least get it first checked - do the add and commit and push then ? [19:51] ok, I got the same failure [19:51] Letozaf, /test_gedit.py", line 241, in test_insert_overwrite_mode [19:51] self.assertThat(typeMode, NotEquals(None)) [19:51] MismatchError: None == None [19:51] do you get that error? [19:51] balloons, yes [19:51] Letozaf, lol.. OHH.. ok [19:51] balloons, its the only errror left to fix :p [19:51] ahh.. gotcha [19:51] sorry :-( [19:52] elfy, once pushed it is up on launchpad, so anything from there you do on launchpad page. So propose to merge or link a bug, request review. [19:53] k, I'll work on the other pending ones then for the moment and come back to gedit [19:53] someone familiar with the jenkins instance here? [19:53] looks like the xunit testresults are not working as intended [19:53] see pyzmq [19:54] DanChapman: so I can add, commit, push my branch and it'll just be in my LP page [19:55] I'd at least be able to follow the logic of the system I guess [20:02] so DanChapman, Letozaf we need to decide what can be pushed to the production branch from these tests also [20:02] anything that is 1.3 and working and makes sense in jenkins, we should place in there [20:02] right now it only has the firefox test in it [20:03] balloons, well if we fix gedit, we also got gedit :p [20:03] exactly [20:03] :-) [20:03] and simple is ok here.. just running the app everyday will make sure it starts and doesn't crash [20:03] that in itself is a smoketest [20:04] balloons, good, so we must get other tests working :-) [20:05] balloons, typeMode = self.app.select_many('GtkLabel', label=' INS ') instead of typeMode = self.app.select_single('GtkLabel', label=' INS ') works ?? [20:05] Letozaf, heh.. there's more than one? [20:05] that's odd [20:06] balloons, I suspected so, but I do not know where to look for it, there is sooooo much stuff in vis [20:06] Letozaf, ohh yes indeed [20:06] did you learn the trick from the hackathon? [20:07] balloons, nope I just had a flash idea [20:07] check out the _find function in here: http://paste.ubuntu.com/5694635/ [20:08] let me give you a better example of me using it [20:08] balloons, I saw this and also looked at it various times [20:08] balloons, yes and example would be fine [20:08] balloons, :p [20:09] http://paste.ubuntu.com/5711368/ [20:10] so that's from the work I was doing on totem [20:10] I implemented his walk to look for stuff in the application for me.. [20:10]