[02:05] <kklimonda> gambs: no, it just means the bug isn't in Unity itself - the second task, against ati driver is confirmed
[02:06] <gambs> Yes, I'm just worried that there aren't enough time or resources to get it working.
[02:06] <gambs> Thank-you for answering, however.
[06:55] <gambs> Is anyone around?
[09:15] <klattimer> hmm, launchpad in read only mode...
[09:15] <klattimer> for how long?
[09:16] <vish> klattimer: looks like 1:30 hrs
[09:17] <klattimer> right
[09:35] <gord> vish, what version of mutter/unity do you have?
[09:36]  * vish checks
[09:38] <vish> gord: unity 0.2.22-0ubuntu1~lucid1
[09:39] <vish> hmm , wait , i have weird apt pinning in place , let me correct that
[09:41] <vish> mutter was 2.28.1~git20091208-1ubuntu7
[09:42] <vish> pinned the unity ppa higher now, updating mutter
[10:06] <Cimi> davidbarth: where's ted? :)
[10:12] <vish> gord: yeah , i think that solved the packaging error , but now i get stuck with http://paste.ubuntu.com/476843/ ;)
[10:12] <vish> Bug #578585
[10:14] <gord> vish, oh dear, you have ati :( we don't really have ati chips to build/test with so we end up with more problems with those. can you file a bug against unity with that once launchpad is back online? the output of glxinfo would help a lot too
[10:15] <vish> gord:  #578585 seems to be the bug.. but i'v tried those workarounds and it doesnt help .. :(
[10:16] <vish> gord: but can file another bug, if it helps?
[10:16] <gord> vish, no need for duplicates, but adding any additional info you feel is relavant to the original bug is helpful
[10:17] <vish> yeah , sure
[10:54] <davidbarth> Cimi: hi
[10:54] <davidbarth> Cimi: not up yet, is in a US timezone
[10:54] <davidbarth> Cimi: however Cody is next to me if needed
[10:54] <davidbarth> Cimi: what's up? do you have changes to propose for the Thursday upload window?
[12:22] <klattimer> seb128: I can't seem to get any of the resources to free correctly in this bug, can it be released as-is?
[12:22] <klattimer> https://bugs.launchpad.net/ayatana-ubuntu/+bug/599844
[12:27] <davidbarth> klattimer: whre's the issue?
[12:27] <davidbarth> klattimer: in your patch?
[12:29] <klattimer> if you search for Karl Lattimer
[12:30] <klattimer> then you'll see a commented out chunk at the end of it
[12:30] <davidbarth> ok
[12:30] <klattimer> which is supposed to free the allocated resources
[12:30] <davidbarth> the xklrec
[12:31] <davidbarth> the crash goes down to libxklavier or?
[12:32] <klattimer> davidbarth: well I don't know how to debug it
[12:32] <klattimer> this is another problem
[12:32] <klattimer> I just can't figure out how to launch it so I can gdb/valgrind or even g_print
[12:32] <klattimer> if I kill it, I can't relaunch it because of some dbus error
[12:32] <klattimer> it's not fun :/
[12:48] <davidbarth> klattimer: one thing, the lbl_title, you can't free it as it's referenced in the label you passed to app_indicator_set_label; you'd need to g_strdup it
[12:48] <davidbarth> klattimer: but then app_indicator would leak it atm
[12:48] <klattimer> davidbarth: tedg said it should be ok to free it
[12:49] <davidbarth> klattimer: according to the code i see it should not, as the string is not dup'ed, and passed directly in the g_object structure
[12:49] <klattimer> ok, but the thing is, regardless of whether or not I free that string
[12:49] <klattimer> it still crashes
[12:49] <davidbarth> klattimer: have you tried free'ing anything else, because if that last string is the only one that crashes, we can live with it for a few days
[12:49] <klattimer> I went through each free and commented them out bottom to top, rebuilt and test
[12:49] <davidbarth> time for ted to review the string lifecycle for that prop
[12:49] <klattimer> and it wasn't until all of them were commented out that it worked
[12:49] <davidbarth> buh....
[12:50] <klattimer> yeah, so basically any of those free's or unrefs will cause a seg fault
[12:50] <klattimer> :/
[12:50] <klattimer> and I can't find a way to launch it in a debuggable way
[12:50] <davidbarth> does a test app using just the xkl code allow you to extract an entry, print it, and dispose everything else after that?
[12:50] <davidbarth> klattimer: ie, is there something weird in the parts of the xkl wrapper that you forgot?
[12:51] <seb128> kamstrup, how much does that leak?
[12:51] <seb128> ups
[12:51] <seb128> klattimer, ^
[12:52] <seb128> kamstrup, sorry wrong completion
[12:52] <kamstrup> seb128, no worries, happens to me all the time :-)
[12:52] <klattimer> seb128: shouldn't be much
[12:52] <seb128> klattimer, we can get it with a small leak and a bug to remember working on that before maverick as well
[12:52] <klattimer> davidbarth: I'd have to create a self confined test case with the code in it
[12:53] <klattimer> k
[13:01] <andreasn> JanCBorchardt_, meeting now?
[13:02] <davidbarth> klattimer: what seb128 said, let's go ahead with that, just open a bug to track the remaining issue then
[13:02] <JanCBorchardt_> andreasn, yep
[13:02] <andreasn> where?
[13:07] <aday> mpt: ping!
[13:08] <klattimer> davidbarth: can that bug be assigned to canonical-desktop-team then?
[13:08] <klattimer> I can't reassign it
[13:48] <davidbarth> klattimer: ok, will do
[17:46] <bratsche> davidbarth, tedg: Can one of you review this once the patch updates?
[17:46] <bratsche> https://code.launchpad.net/~bratsche/appmenu-gtk/correct-key-value-pair/+merge/32468
[17:49] <tedg> bratsche, done
[17:50] <bratsche> Thanks tedg