[00:20] <micahg> fta2: http://feeds.arstechnica.com/~r/arstechnica/index/~3/0xS052Xf1IU/chrome-team-sets-six-week-cadence-for-new-major-versions.ars
[00:38] <micahg> Mook_sb: do you know how soon they're planning on releasing 3.6.8?
[00:39] <Mook_sb> micahg: hmm. no, I do not. I suppose being on.. yesterday's? meeting might have helped
[00:39] <micahg> Mook_sb: there seems to be a single fix for it, just tagged today
[00:40] <Mook_sb> looking at https://wiki.mozilla.org/Firefox/Planning/2010-07-21, probably near blackhat?
[00:41] <micahg> Mook_sb: hmmm...I saw that, but wouldn't that usually carry all the fixes that we have now on the branch?
[00:41] <Mook_sb> micahg: I have no idea.
[00:41] <micahg> Mook_sb: ok
[00:41] <Mook_sb> hmm, reading the #planning logs it sounds like it may be related to 580874? not sure though, I have no access to any of those things (which is why I feel so free speculating ;) )
[00:43] <micahg> private :)
[00:48] <micahg> Mook_sb: is planning a private channel, or would I be allowed in?
[00:49] <Mook_sb> micahg: it's on irc.mozilla.org, public (otherwise I wouldn't have been able to get in there)
[00:49] <Mook_sb> I think you might be confused - I don't have any special privileges :)
[00:49] <micahg> Mook_sb: oh, yeah, I thought you might :)
[01:02] <micahg> jdstrand: ping
[01:03] <gavin> it's bug 575836, fwiw
[01:03] <ubot2`> Launchpad bug 575836 in ubuntu "Can not connect to wireless networks after upgrade to 10.04 (affects: 2) (heat: 52)" [Undecided,New] https://launchpad.net/bugs/575836
[01:03] <gavin> regression from the fix from mozilla bug 572985
[01:03] <ubot2`> gavin: Error: Error getting Mozilla bug #572985: NotPermitted
[01:04] <micahg> gavin: next time I'll just ping you :)
[01:04] <gavin> feel free, I'm glad to help
[01:05] <micahg> gavin: ok, well, we pushed 3.6.7 to everyone now, so I guess we'll have to rush this out as well
[01:05] <gavin> yeah, probably a good idea
[01:05] <gavin> we're not exactly thrilled about it either! :(
[01:06] <micahg> gavin: you're sure that LP bug is the onethat's fixed
[01:06] <gavin> especially with blackhat just around the door
[01:06] <gavin> no, that's a mozilla bug #
[01:06] <micahg> gavin: yeah, I was hoping for a little breathing room
[01:06] <gavin> I just forgot to add "mozilla"
[01:06] <micahg> gavin: ah, that makes mroe sense :)
[01:06] <micahg> another private bug :)
[01:06] <gavin> you have s-g members, right?
[01:07] <gavin> asac?
[01:07] <micahg> gavin: I think asac is the only one
[01:07] <gavin> is he not around?
[01:07] <micahg> gavin: at a sprint ATM
[01:08] <micahg> gavin: what's the likelyhood of a build2?
[01:08] <gavin> relatively unlikely, given that it's only the one patch and that it's been on trunk for a bit
[01:09] <gavin> are you backporting patches manually?
[01:09] <micahg> gavin: no, we're using the complete release
[01:09] <gavin> I can CC you on the bug, if that helps
[01:10] <micahg> gavin: we finally have all releases on FF 3.6 :)
[01:10] <micahg> gavin: nah, that's ok
[01:10] <gavin> good to hear!
[01:10] <gavin> so you pull our release tags and build yourself?
[01:10] <micahg> gavin: yep, after applying nobinonly
[01:10] <gavin> cool
[01:11] <micahg> gavin: I'll spin the tarballs a little later and once I consult w/chrisccoulson in about 7 hrs I'll upload to the devel release
[02:26] <micahg> jdstrand: ping re mozilla update
[03:52] <micahg> gavin: the bug was a regression of something in 3.6.7, right?
[04:54] <gavin> micahg: yes
[04:57] <micahg> gavin: k, thanks
[07:24] <jdstrand> micahg: yes?
[07:24] <micahg> jdstrand: oh, hi, there was a regression in 3.6.7 and 3.6.8 is being prepared, I was wondering if I should use the same USN and -2
[07:24] <jdstrand> micahg: it is just the one fix?
[07:25] <micahg> jdstrand: yes
[07:25] <micahg> jdstrand: http://hg.mozilla.org/releases/mozilla-1.9.2/rev/fd971f28dfd1
[07:26] <jdstrand> micahg: is this security relevant, or functionality?
[07:26] <micahg> jdstrand: topcrash
[07:27] <jdstrand> micahg: -2
[07:27] <micahg> jdstrand: thanks, I don't know if they'll release today or over the weekend, so I figured I'd have the builds ready for chrisccoulson so that either way we could roll it out
[07:28] <jdstrand> micahg: ok. I won't be able to do much testing cause I'll be on holiday/blackhat, so let me know when you are ready and I will publish
[07:28] <micahg> jdstrand: ok, when is that?
[07:29] <jdstrand> holiday - sat - tue, bh wed - mon
[07:29] <jdstrand> (well, bh/defcon)
[07:29] <micahg> jdstrand: ok, is mdeslaur available so I don'
[07:29] <micahg> t have to bother you on holiday?
[07:31] <jdstrand> micahg: well, he could, but our process doesn't work too well with that yet
[07:31] <micahg> jdstrand: ok, I guess we'll ping you when ready then, thanks
[07:31] <jdstrand> k
[07:33] <micahg> jdstrand: I'm assuming I should use the Hardy/Lucid USN or for Jaunty/Karmic use their USN
[07:34] <jdstrand> micahg: actually, we should split it. hardy/lucid should get 957-2 and jaunty and karmic need 930-5
[07:34] <micahg> jdstrand: got it, thanks
[07:34] <jdstrand> micahg: wait
[07:34] <jdstrand> micahg: 930-6
[07:35] <micahg> jdstrand: k
[07:37] <micahg> jdstrand: I'm assuming xulrunner is sharing the USN?
[07:38] <jdstrand> micahg: yes
[07:38] <micahg> jdstrand: k
[08:02] <micahg> jdstrand: are you at the sprint?>
[08:10] <micahg> hi chrisccoulson
[08:10] <chrisccoulson> hi micahg
[08:11] <micahg> chrisccoulson: there's a crash regression in FF 3.6.7 and 3.6.8 is being prepared
[08:11] <chrisccoulson> micahg, nice!
[08:11] <chrisccoulson> thanks
[08:11] <micahg> chrisccoulson: I have the xulrunner branches updated and I'm ready to push xulrunner to maverick
[08:11] <chrisccoulson> cool, thanks
[08:11] <micahg> chrisccoulson: I wasn't sure what you wanted to do with firefox.head, are all those changes ready for maverick as well?
[08:12] <chrisccoulson> micahg - i'm not entirely sure yet. i'll have a look at it shortly
[08:12] <micahg> chrisccoulson: k, I couldn't prepare the updates for firefox branches for hardy, jaunty, karmic because you have local changes of the latest releases
[08:12] <chrisccoulson> oh, i've not pushed them yet?
[08:12] <micahg> chrisccoulson: nope
[08:13] <chrisccoulson> i'll fix that too then
[08:13] <micahg> chrisccoulson: should I push up xulrunner then and you'll worry about Firefox?
[08:13] <chrisccoulson> micahg - yeah, feel free
[08:13] <micahg> chrisccoulson: k, also USN for Hardy/Lucid is USN-957-2, Jaunty/Karmic USN-930-6
[08:17] <micahg> chrisccoulson: thanks, uploading now, will go to sleep after it's done, I'll rebuild gjs in the morning
[08:17] <chrisccoulson> thanks
[08:18] <micahg> chrisccoulson: monday you'll be back in UK?
[08:20] <chrisccoulson> micahg - yeah, i fly back tomorrow
[08:20] <micahg> chrisccoulson: k, I guess I'm lucky that you're on 2 hrs earlier than normal :)
[08:21] <chrisccoulson> it should only be 1 hour, but i've been starting earlier than normal too ;)
[08:21] <micahg> chrisccoulson: right :)
[08:21]  * micahg needs to start doing uploads on a server with more upstream BW
[11:36] <fta> doh! http://people.ubuntu.com/~fta/ppa-dashboard/ubuntu-mozilla-daily--ppa.html
[11:37] <fta> i guess i need a link and an icon for Chroot problems
[13:30] <jdstrand> chrisccoulson: so, what do you think about removing sqlite3 from the ppa? iirc, it was for some firefox build but we now have it embedded
[13:30] <chrisccoulson> jdstrand - yeah, we should remove that
[13:30]  * jdstrand goes to do that
[13:30] <jdstrand> I've been wanting to get rid of that for ages ;)
[13:31] <jdstrand> chrisccoulson: btw, not sure you noticed, but the ppa is really rather clean atm :)
[13:32] <chrisccoulson> jdstrand, yeah, i just noticed that. thanks!
[13:32] <jdstrand> sure!
[13:33] <jdstrand> chrisccoulson: there were a couple of things in there (like hardy/apturl) that I wasn't so sure about, so I left them
[13:33] <jdstrand> chrisccoulson: btw, is seamonkey ok to go?
[13:33] <chrisccoulson> jdstrand, yeah, 2.0.6 is ready to go for lucid
[13:34] <jdstrand> chrisccoulson: 2.0.5 is still there for the others. what about those?
[13:34] <chrisccoulson> jdstrand, i need to update those to 2.0.6 at some point, and we can push them if i ever get round to testing them
[13:34] <chrisccoulson> but nobody has done any testing on them yet
[13:35] <jdstrand> k
[13:35] <jdstrand> I'll push seamonkey
[13:35] <jdstrand> on lucid
[13:37] <chrisccoulson> thanks
[13:37] <jdstrand> chrisccoulson: seamonkey/lucid is published
[13:37] <chrisccoulson> awesome, thanks!
[13:38] <jdstrand> universe is *way* easier ;)
[13:38] <gnomefreak> do we still need *-gnome-support packages?
[13:38] <chrisccoulson> heh, i wish it was as easy for chromium too ;)
[13:38] <chrisccoulson> gnomefreak, yes, they pull in the gnome dependencies if you don't already have them
[13:39] <gnomefreak> ok because autoremove wants to remove them (under gnome)
[13:39] <chrisccoulson> jdstrand, once i have the mozilla crash reporter working, we'll probably need a corresponding change in the apparmor profile
[13:41] <chrisccoulson> meh, X crashed
[13:42] <chrisccoulson> jdstrand - i get X crashing quite often when i press enter the first time after booting. can i blame the people in the foundations room for that? ;)
[13:42] <gnomefreak> im guessing xul193 is no longer needed
[13:42] <jdstrand> well, I don't think you can blame the security team :)
[13:42] <chrisccoulson> gnomefreak, yeah
[13:43] <jdstrand> chrisccoulson: ack re apparmor
[13:43] <gnomefreak> thanks i thought 3.6.* needed it
[13:43] <chrisccoulson> jdstrand, i don't have it working just yet (firefox doesn't exec the crashreporter when i send it kill -11, but the upstream build works ok)
[13:44] <jdstrand> chrisccoulson: well, testing with apparmor is pretty easy. aa is not enabled by default. to enable, use 'sudo aa-enforce /etc/apparmor.d/usr.bin.firefox'
[13:44] <jdstrand> chrisccoulson: then look in dmesg/kern.log
[13:45] <jdstrand> chrisccoulson: you can see DebuggingApparmor in the wiki too. please run any apparmor changes by me or someone from the security team
[13:52] <dholbach> hi guys
[13:52] <dholbach> is anybody working on fixing thunderbird in maverick? :)
[14:01] <chrisccoulson> ok, i think i've half figured out why the crash reporter doesn't work, we need Enabled=1 in the application.ini
[14:02] <chrisccoulson> but that should happen automatically at build time :/
[14:02] <chrisccoulson> dholbach, what's wrong with TB? we'll be upgrading to 3.1.1 soon ;)
[14:07] <dholbach> chrisccoulson: crashing
[14:08] <dholbach> the whole time
[14:08] <dholbach> I just need to start writing an email
[14:08] <chrisccoulson> dholbach, oh, that's not too good. do you get a stacktrace?
[14:08] <dholbach> I just filed a bug
[14:08] <dholbach> hang on
[14:09] <dholbach> 609131
[14:45] <chrisccoulson> jdstrand - oh, the apparmor profile already lets firefox start the crash reporter (presumably because it is shipped in /usr/lib/firefox-3.6.8)
[16:12] <jdstrand> chrisccoulson: hey-- have you tested the new ff in the ppa yet? I did hardy ff and it seemed fine. I did not test hardy/xul though
[16:12] <chrisccoulson> jdstrand - not yet
[16:12] <chrisccoulson> has it been released by mozilla yet?
[16:12] <jdstrand> chrisccoulson: well, the xul builds got behind something, so they won't be fully built tonight it looks like
[16:13] <jdstrand> or at least not til late
[16:13]  * jdstrand goes and checks
[16:13] <jdstrand> chrisccoulson: not released yet
[16:13] <chrisccoulson> cool, that's ok
[16:14] <chrisccoulson> it will probably be after we've finished for the day ;)
[16:42] <micahg> chrisccoulson: anything I need to worry about over the weekend except for trying to get TB3.1 ready for PPA?
[16:42] <chrisccoulson> micahg - i don't think so
[16:42] <chrisccoulson> i'm not sure we'll get round to publishing 3.6.8 today (mozilla still haven't released it and the xulrunner builds have got stuck behind other things)
[16:43] <micahg> chrisccoulson: k, I figured that if we at least get them up today, people can test over the weekend and we can release MOnday
[16:43] <chrisccoulson> i've got 3.6.8 in maverick now with the crashreporter on
[16:43] <micahg> chrisccoulson: how is it?
[16:43] <chrisccoulson> yeah, it's working now, although it didn't work initially
[16:44] <micahg> BTW, I think dholbach's TB crash is a GTK crash
[16:46] <chrisccoulson> micahg - it's caused by the app-menu
[16:47] <micahg> chrisccoulson: ah, do you have a dupe bug?
[16:47] <chrisccoulson> we need to blacklist thunderbird (we already blacklisted firefox because of the same crash)
[16:50] <micahg> chrisccoulson: BTW, I think apport already has blacklisted thunderbird and firefox on Maverick
[16:51] <chrisccoulson> micahg - it shouldn't be. we'd need to ship a blacklist file for that in /etc/blacklist.d
[16:51] <chrisccoulson> apport won't get firefox crashes now as the mozilla crash handler doesn't re-raise the signal
[16:52]  * micahg recalls seeing something, but it's not in the changelog
[16:53] <micahg> https://edge.launchpad.net/ubuntu/+source/apport/1.14.1-0ubuntu4
[16:54] <chrisccoulson> micahg - that's just for the retracer
[16:54] <micahg> chrisccoulson: ok :)
[16:59] <fishor> hallo all, i currently trying to find out why firefox-4.0 use too match CPU (abou 80% on Core 2 Duo E8400  @ 3.00GHz) by playing  webm videos. I use kernel/perf tools... i getting 88% usage by  libxul.so.  xulrunner-2.0-dbg is installed, but i still can't get any symbols in debug. Please can some body point my, what i missing
[17:00] <micahg> fishor: You need other symbols as well, what release are you on?
[17:00] <fishor> micahg: maverick
[17:00] <micahg> chrisccoulson: ^^ does this also need a blacklist for app-menu?
[17:06] <fishor> are there any ctrick to install all xulrunner dbg pack per one shoot?
[17:11] <micahg> fishor: well, you need the firefox-4.0-dbg as well, plus the GTK debug libs, and maybe a few others depending on the stacktrace
[17:21] <fishor> hmm... i have these, but still no result
[17:22] <fishor> micahg: may be it will be better to just compile it by my self
[17:22] <micahg> fishor: what will that help?
[17:36] <fishor> micahg: jast include debug symbols dircet into binary
[17:40] <micahg> fishor: do you have the glib debug symbols, it seems to be  a problem with the app-menu in maverick
[17:43] <fishor> micahg: i have libglib2.0-0-dbg
[17:43] <fishor> do i need libglib2.0-0-refdbg
[17:44] <micahg> fishor: if you use apport-retrace locally it'll install all you need
[17:44] <micahg> fishor: https://wiki.ubuntu.com/DebuggingWithApportRetrace
[17:58] <fishor> micahg: apport-retrace -o trash _usr_lib_firefox-4.0b3pre_firefox-4.0.1000.crash
[17:58] <fishor> report file does not contain one of the required fields: CoreDump Package ExecutablePath
[18:05] <micahg> fishor: ah, I'd say try to reproduce then
[19:41] <fishor> ok, i found the problem with perf
[19:41] <fishor> it is know perf bug, so there is workasound ro make it see debugsymbols
[19:42] <fishor> and now i see why firefox use so mach CPU time
[19:43] <fishor> it use do not optimised, buildin version of vp8decoder
[19:44] <fishor> now is my question: is it possible to build xulrunner with dynlinced libvpx0