[00:02] <chrisccoulson> micahg - i'm not too sure what happens after the sessions at UDS, this is my first time ;)
[00:02] <chrisccoulson> brb, need to recover hard disk again :(
[00:02] <micahg> chrisccoulson: really, cool
[00:05] <micahg> chrisccoulson: one more more thing to discuss when you get back
[00:28] <micahg> chrisccoulson: you back?
[00:29] <chrisccoulson> micahg - i am
[00:29] <chrisccoulson> that took a while to recover my laptop this time
[00:30] <micahg> chrisccoulson: k, so Seamonkey is experiencing a bug with xul191, I just requested landing on the branch, it basically causes it to crash under some circumstances.  It's an issue with cairo 1.8.10 and xul191, so I'm wondering if it's something worth SRUing or if the release next week is soon enough
[00:31] <chrisccoulson> the release next week is probably soon enough
[00:32] <micahg> chrisccoulson: I think we have 2 or 3 reports already, I figure, if it can land on 1.9.1.11 before release, we can include it as a patch, otherwise, I think we have to use in source cairo + our LCD patch
[00:36] <chrisccoulson> hopefully we don't have to go down that route, as that's quite a big change in the stable release
[00:37] <micahg> chrisccoulson: yeah, I figured that
[00:39] <micahg> chrisccoulson: should I prepare stable branches for Seamonkey for the security PPA (Hardy, Jaunty, Karmic)?
[00:40] <chrisccoulson> yeah, can do. that should be a fairly simple update, as it doesn't require updating anything else on the system
[00:43] <micahg> chrisccoulson: k, so, those you can probably push to security PPA tomorrow, I guess 2.0.5 in Lucid with the crash issue isn't any worse than 2.0.4, so you can probably push that too
[00:43] <micahg> chrisccoulson: so, you tag each release as released, but edit the changelog if changes are necessary?
[00:44] <chrisccoulson> micahg - yeah, that's what i've been doing for the stable branches
[00:45] <micahg> chrisccoulson: k, but what about Seamonkey, since we have to spin again once it's released, should we tag still?
[00:45] <micahg> chrisccoulson: I was going to append, ~pre1 to each of the builds for Seamonkey then after release, we can remove that
[00:46] <chrisccoulson> ah, good point. we should probably tag those too if we're going to release them in the PPA
[00:47] <micahg> chrisccoulson: I was also wondering if we need to push the after release builds to PPA since, if we push straight to archive, they'll be available sooner for i386/amd64 (won't have to wait for all arches before pocket copy)
[00:48] <chrisccoulson> that's true. the advantage with pocket copying though is we avoid version skew between arches, which is a problem when a package has some arch all binaries
[00:49] <chrisccoulson> that tends to confuse users, as they can end up with a 2 hour period where they have an uninstallable package
[00:49] <chrisccoulson> (assuming 2 hours is the frequency of the publisher runs)
[00:50] <micahg> chrisccoulson: ok
[00:50] <micahg> well, builders probably won't be too busy anyways, so it'll only be 8hrs after release or so
[00:50] <chrisccoulson> yeah, the builders aren't doing much at the minute
[00:51] <micahg> ah, 5 hrs, armel is the longest build
[00:51] <micahg> so that's not too bad
[00:52] <micahg> chrisccoulson: I might be able to get the list early and have the branches ready locally to push after release with the new changelog
[00:53] <chrisccoulson> the release is going to happen at UDS next week isn't it?
[00:53] <micahg> chrisccoulson: yep :)
[00:53] <chrisccoulson> heh, perfect timing ;)
[00:54] <chrisccoulson> at least with the ff364 update, it's just a case of pocket copying it to -security now
[00:54] <micahg> but it's usually evening UTC when it's released, so it'll be after teh sessions are done for the dat
[00:54] <micahg> *day
[00:54] <chrisccoulson> during the beer drinking session s;)
[00:54] <micahg> heh
[00:55] <micahg> chrisccoulson: yeah, but we need to do stable updates as well as ff35 will be released the same day and ff30 will be vulnerable
[06:47] <micahg> chrisccoulson: sorry, will have to finish up SM stuff in the morning, fading fast
[08:55] <BUGabundo_remote> triim triim, triim triim
[09:58] <DASPRiD> anyone playing quakelive and noticing segfaults of firefox when trying to join a game?
[11:25] <BUGabundo_remote> fta: FYI http://code.google.com/p/chromium/issues/detail?id=43408
[15:16] <micahg> chrisccoulson: I'm testing the SM2.0.5 tarball now
[16:15] <micahg> chrisccoulson: seamonkey is building now
[16:15] <micahg> locally
[16:19] <chrisccoulson> excellent :)
[16:29] <sebner> micahg: another TB related question, my old TB (already 0.3.x but just before the fresh-install) automatically limited my writing to 80chars when composing a mail. Just noticed that this isn't the case now
[16:33] <fta> BUGabundo_remote, pushed your bug to the devs a few minutes ago, you already have a fix
[16:33] <micahg> sebner: I think that's a setting somewhere
[16:33] <micahg> but weird that it would change like that
[16:33] <sebner> micahg: bah, just problem with a clean install :P
[16:33] <sebner> *problems
[16:33] <BUGabundo_remote> fta: fix?
[16:34] <fta> BUGabundo_remote, there's a patch in the review queue now
[16:34] <micahg> sebner: I can look for the setting later if you want
[16:34] <fta> BUGabundo_remote, it's trivial, so it should land quickly
[16:34] <sebner> micahg: would be nice, I'll search myself for now and let you know if I find it so you don't waste your time
[16:35] <BUGabundo_remote> fta: great
[16:35] <BUGabundo_remote> it keeps blowing my session :(
[16:35] <micahg> sebner: will you be at UDS?
[16:36] <sebner> micahg: unfortunately not, no time - no money .. sebner = poor student :D
[16:36] <micahg> jcastro: if I subscribed, but participation isn't required, do I have to show up to the session?
[16:37] <jcastro> no
[16:38] <micahg> k, because I subscribe to 2 sessions at the same time and one of them I'm running :)
[16:42] <micahg> my typing is getting worse
[16:58] <fta> *sigh* i wanted to run the js benchmarks on all the builds of chromium beta, but launchpad no longer has them :(
[17:00] <fta> not even the source tarballs, oh my, this is useless
[17:21] <micahg> chrisccoulson: SM2.dev (head) and SM2.lucid branches pushed
[17:24] <micahg> chrisccoulson: should I make SM2.hardy, .jaunty, .karmic on my way in to $WORK?
[17:24] <chrisccoulson> micahg - yeah, feel free to do that if you get the chance
[18:19] <DASPRiD> can it be that this bug is related to some firefox update? http://www.quakelive.com/forum/showthread.php?p=357899#post357899
[18:22] <Mook_sb> DASPRiD: what version of firefox?
[18:23] <DASPRiD> 3.6.3
[18:24] <DASPRiD> thanks for the reminder, adding that to the bug report there
[18:28] <DASPRiD> Mook_sb, looking into it?
[18:29] <Mook_sb> DASPRiD: not really, but I know it's information useful for whoever does (because 3.6.4 has crazy out of process plugins if I remember correctly)
[18:29] <DASPRiD> wasn't that 3.7?
[18:30] <Mook_sb> no, see https://wiki.mozilla.org/Releases/Firefox_3.6.4
[18:31] <DASPRiD> i see
[18:34] <DASPRiD> oh
[18:34] <DASPRiD> https://bugzilla.mozilla.org/show_bug.cgi?id=559704
[18:34] <DASPRiD> that bug is known
[18:36] <DASPRiD> Mook_sb, when did firefox 3.6.3 get into lucid? with the release or later?
[18:37] <Mook_sb> DASPRiD: I have no clue - I just hang around here, I don't even really use ubuntu :p
[18:37] <DASPRiD> lol :P
[18:37] <DASPRiD> shame on you :)
[18:45] <chrisccoulson> ff3.6.3 has been in lucid since release
[18:45] <chrisccoulson> and you can test ff3.6.4 by downloading it from https://edge.launchpad.net/~ubuntu-mozilla-security/+archive/ppa
[18:46] <chrisccoulson> ^^ Mook_sb / DASPRiD
[18:50] <DASPRiD> ah, hm well i wait ;)
[18:50] <DASPRiD> or…... maybe i try it in a few minutes ;)
[19:00] <DASPRiD> chrisccoulson, i wonder, are there 64 builds of firefox i can just download and put somewhere, so that i do not disturb my package managment?
[19:00] <chrisccoulson> DASPRiD, why not just use the PPA?
[19:00] <DASPRiD> it upgrades my existing firefox then, right?
[19:01] <chrisccoulson> DASPRiD, yeah, that's right
[19:01] <DASPRiD> is it already a branded version with language packs?
[19:02] <chrisccoulson> it is a branded version (it's the version that will be copied to lucid-security next week after the official 3.6.4 release)
[19:02] <chrisccoulson> assuming there are no issues from testing
[19:02] <chrisccoulson> the security updates sit in that PPA for testing until the official mozilla release, and then they are copied in to the archive
[19:02] <chrisccoulson> so don't be afraid of using them ;)
[19:03] <DASPRiD> aha! ^^
[19:03] <DASPRiD> i always thought that security ppa is unbranded
[19:04] <chrisccoulson> no, the security PPA is where we host what will likely become the official security updates
[19:05] <chrisccoulson> but the current 3.6.4 in the PPA now is almost certainly going to be the one that is rolled out next week (i don't see us doing any more updates)
[19:05] <DASPRiD> tho 3.6.4 is also a feature update ;)
[19:05] <chrisccoulson> it is
[19:05] <chrisccoulson> but that's going to be the case more and more with mozilla updates
[19:07] <DASPRiD> alright, lemme check if 3.6.4 still crashes with quakelive
[19:07] <chrisccoulson> you're running 64-bit aren't you?
[19:07] <DASPRiD> i am
[19:08] <DASPRiD> why do you ask?
[19:09] <DASPRiD> hm nope, the bug is still present in 3.6.4
[19:09] <chrisccoulson> you're mostly unaffected by the OOPP support, as long as you're using flash and nspluginwrapper from the archive
[19:10] <chrisccoulson> it's only currently enabled for the standard flash player
[19:10] <DASPRiD> i'm using 64 bit flash plugin
[19:10] <DASPRiD> but i also tried to uninstall flash completly, still same crash
[19:12] <chrisccoulson> well, that's ok for now as long as you don't notice any regressions from 3.6.3 -> 3.6.4 ;)
[19:13] <DASPRiD> i would prefer progression… :P
[19:17] <DASPRiD> chrisccoulson, but well, the lucid upgrade was kinda… bad… usually i have more minor bugs, but now i have three serious ones, quakelive not working, compiz/xorg + nvidia have high cpu usage and video playback stutters (probably due to pulseaudio issues)
[19:17] <chrisccoulson> i'd suspect that the compiz/xorg high cpu and video playback issues are all video driver problems
[19:18] <chrisccoulson> and the firefox crash is more than likely a plugin issue
[19:19] <DASPRiD> the video plackback thing is a bit strange… one thing is: in the first 3 days after lucid upgrade, quakelive worked, when whatching a video, it was stuttering, when i played quakelive afterwards, the sound had a delay of about 2 seconds until i killed pulseaudio and restarted it
[19:19] <DASPRiD> that bugs me even more, that quakelive was already working on lucid with 3.6.4 and suddently stopped working yesterday
[19:19] <DASPRiD> that makes me feel that it isn't a firefox issue
[19:21] <chrisccoulson> yeah, nothing has changed in firefox since a few days before release
[19:22] <DASPRiD> nor has the quakelive plugin changes
[19:22] <DASPRiD> hm, what about that one there? http://www.quakelive.com/forum/showthread.php?t=49471
[19:22] <DASPRiD> 0x00007ffff7ddaae3 in ?? () from /lib64/ld-linux-x86-64.so.2
[19:22] <DASPRiD> what is that file?
[19:23] <chrisccoulson> thats part of glibc, and almost certainly not of any use in helping diagnose the problem
[19:23] <DASPRiD> darn
[19:25] <DASPRiD> interesting,m i deleted the quakelive folder, and it redownloaded the game content, now it works again
[19:28] <DASPRiD> alright, two problems to go ;)
[19:33] <chrisccoulson_> bah, my laptop has ground to a halt
[19:33] <chrisccoulson_> i may as well try out quakelive on my desktop instead ;)
[19:45] <DASPRiD> chrisccoulson, hehe
[20:40] <micahg> chrisccoulson
[20:40] <micahg> oops
[20:41] <micahg> chrisccoulson: seamonkey branches are ready, but not tagged for stable releases, I test build lucid and hardy
[20:42] <micahg> chrisccoulson: I'm not sure if we need a new version of devscripts or not for seamonkey
[20:42] <micahg> *mozilla-devscripts
[20:55] <micahg> chrisccoulson: I also started on teh SRU for gnome-shell
[22:25] <ddecator> micahg: did you ever figure out if the "Report broken website" option was taken out on purpose?
[22:30] <micahg> ddecator: no
[22:30]  * micahg forgot
[22:31] <micahg> ddecator: poke me later
[22:31] <ddecator> micahg: alright, no problem, i've got other stuff to work on in the meantime, i just saw the bug in my inbox and thought i'd ask
[23:04] <BUGabundo> LOLOLOL @ darth vader http://www.youtube.com/watch?v=2ljFfL-mL70&feature=player_embedded
[23:26] <ddecator> micahg: hm, is firefox supposed to offer the ubuntu language packs alongside its own installed languages when spellchecking (bug 576360) possibly a regression from bug 66015?
[23:35] <micahg> ddecator: no, it uses system dictionaries, the thing is Firefox is fixed, so it's no longer a Firefox issue, we need to clean that up for Maverick
[23:35] <micahg> ddecator: or rather, Firefox has done all they are willing to do for the issue :)
[23:35] <micahg> s/Firefox/Mozilla/
[23:35] <ddecator> micahg: gotcha. so what should i do with the report?
[23:36] <micahg> ddecator: low/triaged, tracking bug for multiple dictionaries
[23:36]  * micahg thinks using the old one is like beating a dead horse, note the old bug and explain that Mozilla fixed their end
[23:37] <ddecator> micahg: er, track which bug?
[23:37] <micahg> ddecator: track the need to fix the multiple dictionaries
[23:37] <micahg> the issue is symlinks on the system
[23:38] <micahg> ddecator: we need a dictionary audit
[23:38] <micahg> ccheney: are you going to be at UDS?
[23:39] <ddecator> micahg: ok, i understand the issue, but are you saying to track another report?
[23:39] <micahg> ddecator: well, the bug can be used to track the cleanup of the dictionary packages
[23:40] <ddecator> micahg: ok, so is there anything i need to do on the report for that?
[23:40] <micahg> ddecator: nope, just note it
[23:42] <ddecator> micahg: ah, alright, got it. thanks. and one more quick question: firefox honors the gconf settings for whether it should show icons or not, but only after a restart. is that something that could be made instant? (bug 424711, not sure if i should just close it)
[23:47]  * micahg is looking
[23:48] <micahg> chrisccoulson: ^^^ do you know if this is supposed to be immediate or after restart?
[23:48] <micahg> ddecator: I remember there was a bug for when that was fixed so it would work, but I don't know about this one point
[23:49] <ddecator> micahg: alright
[23:49] <chrisccoulson> micahg - it should update immediately really
[23:50] <micahg> ddecator: k, do you have the original bug where it was fixed, you can see if there's a bug blocking it on b.m.o
[23:50] <micahg> ddecator: otherwise, I'll look later
[23:50] <micahg> ddecator: so, mark the bug confirmed
[23:50] <ddecator> micahg: i'll take a look after i respond to the rest of the bugs in my inbox