[05:05] <rCX> Hey guys do you think this bug should be reopened because of the last 2 comments?
[05:05] <rCX> https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/372647
[05:05] <ubot2> Launchpad bug 372647 in libsoup2.4 (Ubuntu) (and 1 other project) "Clock and Weather applet don't show any weather info (affects: 8) (dups: 2) (heat: 60)" [Low,Fix committed]
[05:23] <pitti> Good morning
[05:36] <TheMuso> Hey pitti.
[06:52] <didrocks> good morning
[06:53] <didrocks> jcastro: what do you mean "not working"? It has no menu, so I guess that's why appmenu doesn't display anything
[07:21] <didrocks> fta: hey, will you put this switch on (http://feedproxy.google.com/~r/d0od/~3/plXWkjG-jvs/chrome-dev-channel-adds-gnome-keyring.html) ?
[07:54] <RAOF> didrocks, fta: Oooh, cool.  Yes please :)
[07:54] <and471> morning all
[07:54] <didrocks> RAOF: especially the --detect seems safe for all environment
[07:55] <didrocks> hey and471
[07:55] <didrocks> RAOF: how are you? when do you live to Prague?
[07:55] <RAOF> “Live to Prague”.  I like it :)
[07:55] <RAOF> I'm flying out tomorrow morning.
[07:56] <RAOF> I get into Prague at the same time as Luke, and 5 minutes after Robert.
[07:56] <and471> didrocks, hi
[07:56] <and471> RAOF, when is the sprint?
[07:57] <RAOF> Next week / never (if you're a stickler for the “Platform Rally” rebranding ;))
[07:57] <didrocks> leave*
[07:57] <didrocks> grrr, this is the morning and I'm already tired it seems :)
[07:57] <TheMuso> heh
[07:58] <RAOF> didrocks: Don't worry, there's a week of relaxing work coming :)
[07:58] <didrocks> RAOF, TheMuso, robert_ancell: have a safe trip
[07:58] <TheMuso> Thanks.
[07:58]  * TheMuso has the vast majority of things packed.
[07:59] <didrocks> RAOF: did someone lied to you? :)
[07:59] <RAOF> didrocks: That it's going to be relaxing, or that there's going to be work? :P
[07:59]  * RAOF will start packing after work.
[08:00] <didrocks> RAOF: on the relax part ;)
[08:01] <RAOF> :)
[08:02]  * didrocks upgrades his netbook to maverick now that RMLL is finished
[08:06] <fta> didrocks, RAOF: those are runtime switches. See /etc/chromium-browser/default
[08:07] <didrocks> fta: right, but this file is shipped by chromium package, right?
[08:24] <and471> kiwinote, hi
[08:24] <kiwinote> morning and471
[08:28] <and471> kiwinote, you know where mvo is?
[08:29] <kiwinote> and471, no I don't sorry
[08:29] <and471> np
[09:05] <and471> mornin mpt
[09:05] <mpt> hi and471
[09:05] <mpt> and471, the gap between the right edge of the review and Summary fields and the right edge of the dialog should be exactly the same as between the right edge of the "Publish" button and the right edge of the dialog.
[09:06] <and471> mpt, hehe cool
[09:08] <and471> mpt, okay sorted that out
[09:08] <and471> mpt, do you have any idea whether this login and review stuff is going to be in for maverick?
[09:11] <mpt> and471, mvo and I know that it's important for selling stuff, especially, for people to see what other people think of it. It's mainly a matter of getting the server-side stuff sorted out.
[09:12] <and471> mpt, cool thanks
[09:17] <vish> mpt: heya , its friday!!!!!!! :)
[09:21] <vish> SC descriptions, docs mail.. needs reply ;)
[09:28] <rickspencer3> good morning everyone
[09:28] <seb128> hey rickspencer3!
[09:28] <seb128> rickspencer3, how are you?
[09:29] <and471> rickspencer3, mornin
[09:29] <RAOF> Guten morgen, rickspencer3
[09:29] <rickspencer3> I'm ok
[09:29] <rickspencer3> said goodbye to my family this morning, so, a bit lonely
[09:30] <rickspencer3> will be better when I see some good friends on Sunday!
[09:30]  * rickspencer3 wipes tear from eye
[09:30] <rickspencer3> seb128, how are you doing? ready for the sprint?
[09:31] <seb128> I'm fine, sort of ready
[09:31] <didrocks> hey rickspencer3
[09:31] <seb128> I didn't start packing or anything but otherwise I'm ready ;-)
[09:31] <seb128> rickspencer3, will be great to see you on sunday ;-)
[09:31] <seb128> you and everybody else
[09:32] <rickspencer3> hi didrocks
[09:38] <rickspencer3> didrocks, je voudrais une beer si vous plais
[09:38] <rickspencer3> ?
[09:38] <rickspencer3> ^ at all comprehensible?
[09:39] <seb128> rickspencer3, you used an english word but I guess most people understand this one ;-)
[09:39] <chrisccoulson> i understand the bit about beer ;)
[09:40] <rickspencer3> maybe chrisccoulson has "beer" set to auto-alert in his irc client
[09:40]  * micahg thinks he said "I would like a beer please", but it's 3AM here :)
[09:40] <chrisccoulson> rickspencer3, that's quite a good idea actually ;)
[09:40] <chrisccoulson> i wouldn't want to miss out ;)
[09:41] <chrisccoulson> pitti - micahg said you wanted to talk about bug 531719
[09:41] <ubot2> Launchpad bug 531719 in xulrunner-1.9.2 (Ubuntu Lucid) (and 6 other projects) "Eclipse crashes using content assist with libcairo2 1.8.10 (affects: 21) (dups: 4) (heat: 127)" [Undecided,Fix released] https://launchpad.net/bugs/531719
[09:42] <pitti> chrisccoulson: I followed up in the bug
[09:42] <chrisccoulson> ah, i've not read the follow up yet ;)
[09:42] <pitti> chrisccoulson: I wondered why we don't have xulrunner-1.9.2 conflict/replaces 1.9.1, to clean up the old version
[09:42] <pitti> adding the conflict to eclipse seems wrong to me in two different dimenstions
[09:43] <chrisccoulson> pitti - there's no need to. there's no real reason for the 2 versions to conflict (they can co-exist quite happily), and we shouldn't force removal of the old one during the upgrade, as some users might hang on to other xul191 applications we dropped from the archive
[09:43] <chrisccoulson> i think users should keep the choice of whether to remove the obsolete packages
[09:43] <pitti> but then users would keep piling up old xulrunner packages
[09:43] <chrisccoulson> and eclipse should be fixed properly to not use xul191, like we've just had to do for the hardy -> karmic backporting
[09:44] <pitti> I actually wonder why we version them at all
[09:44] <chrisccoulson> pitti - in future, we may want to not version them
[09:44] <pitti> chrisccoulson: fix eclipse> ok, but then adding a conflicts: there would also be wrong
[09:45] <chrisccoulson> but we have to version them for now so that we can have multiple versions installed (ie, when we introduce new versions as a security update, we don't want to have to port the whole archive)
[09:50] <chrisccoulson> pitti - i have another question for you actually
[09:51] <chrisccoulson> if we blacklist an application in apport, does it just stop it from catching crash reports? (ie, can users still submit bugs manually with ubuntu-bug and the apport hook?)
[09:51] <chrisccoulson> we want to blacklist firefox now
[09:51] <micahg> chrisccoulson: are you talking about the crash reporter?
[09:52] <chrisccoulson> micahg - yeah
[09:52] <chrisccoulson> i just want to make sure we can disable apport crash reports for firefox
[09:53] <pitti> chrisccoulson: yes, that only affects crashes
[09:53] <chrisccoulson> pitti - awesome, thanks
[09:53] <pitti> chrisccoulson: you're talking about /etc/apport/blacklist.d/, right?
[09:53] <chrisccoulson> pitti - yeah, that's what i was referring to
[09:54] <pitti> chrisccoulson: (because there's another way to avoid reports which also affects bugs)
[09:55] <chrisccoulson> pitti - ah, ok. thanks. we're going to try enabling the firefox crash reporter in the next upload, so our crash reports go directly to mozilla
[09:55] <pitti> makes sense indeed
[09:55] <chrisccoulson> are any launchpad guys going to be at the sprint next week?
[09:56] <RAOF> I'm pretty sure jml at least will be there.
[09:57] <rickspencer3> chrisccoulson, hmm, they are sprinting right now
[09:57] <RAOF> In fact, isn't the launchpad epic being held there right now?
[09:57] <rickspencer3> oh, yeah, jml should be there for buy something stuff I think
[09:57] <chrisccoulson> rickspencer3, ah, never mind ;)
[09:57] <chrisccoulson> i can discuss things with them another time
[09:57] <rickspencer3> chrisccoulson I've been following bryyce's status, sounds hot there
[09:59] <pitti> I demand a new company requirement that team managers buy ice cream for their team every day when it's > 30 degrees
[09:59] <chrisccoulson> is it > 30 degrees then?
[09:59] <chrisccoulson> that would be awesome!
[09:59] <pitti> wasn't yesterday, but had been two weeks long
[09:59] <chrisccoulson> (the ice cream would be, the heat not so awesome)
[09:59] <pitti> and it's going to be again today, I guess
[10:04] <fta> seb128, hi, /wrt my chromium issue from yesterday, downgrading cairo helped. so it's most probably gtk mis-using the cairo api or something like that
[10:05] <seb128> fta, rather chromium mis-using the cairo api no?
[10:05] <fta> seb128, hm, upstream doesn't seem to think chromium is at fault
[10:06] <seb128> I doubt GTK guys will change anything without a small testcase showing it's a gtk issue
[10:06] <fta> yep, agreed
[10:06] <seb128> knowing that gtk and cairo teams work together
[10:07] <seb128> and gtk guys tracks cairo changes
[10:07] <tydeas> I am having some issues witht the mysql service
[10:07] <tydeas> I can not start it up/
[10:07] <seb128> I would not be surprised if the bug was rather in chromium
[10:07] <seb128> tydeas, hi, wrong channel, try #ubuntu
[10:13] <kiwinote> mpt, fyi I've just filled in that evaluation
[10:21] <mpt> kiwinote, so have I
[10:22] <kiwinote> mpt, great, thanks
[10:34] <and471> mpt, I you are interested http://videobin.org/+1hv/1qy.html (the review button will need to be fixed, it is too big)
[10:41] <mpt> and471, hmmmmmm
[10:41] <mpt> Can you think of a better placement for that error message?
[10:42] <and471> mpt, not really I was just following the spec, but I think it is the best place, as all status messages are situated down there
[10:43] <and471> mpt, btw just noticed that should have an error icon next to it
[10:44] <mpt> and471, the difference is, the only error message that appears there is one that will prevent you from submitting the dialog.
[10:44] <mpt> and471, do we know whether it's the e-mail address or the password that's wrong? Or do we know only that it's either?
[10:44] <and471> mpt, I think having them all there is good as it is unintrusive, otherwise you have a dialog on top of a dialog on top of window
[10:45] <mpt> That's another option, but far from the only option
[10:45] <and471> mpt, we don't know yet, but I want to get it implemented
[10:46] <mpt> and471, how about just changing the primary text: "The e-mail address or password you entered was not correct. Try again."
[10:46] <and471> mpt, I've fixed it so now that error message has an icon
[10:47] <and471> mpt, sure, I will do a screenshot of that, though I fear it wil make the dialog too wide
[10:48] <mpt> and471, either way, the dialog shouldn't get wider during its lifetime.
[10:48] <mpt> (Or change width at all, ever, really.)
[10:48] <and471> mpt, yes
[10:49] <and471> mpt, http://imagebin.org/105537
[10:49] <mpt> and471, I meant the primary text at the top, not any text in the corner :-)
[10:50] <and471> mpt, ah sorry, in addition to the primary text, or in place of?
[10:50] <mpt> As in, "To rate and review software, you need an Ubuntu Single Sign-On account." becomes "Your Ubuntu Single Sign-On account details were not correct. Try again."
[10:51] <mpt> sorry I wasn't clear
[10:51] <and471> mpt, no it was my fault, looking back you said primary text :)
[10:52] <and471> mpt, another option would be to have it below the email field, as the problem stems form there, and also the email field will be focused after the error
[10:53] <mpt> and471, that would make sense if we knew whether it was the e-mail address field or the password field that was the problem. But we don't.
[10:53] <and471> mpt, I am sure that we can implement that though, it is a simple case of checking for it in the backend
[10:54] <and471> mpt, i think we receive an authentication error if the username/password is wrong
[10:54] <and471> mpt, an just a general http error if we failed to contact the server
[10:54] <mpt> sure
[10:54] <mpt> That's why I asked if we know whether the problem is with the e-mail address, or the problem is with the password.
[10:55] <mpt> If we don't know which it is, the error message shouldn't suggest that we do.
[10:55] <mpt> Even its placement.
[10:55] <and471> mpt, http://imagebin.org/105539
[10:56] <and471> mpt, ah I see what you mean, individually which is the problem
[10:56] <and471> mpt, no I don't think we will be able to know that
[10:56] <mpt> and471, nice work
[10:56] <and471> mpt, tell you what instead of me making these assumptions, let me play around with the backend to see what information we can gather
[10:57] <mpt> ok
[11:09] <and471> mpt, with my limited testing, I don't think we can differenciate, however I am going to ask the ubuntu sso guys
[11:12] <and471> mpt, do you know where mvo is today?
[11:12] <mpt> and471, no I don't
[11:13] <and471> :-(
[11:15] <asac> ArneGoetje: whats the hostname of the langpack stuff again?
[11:30] <pitti> asac: macquarie
[11:31]  * pitti has a 'langpack' host for that in .ssh/config
[11:38] <seb128> bah, some xorg libs are not installable it seems, it's breaking builds
[11:38] <seb128> clutter can't be installed on the buildds
[11:40] <seb128> kenvandine, could you push your ido changes? seems you forgot to do it
[11:55] <and471> mpt, I have to go now, but I have told the people I am awaiting an answer from to give the answer to you
[11:56] <asac> thx pitti
[11:57] <mpt> thanks and471
[13:34] <asac> kenvandine: its so damn slow on startup and hangs regularly in maverick ... what is it?
[13:39] <kenvandine> seb128, i pushed them yesterday
[13:40] <kenvandine> seb128, lp:ubuntu/ido
[13:40] <kenvandine> asac, what's slow on startup?
[13:41] <ogra> it
[13:41] <ogra> :)
[13:41] <kenvandine> hehe
[13:41] <seb128> kenvandine, hum, it's trying to pull the lucid one for some reason
[13:41] <seb128> sorry about the noise
[13:41] <kenvandine> ah
[13:41] <kenvandine> no worries
[13:42] <kenvandine> i thought bratsche just finished fixing it for armel, guess he introduced more armel failures
[13:47] <seb128> kenvandine, right
[13:50] <asac> kenvandine: gwibber
[13:50] <asac> i removed the system couchdb
[13:50] <asac> it often doesnt startup at all
[13:51] <asac> now wiped all cache etc. to get it going again, but still slow and hangs regularly
[13:51] <kenvandine> how slow?
[13:51] <kenvandine> it got way faster right before lucid released... 1.7s on my laptop and 3s on my netbook
[13:51] <kenvandine> which i still think it too slow
[13:52] <kenvandine> asac, the plan is to move to sqlite for maverick
[13:52] <kenvandine> but still waiting for ryan to finish that
[13:52] <asac> kenvandine: slow == 30 sec
[13:52] <kenvandine> yikes
[13:53] <asac> thinkpad x61
[13:53] <asac> model name	: Intel(R) Core(TM)2 Duo CPU     L7700  @ 1.80GHz
[13:53] <hyperair> yay sqlite gwibber.
[13:53]  * hyperair can't wait to see the last of desktopcouch
[13:53] <hyperair> miserable memory hogging thing.
[13:53] <asac> now we have to convince others to drop couchdb and soon we can drop the whole mozjs mess from main ;)
[13:54] <asac> beam.smp is bad for my CPU
[13:54] <kenvandine> asac, hehe... yeah
[13:54] <asac> especially in summer when heat is dominating the room anyway
[14:38] <asac> seb128: could you sync orc 0.4.6 from debian/unstable ?
[14:38] <asac> thx
[14:38] <seb128> asac, ok
[14:39] <seb128> asac, done
[14:39] <asac> rock!
[14:40] <seb128> asac, do you need it for something or just review the mir bug?
[14:40] <asac> seb128: lol. is there a MIR?
[14:40] <seb128> asac, hint hint for the mir bug
[14:40] <asac> seb128: we need it because they landed great neon/arm bits after 0.4.5
[14:40] <asac> seb128: yesterday i was down to almost zero MIRs ... i can process it now if you want
[14:40] <seb128> asac, yes, I already promoted it, gstreamer use it instead of liboil
[14:41] <seb128> asac, https://bugs.edge.launchpad.net/ubuntu/+source/orc/+bug/600300
[14:41] <ubot2> Launchpad bug 600300 in orc (Ubuntu) "[MIR] orc (affects: 1) (heat: 216)" [Wishlist,New]
[14:41] <asac> yeah
[14:41] <asac> though i found just a few minutes ago that debian ignored soname break (same as upstream) ;)
[14:41] <asac> -void orc_x86_emit_add_imm_reg (OrcCompiler *compiler, int size, int value, int reg);
[14:41] <asac> +void orc_x86_emit_add_imm_reg (OrcCompiler *compiler, int size, int value, int reg, orc_bool record);
[14:41] <asac> but was ok because its not used in archive atm
[14:42] <asac> at least they track shlibs_ver
[14:42] <asac> so i assume they did that explicitly
[14:42] <asac> (in debian)
[14:42] <seb128> right
[14:42] <seb128> I would assume so
[14:42] <seb128> slomo knows what he's doing
[14:45] <asac> approved
[14:45] <seb128> asac, thanks
[14:54] <didrocks> pitti: I'm looking at your HookUI class in apport and don't find a way to enter a text in a label asking the user to enter free text in a textbox. Does it exist?
[15:01] <pitti> didrocks: no, it doesn't right now, sorry
[15:01] <didrocks> pitti: ok, I'll add an ui.information() and ask for reporting afterwards. Thanks :)
[15:02] <pitti> didrocks: but don't call it information() :)
[15:02] <pitti> input_line or so
[15:02] <pitti> anyway, good night everyone!
[15:02] <pitti> and have a nice weekend
[15:03] <pitti> see you in Prague!
[15:03] <didrocks> pitti: see you in Prague pitti :)
[15:03] <didrocks> and enjoy your week-end
[15:05] <kenvandine> see you soon pitti
[15:06]  * chrisccoulson really should start packing for prague
[15:06]  * kenvandine should too
[15:07]  * kenvandine is going to spend my lunch mowing the lawn... ugh!  hoping it isn't too out of control when i get back from prague 
[15:10] <chrisccoulson> kenvandine, our lawn looks pretty dead because it hasn't rained very much for a while
[15:10] <chrisccoulson> but it started raining a couple of days ago
[15:10] <chrisccoulson> so i expect it will be out of control when i get back ;)
[15:11] <chrisccoulson> i'd much prefer a garden covered in concrete
[15:11] <chrisccoulson> less hassle ;)
[15:12] <kenvandine> chrisccoulson: that is what my dad always said.... "I'm going to pave the yard and paint it green"
[15:12] <chrisccoulson> lol, that's a fantastic idea
[15:12] <chrisccoulson> i really hate any form of gardening
[15:13] <kenvandine> me too...  especially as hot as it is here
[15:19] <kenvandine> speaking of heat... i'm going to take an early lunch break... bbiab
[15:21] <seb128> kenvandine, how is the empathy indicator work going? I'm doing an overview of where we stand for the weekly meeting later on
[15:21] <kenvandine> about 1/2 done
[15:21] <kenvandine> or more probably
[15:22] <seb128> ok, nice
[15:22] <kenvandine> should be done before the sprint is over
[15:22] <seb128> any blocker? or just need to be done
[15:22] <kenvandine> i hope :)
[15:22] <kenvandine> nope
[15:22] <seb128> excellent
[15:22] <kenvandine> smop
[15:22] <seb128> thanks
[15:22] <seb128> chrisccoulson: hey, how are you?
[15:22] <kenvandine> np
[15:22] <seb128> chrisccoulson: I noticed you started on some of the changes for chromium in UNE
[15:22] <chrisccoulson> hi seb128, i'm good thanks, how are you?
[15:23] <chrisccoulson> yeah, i started looking at the xulrunner packaging today
[15:23] <seb128> I'm fine thanks
[15:23] <seb128> so you are mostly done with security updates?
[15:23] <seb128> do you think you will able to catch up with your maverick work from now on?
[15:24] <chrisccoulson> seb128 - i'll give it a good try, but i might struggle to fully catch up ;)
[15:24] <seb128> what is on your plates for the next week?
[15:25] <chrisccoulson> seb128 - not much yet. i need to discuss with people about how we're going to provide the search plugin for baidu, but that's about it really
[15:25] <chrisccoulson> (and trying to catch up with blueprint work)
[15:25] <chrisccoulson> we have a round of mozilla security updates on tuesday too, but the work for those is done already
[15:25] <asac> unless there is a firedrill :-P
[15:26] <chrisccoulson> yeah, hopefully there are no last minute rebuilds ;)
[15:26] <seb128> chrisccoulson: I can see you have the xulrunner changes for chromium, the user account spec and some mozilla items...do you think you will have time for everything?
[15:26] <seb128> chrisccoulson: or should we try to see to get you help on the useraccount one for example
[15:26] <asac> i would suggest to drop user account spec ;)
[15:26] <chrisccoulson> seb128 - i probably won't have time for everything. i can make a start on the user-accounts stuff, but that might be something we could ship in a PPA for this cycle
[15:26] <seb128> asac, why? ;-)
[15:27] <asac> drop as in cover by someone else
[15:27] <seb128> asac, you need to steal chrisccoulson away from us for some of your own tasks don't you? ;-)
[15:27] <chrisccoulson> lol
[15:27] <asac> because i think there is plenty of stuff in general to get all the firefox etc. stuff in shape ... so if i would plan this i would try to give chris some help ;)
[15:27] <seb128> asac, don't even think about it :p
[15:28] <seb128> asac, true enough, that's sort of where I was coming but I wanted to check with him if he agrees, I can understand if he wants to do a bit of something different
[15:28] <seb128> chrisccoulson: we will see to dispatch load from this one at the sprint
[15:28] <asac> sure. but he already works from 1000-0200 ;)
[15:28] <chrisccoulson> yeah, no worries
[15:29] <asac> so thats 100% ;)
[15:29] <chrisccoulson> asac - 4 hours? ;)
[15:29] <asac> lol
[15:29] <asac> 4 hours sleep + 4 hours excersizes like going to the gym etc.
[15:30] <chrisccoulson> lol
[15:30] <asac> and having a beer sometimes
[15:31] <seb128> yeah, we will make sure he gets beers at the sprint
[15:31] <seb128> those will be well deserved
[15:31]  * seb128 hugs chrisccoulson
[15:31]  * chrisccoulson hugs seb128
[15:31] <asac> and with some luck chrisccoulson has to start preparing the next major upgrade in 1-2 month ;)
[15:32] <chrisccoulson> lol
[15:32] <seb128> tremolux, hello
[15:32] <chrisccoulson> hopefully 3.6 will be around for a little bit longer ;)
[15:32] <seb128> tremolux, how are you?
[15:32] <seb128> vish, hey
[15:32] <asac> chrisccoulson: they shoot for 8 month total ;)
[15:32] <asac> but realistically i think we can count on 12 month ;)
[15:32] <vish> o/
[15:33] <tremolux> seb128: hi seb128, I'm doing well thanks, how are you?
[15:34] <chrisccoulson> asac - hmmm, i'm not sure whether we are building FF4.0 with webgl support or not :/
[15:34] <chrisccoulson> it doesn't look like there's a build-option, it's just checking for the glx headers
[15:34] <seb128> vish, I think I read some comments from you on a bug about a murrine issue
[15:34] <chrisccoulson> which we're installing (by build-depending on mesa-common-dev)
[15:34] <seb128> vish, do we need to backport some git changes or update our version?
[15:34] <chrisccoulson> so, i'm not sure if we need to do anything else there
[15:34] <seb128> tremolux, I'm fine thanks
[15:35] <vish> seb128: no need to backport for Lucid , we can just update the git version for maverick
[15:35] <asac> chrisccoulson: fta said that webgl worked for him in our 3.7 builds
[15:35] <asac> he just reconfirmed yesterday
[15:35] <seb128> tremolux, doing weekly status updates for the meeting later on
[15:35] <seb128> vish, I'm trying to remember what bug it was, what is the change doing?
[15:35] <asac> chrisccoulson: but yeah. if the headers only get pulled in implicitly, we might want to make that a top level build depend
[15:35] <seb128> tremolux, https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-opportunistic-apps-stable-release
[15:35] <seb128> tremolux, should some of those items be DONE?
[15:35] <vish> seb128: also , we can wait till the maverick theme release , since that is the one requiring it
[15:35] <seb128> tremolux, ie "implement UI in software center for display of new apps: TODO"
[15:35] <vish> let me find the bug
[15:36] <seb128> vish, do you know what it was about, that should be enough
[15:36] <tremolux> seb128: yes, probably should
[15:36] <seb128> tremolux, can you do that? thanks ;-)
[15:37] <tremolux> seb128: it's just that without the backend in place I didn't consider it fully done, but that's kinda silly I guess
[15:37] <tremolux> seb128: yep, I'll update those
[15:37] <vish> seb128: bug 493762 and  Bug 527789
[15:37] <ubot2> Launchpad bug 493762 in gtk2-engines-murrine (Ubuntu) (and 3 other projects) "Hide or deemphasize shortcut keys in menus (affects: 5) (heat: 38)" [Low,Fix committed] https://launchpad.net/bugs/493762
[15:37] <ubot2> Launchpad bug 527789 in light-themes (Ubuntu) (and 4 other projects) "Restore triangle disclosure widget (affects: 8) (heat: 49)" [Wishlist,Triaged] https://launchpad.net/bugs/527789
[15:37] <seb128> tremolux, if it's not done that's fine, I just want to have those reflecting where we stand
[15:38] <seb128> vish, oh right, thanks, didn't the shortcut one got fixed before lucid?
[15:38] <vish> seb128: kwwii and cimi worked on the theme and murrine so there are some nice new changes waiting for maverick :)
[15:38] <seb128> vish, I've the _ displayed only when alt is active there
[15:38] <vish> seb128: thats the underlines , this is the Accel labels , the "Ctrl+F" , those  stuff in the menus
[15:38] <tremolux> seb128: sure, I'll review them and make updates
[15:38] <seb128> vish, oh ok
[15:38] <seb128> vish, thanks
[15:38] <seb128> tremolux, thanks
[15:38] <vish> np
[15:39] <seb128> vish, I guess I will sort details with kwwii during the sprint next week
[15:39] <tremolux> seb128: sure!
[15:39] <vish> yeah
[15:47] <fta> asac, chrisccoulson: we have mesa-common-dev in build-deps so that configure auto-enables webgl. it's been there since last year
[15:48] <asac> kthx
[15:55] <fagan> mpt: I have the changes I did to the software software sources in a branch but the patch is still not right at the backend but all the ui changes are done. Ill probably have a patch monday.
[15:56] <mpt> fagan, excellent! I was just wondering how you were going
[15:56] <fagan> ive been busy over the past few days so I havent looked at it properly
[15:57] <fagan> its a weird weird program
[15:58] <fagan> But I can deal
[16:03] <seb128> Riddell, could you update https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus for the kubuntu weekly update?
[16:09] <chrisccoulson> asac - i think you asked me to remind you about an e-mail yesterday ;)
[16:11] <asac> chrisccoulson: is the commit already merged to 4.0 ?
[16:11] <chrisccoulson> asac - not yet, i will do that now
[16:11] <asac> cool
[16:14] <seb128> chrisccoulson: what is the status for the firefox sru for the search change?
[16:14] <seb128> chrisccoulson: when do you think that could be ready or landing?
[16:14] <chrisccoulson> seb128 - i've got a working searchplugin here, but we need to discuss on where to ship it
[16:14] <chrisccoulson> that will be happening next week though
[16:14] <seb128> ok, let's sort that next week then
[16:22] <chrisccoulson> hmmm, i can't get firefox sync to work on FF4.0
[16:22] <chrisccoulson> it fails to initialize NSS :/
[16:22] <chrisccoulson> that sucks
[16:26] <and471> mpt, any news?
[16:32] <chrisccoulson> wow, it has just gone very very dark here
[16:33] <mpt> and471, hi, I'm just in the middle of e-mailing you
[16:33] <and471> mpt, ah cool
[16:34] <mpt> but since you're here I don't need to
[16:35] <mpt> and471, 1. https://wiki.ubuntu.com/SoftwareCenter?action=diff&rev2=394&rev1=393
[16:36] <mpt> and471, 2. While doing that, I realized why you'd suggested that the error message about incorrect e-mail address or password should go in the corner -- because that's what I'd already written in the spec. Durrrr me.
[16:36] <and471> mpt, hehe
[16:36] <mpt> That's a case where my July 2010 self disagrees strongly with my February 2010 self.
[16:36] <and471> :)
[16:37] <and471> mpt, okay that all looks good :)
[16:38] <and471> mpt, and I take it no one back to you about distinguishing between the email being incorrect or the password?
[16:38] <mpt> no
[16:41] <mpt> Now to tackle that broken-apt-cache thing
[16:44] <bratsche> kenvandine, seb128: Did you guys say something about more armel compile problems with libido?
[16:45] <seb128> bratsche, yes
[16:46] <seb128> bratsche,
[16:46] <seb128> http://launchpadlibrarian.net/51991787/buildlog_ubuntu-maverick-armel.ido_0.1.9-0ubuntu1_FAILEDTOBUILD.txt.gz
[16:46] <seb128> idoscalemenuitem.c: In function 'ido_scale_menu_item_constructed':
[16:46] <seb128> idoscalemenuitem.c:205: error: cast increases required alignment of target type
[16:46] <and471> mpt, good luck :D
[16:46] <seb128>   GtkAdjustment *adj = GTK_ADJUSTMENT (gtk_adjustment_new (0.0, 0.0, 100.0, 1.0, 10.0, 0.0));
[16:46] <seb128> bratsche, ^ that's the concerned line
[16:46] <bratsche> Ah, okay.  I'll fix that really quick.
[16:46] <bratsche> seb128: Sorry about that.
[16:47] <seb128> bratsche, no worry
[16:54] <kenvandine> bratsche, thx
[17:17] <mpt> and471, the good news is, we don't need that "Items cannot be installed or removed until the software catalog is repaired" alert at all any more
[17:18] <and471> mpt, ah good :)
[17:19] <mpt> and471, https://wiki.ubuntu.com/SoftwareCenter?action=diff&rev2=395&rev1=394
[17:20] <and471> mpt, cool, when you say:
[17:21] <and471> When “Installed Software” is selected and focused, the /!\ icon should be next in the keyboard navigation cycle
[17:21] <and471> mpt, is that just for accessibility?
[17:21] <mpt> and471, yes
[17:22] <and471> mpt, ok I shall try to get that polished over the weekend :)
[17:22] <mpt> awesome
[17:22]  * and471 notes to self it is never a good idea to open 30 evince windows at the same time
[17:26] <mdeslaur> seb128: can I please get gnome-pilot support back into evolution?
[17:28] <seb128> mdeslaur, no
[17:28] <seb128> or talk with didrocks to check why it has been dropped in that build
[17:28] <mdeslaur> seb128: so, I can no longer sync my 1.5 year old phone? :(
[17:28] <seb128> but upstream dropped the code in 2.31 anyway
[17:29] <seb128> well it's dropped in the next upstream version
[17:29] <mdeslaur> seb128: oh, well if that's the case, forget it...thanks
[17:29] <seb128> so I don't really want to invest to fix something which is going to be dropped anyway when we update
[17:29] <didrocks> mdeslaur: upstream and debian dropped it, it's not in a good state
[17:29] <seb128> mdeslaur, I'm surprised anybody still use it
[17:29] <seb128> I though it was buggy and not maintained for years and not working with most modern devices
[17:29] <mdeslaur> seb128: worked great for me :)
[17:30] <mdeslaur> seb128: up until maverick that is :(
[17:30] <seb128> sorry about that
[17:30] <mdeslaur> no problem
[17:30] <seb128> let me know if you find a better alternative to sync your phone though ;-)
[17:31] <mdeslaur> oh! the conduits can be moved to gnome-pilot itself apparently...I'll hack on that
[17:31] <mdeslaur> thanks seb128, didrocks
[17:35] <mpt> And finally for today
[17:36] <mpt> and471, <https://wiki.ubuntu.com/SoftwareCenter#software-item-screen> now shows how I'd like screenshot downloading/launching progress to look, as we discussed earlier
[17:36] <mpt> though I guess that will also require custom GTK work
[17:39] <mpt> I wonder if you could plonk an actual GTK progress bar on top of the thumbnail
[17:39] <mpt> Ideally the GTK theme would automatically present a progress bar as a pie whenever its width ≤ its height
[17:52] <and471> mpt, yeah, well I am trying to get myself acquainted with the appdetailsgtk code so hopefully I can more use in the future ;)
[17:52] <and471> mpt, thanks for that, it makes everything a lot clearer :)
[18:24] <vish> mpt: firefox 4 does the pie thingy
[18:24] <vish> pie progress
[18:26] <mpt> does it now
[18:26] <mpt> where?
[18:27] <and471> mpt, in the tab
[18:28] <and471> mpt: http://cache.gawkerassets.com/assets/images/17/2010/07/500x_load-progress.jpg
[18:29] <mpt> ah, right
[18:29] <mpt> (it's been a while since I've used Firefox heavily...)
[18:29] <and471> mpt, you use chromium?
[18:30] <vish> mpt: yeah , in the tabs http://imagebin.ca/popup/BFMXt6.html
[18:30] <vish> heh , and471 beat me to it :D
[18:30] <and471> vish, YES!!
[18:30] <and471> ;0
[18:30] <and471> ;)
[18:46] <mpt> and471, yes
[18:46]  * mpt -> home
[18:46] <and471> see ya
[18:46] <mpt> Have fun kids
[19:35] <and471> have a good weekend everyone
[20:07] <lamalex> bryce2: is it ok if I steal guickly?
[20:08]  * didrocks waves goodnight, enjoy your week-end everybody and see you (for some of you on Sunday/Monday!)
[20:40] <bryce2> lamalex, sure consider it yours!  just include some credit in there for me in case it gets wildly successful :-)
[20:42] <lamalex> done
[20:42] <lamalex> :)
[20:52] <bryce2> lamalex, excellent, guid luck!