[03:22] <spoleeba> no that is odd... compiling libunity from bzr tag:5.92.0  on fedora 17... works fine.. compiling from the 5.92.0 tarball... failure
[03:22] <spoleeba> hmmm
[03:23] <spoleeba> i wonder what is different between the bzr checkout and the tarball release
[03:48] <spoleeba> ah found it
[08:43] <sil2100> didrocks: hello, how are you today?
[08:43] <didrocks> sil2100: hey, I'm fine, thanks, yourself?
[08:44] <sil2100> didrocks: not bad ;)
[08:44] <sil2100> didrocks: is there any news regarding the gsettings metacity/g-c-c/compiz thing?
[08:45] <didrocks> sil2100: unfortunately, it seems that nobody answered
[08:45] <didrocks> sil2100: I was hoping that Tim will answer to the email as "he didn't have time yesterday"
[09:07] <sil2100> JohnLea: hi
[09:15] <JohnLea> sil2100; hyia
[09:21] <sil2100> JohnLea: how are you?
[09:48] <didrocks> sil2100: https://launchpad.net/~sil2100/+archive/ppa/+sourcepub/2578627/+listing-archive-extra
[09:48] <didrocks> sil2100: you took one more commit that you should have for nux FYI
[09:48] <didrocks> sil2100: I did the ~ubuntu-desktop/nux/precise branch
[09:49] <didrocks> but please, don't change anything packaging-wise in a SRU if there is no good reason. It will be rejected otherwise :)
[09:51] <sil2100> didrocks: ah, ok ;) Good to know
[09:51] <JohnLea> sil2100; good, and you?
[09:51] <sil2100> didrocks: since I thought that taking the --parallel change might be harmless
[09:51] <sil2100> JohnLea: same here ;)
[09:52] <JohnLea> sil2100; what's up?
[09:52] <sil2100> JohnLea: would like to get some final clarification about the super+W case
[09:52] <sil2100> The one from https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/933776#47
[09:52] <JohnLea> sil2100; yup, I remember that discussion
[09:53] <sil2100> JohnLea: so, the behavior we expect to be is - when pressing super + W should show windows only from the given workspace?
[09:53] <didrocks> sil2100: you never know what can happen with packaging change :)
[09:54] <sil2100> didrocks: true true ;)
[09:54] <JohnLea> sil2100; the default behaviour when a user presses SUPER + W should be to spread all windows from the *current* workspace only.  However ideally this behaviour should be configurable in 'System Settings/Keyboard/Shortcuts'
[09:55] <sil2100> JohnLea: excellent - just wanted to confirm this
[09:55] <JohnLea> sil2100; thanks!
[09:56] <sil2100> JohnLea: since we're actually making a switch to gsettings now, so for quantal it might be ideal to fix this by changing the keybinding to 'how they're supposed to be'
[09:56] <JohnLea> great, will be good fix some of our keybinding issues
[11:06] <popey> hmm can someone else check https://bugs.launchpad.net/unity/+bug/1013751 please? I have tried to verify with -proposed enabled and it doesn't seem fixed
[11:10] <popey> welcome back sil2100  :)
[11:10] <popey> sil2100, <popey> hmm can someone else check https://bugs.launchpad.net/unity/+bug/1013751 please? I have tried to verify with -proposed enabled and it doesn't seem fixed
[11:18] <sil2100> ;)
[11:19] <sil2100> popey: will try to verify in a moment
[11:36] <popey> https://bugs.launchpad.net/ayatana-design/+bug/987955 makes no sense
[11:36] <popey> it says that with sticky edges _off_ it should still be sticky, as I read it
[11:37] <popey> is that how anyone else reads the section "What should happen:" ?
[11:40] <sil2100> popey: when sticky edges are _off_ and auto-hide is _on_, the edge where the launcher is should still be sticky
[11:40] <sil2100> popey: so that you can reveal the launcher
[11:41] <popey> but what if you dont want to reveal the launcher?
[11:41] <popey> e.g. when moving quickly from screen to screen
[11:41] <popey> or when you're dragging a window
[11:41] <sil2100> popey: not sure, never used this feature
[11:41] <sil2100> JohnLee should probably help here
[11:45] <popey> i mailed him
[12:05] <sil2100> popey: I will try confirming the bug you mentioned now
[12:09] <popey> also https://bugs.launchpad.net/unity/+bug/987156
[12:09] <popey> left a comment on that
[12:10] <popey> i still get flicker
[12:10] <popey> i would video it but kazam is broken for me today
[12:10] <popey> and it's so quick to appear I wouldn't be surprised if at 15fps it doesn't capture the flicker
[12:10] <sil2100> popey: did you try filming that?
[12:10] <popey> lemme try with my phone
[12:10] <sil2100> hm, anyway, strange thing - what about your quantal box?
[12:10] <sil2100> Can you reproduce it on quantal?
[12:11] <sil2100> I need to first make unity 3d run on my old box, eh
[12:11] <popey> yes, same on quantal
[12:11] <popey> both i7 if it matters
[12:11] <nmarques> yo
[12:11] <sil2100> You need to show me that, since I cannot reproduce it at all
[12:12] <popey> ok
[12:12] <popey> doing now
[12:12] <sil2100> It does appear from time to time, but only because I hold the two keys a bit longer
[12:12] <sil2100> And the timeout strikes in
[12:15]  * popey uploads to youtube
[12:15] <popey> I'm pressing the buttons insanely fast
[12:15] <popey> faster than I normally would
[12:18] <popey> sil2100, http://www.youtube.com/watch?v=gEwiUGMkKVk
[12:18] <sil2100> popey: thanks
[12:19] <sil2100> popey: holy shit, this is really a bug
[12:20] <sil2100> popey: I can show you how it looks like on my PC - completely different
[12:23] <popey> https://bugs.launchpad.net/ayatana-design/+bug/939436
[12:24] <popey> also doesn't look fixed to me
[13:09] <popey> how often does http://people.canonical.com/~ubuntu-archive/pending-sru.html run?
[13:11] <didrocks> popey: nice work on SRU confirmation bugs btw :)
[13:12] <popey> np
[13:20] <sil2100> Trevinho: hi
[13:20] <sil2100> Trevinho: are you around? :)
[13:29] <Trevinho> sil2100: just back
[13:29] <sil2100> Trevinho: excellent - I have a question ;)
[13:29] <sil2100> Since we've been testing https://bugs.launchpad.net/unity/+bug/1013751 from the unity SRU - which was supposed to be fixed
[13:30] <sil2100> But when running unity with the unity patch included, we can still reproduce this problem
[13:30] <sil2100> Is the nux patch required as well?
[13:31] <sil2100> Or should the unity patch be sufficient?
[13:33] <Trevinho> sil2100: for 5.0 or 5.0?
[13:34] <didrocks> or also, 5.0? ;)
[13:36] <sil2100> Trevinho: 5.0 ;)
[13:36] <sil2100> Trevinho: since the bug is still there without the nux patch, at least from what we can test
[13:37] <Trevinho> sil2100:  the nux patch was required for 6.0, however.... For 5.0 the change has been different to avoid regressions
[13:37] <Trevinho> basically we only filter Alt keys, not Ctrl keys...
[13:37] <Trevinho> or the ibus wouldn't work
[13:38] <sil2100> Trevinho: hm
[13:38] <sil2100> Trevinho: so the unity 5.0 patch should be enough to fix that bug?
[13:38] <sil2100> Trevinho: or not?
[13:38] <Trevinho> sil2100: I can get the ctlr fix as well with one line patch in nux btw
[13:38] <Trevinho> sil2100: it fixes it partially....
[13:39] <Trevinho> sil2100: it fixes the super and Alt thing, not the ctrl
[13:39] <Trevinho> the super one was priority however, since othwerise when doing Super+W with dash opened would have caused a w to be written in the text entry before initiating the spread
[13:39] <sil2100> Trevinho: when holding down ctrl and typing in some letters I get some strange text
[13:40] <Trevinho> sil2100: yes, that happens... But I can't fix that at unity level without not breaking ibus :/
[13:41] <sil2100> Trevinho: hm, ok, but this still means that the fix is not working in its current form
[13:41] <sil2100> Not good
[13:42] <sil2100> Trevinho: thanks, we'll try sorting this out somehow
[13:42] <sil2100> andyrock: ping!
[13:42] <Trevinho> sil2100: you only have to include this in nux to get it fixed: https://code.launchpad.net/~3v1n0/nux/text-entry-meta-filters/+merge/113137
[13:42] <andyrock> sil2100, pong
[13:42] <sil2100> Trevinho: ah, yes, about that one - I need to poke you too regarding this commit ;)
[13:42] <sil2100> andyrock: hello!
[13:42] <andyrock> sil2100, hey
[13:43] <sil2100> andyrock: can I poke you about https://bugs.launchpad.net/ayatana-design/+bug/939436 ;) ?
[13:43] <andyrock> sil2100, shoot
[13:43] <andyrock> :)
[13:43] <andyrock> I've already answerd btw
[13:44] <sil2100> andyrock: ah, I see - so hm, what was this bug about anyway ;p ?
[13:44] <sil2100> andyrock: since the HUD looks different than in the attached screenshot right now
[13:45] <andyrock> we used to highlight hud keyword using bold font
[13:45] <sil2100> Trevinho: well about this nux fix - since we're doing a nux SRU release this week anyway, and Brandon was gluing together some commits that could be ported to 2.0
[13:46] <andyrock> sil2100, now we use alpha .50 for normal words/letters
[13:46] <sil2100> Trevinho: and he wanted to include rev 627 (the merge/branch) you have mentioned, but said that it depends on some other change in the past and could break the ABI
[13:46] <andyrock> sil2100, and alpha 1.0 for highlighted words/letters
[13:46] <sil2100> andyrock: ah!
[13:46] <sil2100> andyrock: so it's not about how it should look, but what techniques for matching should be used?
[13:47] <sil2100> andyrock: so it is indeed fixed in this case
[13:47] <andyrock> sil2100, yeah... i think we should open another bug for "but what techniques for matching should be used"
[13:48] <andyrock> not sure it's a unity bug though
[13:49] <sil2100> andyrock: anyway, thanks for clearing this up
[13:49] <andyrock> sil2100, np :)
[13:50] <didrocks> nice work sil2100 ;)
[13:50] <sil2100> didrocks: thanks ;)
[13:51] <didrocks> sil2100: speaking of which, did you have a documentation summarizing the upgrade tests you did from gconf -> gsettings? (just to know if all is green on your side)
[13:51] <didrocks> and if we are just blocked by the metacity/g-c-c/unity-2d fun
[13:51] <sil2100> didrocks: no, I'll prepare it later today - since I actually wanted to test it also somewhere else, since VMs seem to have some problems
[13:52] <didrocks> sil2100: ok ;)
[13:52] <Trevinho> sil2100: it breaks the api too...
[13:52] <sil2100> Trevinho: aww :(
[13:52] <Trevinho> sil2100: I can prepare one that doesn't break the abi, but that fixes the ctrl issue
[13:53] <didrocks> sil2100: so I see at least 2 upgrades tests (in fact 3, but 2 should be enough to cover the 3rd)
[13:53] <didrocks> - install old compiz/unity, tweaks a lot of settings, upgrdae to newer compiz/unity, restart the session
[13:53] <didrocks> all tweaks should be there
[13:54] <didrocks> - and same test, with compiz/unity, but in the fallback session (default profile = Default)
[13:54] <sil2100> didrocks: will do! Francis also wants to help me out prepare some automatic tests for the migration script
[13:54] <didrocks> excellent!
[13:55] <didrocks> sil2100: if you have good automatic tools, we can even include them in the precise -> quantal migration upgrader test
[13:57] <sil2100> Trevinho: thanks ;) But we might think about that next time - for now anyway the unity fix is not enough, and that's all I wanted to know
[14:04] <sil2100> didrocks, seb128: what should we do if a bug that was supposed to be fixed in an SRU is not fixed completely?
[14:05] <seb128> sil2100, if there are no regression set the bug verification-done anyway and reopen it once the update is copied to -updates or open a new bug for remaining issue
[14:06] <sil2100> seb128: ok, thanks - no regression, just the fix that landed requires some nux changes that we _currently_ cannot land due to possible ABI/API breaks
[14:06] <jaytaoko> sil2100: hello
[14:06] <sil2100> seb128: but without those it just doens't fix all the problems
[14:06] <sil2100> jaytaoko: hi!
[14:06] <jaytaoko> sil2100: I am on precise. trying to compile unity i get an error related to missing 'unity-protocol-private'
[14:06] <seb128> sil2100, that's fine as long as there are no regression
[14:06] <seb128> sil2100, or just keep a nux component open on the bug
[14:07] <sil2100> seb128: thanks :)
[14:07] <seb128> sil2100, set it verification-done anyway if you verified there are no regression, so it doesn't block the SRU
[14:07] <sil2100> jaytaoko: hm, what unity you try to compile? lp:unity trunk?
[14:07] <jaytaoko> sil2100: yes lp:unity
[14:08] <jaytaoko> sil2100: do I need to compile lp:libunity
[14:09] <sil2100> jaytaoko: yes, sadly...
[14:09] <sil2100> jaytaoko: you need the latest libunity - and also, you probably need to use the latest packaging for unity as well
[14:09] <sil2100> jaytaoko: are you building a package, or just the source?
[14:10] <jaytaoko> sil2100: just the source
[14:10] <didrocks> jaytaoko: you should upgrade to quantal, at least, you will have the latest stack :)
[14:11] <sil2100> jaytaoko: as didrocks once said, it is almost always better to build with packaging ;) But anyway, if you just build from source, be sure to have trunk libunity
[14:11] <sil2100> jaytaoko: and then somehow ensure that the private libunity libraries are accessible for unity
[14:11] <jaytaoko> sil2100: yes, I will probably upgrade this week
[14:11] <sil2100> (if there are any problems)
[14:11] <jaytaoko> sil2100: will do! thanks!
[14:46] <sil2100> popey: ok, so I verified a few bugs more for the SRU - the only 2 ones left for verification are:
[14:46] <sil2100> https://bugs.launchpad.net/unity/+bug/987156 <- which you can still reproduce
[14:47] <sil2100> and https://bugs.launchpad.net/ayatana-design/+bug/987955 <- which you needed John's answer, right?
[14:57] <sil2100> jaytaoko: hm, I remember we had some manual-tests in nux in the past - did those get removed?
[14:59] <jaytaoko> sil2100: well we have a description of a few manual tests, but not more than that
[14:59] <jaytaoko> sil2100: are you referring to executable programs?
[15:04] <sil2100> jaytaoko: no, to text files with test steps
[15:05] <sil2100> jaytaoko: ah, so they're removed now
[15:05] <sil2100> Ok
[15:05] <sil2100> Thanks
[16:05] <spoleeba> mhr3, just a follow up ping. got libunity building and packaged for submission in Fedora. I need to do a make clean in the tarball release to clean out some pregenerated vala files in the tarball that do not exist in the bzr checkout.
[16:05] <spoleeba> mhr3, thanks for the pointer
[16:06] <mhr3> spoleeba, cool :)
[16:11] <sil2100> Trevinho: could you help me with something ;)?
[16:11] <sil2100> Trevinho: https://code.launchpad.net/~3v1n0/unity/missing-launcher-icon-fix-5.0/+merge/106644 <- what do you think could be a regression potential here?
[16:13] <spoleeba> mhr3, need to figure out the next bit of the stack that isnt in yet.  i have dbusmenu que'd for review  libindicator just needs a revision bump, dee is in.
[16:16] <mhr3> spoleeba, perhaps check the jhbuild modules we have for unity?
[16:16] <sil2100> seb128: ok, there are like only 4 bugs that need their description SRUable, but besides that we're done - 2 bugs still need verification, but we'll probably have those verified soon
[16:16] <seb128> sil2100, great!
[16:17] <seb128> sil2100, well done, the unity SRU seems going smoothly so far ;-)
[16:18] <sil2100> seb128: thanks - more or less smoothly ;) I also started testing the nux SRU, but we'll probably be done with that around tomorrow...
[16:19] <seb128> sil2100, ok
[16:38] <Trevinho> sil2100: hopefully nothing :)
[16:39] <Trevinho> sil2100: it could happen that an icon is not removed on close...or that this happen with some dealy
[16:39] <sil2100> Trevinho: thanks :)
[16:40] <sil2100> seb128: could you ACK the nomination for https://bugs.launchpad.net/ubuntu/+source/unity/+bug/920258 ?
[16:41] <sil2100> seb128: with this one we're officially done with the SRU bug handling (I hope)
[16:41] <seb128> sil2100, done
[16:41] <sil2100> I'll double check everything tomorrow, but my list shows all bugs modified
[16:41] <sil2100> Thank you ;)
[16:41] <seb128> sil2100, excellent!
[16:42] <seb128> sil2100, wait a few days and check the bugs showing on http://people.canonical.com/~ubuntu-archive/pending-sru.html as non green I guess
[16:42] <seb128> sil2100, in fact they are all green but 2
[16:43] <seb128> https://bugs.launchpad.net/ayatana-design/+bug/987955
[16:43] <seb128> https://bugs.launchpad.net/unity/+bug/987156
[16:44] <sil2100> seb128: yes, those 2 still need verification - one we're still checking, since popey is able to reproduce the problem while it's fine on my system
[16:44] <sil2100> seb128: where the other one seems fine but popey woould like to get some feedback from the design team
[16:44] <sil2100> Since one case is not completely clear
[16:53] <popey> I am happy to set https://bugs.launchpad.net/ayatana-design/+bug/987955 green if someone can confirm the "What should happen" text is accurate seb128
[16:53] <popey> I just held off because it felt a bit odd, but I am not a designer :D
[16:53] <seb128> popey, ok, no hurry, you have a week to find somebody
[16:53] <popey> i have mailed john, will poke him though
[16:53] <popey> nice to have lots of green there
[16:54] <sil2100> ;)
[17:04] <sil2100> Ok guys, see you tomorrow!
[22:41] <bobweaver> Hello I was wondering what the command are or Desktopfile that are being used to "reboot ,shutdown,suspend "  So That I can call them With Unity2d on a launcher thanks
[22:46] <bobweaver> This is why I ask I am adding this to Ubuntu TV or what it is ATM  http://imagebin.org/222016    thanks again
[23:16] <Jake7> I'm not sure if this is the right channel to use, but I'm having a quicklist problem with 12.04 lts. I've saved an app there several times and when I reboot it's gone. Also, if I install it to the quicklist again I can't see it if I try edit the quicklist with ubuntu tweak. It's still there though and functional. That is until I reboot. Any ideas?