[12:42] joejaxx: about 3g i guess [12:43] gnomefreak: lets talk tomorrow about the pitti thing. Not sure what he wants us to do from reading the log :) [12:45] There was a "thing"? [12:47] thing? [12:47] ah :) [12:47] yeah in log ... gnomefreak toled me that pitti wanted us to do something ... so I called it "thing" [12:50] are we in trouble :( [12:50] lol [12:50] gotcha [12:51] i have no troubles :) ... just tired. [12:52] ok night all [12:52] night [12:55] who is the one that can help me with retraces in Feisty? [12:55] gnomefreak: can you ? [01:18] Admiral_Chicago: i can but hjmf is better than me at them [01:19] no me and asac are in trouble everyone else is safe :( [01:20] oh nose.... [01:20] what happened [01:20] Admiral_Chicago: its a flash and apport thing [01:20] gonne work on a hook for it [01:20] actually, speaking of which, I think I made sebastian bacher mad at me [01:20] triaging incorrectly... [01:21] a lot of bugs. [01:21] a lot. [01:21] eh [01:21] gnomefreak: am i wrong on this Bug #85763 [01:21] Malone bug 85763 in metacity "[apport] metacity crashed with SIGSEGV" [Medium,Needs info] https://launchpad.net/bugs/85763 [01:21] i think I may be (and probably am wrong) [01:22] looking and hes most likely not mad but he gets agrevated sometimes [01:23] yea i know, i just want to make sure I'm triaging correctly [01:23] i'd rather learn i'm doing it wrong and learn to do it correctly [01:25] i think what he means is the coredump is giving wrong values (not unusable) in the sense me nad yuo would think. i wouldnt worry too much about it right now. metacity and other things are nothing like firefox so you kind of have to get used to them. [01:26] blah okay [01:26] i thought that with a new kernel in Feisty, a new crash report would be useable [01:38] it would be if he thinks he can do something with that one thats fine [01:39] s/be if/ be, but if [01:40] bug 1 [01:40] Malone bug 1 in ichthux "Microsoft has a majority market share" [Critical,Confirmed] https://launchpad.net/bugs/1 [01:40] hmmmmmm [01:47] Admiral_Chicago: easiest way to retrace feisty "sudo apport-retrace -v -d 88888 2>&1 | tee retrace.log" replace 88888 with just the number of the bug. and make sure you have everything you would need to retrace it. you normally wont know until you try it once the warnings will tell you what your missing. ignore the /var/cache/flashplugin-nonfree/libflash.so --ignore. you wont get dbg or dbgsym packages for that. but you need to h [01:49] Admiral_Chicago: also depends on version of apport and how the bug is laid out. is everything seperate on bug or 1 totel crash file [01:49] right. i'm thinking of looking at that wiki again, i got lost at one point of it [01:50] bbl [01:50] Admiral_Chicago: dont use the wiki for feisty it has changed too much [01:50] i havent figured out the easiest best way [02:01] night === poningru [n=poningru@adsl-074-245-140-197.sip.gnv.bellsouth.net] has joined #ubuntu-mozillateam [04:28] https://lists.ubuntu.com/archives/feisty-changes/2007-March/006546.html [04:35] [23:33:59] I mean when the font "sans-serif" is requested, how does firefox pick which font to use [04:35] [23:33:59] which font in that family [04:35] [23:33:59] It doesn't seem to use the ordering in fontconfig [04:36] anyone? [04:37] poningru: I think it's defined within FF [04:38] maybe not, nvm [04:40] do you know? [04:40] asac: ping === asac_ [n=asac@debian/developer/asac] has joined #ubuntu-mozillateam === AlexLatchford [n=alex@82-44-193-109.cable.ubr07.haye.blueyonder.co.uk] has joined #ubuntu-mozillateam [07:39] grrrrrr [07:46] whats the issue? [07:50] im still awake [07:51] its almost 3am [07:55] same here [07:55] i'm going to hang out [07:55] see ya === poningru [n=poningru@adsl-074-245-140-197.sip.gnv.bellsouth.net] has joined #ubuntu-mozillateam [09:53] asac: pitti > gnomefreak: I just committed support for "UnsupportableReason: " to apport [09:54] asac: Fujitsu > pitti: Where does that go? [09:54] 04:00 < pitti > Fujitsu: into the crash report file in /var/crash; intended to be set in a package hook [09:54] 04:00 < Fujitsu > Ah. [09:54] 04:01 < pitti > Fujitsu: the idea is: check report['ProcMaps'] for libflashplugin.so, and if so, set report['UnsupportableReason'] = _('Flash is b0rked blabla') [09:54] so im assuming he did it for us so we dont have to? [09:54] hmm [09:54] can't tell [09:54] better go to sleep gnomefreak :) [09:54] i will find out ;) [09:55] ok ty. i havent slept yet but i will in the next hour or so [10:28] asac: bug 88730 looks like colorzilla can you please confirm that when you get a chance? [10:28] Malone bug 88730 in firefox "[feisty] Firefox Crashed " [High,Needs info] https://launchpad.net/bugs/88730 [10:30] i hate to say it but it looks like newest apport is doing good on feisty ones thats 2 that ive gotten good ones on [10:36] hmm [10:36] i tried to setup a new feisty chroot [10:36] now apport-retrace [10:36] has problems to install dbgsym packages [10:36] The following packages have unmet dependencies: [10:36] libnss3-dbgsym: Depends: libnss3 (= 2.0.0.2+1-0ubuntu1) but 2:1.firefox2.0.0.2+1-0ubuntu1 is installed. [10:36] libgcc1-dbgsym: Depends: libgcc1 (= 4.1.2-0ubuntu4) but 1:4.1.2-0ubuntu4 is installed. [10:36] libnspr4-dbgsym: Depends: libnspr4 (= 2.0.0.2+1-0ubuntu1) but 2:1.firefox2.0.0.2+1-0ubuntu1 is installed. [10:37] yeah its colorzilla [10:38] gnomefreak: did you get past that point (e.g. package dependencies?) [10:38] ? [10:38] yeah i noticed that issue also [10:38] i did yesterday i just dont remember how :( [10:38] stil you can retrace? [10:39] or did i skip them [10:39] libnss3: Installed: 2:1.firefox2.0.0.2+1-0ubuntu1 [10:40] so i think i was able to just leave them alone. you can try apt-get -f install but iirc it didnt help [10:42] hmm [10:42] how? [10:42] for me apport-retrace bails out [10:43] you using sudo? with newest apport? [10:45] hmm [10:46] i am root in chroot [10:47] for feisty are you using #apport-retrace -s -v -u bug# 2>&1 | tee retrace.log? and what is the error? [10:48] what does -u do? [10:48] unpack only dont set up [10:49] something like that [10:49] hmm [10:49] now i don't get the error anymore [10:49] i ran apport-retrace -s bug# before [10:50] -u, --unpack-only Only unpack the additionally required packages, do not configure them; purge packages again after retracing [10:50] pitti told me on one of the many apport bugs i filed to use -u see if it still happens so i have been using it [10:51] does this look ok(when you get a chance) http://librarian.launchpad.net/6718918/Stacktrace [10:51] hmm [10:52] funny thing is [10:52] after using -u once [10:52] i don't get the same problem as before anymore [10:52] anyway ... its just garbage ... e.g. what is produced as trace [10:52] --- stack trace --- [10:52] #0 0x00002af41d0c30a0 in ?? () [10:52] --- thread stack trace --- [10:53] what bug? [10:53] for Bug 86277 [10:53] Malone bug 86277 in firefox "[feisty] Firefox Crashed x86_64" [High,Needs info] https://launchpad.net/bugs/86277 [10:53] damn [10:53] i dont have 64 [10:54] i think we should close that one [10:54] no way to get a better trace apparently [10:54] i would ask him to backtrace it or steps to repro it other than that there isnt anything we can do but close [10:54] lets just close [10:54] then [10:54] asking users to retrace if we don't know on our own how to do it won't help a lot [10:55] trrue [11:00] have you ever seen apport retracing dropping a useful retrace? [11:00] e.g. the service [11:02] is beta out? [11:03] not sure about beta. and i have retraced some nice ones the past 24 hours. some 64bits the stack that is uploaded for feisty sometimes have good ones [11:03] yeah ... some look somehow ok [11:04] there are a few things we need to think about. we need a list of all dapper crashes for fx and tb. sinse we cant retrace them i would think check them see if anything helpfule from bug buddy if not find out if repro on edgy if so retrace them or if not close them [11:04] not sure how to get a list of dapper crashes [11:06] ok i just retraced one of the gtk_defaultbackground ones and it is correct stack and thread. another great output of one [11:06] bug 90583 is the one [11:06] Malone bug 90583 in firefox "Firefox crashes on opening pdf" [High,Needs info] https://launchpad.net/bugs/90583 [11:08] i just uploaded my .log file to it [11:10] ok now its uploaded :( [11:12] Bug 93762 ... can be closed i guess :) [11:12] Malone bug 93762 in firefox "Firefox crashed on feisty" [Undecided,Rejected] https://launchpad.net/bugs/93762 [11:14] i agree [11:17] hmm ... again there is a user that complains about launchpad not accepting crash reports [11:17] is that really the case? e.g. maybe there is a constraint for attachments? [11:18] asac: i think its they are too big for users connection (or they kill it maybe due to it takes too long) [11:18] i thought that too initially [11:18] but the more i read the comments, the more i guess there might be indeed a constraint [11:18] i have uploaded huge crash reports in past they take forever but ive done it [11:19] how huge? [11:19] maybe. would need to talk to #launchpad [11:19] 25mb [11:19] give or take [11:19] Yeah, I realize that the small report is pretty useless. How should I get [11:19] the complete report to you guys? Launchpad would not accept the file, maybe [11:19] because it's around 30 MB or so... [11:20] well after what happened to my home dir i wont be accepting them by email. maybe we need to set up a site or something to take them? [11:21] maybe a wiki wiht a table for them to fill out? (name date bug# file) but i dont think wiki is the best to try that with [11:22] try taring it or zipping it to save 10mb or so? [11:22] don't think it helps [11:22] coredump is already gzipped [11:25] something to talk to LP and pitti about maybe see if there is something else we can do [11:25] i asked on launchpad [11:25] #launchpad [11:25] lets see [11:26] i see [11:26] oh i am sooo tired [11:26] i currently experiment how to survive a day without coffee [11:26] i have one im downloading that is 30mb [11:26] bug 90891 [11:26] Malone bug 90891 in firefox "firefox crashes" [High,Needs info] https://launchpad.net/bugs/90891 [11:26] hmm [11:26] ever downloaded one that is about 35mb? [11:26] ah he didnt upload to LP though [11:26] ah [11:27] I can't upload the file here (I don't know why) so I've stored it in my web space. The adress is: http://frank95com.homelinux.com/pub/media/other/_usr_lib_firefox_firefox-bin.1000.crash [11:27] yes [11:27] lets bug lp folks [11:27] k [11:28] pastebin.ca allows uploads but they restrict them to like 100kb [11:29] usually every webapp where you can upload to has some constraint [11:29] however, i don't know what size it is for launchpad [11:32] i think im gonna start marking the background ones as dupes as soon i as remember the one i got great stack on for it [11:34] or not since i cant find it :( [11:37] well if ther eis no limit what are people getting errors === AlexLatchford [n=alex@82-44-193-109.cable.ubr07.haye.blueyonder.co.uk] has joined #ubuntu-mozillateam [11:53] ok last retrace than im goin gto bed. im getting tired and its almost 7am [12:09] asac: i made bug 90583 master of gtk_style_apply_default_background [12:09] Malone bug 90583 in firefox "MASTER Firefox crashes [@gtk_style_apply_default_background] " [High,Needs info] https://launchpad.net/bugs/90583 [12:10] its feisty bug and since we dont know anything about it atm im going through email cause i saw a crap load of them iirc [12:11] since the new totem has fixed most of the edgy bugs in feisty im going to assume this is different for now. [12:32] night === AlexLatchford [n=alex@82-44-193-109.cable.ubr07.haye.blueyonder.co.uk] has joined #ubuntu-mozillateam [01:52] gnomefreak: ok ... so this is a new top-crash for us [01:53] we need to find way to reproduce [01:53] wo i can work on a fix [01:53] or better find fix upstream :) === hjmf [n=hjmf@62.Red-83-45-116.dynamicIP.rima-tde.net] has joined #ubuntu-mozillateam [03:19] hmmm Bug 94921 [03:19] Malone bug 94921 in firefox "[apport] firefox-bin crashed with SIGSEGV in __kernel_vsyscall()" [Medium,Unconfirmed] https://launchpad.net/bugs/94921 [03:19] apport did his best, but not suceeded :) [03:25] hjmf: Bug 94861 [03:25] Malone bug 94861 in firefox "[apport] firefox-bin crashed with SIGSEGV in __kernel_vsyscall()" [Medium,Rejected] https://launchpad.net/bugs/94861 [03:25] maybe installing that extension hels? [03:26] hjmf: however, where can one get that? Its a native extension and thus if its free-software we should add it to ubuntu archives [03:28] i asked the author :) [03:30] asac: hi! about bug 94921 [03:30] Malone bug 94921 in firefox "[apport] firefox-bin crashed with SIGSEGV in __kernel_vsyscall()" [Medium,Unconfirmed] https://launchpad.net/bugs/94921 [03:30] im going to retrace it but I bet that is flashplayer [03:45] ... Ive lost my bet :/ [03:46] I cannot get a better retrace. I've asked the reporter for additional info about the crash [03:46] ok [03:50] ok incompatible allpeers extension causing crashes is now a new master bug ... there appear to be plenty of those. [03:52] bug 95091 it is [03:52] Malone bug 95091 in firefox "MASTER incompatible native extension: allpeers" [High,Needs info] https://launchpad.net/bugs/95091 [03:56] ok i have resurrected a few about this that have previously been rejected [04:05] noticed, Ive marked the one I retraced as dup of new master [04:06] good ... if its allpeers its a safe bet :) [04:06] the new master needs someone to take care ... so if anyone likes to communicate with upstream authors, its probably the right bug. [04:06] maybe I should assign it to DFarning? [04:07] sure he is the guy [04:07] i am pretty bad at it :( ... i even dropped the ball on colorzilla ... i think I should ping him as he wanted to release under GPL [04:07] ... he seems to like those things :) [04:07] so we can package it [04:09] I have to confess that I've never tried those extensions... === hjmf thinks that firefox already does what it has to do [04:09] :) [04:09] asac: why do we need bug#95091 [04:09] bug 95091 [04:09] Malone bug 95091 in firefox "MASTER incompatible native extension: allpeers" [High,Needs info] https://launchpad.net/bugs/95091 [04:10] Admiral_Chicago: look at the bug ... there are duplicates already [04:10] Allpeers is a closed source (moving to open source) extension that isn't in the repos though [04:10] Admiral_Chicago: though its not exactly our problem we should try to shake things out ... we should at least contact author and ask him to open-source it [04:10] :) [04:10] if possible [04:11] colorzilla author will open his source after i discussed this with him :) [04:11] there was an announcement about moving it to open source, but open source doesn't mean GPL [04:12] we can try to contact them for sure [04:12] perhaps with some more detailed bug reports though [04:12] yes ... do you like that or should i ask dfarning ? [04:12] i'll do it [04:13] i'll assign it to myself temporarily [04:14] Admiral_Chicago: cool :) ... if you need arguments why GPL et al, let me know :) [04:14] will do [04:14] tell him that we could build package and it will automatically become available on lots of architectures (which he will probably not be able to build) [04:15] right. [04:16] its a team afaik [04:16] but I have to grab breakfast and head to class [04:16] ok them :) [04:20] awk for a while === poningru [n=poningru@adsl-074-245-140-197.sip.gnv.bellsouth.net] has joined #ubuntu-mozillateam [06:38] wtf is a memory error when doing retrace :( [06:41] https://bugs.beta.launchpad.net/ubuntu/+source/firefox/+bug/1 [06:41] Malone bug 1 in ichthux "Microsoft has a majority market share" [Critical,Confirmed] [06:41] gnomefreak: Why is this on us? [06:42] i dont know [06:42] reject? === gnomefreak doesnt play with bug #1 [06:42] well To me it is not a firefox bug, it is purely an Ubuntu bug [06:43] AlexLatchford: i would say find out who added it first [06:43] will do === mode/#ubuntu-mozillateam [+o AlexLatchford] by ChanServ === mode/#ubuntu-mozillateam [-o AlexLatchford] by AlexLatchford [06:57] i feel that we are of real importance to resolve bug 1 [06:57] Malone bug 1 in ichthux "Microsoft has a majority market share" [Critical,Confirmed] https://launchpad.net/bugs/1 [06:57] if we do wrong we bug 1 can't be resolved :) [06:57] ok out too [07:02] ill be back later.