[01:28] <will> hey guys. do you think the latest performance improvements to unity will be backported to 12.04?
[02:03] <elky> will, no.
[02:04] <thumper> will: some will
[02:04] <thumper> will: when we get them stable
[02:04] <elky> But you never know. I'm also not on the team, but I'd not be expecting performance enhancements to go into a stable release.
[02:05] <thumper> there is an SRU bug around some of this, so some will
[02:47] <will> elky, thumper: thanks! the latest commit for unity apparantly hugely improves performance
[02:47] <will> they said something like 20 - 40% per monitor
[02:47] <will> (i assume that means 20% faster for just one monitor...)
[02:47] <will> i'd love to see that in 12.04
[02:49] <thumper> will, the latest commit also introduces a number of regressions we are trying to fix
[02:52] <will> thumper: fair enough - i can see why it might not be a good idea to publish it right away then :)
[05:33] <Mirv> didrocks: yeah I actually submitted an ARM build fix later on but there was a change request
[05:34] <Mirv> I'll submit another merge request with that wish fulfilled
[05:34] <didrocks> hey Mirv, thanks!
[05:34] <didrocks> then it has to be reviewed upstreamed, UNBLOCKED and so on
[11:00] <sil2100> didrocks: just to be sure - all unity stack projects need to have the upstream unity task in their bugs?
[11:06] <sil2100> didrocks: the ubuntu branch for unity is missing some more libunity-core 5.0 -> 6.0 switches
[11:06] <sil2100> https://code.launchpad.net/~sil2100/unity/ubuntu_quantal
[11:07] <sil2100> I gave you this branch yesterday - could you merge those 2 commits I appended?
[11:07] <sil2100> didrocks: since otherwise the automerger is failing
[11:08] <sil2100> https://jenkins.qa.ubuntu.com/job/automerge-unity/897/console
[11:08] <sil2100> (you missed this one place)
[11:09] <sil2100> didrocks: we need this ASAP, since otherwise all the UNBLOCKed merges will fail
[11:11] <Mirv> sil2100: ah thanks for giving that link, so it's indeed the same automerger failing that blocks my ARM build fix
[11:11] <Mirv> (https://code.launchpad.net/~timo-jyrinki/unity/fix-arm-building)
[11:16] <sil2100> Mirv: yes, all merges will fail sadly
[11:16] <sil2100> didrocks: ^
[11:18] <didrocks> sil2100: pushed
[11:35] <sil2100> didrocks: thanks!
[11:35] <sil2100> didrocks: and, should I also add unity upstream project to bugs from dee?
[11:37] <didrocks> sil2100: depends, if you want to automatically close the bugs with my script, yeah, as we discussed during the sprint :)
[11:38] <sil2100> I fear of your scipt... ;) I know it's powerful, but it.. it's seems so risky!
[11:41] <didrocks> sil2100: I run it so many times, there is no risk :p
[11:41] <sil2100> didrocks: you sure..? I won't break anything?
[11:42] <didrocks> well, if you use it properly :)
[11:45] <didrocks> sil2100: I can run it for you when you are ready if you fear it and give you the output :)
[11:46] <sil2100> ...;)
[11:46] <sil2100> I think I'll ping you then when needed ;)
[12:45] <sil2100> didrocks: the merges take a while to get into trunk... could we in the meantime just cherry-pick those to-be-merged changes and test it like that?
[12:45] <sil2100> didrocks: without actually waiting for everything to get merged in and creating a new tarball?
[12:46] <didrocks> sil2100: we want to release a working tarball, don't we?
[12:46] <didrocks> so for that, we need trunk in a good state
[12:46] <sil2100> didrocks: yes of course - but to start testing the new tarball we'd have to wait for all the merges to go in
[12:46] <didrocks> (it's 30 minutes per merge)
[12:46] <didrocks> sil2100: hum, how would you make a tarball then?
[12:47] <didrocks> you mean, creating a fake trunk branch
[12:47] <didrocks> merge that manually
[12:47] <mpereira> can anyone give me a hand? i tried writing a very simple indicator, just to see something working before writing anything serious. but i couldn't get it to show up on the indicator bar https://gist.github.com/3026227
[12:47] <didrocks> creating the tarball from it
[12:47] <didrocks> and ditching it?
[12:47] <sil2100> didrocks: no no, I mean for testing purposes now
[12:47] <didrocks> sil2100: for testing, you can just bzr merge in your packaging branch
[12:47] <sil2100> didrocks: since we have to re-do autopilot tests, checkbox tests and manual-tests with the new changes, right?
[12:47] <didrocks> (without using that packaging branch later on)
[12:47] <didrocks> sil2100: indeed
[12:48] <didrocks> so I would say, use the previous packaging branch
[12:48] <sil2100> didrocks: that's what I was proposing - will that count as testing the latest release?
[12:48] <didrocks> with the previous tarball
[12:48] <didrocks> and cherry-pick the commits :)
[12:48] <didrocks> yeah
[12:48] <didrocks> it's basically the same, apart that the tarball isn't greta :)
[12:48] <didrocks> but we don't care for testing
[12:48] <sil2100> That's what I wanted to know ;) Thanks
[12:48] <sil2100> \o/
[12:48] <didrocks> sil2100: yw ;)
[13:01] <dandrader> When I call QueueDraw() on the SwitcherView, sometimes it redraws instantly and sometimes it takes a few seconds to do so. Any ideas on what's causing this delay and what else I should call to ensure the redraw takes place ASAP?
[13:46] <marco> there's a bug in hud. Start an application and close it. Tap alt. The menu entries for the closed app will still appear in hud. Was it already reported?
[13:47] <sil2100> marco: oh, I can reproduce it here as well
[13:47] <sil2100> marco: not sure, I personally didn't know about it, but maybe someone reported it already
[13:48] <marco> sil2100: cant find it in google.
[13:48] <marco> sil2100: the bug is present ever since hud was first released. Do you think it is hard to fix?
[13:50] <sil2100> marco: the bug doesn't look very hard, although it might be bamf related - could you file a new one please?
[13:50] <sil2100> For unity for now
[13:50] <didrocks> marco: I can't reproduce it though, do you have nautilus rendering your desktop?
[13:50] <didrocks> it's like, you are on an empty workspace?
[13:51] <marco> didrocks: I'm running stock. No changes made to the system. Empty workspace
[13:52] <sil2100> didrocks: I can reproduce it here on quantal
[13:52] <didrocks> sil2100: what's your steps exactly?
[13:53] <popey> i can't on precise or quantal
[13:53] <sil2100> didrocks: I go to an empty workspace, open nautilus, close nautilus, open HUD and type in a 'nautilus-like' query
[13:54] <sil2100> It's strange, because the names of the menu entries are there, but no name of the application in those
[13:54] <sil2100> So it's just like "Quit"
[13:56] <didrocks> sil2100: are you just trying with nautilus?
[13:56] <didrocks> can you try with gedit?
[13:57] <didrocks> because nautilus is rendering your background, so it's normal you still see nautilus in the HUD
[13:57] <marco> didrocks: I could reproduce it with gedit on precise
[13:57] <sil2100> didrocks: only with nautilus, but when I don't open and close nautilus, I don't see those entries in the HUD
[13:57] <didrocks> sil2100: nautilus isn't a bug
[13:57] <sil2100> didrocks: I only see them when opening and closing
[13:57] <didrocks> sil2100: because your root window is nautilus
[13:58] <marco> I'll re-test in quantal, wait a bit...
[13:58] <sil2100> didrocks: actually, I can also reproduce it with gedit
[13:58] <didrocks> marco: yeah, I think we are speaking about 2 things, if you can confirm on quantal… :)
[13:58] <didrocks> so opening gedit
[13:58] <didrocks> closing it
[13:58] <didrocks> taping alt at you have it's entry?
[13:58] <didrocks> its
[13:58] <didrocks> (I get the nautilus ones here)
[13:59] <marco> booting vm...
[13:59] <sil2100> Yes, I have "File > Open"
[13:59] <sil2100> With the gedit icon even ;p
[13:59] <didrocks> well, this is on nautilus also :p
[13:59] <sil2100> (absurd)
[13:59] <didrocks> ok
[13:59] <didrocks> so before tapping alt
[13:59] <didrocks> what's written in the panel?
[13:59] <sil2100> When clicked, it does nothing
[13:59] <sil2100> One moment
[13:59] <sil2100> "Ubuntu Desktop" in Polish ;)
[14:00] <didrocks> waow
[14:00] <didrocks> so the focus is right
[14:00] <didrocks> if you click/hover the panel
[14:00] <marco> didrocks: I confirm it is reproducible in quantal with gedit
[14:00] <didrocks> you have the menu content?
[14:00] <didrocks> (for nautilus)
[14:00] <didrocks> then, tapping alt
[14:00] <didrocks> and you still have the gedit icons with the gedit content?
[14:00] <didrocks> marco: if you can test that as well ^
[14:00] <sil2100> didrocks: one moment
[14:00] <marco> didrocks: the "documents" menu is listed in hud
[14:01] <marco> didrocks: even the gedit icon still appears
[14:01] <sil2100> didrocks: no, I have the desktop menu on the panel :|
[14:01] <sil2100> didrocks: but HUD was still finding gedit
[14:01] <marco> sil2100: try tapping alt and search for a gedit exclusive menu: like the documents menu
[14:02] <didrocks> ah, in fact, I have the same without closing
[14:02] <didrocks> like
[14:02] <didrocks> have an application in one ws
[14:02] <didrocks> switch to another one
[14:02] <didrocks> press alt
[14:02] <sil2100> Well, I don't have gedit open anywhere ;)
[14:02] <didrocks> you have the content of the last app
[14:02] <marco> didrocks: I can reproduce it without any app running!
[14:02] <didrocks> basically, if active app == desktop, last activate app is showing in the HUD
[14:03] <didrocks> marco: yeah, just trying to find the common pattern here :)
[14:03] <sil2100> Ah
[14:03] <sil2100> Makes sense!
[14:03] <marco> that's what I was trying to describe
[14:03] <didrocks> maybe some valuable info to add to the bug report ^
[14:03] <marco> so... Is it hard to solve?
[14:03] <didrocks> marco: look if there is not already a bug report about it
[14:03] <didrocks> it rings a bell to me
[14:04] <didrocks> well, can be :/
[14:04] <marco> tried google, nothing found
[14:06] <marco> didrocks: what do you mean by "it rings a bell to me"?
[14:07] <didrocks> like, I think I read something similar on a bug report
[15:12] <jaytaoko> sil2100: popey: hello
[15:13] <sil2100> jaytaoko: hi!
[15:15] <jaytaoko> sil2100: Daniel is investigating the issue on rev 2470. Are you postponing the release for this week? or another option?
[15:18] <sil2100> jaytaoko: it's already fixed
[15:19] <sil2100> jaytaoko: probably even merged into trunk!
[15:19] <jaytaoko> sil2100: great!
[15:20] <didrocks> sil2100: how probably? it is for 2 hours :p you should look at merge requests emails ;)
[15:20] <didrocks> Mirv: nice to see unity building on armfh again (just confirmed in the unity staging ppa!)
[15:20] <sil2100> didrocks: sorry, got too much to do, since we're hasting with testing
[15:22] <didrocks> sil2100: so, we adressed the first untested branch, I guess it's the same answer for https://code.launchpad.net/~vanvugt/unity/fix-1010335/+merge/109513, right?
[15:22] <didrocks> sil2100: I didn't see that one reverted and merged
[15:22] <sil2100> didrocks: it didn't get merged
[15:22] <sil2100> It's 'work in progress'
[15:23] <didrocks> sil2100: oh right, I must have my eyes not looking right when listing it!
[15:23] <sil2100> didrocks: so not sure what you want to revert...
[15:23] <didrocks> sil2100: ok, cleaning the google doc then :)
[15:26] <sil2100> didrocks: but we have a problem - since unity-2d fails building on quantal and I don't see anyone from the unity-2d team around
[15:28] <sil2100> I was even looking for them yesterday
[15:30] <sil2100> I think we're missing some quantal-build fixes from trunk, I'll look for those
[15:31] <didrocks> sil2100: please, escalate to popey or patt. they have to maintain unity-2d
[15:37] <sil2100> didrocks: I think I have this fixed
[15:37] <sil2100> didrocks: I cherry-picked it from upstream
[15:37] <didrocks> sil2100: but, the branch is not the upstream one?
[15:37]  * didrocks is puzzled
[15:38] <sil2100> didrocks: yes, but we're not doing a unity-2d release yet
[15:38] <sil2100> didrocks: we're just bumping unity-2d from precise
[15:39] <sil2100> didrocks: you just said to perform a rebuild against new unity
[15:39] <sil2100> So that's what I'm doing
[15:39] <didrocks> sil2100: oh, if you need to ship latest trunk, please be my guest :)
[15:40] <sil2100> oooh nononono ;) Next time - I'm already very late with unity 6.0 itself!
[15:40] <sil2100> ;)
[15:40] <didrocks> sil2100: what commit are you taking?
[15:40] <sil2100> http://bazaar.launchpad.net/~unity-2d-team/unity-2d/trunk/revision/1113 <- ;p
[15:41] <didrocks> oh my commit :)
[15:41] <didrocks> weird, I was thinking we were already shipping it
[15:42] <didrocks> oh, indeed, we don't
[15:42] <sil2100> https://code.launchpad.net/~sil2100/unity-2d/ubuntu_quantal <- here's the packaging branch if anything
[15:43] <didrocks> sil2100: you will need to push the changelog to trunk for next release, keep that in mind :)
[15:44] <didrocks> sil2100: and also, pushing the change as proper upstream merge request
[15:44] <didrocks> sil2100: I don't care about merging the right commit in that case only because this branch will be useless in the end for merging back the changes
[15:45] <didrocks> (otherwise, it can lead to conflicts)
[15:45] <didrocks> the changes looks good otherwise
[15:47] <sil2100> didrocks: I requested a merge for the 5->6 change
[15:47] <sil2100> But sadly there's no one to look and review ;)
[15:47] <didrocks> sil2100: ok, I'll review it for you then :)
[15:47] <sil2100> So it's just there, waiting for attention
[15:48] <sil2100> https://code.launchpad.net/~sil2100/unity-2d/bump_new_nux_libunity/+merge/113563
[15:48] <sil2100> Jenkins said needs fixing since I had to push in some modifications
[15:48] <didrocks> yeah, I'm on it
[15:48] <didrocks> the diff doesn't look good
[15:48] <didrocks> isn't there a check for unity-core in the cmake file?
[15:48] <sil2100> didrocks: in the main one?
[15:48] <sil2100> No
[15:48] <sil2100> Just in panel/ and unity-2d-private/
[15:49] <sil2100> You can double check ;)
[15:49] <didrocks> ah :=
[15:49] <didrocks> maybe the diff didn't refresh
[15:49] <didrocks> let me look :)
[15:50] <didrocks> sil2100: approved!
[15:50] <sil2100> \o/
[15:50] <sil2100> Thank you
[15:52] <didrocks> sil2100: thank *you*
[15:52] <didrocks> :)
[16:08] <sil2100> didrocks: we did autopilot and checkbox tests, I also confirmed the autopilot tests manually
[16:09] <sil2100> didrocks: we're all green with those \o/
[16:09] <didrocks> sil2100: phew ;)
[16:09] <didrocks> good work!
[16:10] <didrocks> it's too late for tonight though, I think we will upload on Monday, and the time you do the tarball, tag for release and such
[16:11] <sil2100> didrocks: should we upload the unity 6.0.0 tarball today, or everything on MOnday?
[16:12] <gord> isn't there some sort of rule about friday uploads and not wanting to work on saturday? ;)
[16:12] <popey> friday uploads \o/
[16:12] <didrocks> sil2100: I'm not confident uploading something just before leaving
[16:12] <didrocks> gold rule :)
[16:12] <popey> pffft.. wuss ;)
[16:12] <didrocks> gord: I bought FFXIII-2 this week, I really don't want to work this week-end :)
[16:12] <sil2100> ;)
[16:13] <sil2100> Ahh, nothing beats FFVII !
[16:13] <didrocks> yeah, I have the same feeling :)
[16:13] <didrocks> (like a lot of people)
[16:14] <gord> you are all wrong, ffVI is the best
[16:15] <gord> and then FFXII
[16:15] <didrocks> gord: I still prefer the X to VI ;) (VII, X, VI for me)
[16:15] <didrocks> but here, a lot of people will disagree :)
[16:16] <gord> i hated X so much... buy me a beer some time and i'll rant about it for hours and hours ;)
[16:16] <sil2100> FFVI was indeed nice
[16:16] <didrocks> gord: let's do that \o/
[16:17] <sil2100> Ok, I'll shutdown the PC, another storm coming - finally!
[16:17] <sil2100> Finally some wind and coolnes
[16:17] <sil2100> s
[16:17] <didrocks> sil2100: enjoy your week-end!
[16:17] <sil2100> didrocks: same for you :)
[16:17] <sil2100> See you on Monday everyone!
[16:19] <popey> thanks for helping us didrocks, much appreciated!
[16:21] <didrocks> popey: you're welcome :)
[16:21] <didrocks> thanks for the hard work ;)
[16:21] <didrocks> at least, from now on, you see what an unity release is and takes :) (even if there were few components involved in that release)
[17:16] <mpereira> sorry for reposting this, but can anyone point me to the right direction? i tried writing a very simple indicator, just to see something working before writing anything serious. but i couldn't get it to show up on the indicator bar https://gist.github.com/3026227
[17:19] <c10ud> mpereira, there seems to be something wrong in your OS because it cannot connect (to dbus..?)
[17:20] <c10ud> also i guess if you run it as root it won't be in the same session as yours..?
[17:23] <c10ud> mpereira, also, you might want to check this out: https://wiki.ubuntu.com/DesktopExperienceTeam/ApplicationIndicators#Typical_usage_.28C_version.29
[18:23] <mpereira> c10ud: thanks for the link. re not being able to connect to dbus maybe i need to call the binary with some dbus wrapper or something?