[09:24] <micahg> good morning chrisccoulson
[09:25] <chrisccoulson> hi micahg
[09:25] <micahg> I'm testing something to see if there's any difference if i fix that error for nobinonly
[09:25] <micahg> otherwise I have the build2 upload ready to go for natty
[09:25] <micahg> and it builds :)
[09:25] <chrisccoulson> cool!
[09:25] <micahg> at least on everything except for ARM :-/
[09:26] <micahg> will look into that later
[09:26] <chrisccoulson> thanks
[09:26] <micahg> chrisccoulson: only packaging change is to drop the libpixman patch as it landed
[09:27] <chrisccoulson> yeah, that's good :)
[09:50] <micahg> chrisccoulson: yeah, so it's not working...
[09:52] <micahg> ah, I think I got it...trying again
[10:44] <micahg> chrisccoulson: so, I can make the warning go away, but not make the nobinonly script work, I think it's only going one level deep instead of 2, but I don't have any more time tonight to fix it
[10:45] <micahg> chrisccoulson: should I upload the current version to natty now and try for a fix later this week?
[10:46] <chrisccoulson> micahg - yes please, i really need to get those built in the security PPA today
[10:46] <micahg> chrisccoulson: k, will be uploading in a couple minutes
[10:46] <chrisccoulson> thanks
[10:48] <micahg> chrisccoulson: the nobinonly script has been broken since lucid AFAICT so another week won't hurt
[10:53] <chrisccoulson> yeah, that's ok
[10:53] <chrisccoulson> right, couchdb fixed now hopefully :)
[10:54] <chrisccoulson> time for me to get the security uploads done now
[10:54] <micahg> chrisccoulson: cool
[10:54] <micahg> chrisccoulson: 4MB left on upload
[10:54] <chrisccoulson> at least i haven't got to generate a tarball here ;)
[10:54] <micahg> chrisccoulson: yep, glad to help :)
[10:55]  * micahg needs to learn how to generate from a local hg repo :)
[10:55] <chrisccoulson> micahg - i've just been talking to Usul about mozilla bug 595945
[10:55] <ubot2> Mozilla bug 595945 in General "Automatic upgrade causes inbox (only) was overwrited with an empty fájl." [Critical,Unconfirmed] http://bugzilla.mozilla.org/show_bug.cgi?id=595945
[10:55] <micahg> chrisccoulson: I commented about an hour ago
[10:55] <chrisccoulson> he said he's tempted to just close it because there's not really any useful information there
[10:55] <micahg> right
[10:55] <chrisccoulson> and i've got no idea what to do ;)
[10:56] <micahg> well, if the "Inbox" was a local mailbox that got moved, that might have had an affect, but the whole profile should've been gone
[10:56] <micahg> *effect
[11:00] <micahg> and the new migrator should avoid any more problems with TB2 to TB3 upgrade (I hope)
[11:01] <micahg> chrisccoulson: I"m going to send a call for testing for TB3.1 in the security PPA for Lucid
[11:04] <micahg> chrisccoulson: where should I tell people to file bugs for the security PPA?
[11:05] <micahg> chrisccoulson: BTW, I got the archive email, so the tarball's accessible
[11:07]  * micahg is off to sleep will send the call for testing when I get up 
[11:08] <micahg> chrisccoulson: BTW, I also started on teh gnome-shell upgrade to 2.91.3
[11:09] <chrisccoulson> micahg - thanks. i'd talk to robert about that perhaps
[11:09] <chrisccoulson> (sorry, i was off playing with my new phone)
[11:09] <micahg> chrisccoulson: I already asked Robert and Seb and they're not working on it (probably because it's in universe)
[11:10] <micahg> they said they'd help with any missing deps that need to be packaged though
[11:12]  * micahg wants to hear about the new phone later ;)
[13:28] <jdstrand> fta: hi! so that's weird, the maverick/armel build seems to have been retried (I didn't do that). I guess we'll see what happens
[13:28] <jdstrand> mdeslaur: did you do that? ^
[13:29] <fta> jdstrand, yep, we discussed that in #lp yesterday, they restarted half a dozen builds
[13:29] <fta> it's a known bug
[13:29] <jdstrand> I see
[13:29] <mdeslaur> jdstrand: nope, not me
 ScottK, fta, lifeless: it looks like there were some temporary issues scanning builders late yesterday. I'm going to file a bug about this and retry the problematic (half a dozen) builds.
[13:30] <fta> jdstrand, ^^
[13:30]  * jdstrand nods
[13:31] <fta> did it work?
[13:31] <jdstrand> fta: it is still building
[13:31] <jdstrand> 16 hours in
[13:31] <fta> :P
[13:42] <chrisccoulson> jdstrand, i've got most of the mozilla respins uploaded now
[13:42] <chrisccoulson> just doing seamonkey
[13:44] <jdstrand> chrisccoulson: thanks
[13:45] <jdstrand> chrisccoulson: is there a wiki page on the tbird transition?
[13:46] <chrisccoulson> jdstrand, no, i wasn't sure if it was worth creating a wiki page. it's not quite as substantial as the ffox 3.6 update
[13:50] <jdstrand> chrisccoulson: 3.0 to 3.1 has not perfect for someone I know on Windows, but that was a while ago...
[13:54] <chrisccoulson> right, time to carry on hacking on global menu :)
[15:15] <fta> jdstrand, it worked
[15:17] <jdstrand> fta: oh good. I'll test it and push it out hopefully today
[16:20] <bdrung> wiki.ubuntu.com sites have a 1 sec lag with minefield on maverick, but ff on natty works smoothly
[16:55] <chrisccoulson> bdrung, viewing or editing? when did that start? (ie, is this the first nightly build where it happens?)
[16:57] <bdrung> chrisccoulson: viewing. it's not the first nightly build it's there for some days (or weeks?)
[16:57] <chrisccoulson> oh, that makes things difficult ;)
[16:58] <bdrung> chrisccoulson: the lag is caused by 100% cpu load
[16:58] <chrisccoulson> have you used sysprof before?
[16:59] <bdrung> chrisccoulson: nope
[16:59] <bdrung> chrisccoulson: maybe it's caused by a plugin or extension
[16:59] <chrisccoulson> possibly
[17:00] <chrisccoulson> but sysprof is pretty easy to use, it might be worth running that if you can get firefox to use 100% CPU several times in a row
[17:00] <chrisccoulson> but try a new profile first ;)
[17:00] <chrisccoulson> just in case it's something wrong with that
[17:02] <bdrung> chrisccoulson: i disabled all plugins and extensions. then i failed to reproduce the load. i enabled all plugins and extensions, but i still fail to reproduce the load.
[17:03] <bdrung> aha, found the trigger
[17:03] <chrisccoulson> bdrung - nice, heisenbug :)
[17:03] <chrisccoulson> oh?
[17:04] <bdrung> chrisccoulson: go to "group your tabs" and go back. then the tab switching will lag
[17:05] <chrisccoulson> bdrung, you're not an nvidia user are you?
[17:05] <bdrung> even with plugins and extension disabled
[17:05] <bdrung> chrisccoulson: ati
[17:05] <bdrung> using the floss ati driver
[17:06] <chrisccoulson> hmmm, i don't get the issue here
[17:07] <micahg> chrisccoulson: where should I ask the security PPA bugs go?
[17:07] <bdrung> chrisccoulson: i can reproduce it with a new profile
[17:08] <chrisccoulson> micahg - the security PPA bugs should just go to the official package bugs shouldn't they?
[17:08] <chrisccoulson> or did i misunderstand the question? :)
[17:08] <micahg> chrisccoulson: I'm wondering if apport will complain
[17:09] <bdrung> chrisccoulson: how do i use sysprof?
[17:09] <chrisccoulson> bdrung - might be worth reporting a bug upstream about that, but it would be helpful to know roughly when it started
[17:09] <chrisccoulson> bdrung - you can install sysprof from the archive, and it's just a matter of hitting the start button to start profiling
[17:10] <chrisccoulson> then you need to trigger firefox to use lots of CPU, preferable several times in quick succession
[17:10] <chrisccoulson> then when you press the profile button, you'll see a lot of data showing you what your CPU was doing
[17:11] <bdrung> sudo modprobe sysprof-module
[17:11] <bdrung> FATAL: Module sysprof_module not found.
[17:15] <chrisccoulson> bdrung, yeah, you need to actually build the module first
[17:15] <chrisccoulson> did you install sysprof-module-source?
[17:15] <chrisccoulson> i can't remember whether i was offered to build it on install or not
[17:16] <bdrung> chrisccoulson: i build it with sudo m-a a-i sysprof-module
[17:16] <chrisccoulson> hmmm, that should work then
[17:17] <bdrung> chrisccoulson: now i have a profile: http://pastebin.com/EyB9s0H1
[17:19] <bdrung> what does it tell me?
[17:19] <chrisccoulson> i'm not sure yet ;)
[17:23] <chrisccoulson> is it firefox or X that's using all the CPU? it looks like it's Xorg
[17:24] <bdrung> chrisccoulson: it's X - i can't change the application while it lags
[17:24] <chrisccoulson> interesting
[17:24] <chrisccoulson> i think it would be worth reporting this upstream
[17:25] <bdrung> chrisccoulson: upstream bug reporting guidelines?
[17:25] <chrisccoulson> bdrung, https://developer.mozilla.org/en/Bug_writing_guidelines
[21:13] <bdrung> chrisccoulson: i found a bunch of these in the dmesg output: [176590.643408] radeon 0000:01:00.0: ffff8800b1e72800 reserve failed for wait
[21:14] <chrisccoulson> bdrung - interesting, so it could be a driver issue too :/
[21:14] <chrisccoulson> would be nice to figure out what triggers that, but i'm not sure how
[21:14] <bdrung> chrisccoulson: i assume that it's a driver issue (because i can't reproduce it on intel graphic hardware)
[21:16] <chrisccoulson> yeah, those messages do suggest that
[21:23] <micahg> chrisccoulson: do you want to preview my call for testing e-mail to the team ML or should I just send it?
[21:32] <chrisccoulson> micahg - feel free to just send it, i don't think i need to look at it first :)
[21:32] <chrisccoulson> i didn't check if things finished building yet actually
[21:33] <chrisccoulson> i think i flooded the buildd's a bit today
[21:35] <micahg> chrisccoulson: eh, build1 to build2 shouldn't be too noticable anyways
[21:37] <chrisccoulson> it's ok, it's built on all the arch's we care about :)
[21:37] <chrisccoulson> it's still building on ia64, and i don't think anyone cares about that
[21:38] <micahg> err, I forgot to update the locales for lucid...maybe I can get to that before the release is pushed otherwise, I'll just SRU it
[21:39] <chrisccoulson> do they need updating?
[21:40] <micahg> chrisccoulson: we might be able to pick up another language, definitely some string updates
[21:40] <micahg> the one in the PPA ATM will work though
[21:40] <chrisccoulson> yeah, i'm too concerned about that, we can update those after the security update
[21:40] <chrisccoulson> and do lucid + maverick at the same time
[21:41] <micahg> chrisccoulson: the only thing I was concerned about actually was using the maverick package in lucid for the translations since the path changed
[21:42] <micahg> but if your upgrade testing didn't break I guess it's ok
[21:43] <chrisccoulson> well, i use an english locale ;)
[21:43] <micahg> jdstrand: are you planning any non-english upgrade tests?
[21:44] <jdstrand> micahg: I don't normally. I can if there is something you think is broken. but if that is the case, I encourage you to test first ;)
[21:45]  * micahg is thinking it might be safer to just upgrade the existing lucid package to 3.1.2 or 3.1.7
[21:48] <micahg> chrisccoulson: if I have a new package for you in the morning will that be enough time for sufficient staging before releasing to Lucid?
[21:50] <micahg> or should I just wait to see if anyone reports any issues?
[21:59] <jdstrand> fta: are you aware that chromium is now calling pdf files 'dangerous'?
[21:59] <jdstrand> "This type of file can harm your computer. Are you sure you want to download case_Contact.pdf?"
[21:59] <jdstrand> [Discard] [Save]
[22:05] <chrisccoulson> it should be "This type of file can harm your computer if you view it in Adobe Reader" :)
[22:05] <micahg> supposedly Reader has a sandbox in Windows with version 10
[22:05] <chrisccoulson> micahg - i'll test a non-english locale now
[22:06] <micahg> chrisccoulson: thanks, I probably should have a lucid VM set up
[22:06] <chrisccoulson> i'll do that now i've had enough of angry bird ;)
[22:16] <chrisccoulson> micahg - language packs work ok, i just tried french
[22:17] <micahg> chrisccoulson: ok, then I'll just plan to SRU all 3 versions based on the maverick/natty packaging
[22:17] <chrisccoulson> thanks
[22:17] <micahg> thanks
[22:18] <micahg> charlie-tca is happy about TB 3.1.x in Lucid, gives him something to trumpet in the next point release
[22:18] <chrisccoulson> lol
[22:25] <micahg> 10.04.3 will be more fun with FF 4.x
[22:27] <micahg> maybe :-/