[12:28] <asac> gnomefreak: yeah ... now gnash is the future ... which i do :)
[12:28] <gnomefreak> asac: i think it would be a good idea. only problem is the bugsquad wont like that a bit
[12:28] <asac> bugsquad is pretty unorganised
[12:28] <asac> i mean ... i really would love to see them contribute to our initial triaging
[12:28] <gnomefreak> yeah well im not happy with some of them for all kinds of reasons
[12:29] <asac> actually i hope that on the long run they can do most of the basic triage
[12:29] <asac> gnomefreak: what is the problem with bugsquad in your opinion?
[12:29] <gnomefreak> this weekend i will look at wishlists and make a list if your not here for you to ack or reject if i feel they get a chance
[12:30] <asac> i mean we see little contribution from them on mozilla packages
[12:30] <asac> ... even less if you just count the contributions that make sense somehow
[12:31] <asac> why is it that way?
[12:31] <asac> is it because we assign bugs to mozilla-bugs?
[12:31] <gnomefreak> asac: well the people that triage our bugs in past not knowing not caring, one of the heads not pushing iceape because IT WILL bring in more bugs. that IMHO is not an open mind just no more bugs is best and i feel that it will add to him/them rejecting mozilla bugs just because theres too many
[12:31] <asac> bugsquad is not responsible for iceape non-push
[12:31] <gnomefreak> the lack of docs pointing to us (unless that has changed recently)
[12:31] <asac> i will raise the iceape issue
[12:32] <gnomefreak> asac: seb is and he is head of bugsquad not
[12:32] <gnomefreak> now
[12:32] <asac> its getting ridiculous ... i mean the debian NEW queue has more momentum then our
[12:32] <Admiral_Chicago> gnomefreak: what do you mean docs?
[12:32] <gnomefreak> Admiral_Chicago: the bugsquad docs not poiinting to our pages on how to triage
[12:32] <asac> gnomefreak: i agree on the docs
[12:32] <gnomefreak> i havent looked recently so if it has changed than kill that comment
[12:33] <Admiral_Chicago> oh yea we can change that, that is something I can talk to Daniel about
[12:33] <asac> that might be improvable ... however i doubt that existing bugsquad members read the docs regulary ... searching for updates
[12:33] <gnomefreak> Admiral_Chicago: i had added our page to one of thiers before and it was taken down
[12:33] <asac> how can we reach bugsquad? is there a dedicated mailing list?
[12:33] <Admiral_Chicago> asac: sec, i'll get the link
[12:33] <gnomefreak> yeah ill get it for you
[12:34] <Admiral_Chicago> ubuntu-bugsquad@lists.ubuntu.com
[12:34] <asac> good ... is that the list where all bugs are going?
[12:34] <asac> i guess noone is subscribed to that :)
[12:34] <gnomefreak> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad-announce
[12:34] <gnomefreak> Admiral_Chicago: that is bugs i think
[12:34] <gnomefreak> it says high volume near it
[12:35] <asac> no messages posted to -announce
[12:35] <asac> hmmm ... not much activity on that list
[12:35] <gnomefreak> it looks new
[12:35] <asac> are bugsquad members automatically subscribed?
[12:35] <gnomefreak> i dont even remember it
[12:35] <gnomefreak> no
[12:35] <asac> gnomefreak: no i mean the ubuntu-bugsquad list even
[12:35] <Admiral_Chicago> gnomefreak: that foes to the whole bugsquad
[12:35] <Admiral_Chicago> asac: no
[12:36] <asac> Admiral_Chicago: hmmm ... so we cannot reach them through that list ;)
[12:37] <gnomefreak> the one Admiral_Chicago gave you was the comment one
[12:37] <gnomefreak> not sure wha tthe new one is for
[12:37] <asac> maybe going through current bugsquad wiki documentation and analyzing if we can at least improve our presence there is the only thing we can do for now
[12:37] <Admiral_Chicago> we could but it wouldn't give you all of them. it'll give you the ones that care enough to sign up (likely the most active ones)
[12:38] <asac> Admiral_Chicago: ok ... so maybe announcing there might be effective
[12:38] <gnomefreak> pretty much pm the heads if you need them
[12:38] <Admiral_Chicago> asac: i think so
[12:38] <gnomefreak> daneil and seb should be gone tonight already
[12:38] <Admiral_Chicago> asac: at the very least, we can get a great deal of discussion going about what we need
[12:38] <asac> seb is on holiday
[12:38] <gnomefreak> thats right
[12:38] <gnomefreak> all week?
[12:39] <Admiral_Chicago> i'm off to meet up for some hacking. be back around 3 UTC i think
[12:39] <asac> Admiral_Chicago: so you say we should just start discussion by asking how we can better work together?
[12:40] <asac> gnomefreak: i mean through ML
[12:40] <gnomefreak> its the bugsquad list he gav eyou
[12:40] <asac> if anyone posts to bugsquad about that ... please CC me :)
[12:40] <asac> yea
[12:40] <asac> h
[12:40] <Admiral_Chicago> asac: yes. come out directly and ask what we want but ask for concenses...
[12:40] <Admiral_Chicago> bbl.
[12:41] <asac> ok ... i am out for today
[12:41] <gnomefreak> k night
[12:41] <gnomefreak> tbird is still building
[12:41] <asac> thanks
[12:41] <asac> cu
[03:27] <gnomefreak> repo is going down sometime tonight. i dont forsee me uploading it all tonight
[04:55] <gnomefreak> Admiral_Chicago: can you email me davids email address i will write up email tomorrow. asac i started on the forums post but im not happy with it (its late) i will post it somewhere tomorrow if you remind me and we can work on the rest of it. anyone interested in being a team contact let me know. people will ping you email you about membership or just with questions (mainly from forums users) i need one or 2 other people i have m
[04:55] <gnomefreak> im gone for tonight its already 11 pm
[04:55] <gnomefreak> repo is back up with new tbird 2.0.0.4 rc1
[08:29] <hjmf> morning!
[08:29] <hjmf> asac: bug 116421
[08:29] <ubotu> Launchpad bug 116421 in firefox "firefox shell breaks "profile" option" [Medium,Fix released]  https://launchpad.net/bugs/116421
[08:31] <hjmf> shame on me! I had that day my eyes bloated :(
[08:31] <hjmf> I've tested the solution posted and works
[09:00] <asac> morning
[09:03] <asac> hjmf: isn't bug 116421 fixed or what? (sorry, still not yet at 100%) :)
[09:03] <ubotu> Launchpad bug 116421 in firefox "firefox shell breaks "profile" option" [Medium,Fix released]  https://launchpad.net/bugs/116421
[09:06] <Admiral_Chicago> morning asac
[09:09] <Admiral_Chicago> my machine is dragging its feet moving a very large folder...
[09:10] <asac> Admiral_Chicago: morning :)
[09:10] <asac> Admiral_Chicago: though I think its still night where you are :)
[09:10] <asac> @now chicago
[09:10] <ubotu> Current time in America/Chicago: June 08 2007, 02:10:39 - Next meeting: Kernel Team in 4 days
[09:10] <asac> oh ... its not even bedtime :)
[09:11] <Admiral_Chicago> nah...
[09:11] <Admiral_Chicago> early still
[09:13] <asac> right
[09:34] <Admiral_Chicago> great, I learned something new about bughelper, should make bugxml -a work for our purposes...
[09:35] <asac_> Admiral_Chicago: night!
[09:39] <Admiral_Chicago> have fun without me...
[11:18] <asac> hjmf: how many gtk_style_realize crashes have we seen for feisty (post release)?
[11:19] <asac> hjmf: if they are close to zero I would like to push the totem fix into edgy as well
[11:24] <DarkMageZ> iirc, the totem plugin isn't the only plugin which causes firefox to trip out at that point. there are probably a lot of random plugins and bug reports due to it. tho yes, pushing the totem fix into edgy would help those few users still using edgy.
[11:25] <DarkMageZ> totem workaround*
[11:32] <DarkMageZ> with my small sample of the 5 latest duplicates. 1 was feisty, 4 was edgy.
[11:38] <asac> Bug 119269
[11:38] <ubotu> Launchpad bug 119269 in firefox "i can print from firefox, but it's empty paper out." [Undecided,Unconfirmed]  https://launchpad.net/bugs/119269
[11:38] <asac> can someone figure out what the reporter wants?
[11:39] <asac> DarkMageZ: it causes most crashes for us
[11:39] <asac> DarkMageZ: you have the recent feisty dupe?
[11:40] <DarkMageZ> i'll refind it
[11:47] <DarkMageZ> with 1 error in counting against feisty :s
[11:49] <gnomefreak> Admiral_Chicago: email sent lets see what happens
[11:50] <gnomefreak> asac: asking what the hell do you want mr/mrs reporter a bit too forward ;)
[11:51] <gnomefreak> i got it :)
[11:52] <gnomefreak> done
[11:53] <asac> gnomefreak: thx
[11:53] <asac> :)
[11:53] <gnomefreak> https://wiki.ubuntu.com/MozillaTeam/Bugs/Triage/Responses?highlight=%28mozilla%29   <<< pretty helpful :)
[11:53] <gnomefreak> its early and i slept like shit
[11:54] <gnomefreak> send david an email to see whats up so lets see if i get reply. if we dont hear from him in next month we may need the CC to change ML access and stuff over :(
[11:55] <gnomefreak> DarkMageZ: firefox-trunk working ok for you now?
[11:56] <DarkMageZ> i'm running a hacked up 70601
[11:57] <DarkMageZ> cvs june 01 *
[11:57] <DarkMageZ> reloading repositories now
[11:59] <asac> gnomefreak: there has been some issue with david ... we can chat about that in private
[12:00] <gnomefreak> ok ty
[12:00] <DarkMageZ> new version applies
[12:00] <asac> gnomefreak: do you have a jabber id?
[12:00] <asac> gnomefreak: so we can use gpg discussion for "private" things?
[12:00] <asac> gpg encryption i mean ;)
[12:01] <gnomefreak> speaking of hacked. i have a hacked version of the forum post for you to look over add fix so on.
[12:01] <gnomefreak> asac: no jabber never did learn how to use it
[12:01] <gnomefreak> asac: you can encrypt email if you like
[12:01] <asac> gnomefreak: will do
[12:01] <asac> remind me if you don't have a mail in a few hours
[12:01] <gnomefreak> ok
[12:08] <gnomefreak> asac: not important but when you get time please add change hack throw away and start over (if no good) it was a late night thing i wanted to get started on since i was up :(   http://gnomefreak.pastebin.ca/550115 if you can post changed version incase i have other ideas in the next few days or after you get to it.
[12:08] <gnomefreak> brb coffee
[12:10] <asac> gnomefreak: maybe ad an url where people can get bugs/blueprints for which we offer mentoring
[12:20] <gnomefreak> i dont know what we offer in the way of mentoring. maybe we should have a wiki for mentoring with the urls on how to get it for each thing we offer it on and it can be added to the we need people...... part of the post
[12:23] <gnomefreak> i know Admiral_Chicago is offering it for bughelper we need someone to offer it for bug triage (atleast IMO) I can offer mentoring on anything we need for the most part (depending on what it is)
[12:31] <gnomefreak> AlexLatchford: you around?
[12:31] <AlexLatchford> just got back.. yes
[12:31] <AlexLatchford> (literally just sat down)
[12:33] <gnomefreak> if its cool with asac we can go ahead with the testing team set up
[12:33] <AlexLatchford> nice
[12:34] <asac> gnomefreak: you should be able to get a list of mentored bugs that are marked beneficial for mozillateam
[12:34] <asac> there should be a bunch already
[12:35] <asac> gnomefreak: i mean there should be a single url to get those bugs (though not sure)
[12:35] <gnomefreak> if you want to do it feel free or i can its up to you. asa_c and i are the only uploaders to it (would like to keep it that way)
[12:35] <gnomefreak> asac: there should be is what i was hoping for
[12:35] <gnomefreak> lol
[12:35] <asac> https://bugs.launchpad.net/~mozillateam/+mentoring
[12:35] <gnomefreak> ill see what i can find
[12:35] <gnomefreak> oh ty
[12:35] <asac> that url should be fine
[12:35] <asac> to include in the mail
[12:36] <gnomefreak> k
[12:36] <asac> actually I would like to post it to forums (e.g. like "this is what gnomefreak announced on the mailing lists) ... so if you are done with drafting let me know
[12:37] <asac> i will read through this and maybe post some more bugs for mentoring before we post
[12:37] <asac> gnomefreak: of course if you want to post to forums on your own ... i am fine as well :)
[12:37] <gnomefreak> that is fine im more concered about getting everything in it to be sane since it will be stickied
[12:37] <asac> yes
[12:37] <asac> right
[12:37] <asac> so ... i will seriously review your text later today
[12:37] <gnomefreak> a changed the conttacts page so i may use that instead of names
[12:38] <asac> yes
[12:44] <gnomefreak> asac: how kept up is your edgy repo? is this something i should work on (setting edgy one up for trunk and tbird mainly)
[12:44] <asac> gnomefreak: no ... lets not support egdy for now
[12:44] <asac> unless we get loads of requests
[12:45] <gnomefreak> should we remove it from preview archive wiki?
[12:45] <asac> i think so ... yes
[12:45] <gnomefreak> wait and see what people say about edgy packages (not sure if anyone is using it. it was just us at one time
[12:45] <asac> unless someone really cares
[12:46] <gnomefreak> lets remove it and see what responces we get from this.
[12:46] <asac> :)
[12:46] <asac> exactly
[12:47] <gnomefreak> AlexLatchford: are going to set up team or do you want me to do it?
[12:47] <AlexLatchford> erm.. Can you set it up if possible
[12:47] <AlexLatchford> I am still in the middle of exams, will be finished in about 2 weeks though
[12:48] <AlexLatchford> so I can take over if you wish then..?
[12:48] <gnomefreak> thats fine i can do it
[12:48] <gnomefreak> i can add you as admin. ill set it up today sometime
[12:48] <asac> a new team?
[12:48] <gnomefreak> testing team
[12:49] <asac> ah
[12:49] <asac> do we really need a formal team for that?
[12:49] <asac> (though i see the benefit of having a list of people that contribute)
[12:49] <gnomefreak> if we have it than we can get a ML for bugs on our repos
[12:50] <gnomefreak> and a better, more organized way of testing and setting up a testing base
[12:50] <asac> gnomefreak: can you please ping heno about that?
[12:50] <asac> gnomefreak: he is currently working on making the QA team more effective
[12:50] <asac> gnomefreak: maybe we can find ways to interface with them
[12:50] <gnomefreak> heno about what? our unofficial bugs?
[12:51] <asac> our preview archive ... QA on preview packages et al.
[12:51] <gnomefreak> part of the bugsquad qa team?
[12:52] <asac> hmmm ... i will think a bit, ok? lets talk after lunch (a bit exteded today)
[12:52] <gnomefreak> asac: thats fine :)
[12:54] <asac> ok lunch
[12:55] <gnomefreak> have a good lunch
[12:56] <gnomefreak> !moztest
[12:56] <ubotu> The Mozilla-testing repos can be found at: https://wiki.ubuntu.com/MozillaTeam/PreviewArchives. Please remember these are testing repos, the packages in these repos are not stable and may break things on your system. Use with caution. Please report bugs found from these packages to: https://wiki.ubuntu.com/MozillaTeam/PreviewArchives/Bugs.
[01:14] <gnomefreak> AlexLatchford: me and asac will discuss this, if we can find a way to intergrate a way to track testing and bug reporting for it im happy with having it as a part of the mozilla team but lets see what happens
[01:15] <AlexLatchford> cool cool
[01:35] <gnomefreak> ok im gone for a while i have to be somewhere soon.
 hjmf: how many gtk_style_realize crashes have we seen for feisty (post release)?
[03:14] <hjmf> none that I remember
[03:15] <hjmf> among all the dups of gtk_style there are very few from feisty and all quite old
[03:15] <hjmf> asac: ^^^
[03:15] <hjmf> I'm off
[03:15] <asac> 11:32 < DarkMageZ> with my small sample of the 5 latest duplicates. 1 was feisty, 4 was edgy.
[03:15] <asac> hjmf: ^^^
[03:15] <DarkMageZ> with 1 miscount against feisty
[03:16] <asac> what do you mean by "miscount" ?
[03:16] <asac> so we have 0 feisty?
[03:16] <hjmf> asac just look at the dups, I title them [RELEASE]  firefox crash
[03:16] <asac> hjmf: yep
[03:16] <hjmf> from some time ago
[03:17] <hjmf> not more than 10 are [FEISTY]  or [apport] 
[03:17] <hjmf> asac: I'm really off now :)
[03:17] <asac> hjmf: yes thanks!!
[03:49] <JakubLe> hi, asac - this is jakub from allpeers
[03:50] <asac> hi JakubLe
[03:50] <asac> welcome
[03:51] <asac> JakubLe: does your extension have native extensions?
[03:51] <asac> aeh native components :)
[03:54] <JakubLe> asac: yes, our extension contains a lot of C++ compiled code
[03:54] <JakubLe> as far as our experience reaches, the crash can occur due to incompatibility with some of the library installed probably?
[03:54] <asac> ABI compatibility due different libs and gcc is the most likely cause
[03:55] <asac> s/compatibility/incompatibility/
[03:56] <asac> JakubLe: point is if your code is licensed unter a free license then we would be happy to package it ... which will resolve these problems and bring your extensions to all architectures we have
[03:56] <asac> otherwise we would need to work somthing out
[03:56] <asac> e.g. a way that you can distribute your "compatible" extension
[03:58] <JakubLe> we should discover the cause of the crashes - our extension have some logging ability - logs are placed in profile directory of mozilla - would it be possible to send us logs from some crashed instance? ...
[03:59] <asac> JakubLe: no ... we only get crash files ... so we basically just can create backtraces
[03:59] <asac> JakubLe: you can contribute to the bug and ask the reporters
[03:59] <asac> maybe they still have the logs in their profile directory
[04:00] <JakubLe> asac: thanks, I will ask them - we have also unstripped versions with symbols available to download - it would help very much to see the backtrace and exact causes of crashes
[04:00] <asac> JakubLe: but as long as you are sure you build with our gcc and libstdc++ version its unlikely that its really a code issue
[04:01] <asac> JakubLe: the backtraces are attached to the bug
[04:01] <asac> and the duplicates
[04:01] <asac> (on the right there is portlet where you can navigate to duplicate reports)
[04:03] <asac> JakubLe: actually we have not yet enabled automatic crash report submission for gutsy ... i expect lots of crashes to come in (depending on how popular your extension is) once that is done (most likely in one or two weeks)
[04:04] <asac> JakubLe: you can resymbolize our coredumps ... even though the users don't use a symbolized extension)
[04:05] <asac> JakubLe: you can use apport-retrace command on ubuntu for that. Just be sure that gdb finds your symbols
[04:06] <JakubLe> we store the symbol tables for the builds released, so we can put this together, I hope. We've had issues with listdc++ before. Due to various usage of version 5 and 6, we decided to build it on our own and it is contained in the extension
[04:07] <asac> oh
[04:07] <asac> ouch
[04:07] <JakubLe> this can be probably the source of problems?
[04:08] <asac> if you statically link libstdc++ you might run into problems because of gcc ABI difference i guess
[04:08] <asac> your would run them even with dynamic linked libnstdc++ ... i just mean that its a different issue
[04:09] <asac> though we can hope that gcc ABI did not break in recent history
[04:10] <asac> I don't know how popular your extension is ... but if it was popular about 3 month ago we would have seen more crashes
[04:10] <asac> so i guess its not really an ABI problem
[04:10] <asac> what we see in the few duplicates we have
[04:10] <JakubLe> We've made first public release last summer
[04:11] <JakubLe> we have had 300000 downloads since that time (it is something around 40000 per month), however the vast majority are windows users
[04:11] <asac> right
[04:11] <asac> look at bug 85382
[04:11] <ubotu> Launchpad bug 85382 in firefox "MASTER firefox crashed - colorzilla - [@nsNativeComponentLoader::AutoRegisterComponent] " [Medium,Confirmed]  https://launchpad.net/bugs/85382
[04:11] <asac> thats an example of incompatible libstdc++
[04:12] <asac> it has 29 duplicates
[04:12] <asac> JakubLe: so at best you would subscribe to the allpeers bug and try to support reports on allpeer crashes (e.g. ask them to submit logs et al)
[04:12] <asac> (i think you are already subscribed)
[04:13] <asac> once we have auto-crash report submission on for gutsy we will see how hard allpeers crashes
[04:14] <JakubLe> yes, I am subscribed - I will give the support for this and hope we can nail down the problem - I will handle the information to our linux-expert here
[04:14] <asac> cool
[04:14] <asac> do you link everything static?
[04:14] <asac> or do you have some other libs you pull in from system?
[04:15] <asac> JakubLe: actually it might be beneficial for your linux-expert to subscribe to all firefox bugs ... as we might miss allpeers related crashes
[04:15] <asac> ... we try to merge them into our master bug ... but who knows
[04:15] <JakubLe> yes, we use also system linux libraries
[04:15] <asac> which ones?
[04:16] <JakubLe> libz.so.1
[04:16] <JakubLe> libxpcom.so
[04:16] <JakubLe> libxpcom_core.so
[04:16] <JakubLe> libplds4.so
[04:16] <JakubLe> libplc4.so
[04:16] <JakubLe> libnspr4.so
[04:16] <JakubLe> libpthread.so.0
[04:16] <JakubLe> libdl.so.2
[04:16] <JakubLe> libmozjs.so
[04:16] <JakubLe> libsmime3.so
[04:16] <JakubLe> libssl3.so
[04:17] <JakubLe> libnss3.so
[04:17] <JakubLe> libsoftokn3.so
[04:17] <JakubLe> libm.so.6
[04:17] <JakubLe> libgcc_s.so.1
[04:17] <JakubLe> libc.so.6
[04:17] <asac> oh
[04:17] <JakubLe> asac: sorry, for long list - it's the output from ldd on our .so library
[04:17] <asac> no problem
[04:17] <asac> you will run into problems
[04:17] <asac> in gutsy
[04:17] <asac> libnss3.so libnspr4.so don't exist anymore
[04:17] <asac> they have no proper sonames for us
[04:17] <JakubLe> I think these are linked from firefox directly?
[04:18] <asac> JakubLe: yeah at best don't link against these and hope that the symbols are already resident
[04:18] <asac> libnss3.so -> libnss3.so.0d
[04:18] <asac> libnspr4.so -> libnspr4.so.0d
[04:18] <asac> for us
[04:19] <asac> JakubLe: i think it would be nice if your linux-expert could come in here :)
[04:20] <asac> i would like to shake such issues out as early in the release cycle as possible
[04:20] <JakubLe> OK, he'll conenct ;)
[04:20] <asac> JakubLe: great ... but i will be out for weekend in a few. I will be here next week ... as usual :)
[04:21] <asac> my timezone is @now Berlin
[04:21] <asac> @now Berlin
[04:21] <ubotu> Current time in Europe/Berlin: June 08 2007, 16:21:22 - Next meeting: Kernel Team in 4 days
[04:21] <asac> i am guaranteed to be here during business hours
[04:21] <asac> in the evening ... mostly as well ... but in some lazy mode :)
[04:22] <JakubLe> asac, micha1 is our linux guy
[04:22] <asac> heya micha1
[04:22] <asac> welcome
[04:22] <micha1> hi asac
[04:24] <asac> micha1: http://pastebin.mozilla.org/86769
[04:24] <asac> the last few lines
[04:26] <asac> micha1: do you think you can setup a gutsy system somewhere so we can shake out issues as early in the release cycle as possible?
[04:27] <asac> micha1: we just released our first milestone CD for gutsy
[04:27] <asac> http://cdimages.ubuntu.com/releases/gutsy/tribe-1/
[04:27] <micha1> One my colleague just installs ubuntu onto his machine, so I'll tell him to install gutsy
[04:28] <micha1> Just to clear, what the problem is, there will be no libnspr4.so and libnss3.so anymore?
[04:28] <asac> yeah ... might not be a suitable for general production use (well if you are a developer it should be fine)
[04:29] <asac> micha1: its named different ... with proper soname
[04:29] <asac> libnss3.so -> libnss3.so.0d ... libnspr4.so -> libnspr4.so.0d
[04:29] <micha1> Why you decided to rename it?
[04:30] <asac> the symbols should be resident already ... so maybe you don't need to link explicitly
[04:30] <micha1> I'm nopt sure, we can try this
[04:30] <asac> micha1: so we can track binary compatibility? do proper transitions
[04:31] <asac> its just a pita to ship things with no proper soname for distributors
[04:33] <micha1> If it will work without linking to these libraries, then we'll do it. But if not, I think that easiest solution would be to link to them statically. But the extension would be huge :-/
[04:34] <asac> you already link libstdc++ :)
[04:34] <micha1> Yes :)
[04:36] <micha1> I'm not sure, what all will be used, but the difference can be up to around 2MB
[05:14] <asac> ok weekend
[05:16] <gnomefreak> im back i think
[05:20] <gnomefreak> did i miss anything fun?
[05:55] <gnomefreak> asac: you told me to remind you about email if i didnt get it in a few hours
[05:58] <bluekuja> gnomefreak, he left for sea
[05:58] <bluekuja> :)
[05:58] <bluekuja> will be away the weekend i think
[05:58] <gnomefreak> damn already
[05:58] <bluekuja> yup
[05:59] <gnomefreak> hmmmm im missing a channel
[06:00] <bluekuja> huh?
[06:00] <gnomefreak> im only in 19 channels i should be in 20 atleast
[06:00] <gnomefreak> i found it
[06:00] <gnomefreak> brb
[06:00] <bluekuja> lol
[06:01] <gnomefreak> connect got lost this morning and one of the channels are invite only and this nick is set to join not any of my others
[06:02] <bluekuja> oh :D
[07:42] <Admiral_Chicago> seems like i missed all the fun
[07:45] <Admiral_Chicago> bug Bug 52670 fall in our court?
[09:11] <hjmf> Admiral_Chicago: seems that someone got annoyed when I autoassinged all the unassigned thunderbird reports (w/o looking at them)
[09:11] <hjmf> among which was bug 52670
[09:11] <ubotu> Launchpad bug 52670 in kde-systemsettings "Kubuntu setting default components don't affect gnome/gtk apps" [Undecided,Unconfirmed]  https://launchpad.net/bugs/52670
[09:11] <hjmf> thanks god, they rejected the thunderbird task
[09:11] <hjmf> quite nasty people ;)
[09:56] <Admiral_Chicago> hjmf: yea Hobbsee got mad at them