[00:23] <JanCBorchardt> vish, is there already a bug, blueprint or similar poking stick for Launchpad to not send out mails to group members when the bug they are subscribed to through a project has been marked as invalid for it? (tl;dr hundredpapercuts ;)
[00:25] <JanCBorchardt> vish, darn, it’s always that I _really_ think about it only when I already sent the message.
[02:31] <ScottK> JanCBorchardt: Yes.
[02:31] <ScottK> #launchpad is a better channel for such a question though.
[10:03] <klattimer> hey, I'm having a problem with updates in maverick
[10:03] <klattimer> the ubuntu-desktop package wants to remove Xorg
[10:04] <lucidfox> o_O
[10:04] <klattimer> :/ thinking this is a little weird
[10:04] <lucidfox> Could you pastebin the exact output of apt-get?
[10:04] <klattimer> well, ubuntu-desktop wants to remove itself too for some reason
[10:04] <klattimer> lucidfox sure, I'm just updating everything else and doing some installs
[10:04] <klattimer> soon as I've done that I'll provide a paste of the stuff
[10:17] <klattimer> lucidfox: nevermind, on the command line the packages are being held back
[10:17] <klattimer> I was using synaptic to update while I was doing some installs
[10:57] <lucidfox> bug #541756 - OK to close this?
[10:57] <lucidfox> Monochrome icons are basically a feature of Ubuntu indicators, and Liferea uses the messaging indicator
[11:27] <vish> lucidfox: i'd suggest you wait for symbolic icons to land.. app cannot add icons for two different themes
[11:28] <vish> lucidfox: afaik, that would be in gnome3
[12:06] <Tiibiidii> hi, sorry if i ask this here, but it seems the ubuntu channel more closely related to unity
[12:06] <Tiibiidii> where should i report a unity bug?
[12:06] <Tiibiidii> here? https://bugs.launchpad.net/unity
[12:07] <Tiibiidii> or here? https://bugs.launchpad.net/ubuntu/+source/unity
[12:07] <Tiibiidii> the first one is upstream, so it should be better
[12:07] <Tiibiidii> but it seems that only with the second one i can automatically upload my system's information with ubuntu-bug
[12:08] <Tiibiidii> upstream seems to have sligthly more bugs (so, it seems more used and more relevant)
[12:09] <Tiibiidii> downstream seems to have more new bugs... but this may be a symptom that the developers pay more attention to the upstream bug tracker
[12:25] <lucidfox> Tiibiidii> you can link the same bug to both locations
[12:25] <rye> hi all, is there anyone with Acer Aspire One with Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller ? unity does not really start now, (unity:2446): ClutterGLX-CRITICAL **: Unable to make the stage window 0x1a0004f the current GLX drawable - Mesa 7.9-devel implementation error: Bad renderbuffer format: 21 - am I the only lucky one now?
[12:26] <Tiibiidii> rye, njpatel said that the latest graphics updates in maverick wreak havoc with unity
[12:26] <Tiibiidii> (with intel graphics, that is)
[12:26] <Tiibiidii> i've also an intel card and i'm refraining to update
[12:26] <njpatel> yeah, for me it's with anything gl on intel
[12:26] <njpatel> on 945
[12:27] <njpatel> 965, compiz works okay, but clutter fails
[12:27] <Tiibiidii> he wrote that... uh, here he is :) ... hopefully friday it'll be fixed (if i remeber correctly)
[12:29] <Tiibiidii> lucidfox, you're right, but it's more manual work to do :D, and actually i'm not accustomed to link bug in more projects
[12:30] <Tiibiidii> until now i've almost only reported bugs to ubuntu, and tried helping with translation on other projects... but maybe it's time to get a little more experience with these things
[12:34] <rye> Tiibiidii, njpatel thanks for the info
[14:58] <klattimer> davidbarth, kenvandine are either of you aware of any memory leaks currently affecting libdbusmenu-glib?
[14:58] <klattimer> I think I've found some and want to avoid duplicates where possible
[14:59] <kenvandine> klattimer, i am not
[14:59] <kenvandine> tedg, ^^
[15:00] <tedg> klattimer, Hmm, okay.  I'm not aware of any.
[15:00] <kenvandine> tedg, your code never leaks, right?
[15:00] <klattimer> tedg: check out the valgrind log on https://bugs.launchpad.net/indicator-application/+bug/569273
[15:00] <tedg> kenvandine, Of course.  By design.  I just free memory randomly just in case ;)
[15:00] <klattimer> it really seems it's libdbusmenu-glib
[15:01] <tedg> klattimer, Yeah, so ayan has a small GTK program that creates and destroys menus and causes a leak in GTK...
[15:02] <tedg> Not that dbsumenu isn't at fault also :)
[15:02] <klattimer> tedg: ah, that was my second guess
[15:02] <tedg> But, I think that there more than one contributor there.
[15:02] <klattimer> yeah, there's lots of small ones in gtk
[15:02] <tedg> I think it's caused by the fact that no one creates and destroys menus as rapidly as gpm does with that patch.
[15:03] <klattimer> yeah, that's possibly one way to solve it
[15:03] <klattimer> the issue is that it updates frequently
[15:03] <klattimer> although I've heard some noise from your branches you have a signal for menu clicked now?
[15:03] <tedg> I was talking to hughsie a while back and he was saying it depends on the battery firmware how often it updates.
[15:03] <tedg> Which probably explains the variation of folks reporting things on the bug.
[15:04] <klattimer> yeah, that was a bit of a question up in the air
[15:04] <klattimer> so some people's battery goes like crazy updating the menu, others more leisurely but still gpm grows
[15:04] <klattimer> :/
[15:05] <klattimer> maybe we can fix the gpm patch by hooking up to your menu clicked signal, and only updating the menu then
[15:05] <klattimer> it would lessen the impact of the leak
[15:05] <tedg> Or I was thinking just having it update the label instead of rebuilding the whole menu.
[15:05] <tedg> It'd save dbus traffic as well.
[15:05] <klattimer> that's another option
[15:05] <klattimer> I'll look at doing it that way
[15:05] <tedg> The valgrind log is interesting.
[15:06] <tedg> I wonder if there's something of the wrong type so that hashtable isn't getting free'd.
[15:06] <tedg> In theory dbus-glib should do that... but I don't have a huge amount of faith in it.
[15:06] <klattimer> tedg: line number?
[15:06] <tedg> klattimer, The last entry in the valgrind log.  For properties_copy
[15:07] <tedg> It allocated a hashtable which get's passed to dbus-glib.
[15:07] <klattimer> yeah
[15:08] <tedg> No, I think that serialze_menu item has a leak of that hashtable....
[15:08] <tedg> Uhg.
[15:14] <davidbarth> klattimer: hi; thanks for checking that; do you think you could have a patch for maverick still?
[15:14] <klattimer> davidbarth: what's the deadline
[15:14] <davidbarth> ie, should i target that against the 10.10 milestone?
[15:14] <davidbarth> well, the hard FF is this thursday
[15:14] <klattimer> tomorrow?
[15:14] <davidbarth> yes
[15:14] <klattimer> OK, I'll do my best
[15:14] <davidbarth> if the leak is severe, it should be commitable after that, or if not, as an SRU or Natty
[15:15] <davidbarth> klattimer: cool, thanks for your help
[15:17] <klattimer> davidbarth: this is probably fixable now
[15:18] <klattimer> just looking at the code and in theory it's possible
[15:18] <klattimer> oh
[15:18] <klattimer> :/
[15:18] <klattimer> davidbarth: nope
[15:18] <klattimer> it's not fixable quickly
[15:18] <davidbarth> doh
[15:18] <davidbarth> what's the issue
[15:18] <klattimer> adding/removing devices requires a new menu to be created
[15:19] <klattimer> so it's not just a matter of when the battery level changes, change the menu item
[15:19] <klattimer> it all routes through the same portion of code for adding/removing and updating values
[15:19] <klattimer> so the proper fix is to try and fix the libdbusmenu-glib issues, and possibly an upstream bug on gtk
[15:19] <klattimer> davidbarth: bare in mind, the most major memory leaks are already fixed
[15:21] <davidbarth> klattimer: so it's a minor leak
[15:22] <klattimer> davidbarth: in theory it's only minor
[15:22] <davidbarth> klattimer: if a gpm triggers the leak every 10s, how long for it to eat 10M, 100M?
[15:22] <klattimer> 2Mb per hour is as high as I've seen it
[15:22] <davidbarth> so 48MB a day
[15:22] <klattimer> give or take
[15:22] <klattimer> but as tedg says, it's dependent on battery firmware
[15:22] <davidbarth> but for HW that is really verbose
[15:22] <davidbarth> right
[15:23] <klattimer> davidbarth: https://bugs.launchpad.net/indicator-application/+bug/569273 comment #53 has some details
[15:23] <davidbarth> makes sense for an SRU if that can't get into the release within the next 2 weeks (RC)
[15:24] <klattimer> maybe you want to reassign to libdbusmenu-glib for now?
[15:25] <tedg> klattimer, I think there's two bugs.
[15:25] <tedg> klattimer, The one there with the hashtable, but it's in a new function we only started using a lot in Maverick.
[15:25] <klattimer> tedg: in libdbusmenu and gtkmenu?
[15:26] <tedg> klattimer, I think the leak above it in the valgrind log is the same one that was in Lucid, which is the gtkmenu one.
[15:26] <tedg> klattimer, So Maverick made it worse, but it's still a problem :)
[15:26] <klattimer> has the gtkmenu bug been upstreamed yet?
[15:26] <klattimer> do you have details/ayan's test code?
[15:26] <tedg> klattimer, I believe that ayan hadn't found the leak 100% yet.  Just had a small program to exercise it.
[15:27] <klattimer> I could produce a decent valgrind log for upstream to gtk
[15:27] <tedg> I'm not sure where ayan is on that... but certainly helping out there would be good.
[15:29] <tedg> klattimer, Can you double check this for me?  https://code.edge.launchpad.net/~ted/dbusmenu/hashtable_free/+merge/35540
[15:29] <klattimer> sure
[15:29] <tedg> It passes the test suite, so it must be perfect :)
[15:31] <klattimer> in serialize_menuitem
[15:31] <klattimer> tedg: it looks good to me
[15:32] <tedg> Cool.  Thanks klattimer!  One down :)
[15:32] <tedg> A million more memory leaks to go :)
[15:32] <klattimer> well, that'll probably solve the majority of the issue
[15:32] <klattimer> heh
[15:32] <klattimer> tracing memory leaks is sometimes like trying to walk on marbles
[15:34] <klattimer> tedg: the good thing about fixing in libdbusmenu is that we save memory in a lot of apps
[15:34] <klattimer> fixing in gtk would be better wins
[15:36] <tedg> Yup.  The more the code's used, the more each line counts.
[15:37] <tedg> Might be an interesting metric to calculate using something like Ohloh's DB.
[15:37]  * tedg needs interns
[15:40] <klattimer> heh
[15:41] <Paddy_NI> Will indicator-appmenu be available for lucid at all?
[15:42] <tedg> Paddy_NI, We have no plans to backport it, but someone could.  I believe their are packages in the Unity PPA, but I don't believe they're up-to-date.
[15:43] <tedg> there are....
[15:43] <Paddy_NI> Oh that would be nice
[15:43]  * tedg apparently offended mpt with his misuse of "there" :)
[15:43] <Paddy_NI> As far as I can see there will be no need for the gnome-globalmenu project
[15:46] <Paddy_NI> He another question, how much of the gnome global menu code did you use?
[15:46] <Paddy_NI> *hey
[15:50] <tedg> Paddy_NI, Not any, we have a different approach.  Mostly using DBus which they weren't.  So we talked to them to learn about the issues get ideas, but the code sadly wasn't useful.
[15:51] <klattimer> tedg: would be nice of have an "application" menu as part of appmenu
[15:51] <klattimer> i.e. the current application name
[15:51] <klattimer> sort of bold... with window manager functions ;)
[15:51] <klattimer> like a certain fruit company we all know and love
[15:52] <tedg> klattimer, Yeah, we were just focused on getting the menus out for now.  It'd be interesting to do something like that.
[15:52] <tedg> klattimer, Not sure.  It seems like it's a lot of duplication with the File menu in most Linux apps though.
[15:52] <klattimer> it's a massive improvement over globalmenu anyway
[15:53] <klattimer> well, file->quit never makes sense
[15:53] <tedg> The problem is changing applications just sucks.  I think we learned that with appindicators :)
[15:53] <klattimer> yeah, I can see the problems
[15:53] <klattimer> it's just not easy to say "look, this is a great api, and much better interaction, lets all switch"
[15:54] <klattimer> and get people on board that way
[15:55] <tedg> Yeah, unfortunately there's a perception problem we have there.  Where any Canonical project is "not upstream" so therefore people sadly avoid dependencies.  Hopefully that'll change over time :(
[15:56] <Paddy_NI> tedg, Well I for one look forward to trying indicator-appmenu and Unity
[15:57] <Paddy_NI> :)
[15:57] <Paddy_NI> from what I hear the dbus approach is much better
[15:57] <klattimer> Paddy_NI: it is and doesn't rely on deprecated gnome libs
[15:57] <klattimer> so it'll survive the gnome 3 turmoil
[15:57] <Paddy_NI> Excellent
[15:59] <Paddy_NI> Was getting QT applications to work with it very difficult?
[16:03] <tedg> agateau, ^
[16:03] <Paddy_NI> I was also wondering when application indicators land will the top panel in gnome be a little crowded on the netbook edition with the window controls and appmenu?
[16:04] <Paddy_NI> It is just I have not seen a screenshot of this as yet
[16:04] <agateau> Paddy_NI: we have a Qt implementation of dbusmenu and a Qt patch
[16:04] <tedg> Paddy_NI, It depends on how many applications you run :)
[16:53] <jcastro> https://bugs.edge.launchpad.net/ubuntu/+source/tomboy/+bug/627744
[16:53] <jcastro> is anyone available to look at this?
[16:56] <jcastro> klattimer: how's your c# these days?
[16:57] <klattimer> my c# is practically non existent atm
[16:57] <klattimer> haven't used it in 2years
[16:57] <jcastro> k, maybe sense has time
[16:57] <klattimer> but it's all code at the end of the day
[16:57] <klattimer> so if you're hardup assign it to me
[16:57] <jcastro> I'll assign for now but ask for help
[17:00] <klattimer> k
[17:00] <jcastro> heya vish
[17:05] <klattimer> jcastro: if it's any help, i cant reproduce the above bug
[17:05] <klattimer> worksforme
[17:05] <jcastro> it also worksforme
[17:07] <vish> jcastro: hey.
[17:09] <jcastro> vish: if any of your papercutter gang wants to look at #627744 then I won't complain. :D
[17:10] <vish> bug 627744
[17:10] <jcastro> kenvandine: how's your tomboy applet dropdown?
[17:12] <vish> jcastro: hehe , the gang got scattered after the UIF! ;)  but i think lucidfox likes those.. and sense is in hiding :D
[17:12]  * vish tries to find someone..
[17:12] <jcastro> cool, if I see them I'll ping them, but since you're on opposite time zones if you see them ... :)
[17:13] <vish> sure..
[17:56] <ronoc> Cimi: you there ?
[18:20] <Cimi> ronoc: yep
[18:20] <ronoc> hey Cimi, hows it going ?
[18:20] <Cimi> could be better but it's ok ;)
[18:20] <Cimi> thank you
[18:21] <ronoc> good stuff, this bug is annoying me -> https://bugs.launchpad.net/indicator-sound/+bug/632774
[18:21] <Cimi> eheh
[18:21] <Cimi> me too
[18:21] <ronoc> its seems as if the bg colour for ambience is slightly off in contrast to what is use to draw the border of the menuitme
[18:22] <Cimi> the problem is that the GtkDrawinArea seems filled with bg[NORMAL]
[18:22] <ronoc> is that not correct ?
[18:22] <ronoc> should it not be ?
[18:22] <Cimi> I mean
[18:22] <Cimi> I would prefer to have it transparent
[18:22] <Cimi> bratsche: ?
[18:22] <ronoc> ahh its not a biggie
[18:23] <ronoc> i was just hoping to get a quick fix in for tonight
[18:23] <Cimi> maybe he has an idea
[18:23] <ronoc> i think bratsche is at lunch
[18:23] <ronoc> cool
[18:24] <ronoc> bratsche, can you ping me when you are back
[18:25] <ronoc> biab
[18:34] <bratsche> I'm back.
[18:34] <bratsche> ronoc, Cimi
[18:36] <bratsche> Cimi: We can't really fill anything with transparent until we land rgba.  But we need an idea of how to specify rgba colors in the theme, per-widget and per-state.
[18:38] <Cimi> bratsche: ok thank you
[18:38] <bratsche> Cimi: I haven't been following, but is there anything new theming-wise in git master that we should be aware of?
[18:38] <bratsche> Do you know?
[18:38] <Cimi> bratsche: maybe the css thing by carlos garnacho
[18:38] <Cimi> wait a second
[18:39] <bratsche> But has that landed?
[18:39] <Cimi> http://blogs.gnome.org/carlosg/2010/08/23/css-like-styling-for-gtk/
[18:39] <bratsche> Cimi: I updated my patch to add corner resize grips today, btw.
[18:40] <Cimi> cool
[18:40] <bratsche> Cimi: I'll pull down garnacho's branch and look at it.  Ideally I want to be able to specify an RGBA color to background-color or foreground-color properties in the CSS.
[18:40] <bratsche> If it doesn't support that, I'll just add it. :)
[18:47] <ronoc> bratsche, so will I park this bug for now ?
[18:48] <ronoc> i.e. can't be fixed until this rgba stuff lands
[18:49] <bratsche> Uhh.. that doesn't look like an RGBA issue.  That just looks like there are two slightly different colors being themed somewhere.
[18:49] <ronoc> yeah that is what I thought
[18:49] <bratsche> But I dunno.
[18:50] <ronoc> Cimi, ^
[18:50] <ronoc> would it be possible Cimi  that the bgnormal is slightly different in the theme compared against what is actually used to draw the border of the menu
[19:08] <Cimi> ronoc: bratsche simply, the menu background has a horizontal gradient :)
[19:08] <Cimi> it's not a flat bg[normal]
[19:08] <Cimi> while the gtkdrawingarea is a flat bg[NORMAL]
[19:08] <bratsche> Ah, makes sense.
[19:08] <ronoc> ah
[19:08]  * Cimi had to go, leaving irc on anyway
[19:08] <bratsche> No worries.
[21:05] <vish> kenvandine: tedg: seen Bug 636693 ? it has a patch..
[21:05] <kenvandine> i haven't
[21:07] <vish> seems like we are doing it twice there.. would be nice if someone commented on the patch
[21:08] <tedg> vish, No, looking.
[21:09] <vish> thx
[21:43] <Paddy_NI> Hey this is a little offtopic but have any of you read this or had to sign the agreement --> http://aseigo.blogspot.com/2010/09/copyright-assignments-gone-wild-or-why.html
[22:22] <kklimonda> Paddy_NI: it's completely offtopi but I've read it :)
[22:23] <Paddy_NI> Perhaps canonical should rethink how they treat their contributors :)
[22:24] <kklimonda> I disagree but that's my humble opinion
[22:24] <kklimonda> sure, there is a question whether it's a valid copyright assignment at all as it isn't signed in any way.
[22:27] <kklimonda> I haven't had any objections to sign the agreement myself - but then I have a pragmatic view about things and what I care about is getting things fixed and not about who owns the code or what can he do in the future with it.
[23:29] <JanCBorchardt> vish, I actually just came online to ask: »WTF is up with the bug watch updater!?« :)
[23:29] <vish> JanCBorchardt: yeah.. they just turned them on.. :)
[23:30] <nigelb> JanCBorchardt: there was un update
[23:30] <nigelb> so, now it updates importance too
[23:30] <vish> JanCBorchardt: also , re: the lp unsubscribe , there is a bug about that , but no one seems to have reached a consensus how to handle it
[23:31] <JanCBorchardt> vish, nigelb: ah, thanks!
[23:31] <JanCBorchardt> vish, do you have a link?
[23:32] <vish> JanCBorchardt: not sure , but ask in #launchpad or try searching ;)
[23:34] <JanCBorchardt> vish, ok
[23:36] <vish> JanCBorchardt: oh , i havent forgotten the mail either.. :)
[23:38] <JanCBorchardt> vish, this looks like it: https://bugs.edge.launchpad.net/malone/+bug/204980
[23:39] <vish> JanCBorchardt: yup , thats the one :)
[23:39] <devildante> vish, now that's five :p
[23:39] <vish> devildante: fail! ;p
[23:39] <devildante> argh
[23:39] <vish> devildante: this was already in the 3 ;)