[09:11] <jibel> good morning
[09:18]  * mterry waves at jibel 
[09:23] <sil2100> mterry: hi! Isn't it a bit too early for you? ;)
[09:24] <mterry> sil2100, yes but I'm in Bluefin this week
[09:27] <sil2100> Ah! Excellent ;)
[09:28] <jibel> hey mterry
[09:35] <smspillaz> sil2100: hey, so I have a fix/workaround for the virtualbox thing as per my mail
[09:35] <jibel> didrocks, mterry I restarted the cu2d jobs this morning excepted unity. They all failed due a corruption of the LP cache.
[09:36] <didrocks> jibel: saw that. Thanks jibel :)
[09:36] <didrocks> I'm wondering why it's starting to get frequent
[09:36] <sil2100> smspillaz: hi! I saw the e-mail, the situation is pretty messed up
[09:36] <sil2100> smspillaz: I'll do a test build and test it around with me and popey and comment at the merge requests
[09:37] <sil2100> smspillaz: I know that usually workarounds are put as quilt patches, but are you sure this won't make introducing compiz changes more troublesome? As in, breaking the patch and needing to refresh it with changes made to trunk?
[09:38] <didrocks> mterry: https://code.launchpad.net/~stolowski/unity-lens-video/vala-rewrite/+merge/135935
[09:39] <mterry> jibel, thanks
[09:41] <didrocks> jibel: nvidia is dead thougH?
[09:43] <jibel> didrocks, they all look dead.
[09:43] <didrocks> :/
[09:43] <jibel> indicators tests started 2 hours ago or so
[09:43] <didrocks> the other started 30 minutes ago, isn't it?
[09:43] <didrocks> (for running the tests)
[09:44] <didrocks> oh no, 1h30
[09:44] <didrocks> not yet get used to have my clock aligned with jenkins :)
[09:44] <jibel> there's been a power outage again Friday night. The machines might not have liked it.
[09:46] <smspillaz> sil2100: I don't anticipate it will cause problems, in lp:compiz the maintainers refresh the patches themselves anyways
[09:46] <jibel> didrocks, if you roll over the progress bar it tells you for how long it's been running and (a not so reliable) ETA
[09:46] <smspillaz> sil2100: its just there in patch form because I know the proper fix for virtualbox itself, but it could take some time for them to deliver it in a release
[09:47] <sil2100> smspillaz: true true - ok, I'll be testing it today with the help of popey as well
[09:47] <smspillaz> :)
[09:48] <sil2100> ;)
[09:48] <popey> \o/
[09:48] <didrocks> jibel: yeah… I'm asking to the relevant people right now and see what they are telling about UTAH
[09:48] <smspillaz> sil2100: it might be a bit flakey because I don't know how well copytex can handle destroyed pixmaps. But I guess having a corrupted image rarely is better than a guarunteed hang for now
[09:49] <jibel> didrocks, ok :)
[10:02] <mterry> Does alt-tilda work for anyone else on the daily-build PPA?  It seems to be broken for me
[10:09] <didrocks> mterry: dist-upgrading
[10:17] <mterry> sil2100, ^ alt-tilda doesn't work for me or didrocks in the daily-build PPA.  Do you have a second to look at that?
[10:26] <sil2100> mterry: one moment, will check that
[10:35] <jibel> mterry, mmrazik there is a problem with the preseed utah-jenkins/resources/preseed.cfg
[10:36] <jibel> mterry, mmrazik there should be a chown jenkins utah_ap_stuff after line 51 mkdir -p /target/home/jenkins/utah_ap_stuff
[10:36] <jibel> otherwise bzr will fail with a permission denined
[10:36] <jibel> denied
[10:36] <jibel> mterry, mmrazik can you fix that?
[10:37] <mmrazik> jibel: I'm on it. sorry for that
[10:38]  * mterry hugs jibel
[10:39]  * jibel hugs mterry back 
[10:40] <mmrazik> jibel: just pushed this: http://pastebin.ubuntu.com/1676471/
[10:40] <jibel> mterry, this is another occurrence of bug 1126115
[10:42] <jibel> mmrazik, looks good, thanks.
[10:53] <mterry>  mmrazik, jibel: so should we restart the jobs?
[10:53] <mmrazik> mterry: yes
[10:54] <mterry> didrocks already did, cool
[11:04] <mmrazik> mterry: are you sure the job was started? I only see #136 running and that one seems to running since ~8am UTC
[11:04] <mmrazik> ps-indicators-autopilot-release-testing, i.e.
[11:05] <mterry> hmmm, you're right.  I think I got confused by the web page
[11:58] <smspillaz> andyrock: Trevinho: can I get one of you two to have a look at https://code.launchpad.net/~compiz-team/compiz/compiz.fix_1120009.3/+merge/148839
[11:58] <smspillaz> (might be helpful for the unity xorg-gtest stuff too)
[12:08] <andyrock> smspillaz, sure
[12:10] <smspillaz> andyrock: great, thanks
[12:10] <sil2100> Oh, I finally see the CI approved that one \o/
[12:10] <smspillaz> yeah, took forever
[12:10] <smspillaz> the catch-exceptions-and-retry approach is so ugly but works
[13:40] <mterry> cyphermox, finally got jenkins back up and working.  See http://10.97.0.1:8080/job/ps-indicators-autopilot-release-testing/label=autopilot-intel/lastCompletedBuild/testReport/ for why the indicator stack failed
[13:41] <cyphermox> yay
[13:41] <cyphermox> well. it's not super informative
[13:42] <cyphermox> but I had noticed you'd started the job
[13:42] <mterry> cyphermox, only intel had any failures; those 3 tests
[13:43] <cyphermox> yeah
[13:43] <mterry> unity stack is still blocked on test failures too.  Especially now that the alt-` tests fail.  sil2100, any luck on that?
[13:44] <sil2100> mterry: will get back to you after lunch regarding this one :)
[13:44] <mterry> sil2100, OK
[13:46] <mterry> thomi, if you have some time, it would be swell if you could re-look at https://code.launchpad.net/~sil2100/unity/autopilot_ibus_improve/+merge/147951
[13:53] <smspillaz> andyrock: Trevinho: thanks. If you get time, a look at some of the smaller things in the queue owuld be good too. Let me know if you need me to look at anything for you as well
[13:54] <andyrock> smspillaz, will do (pretty busy right now :/
[13:54] <Trevinho> smspillaz: you don't have small things :D
[13:54] <smspillaz> there's a 17 line change in there somewhere :P
[13:55] <Trevinho> smspillaz: I've given a general look to other branches (the one you provided the benchmarks for too)
[13:55] <smspillaz> argh, dammit, xorg-gtest has some code that doesn't compile on arm in it
[13:55] <Trevinho> smspillaz: however, that wil work for nvidia only, for now, isn't it=
[13:55] <smspillaz> Trevinho: right, although the boost you get on nvidia is massive
[13:56] <smspillaz> Trevinho: trust me, performance on nvidia right now is awful
[13:56] <smspillaz> I get 3fps when moving GL-rendered windows around :)
[13:56] <Trevinho> smspillaz: I believe, but I've not their hw here anymore :/
[13:56] <smspillaz> Trevinho: well, its mostly covered by regression tests, and I need testers for the non-buffer_age case too
[13:57] <smspillaz> Trevinho: I had a look into what it would take to implement GLX_EXT_buffer_age on mesa drivers and its not trivial
[13:57] <smspillaz> my understanding is that they're working on it
[14:00] <sil2100> mterry: thomi commented privately on that branch, I'll be pushing a small fix regarding this
[14:01] <mterry> sil2100, cool
[14:01] <sil2100> mterry: we're also testing the ibus branches on a private jenkins job too
[14:01] <sil2100> To make sure they work swell
[14:01] <mterry> sil2100, can't be worse than current tests :)
[14:02] <sil2100> mterry: ;) Francis and Alan confirmed those working well, but better be safe than sorry! Although, the jenkins build job is still in the queue since morning :(
[14:03] <vibhav> Does Unity use libnotify?
[14:03] <mterry> sil2100, I don't see anything in the queue on my normal jenkins view, but I don't know what private jenkins shenanigans you have
[14:03] <vibhav> Or do I need to implement different notification systems for my apps (GNOME and Unity)
[14:03] <mterry> vibhav, yes, libnotify works
[14:04] <mterry> vibhav, though GNOME's shell allows buttons, but Unity's does not
[14:04] <vibhav> perfect
[14:04] <vibhav> mterry: How do I check the DE used then?
[14:05] <vibhav> Is there any macro defined for Unity/GNOME?
[14:05] <vibhav> (Which I could #ifdef)
[14:05] <mterry> vibhav, this isn't the right channel for detailed help like that.  This channel is for unity development
[14:06] <mterry> vibhav, but http://developer.ubuntu.com/resources/technologies/notification/ has details on checking notification server capabilities (including whether it accepts action buttons)
[14:06] <vibhav> mterry: Ah, thanks!
[14:49] <andyrock> smspillaz, ping
[15:40] <mterry> sil2100, any word on the alt-` bug?
[15:49] <mterry> didrocks, https://launchpad.net/~mterry/+sshkeys  (add conga)
[15:59] <sil2100> mterry: test building something that might fix the problem
[16:57] <didrocks> sil2100: did the "may" worked? :)
[17:02] <sil2100> didrocks: hm, strangely, no, but I need to re-check I think
[17:03] <didrocks> sil2100: should we revert the commit, do we know what created it?
[17:04] <sil2100> didrocks: I also tried that, since I thought that rev 3158 created the regression - but after reverting it, it didn't seem to help, which was a bit strange
[17:05] <didrocks> sil2100: hum, ok… :/
[17:58] <sil2100> didrocks: I think I might have found the affecting commit
[17:58] <didrocks> sil2100: \o/
[17:58] <didrocks> o/\o/\o/\o
[17:58] <sil2100> didrocks: it's probably 3153, making double sure
[17:58] <sil2100> But let me poke andyrock about it anyway
[17:58] <didrocks> sil2100: with a double build? ;)
[17:58] <sil2100> andyrock: ping
[17:58] <sil2100> didrocks: I'm building the revision right before the change was introduced ;p
[17:58] <andyrock> sil2100, pong
[17:58] <andyrock> what's up?
[17:59] <didrocks> andyrock: it's your fault! all your fault! :-)
[17:59] <sil2100> andyrock: hi! alt+` got broken, i.e. detail switching is broken
[17:59] <didrocks> (well, sil2100 thinks… :p)
[17:59] <sil2100> andyrock: and I checked that rev 3150 didn't suffer from the issue
[17:59] <sil2100> andyrock: 3153 suddenly had the problem already
[18:00] <sil2100> andyrock: checking if 3152 if safe right now, but it seems maybe some LauncherIcon changes you made could have broken it?
[18:00] <andyrock> sil2100, could be
[18:00] <sil2100> andyrock: since it's not possible to switch between applications of the same type witl alt+` or alt+tab in detail
[18:07] <andyrock> sil2100, i can reproduce it... weird
[18:14] <andyrock> sil2100, yeah rev 3153's fault
[18:15] <andyrock> actually a faster alt + \ still does not work
[18:17] <sil2100> andyrock: yea
[18:17] <sil2100> andyrock: just double checked that
[18:17] <sil2100> 3152 is ok
[18:17] <sil2100> andyrock: will you be able to fix it till EOD?
[18:18] <sil2100> andyrock: it's blocking the daily release ;)
[18:18] <andyrock> sil2100, i can try
[18:18] <sil2100> Since every Monday is a daily-release-blocker!
[18:18] <sil2100> :)
[18:18] <sil2100> andyrock: thanks
[18:18] <andyrock> np
[18:21] <sil2100> andyrock: I'll be anticipating a merge request on my e-mail :)!
[18:28] <andyrock> sil2100, fixed
[18:28] <andyrock> stupid "typo"
[18:29] <andyrock> sil2100, is there a bug (I don't need it but if there is I can link in the commit)
[18:31] <rye> Hi, quick question - somehow I lost the panel dbusmenu and all indicators - I am running the latest unity-team/staging builds - is it known or I got something broken/misconfigured
[18:32] <rye> The state persists after cleaning the dconf and compiz settings
[18:32] <andyrock> rye, known issue
[18:33] <rye> andyrock: phew, thank you
[18:34] <andyrock> rye, np
[18:34] <andyrock> sil2100, https://code.launchpad.net/~andyrock/unity/fix-alt-grave-reg/+merge/149123
[18:34] <andyrock> sil2100, feel free to test it ;)
[18:36] <sil2100> \o/
[18:36] <sil2100> andyrock: I don't think there's a bug, I'll create one and link
[18:36] <sil2100> andyrock: you rock!
[18:36] <andyrock> sil2100, well my fault my fix ;)
[18:36] <sil2100> andyrock: actually, you andy rock!
[18:36] <sil2100> ;)
[18:46]  * didrocks will make a banner, "my fault my fix"
[18:47] <didrocks> thanks sil2100, andyrock :)
[18:48] <andyrock> np
[18:50] <didrocks> sil2100: approving once you finished to test it?
[18:51] <sil2100> didrocks: yes :) It's almost built
[18:51] <didrocks> \o/
[18:51]  * didrocks hopes that tomorrow, we'll have a daily release
[19:08] <sil2100_> andyrock: works!
[19:09] <andyrock> nice
[19:16] <davmor2> didrocks: why do that,  assignblame.py x = 0 while x !=10:  print "didrocks broked it again " x += 1    me hopes he got the context right :)
[19:33] <didrocks> davmor2: ahah, no, it wasn't me. (stickers ;))
[19:35]  * davmor2 now pictures didrocks doing impressions of shaggy