=== poningru [n=poningru@adsl-074-245-140-197.sip.gnv.bellsouth.net] has joined #ubuntu-mozillateam === asac_ [n=asac@debian/developer/asac] has joined #ubuntu-mozillateam [07:18] someone around to test a bug [07:21] someone check out All in One Gestures, see if it breaks the spell checker [07:22] https://addons.mozilla.org/firefox/12/ [07:22] i'm using the EN-US build. [08:38] asac: TB Update just showed up by the way [10:38] yep [11:52] Bug 89704 [11:52] Malone bug 89704 in firefox "No backport of Firefox 2.o to Dapper" [Undecided,Needs info] https://launchpad.net/bugs/89704 === cjwatson [n=cjwatson@82-69-40-219.dsl.in-addr.zen.co.uk] has joined #ubuntu-mozillateam [01:20] hi all :-P [02:08] good morning [02:11] asac: did you release a new firefox to feistys repos? [02:12] hmm [02:12] thunderbird is updated [02:12] 2.0.0.2+1-0ubuntu1 [02:12] is that newer that mt2? [02:12] no [02:12] ok [02:13] mt2 is prepatch on top of that [02:13] updates are trying to update me was wondering [02:14] BTW im taking edgy retraces (since feistys are borked for me) if you run into any please assign to me ;) [02:15] ah found the problem it was the -dbgsym packages that failed the upgrade :( [02:20] asac: why is gothic marking every bug as a duplicate? :( [02:23] already kicked him [02:23] :) [02:23] he excused [02:23] its about the raise() thing [02:24] apparently we were late [02:24] :) [02:24] i tried go unmark some [02:24] i guess you found that [02:24] gnomefreak: so you are edgy man now? [02:24] :-D [02:24] yep i can be :) [02:24] i cant do feisty until i find out wth is going on [02:25] can you mesaure bandwidth [02:25] when downloading dbgsym packages for a feisty retrace [02:25] ?? [02:25] no:( [02:25] its that the reason why we have don't retrace on client machines is officially that it takes more bandwidth then uploading the crash report [02:25] which I can't believe [02:26] as -dbgsym packages appear to be really tiny [02:26] they are [02:26] apport will be doing retraces before report upload AFAIK atleast thats how i understood it from pittis email [02:28] my last info is that this will be done automatically on server side [02:29] well if hjmf wants he can fous on feisty crashes and ill focus on edgy crashes (plus the other things we do. that way it leaves you david alex and freddy for other things [02:30] asac: at one time he wanted LP to do it but i dont know what ended up with that [02:32] cool :) ... hopefully, we don't just do crashes and everything else is missed in the noise :) [02:32] i do crashes on down time. if you need anything else just ping and i will stop retracing asap and get to it :) [02:33] if hjmf script works well, I will try to add some automated service that does nothing else, but trying to retrace all reports [02:33] but while the scripts are being automated apport is changing [02:33] like now apport-retrace is a package on its own and options changed [02:34] -d and -C were dropped [02:34] yes [02:34] now i remember [02:35] he goes straight server: [02:35] apport-retrace is moved to separate package beacuse users don't need it [02:35] because retraces are only done automatically or by triagers [02:35] right [02:35] thats status quo [02:35] i don't like core dumps submitted to public [02:35] i was gone for 3 days and everything changed [02:35] thats why I would like to push in other direction before too much work has been put into automating onserver side [02:36] but for that i need bandwidth data [02:36] to get discussion started [02:36] good is ... the -C option (for cache) should be there [02:36] asac: if qa team was able to remove coredumps... that would be nice but i dont know who can remove anything from LP other than Lp devels [02:36] so you can just do du -HS /cachefolder [02:36] to get info how much bytes were pulled for retrrace [02:37] asac: its done automagicly so no need for -C and -d [02:37] gnomefreak: i have a contact for that [02:37] can you do a ls -l and du -Hs on cache folder [02:37] asac: ive had a few people ask me to remove it [02:37] and paste please? [02:37] apt/cache folder? [02:38] hmm [02:38] dbgsym packages should be cached somewhere [02:38] probably not in /var/... as you can run as user [02:38] not anymore you dont [02:38] from what i read pitti added option to say which polder [02:38] you cannot run as user? [02:39] not really [02:39] thats a bug [02:39] nope [02:39] actually pitti invests lots of time [02:39] to even deal with chroots automatically as user [02:39] won't make sense if you cannot run as user [02:39] what happens? [02:39] if you try to run as user? [02:39] i filed a bug about it not grabbing the -dbgsym packages and it needs to be run as root to grab them (but when i do it crashes [02:39] crashing == bug :) [02:40] hold on a sec [02:40] oh [02:40] i guess you should not run as root [02:40] this might cause serious hazards [02:40] as apport is really tested by uploading to feisty [02:40] so any bug can go in [02:40] especially with auto chroots [02:40] and stuff like that [02:40] its getting dangerous :) [02:40] bug 899169 [02:41] bug 89916 [02:41] yeah [02:41] Malone bug 89916 in apport "[Feisty] apport-retrace fails to retrace bugs." [Low,In progress] https://launchpad.net/bugs/89916 [02:41] better [02:41] :) [02:41] either run as root or download -dbgsym packages by hand [02:41] either way IMHO isnt real great [02:42] i have to try the -u option ill see what happens [02:42] You need to either install the missing packages ma [02:42] You need to either install the missing packages manually (apport-retrace lists them) or run apport-retrace as root, or in a fakechroot with apport-chroot. [02:42] try fakechroot [02:42] i think thats the only thing pitti currently tests [02:43] i dont have a clue wth fakechroot is [02:43] me neither [02:43] but i guess its a package [02:43] and man fakechroot tells a lot :) [02:44] but is it just a package or is it another chroot environment needed? [02:44] its a package [02:44] how it fakes the chroot ... i don't know [02:44] i guess its just that users can setup chroots without being root [02:45] i will look into it this afternoon i think === gnomefreak has mine set up to not use root [02:45] fakeroot runs a command in an environment wherein it appears to have root privileges for file [02:45] manipulation. This is useful for allowing users to create archives (tar, ar, .deb etc.) with [02:45] files in them with root permissions/ownership. Without fakeroot one would need to have root [02:45] privileges to create the constituent files of the archives with the correct permissions and own [02:45] ership, and then pack them up, or one would have to construct the archives directly, without [02:45] using the archiver. [02:45] ok [02:45] so probably run ... [02:45] so like fakechroot apport-retrace -v -d ..... ? [02:47] hmm [02:47] no [02:47] i pasted wrong man [02:47] :) === gnomefreak adding fakechroot to my to-do list [02:47] lol that was fakeroot you pasted [02:47] i will find out [02:47] afaik [02:47] there is a command [02:47] apportfakechroot [02:47] or something [02:47] that does magic [02:47] is fakechroot in dependencies of apport-retrace package? [02:47] ill look into it there has to be something on it (wiki or something) [02:48] not that i remember but will look [02:48] Depends: python (>= 2.4), python-apport (>= 0.45), lsb-base (>= 3.0-6), sysv-rc (>= 2.86.ds1-14.1ubuntu2) [02:48] nope [02:48] oops === asac looking to pitti mail [02:49] Suggests: debootstrap (>= 0.3.3.2ubuntu2), fakeroot, fakechroot [02:49] its a suggestion [02:49] not a depends [02:49] This package also ships apport-chroot. This tool can create and manage chroots for usage with apport-retrace. [02:50] not real sure wth that is either. but i need to try this retrace with -u see if it works brb [02:50] hmmm procmail failed [02:50] delivered bugmail to inbox instead of bugbox [02:51] yes thats the one [02:51] i guess you can use fakechroot apport-chroot [02:51] or something [02:51] gnomefreak: let us know how it works if you find :) [02:57] i will. if you run into pitti today for anything else please ask him a little more about this. i think we need to add this to agenda for meeting, but how since its changing daily? but i will man the packages --help them and search them when i get caught up hopfully before meeting [02:58] not very frigging helpful at all :( [02:58] wtf [02:58] lets try this in chroot [03:01] *mental_note* -u stops crash and stops the save on pc error === gnomefreak has to update chroot :( [03:10] hmm [03:11] i dont like this [03:11] asac: are you watching -devel? [03:11] newer packages == need updated crashreport? [03:12] will try to install the -dev packages anyway see if i get useful stack at all [03:14] yes [03:14] watching -devel [03:14] why? [03:16] asac: about the feisty retraces. he stated the feisty packages might be newer than the ones needed on retrace. what do we do? ask for a newer report? [03:18] maybe hjmf still has older packages? [03:18] otherwise for crashers, lets close them and say reporter that if crashes again he should reopen a new bug [03:18] ... as next crash is often of different type then initial posted [03:19] true [03:19] further add info to that comment [03:19] how to do retrace on his own [03:19] stating that this is the only reliable way that we can process his report for development ubuntu (aka feisty) [03:20] i have a greasemonkey script that allows to do bulk answers by one click [03:20] i dont like the idea of giving the user instructions on it because they have a hard enough time getting backtraces using gdb [03:20] it extends launchpad html ui [03:20] and adds links that insert the text in the proper text field [03:21] gnomefreak: yes ... lets not ask for gdb backtraces [03:21] greasmonkey would need to be used via email reply [03:21] why? [03:21] greasemonkey works in browser [03:21] you navigate to bug [03:21] oh [03:21] it extends webpages [03:21] you can add elements and arbitrary javascript [03:21] so we can extend launchpad [03:21] as we like === gnomefreak will play with that today [03:21] i can give you an example script [03:22] though it works only on non-beta [03:22] because relevant html elements and page names are different [03:22] asac: i dont ask for gdb unless they have a useless crash report. but i still think asking them to retrace thier own reports is not a great idea either [03:23] install greasemonkey [03:23] then open [03:23] http://people.ubuntu.com/~seb128/bugtriage.user.js [03:24] goto non-beta comment page [03:24] and you will see links for bulk answers [03:24] if you open the change state panel [03:24] hmm [03:24] i think retrace is more user friendly then gdb [03:24] as gdb needs to be run for a long time to eventually recapture [03:24] and retrace is definitly right [03:24] however if old [03:25] just close and say if it ever crashes they should report new bug [03:25] and that we are sorry, that we couldn't help [03:27] ok i think letting hjmf know until i can get feisty retraces to work. [03:28] i cant seems to open non beta pages :( i re-did URL to not use beta but still didnt brb i need to figure a few things out before i forget [03:28] ok [03:30] asac: this addess should open non beta https://launchpad.net/ubuntu/+source/apport/+bug/89916 [03:30] Malone bug 89916 in apport "[Feisty] apport-retrace fails to retrace bugs." [Low,In progress] [03:30] but it doesnt it re-adds beta to it [03:30] is there a way to disable beta view? [03:32] oh and sebs link above does do anything [03:45] Done downloading [03:45] --- stack trace --- [03:45] #0 0xb7f00410 in _start () from /lib/ld-linux.so.2 [03:45] #1 0xb7d504f1 in ?? () [03:45] #2 0x0805b30c in SIGTERM_oldact () [03:45] #3 0x0000000b in ?? () [03:45] #4 0xbfe63dc8 in ?? () [03:45] #5 0x08057596 in nsProfileLock::operator= (this=0xb, rhs=@0xbfe63d3c) at nsProfileLock.cpp:96 [03:45] No locals. [03:45] Backtrace stopped: frame did not save the PC [03:46] in chroot it works as far as grabbing the -dbgsym packages but ends in that. in non chroot it doesnt really grab the dbgsym packages and doesnt end in that [03:47] he? [03:48] what issues are we on here? [03:48] first: greasemonkey script of seb ? [03:48] there is no script there [03:48] second: stacktrace [03:48] what? [03:48] its untitled page without a popup for download [03:48] definitly [03:48] http://people.ubuntu.com/~seb128/bugtriage.user.js [03:48] i just opened [03:48] there is a java script file [03:49] im not getting anything there [03:49] you have greasemonkey installed already? [03:49] its blank [03:49] yes [03:49] and restarted ff already after installing it [03:49] which vversion? [03:50] firefox-greasemonkey: Installed: 0.6.6.20061017.0-2ubuntu1 [03:52] even if i open http://people.ubuntu.com/~seb128/ and click on bugtriage... it doesnt do anything at all. wont load wont think about loding [03:52] loading [03:54] and JS is enabled [03:54] firefox version 2.0.0.2+1-0ubuntu1.mt2 [03:57] all the other links on the page work fine its just that one that doesnt do anything [04:07] hmm [04:07] for me it pops up [04:07] asking me if i want to install the greasemonkey script [04:07] maybe i should check pop up blocker [04:07] hmm [04:07] don't think so [04:08] extension can always break popup blocker [04:08] maybe download with wget [04:09] and add through tools->greasemonkey->manage scripts [04:09] and there Edit [04:09] good idea :) [04:09] where you can choose script on hd [04:09] where did you get greasemonkey from [04:09] ?? [04:09] i installed it as ubuntu package iirc [04:09] asac: ubuntu [04:11] ok i have manage scripts open. so add it? [04:11] to included pages? [04:12] no [04:12] on the left [04:12] edit [04:12] and then there is a filepicker [04:12] again its not poping one up [04:12] wtf is going on here [04:12] you press on edit and nothing happens? [04:13] you see anything in javascript console? [04:13] asac: right [04:13] nope [04:16] crazy [04:16] what if you remove greasemonkey package and install from addons? [04:17] trying [04:20] nope still not opening anything [04:20] asac: what version of ff are you using? [04:21] hmm [04:22] egy [04:22] edgy [04:22] 2.0.0.2+... [04:22] maybe you have other extension installed [04:22] that breaks greasemonkey? [04:24] ill look at it in a bit i need to do something. [04:27] sure [04:33] i think i know what is messing it up :) checking now [04:35] thats strange [04:35] Warning: Error in parsing value for property 'display'. Declaration dropped. [04:35] Source File: https://beta.launchpad.net/+icing/style.css [04:35] Line: 12 [04:35] im gonna clear them and try again [04:36] hmm [04:37] those are page errors i also get them with wikis [04:37] you have problems i cannot tell :) [04:37] i guess they are not that bad [04:37] maybe they just exist for ie [04:37] http://tldp.org/LDP/Bash-Beginners-Guide/html/index.html this doesnt spit out anything [04:37] and firefox just verbosely ignores them [04:38] do you have extensions installed? [04:38] i think there are really some that are incompatible with greasemonkey [04:38] yes im disable them now [04:39] got a bigger edit button but still not poping anything up :( [04:39] try invoking the js by url too [04:39] cannot remember if one can really add by edit [04:39] maybe its indeed just update already added scripts [04:39] i have one installed and pressing edit brings file dialog [04:40] navigating to .js url pops up install script dialog [04:40] similar to the install extension dialog [04:40] ok ill try [04:40] that worked [04:42] still cant get out of beta :( [04:42] https://launchpad.net/ubuntu/+source/firefox/+bug/80533 [04:42] Malone bug 80533 in firefox "Firefox crashed while downloading flashplayer from adobe site" [Medium,Needs info] [04:42] that pulls up beta :( [04:44] it doesnt look like you can disable LP beta view [04:46] hmm [04:46] i managed [04:46] last time i tried :) [04:47] ah i found it [04:47] where ... now i can't find it :) [04:47] https://launchpad.net/ [04:47] you ahve to go to www.launchpad.net [04:47] asac: on top says disable for 2 hours [04:48] yes [04:48] ok what am i looking for on the page? [04:48] go to some bug [04:48] go to place where you would change statet [04:48] e.g. needs info [04:48] there should be new links [04:48] for bulk replies [04:49] Needs Backtrace] [Needs Details] [No Reply] [Forwarded] [Support Request] [Default Change] [Duplicate] [04:49] that? [04:50] sweet [04:51] now if we can get that for beta it would be alot of help ;) but beta always changes so maybe not best idea [04:55] gnomefreak: yes [04:55] i will work on this [04:55] noone asked why this person was Right click and choose save as for the flash rpm file. [04:55] beta should be not too unstable [04:55] i hope [04:55] asac: cool ty. might want to add "our" responces to some if you van :) [04:56] s/van/can unless its too much work than we can use them as is [04:58] its not #1 priority, i would say add that to your to-do-list on freetime :) [04:58] gnomefreak: definitly [04:58] we need our own responses [04:58] i might have a look at it see if i cant change it. [04:58] those are not of much help [04:59] it shouldnt be too hard, all the calls and everything are there just woud need to replace launchpad.net to beta.launchpad.net and things like that [04:59] atleast that is without looking at it [05:00] gnomefreak: i guess the html elements are not the proper one [05:00] form field might be in different place in hierachy [05:00] oh [05:00] so some html reading is necessary for beta too [05:01] anyway, skeleton is there [05:01] the rest is just work [05:01] you might have to do it than but i will look at it see if my limited knowledge can do it [05:01] there are xpath strings [05:01] those need to be adapted [05:01] maybe you recognize them [05:02] if not i can take a look at some point in near future [05:02] i will try to look at it before meeting and sometime after or before meeting i will let you know [05:02] oh damn meeting [05:02] i have to dial in [05:02] to mozilla status meeting [05:02] hmmm [05:03] i guess i can only comment sporadically [05:03] damn damn damn [05:03] its 1900 ? [05:03] UTC? [05:03] 18:00 UTC [05:03] oh [05:03] that might work [05:03] :) [05:03] so 1900 for you i think [05:03] 1900 utc is mozilla conference [05:03] ok [05:05] @schedule [05:05] Schedule for Etc/UTC: 06 Mar 18:00: Mozilla Team | 06 Mar 20:00: MOTU meeting | 06 Mar 23:00: New York LoCo Team | 07 Mar 12:00: Edubuntu | 07 Mar 17:00: First Launchpad Users meeting | 08 Mar 16:00: Ubuntu Development Team [05:05] @schedule europe/berlin [05:05] Schedule for Europe/Berlin: 06 Mar 19:00: Mozilla Team | 06 Mar 21:00: MOTU meeting | 07 Mar 00:00: New York LoCo Team | 07 Mar 13:00: Edubuntu | 07 Mar 18:00: First Launchpad Users meeting | 08 Mar 17:00: Ubuntu Development Team [05:05] ok === hjmf [n=hjmf@140.Red-217-125-227.dynamicIP.rima-tde.net] has joined #ubuntu-mozillateam [05:27] hjmf: would you mind if you did feisty retraces and i did edgys? i cant get feistys to run properly yet. this way you can focus on feisty and i can focus on edgy retraces. [05:28] gnomefreak: OK, I'll do feistys [05:28] ok cool :) thank you [05:28] btw have you tested new apport? [05:28] yes there are alot of things we need to look into === Admiral_Chicago [n=Admiral_@st074039212101.monm.edu] has joined #ubuntu-mozillateam [05:28] does it work fine [05:28] ? [05:29] for what Ive read it creates it's own chroot [05:29] not on edgy i didnt try it but on feisty theres alot i need to know before i can work it properly [05:29] you need to use either root or retrace-chroot/ fakechroot [05:29] hjmf: if you have not old apport in cache better not upgrade ... John said feisty is broken atm [05:30] but i havent had time yet to deeply look into that [05:30] for me it has been so i have alot of working to do with it [05:30] running it now after installing packages [05:30] asac: I'm using an old apport since I was not confident with the new improvements [05:30] see if it helped [05:31] hjmf: new improvments suck IMHO makes it that much harder to use [05:31] but i will keep you guys informed when i figure these things out [05:31] hjmf: wise man :) [05:32] gnomefreak: ok. But afaik it now downloads each time all the dbgsyms [05:32] gnomefreak: i think its just temporarily [05:32] asac: :) [05:32] yes sort of [05:32] if bugs are gone things will be more powerful [05:32] though maybe for most simple things a bit more difficult [05:32] but who knows [05:33] hjmf: for that to worky ou need to either use fakechroot or root [05:34] gnomefreak: ok. I'll read the docs. if any. [05:35] hjmf: bug 89916 might get you started [05:35] Malone bug 89916 in apport "[Feisty] apport-retrace fails to retrace bugs." [Low,Needs info] https://launchpad.net/bugs/89916 [05:35] *might* [05:36] @schedule barcelona [05:36] i keep getting WARNING: could not install missing packages: dpkg failed to unpack archives [05:36] @schedule Madrid [05:36] Schedule for Europe/Madrid: 06 Mar 19:00: Mozilla Team | 06 Mar 21:00: MOTU meeting | 07 Mar 00:00: New York LoCo Team | 07 Mar 13:00: Edubuntu | 07 Mar 18:00: First Launchpad Users meeting | 08 Mar 17:00: Ubuntu Development Team [05:37] I won't be online for the meeting [05:37] @schedule Chicago [05:37] Schedule for America/Chicago: 06 Mar 12:00: Mozilla Team | 06 Mar 14:00: MOTU meeting | 06 Mar 17:00: New York LoCo Team | 07 Mar 06:00: Edubuntu | 07 Mar 11:00: First Launchpad Users meeting | 08 Mar 10:00: Ubuntu Development Team [05:37] heh [05:37] http://bugzilla.gnome.org/show_bug.cgi?id=415179 [05:37] i may be in class as well [05:37] Gnome bug 415179 in general "crash in Movie Player: smoking a joint." [Critical,Resolved: duplicate] [05:37] :) [05:37] so lets reproduce that one [05:37] wait, no i'll be here... [05:37] :) [05:39] ok just uploaded log file to bug report for pitti [05:42] asac: that looks alot like the bugs we have with #34 0xb72d43f7 in pthread_mutex_lock () in retrace. (i dont remember numbers i do too many bugs at a time) [05:43] ok im off for lunch i should be here before meeting ;) [05:43] hmm [05:43] 0xb72d43f7 [05:43] is illegal [05:43] is that a long stack? [05:43] on the upstream bug yes on ours not so long [05:43] ok [05:43] if you find such a bug, let me know :) [05:44] 129 on upstream [05:44] i will [05:44] brb [06:22] see you, have to go [06:22] bye [06:27] grammar is *hard* === Admiral_Chicago points room to #ubuntu [06:28] err #ubuntu-meeting [06:30] asac: should i bother with a dapper chroot for retraces? [06:30] Admiral_Chicago: still have 30minutes [06:30] ;) [06:30] i know. [06:31] i may be in and out, i have my grammar hw to look at still... [06:33] gnomefreak: dapper has no apport nor crash reports i guess [06:34] asac: good point [06:34] dapper chroot would be of benifit to help on QA on security releases [06:34] :) [06:35] ok today ill try to get to it [06:35] have a problem here [06:36] seems bug 19552 is a dump bug. everyone just throws reports there and so far after the first 5 only 1 report is good. im assuming we have done most of them on other bug as i remember the users [06:36] Malone bug 19552 in firefox "Crash after firefox is opening a new window (when it should open the new URL in the same window/tab) - No More Crash Report Please!" [High,Needs info] https://launchpad.net/bugs/19552 [06:37] i would like to close this or do something with it. [06:37] i know 3 or 4 or the users were posting reports on any bug that looked the same. serge for example attached his crash report to over 6 bugs on the same day [06:38] what do you think best way would be [06:40] looks like i did most of them already. i will do the last one on there and see what i come up with [06:44] asac: heres one with #6 0xb7e15cc0 in __pthread_mutex_unlock_usercnt () from /lib/tls/i686/cmov/libpthread.so.0 [06:45] https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/19552/comments/52 [06:45] Malone bug 19552 in firefox "Crash after firefox is opening a new window (when it should open the new URL in the same window/tab) - No More Crash Report Please!" [High,Needs info] === dfarning [n=dfarning@72-160-220-159.dyn.centurytel.net] has joined #ubuntu-mozillateam [06:53] good morning all [06:54] hey david [06:54] Am I here at the correct time [06:54] good morning [06:54] yes [06:55] hey gnomefreak is every thing going ok at home [06:55] so far so good, aunts really sick thats why im in PA [06:56] ill be here for about a month. i hope less [06:58] Im sorry [06:58] its ok just have to see what happens with new meds [06:59] dad started a new cycle of chemo today so it is a bit touchy here [06:59] thats rough [07:00] sorry to hear that [07:00] ty [07:00] Howdy [07:01] hang in there.. I'v been where you are myself. [07:01] hi AlexLatchford [07:02] :) [07:02] AlexLatchford: you ready? and are you still chairing? [07:03] dfarning: some other time, i'd like to talk about the DerivativeTeam [07:20] asac: i assigned you to bug 19552 ;) please dont hate me :) [07:20] Malone bug 19552 in firefox "Crash after firefox is opening a new window (when it should open the new URL in the same window/tab) - No More Crash Report Please!" [High,Needs info] https://launchpad.net/bugs/19552 [07:20] gnomefreak: ok [08:06] Admiral_Chicago, you had a question about DerivativeTeam? [08:07] yea, what are you guys doing [08:07] just kicking it off? [08:07] yes [08:08] cool! need help? [08:08] basically I am trying to get a policy together where it is easier for our derivates to work with us [08:08] not just chuck our packages over the fence and forget about them;( [08:08] i think a large part is getting resources to work for another team. [08:08] i'd like to see more people doing xubuntu-doc work. [08:09] dfarning: you should talk to LP Team to get a +Downstream button added [08:09] so we can track stuff [08:09] working on that;) [08:10] I want downstreams to pass us good issues report [08:10] but they mostly use bugzilla [08:10] LP is more capable bt propritary;( [08:12] goodness, this grammar is impossible [08:12] dfarning: send me an email, i like your team idea [08:12] i'll be winning to help out as much as I can [08:13] will do and thanks === dfarning going to harass the LP guys about downstream tracker [08:13] just make sure its an email or else I won't get to it...i've become one of those people [08:14] Downstream tracker is important to us here at linspire. [08:15] nothing I sucks up more of my time than searching multiple databases for the same bugs [08:15] heh === ..[topic/#ubuntu-mozillateam:Admiral_Chicago] : Home of Ubuntu Mozilla Team - https://wiki.ubuntu.com/MozillaTeam | Bug Triagers read: https://wiki.ubuntu.com/MozillaTeam/Bugs/States & https://wiki.ubuntu.com/MozillaTeam/Bugs/Tags | Preview archives at https://wiki.ubuntu.com/MozillaTeam/PreviewArchives | [08:17] yup, thats a big waste === Admiral_Chicago goes to hw then class [08:21] hehe ... funny thing such a conference :) [08:22] Majost: what do you mean by downstream tracker? [08:22] what do you have in mind ... any specific ideas on how to improve launchpad in this regards? [08:24] Minutes available at.. https://wiki.ubuntu.com/MeetingLogs/Mozilla/20070306 [08:37] ty AlexLatchford [08:38] thanks AlexLatchford [08:44] asac, to check bugs on our side as well [08:44] and viceversa [08:48] I think a use case is in order here... [08:48] Lets start with an application crashing, and apport coming into action [08:49] user is directed to the launchpad site, enters the description of the bug and a search is executed for a similar bug [08:51] however a similar/same bug does not exist on launchpad, but may exist on bugzila.freespire.org or even upstream at Debian [08:53] ok [08:53] for crash reports its probably a traceback db which is needed [08:54] a central one where you can make your users commit to as well [08:54] but for other bugs i don't know [08:54] *nod* [08:54] it is a tough problem [08:55] if we have central db we need to ensure that we can properly identify issues that do not come from us/you [08:55] yup [08:55] thats where things get sticky [08:55] whos bug is it REALLY [08:55] i don't see a problem [08:55] is it a mozilla bug, a debian bug, etc. [08:55] if we have a db and can see that it originates from linspire [08:56] we have to look into crashes anyway [08:56] however for matching already found dupliates its helpful [08:59] I agree [09:00] in the end we cannot demand anything from the other side (e.g. fix now or else ...); so its only about improving information infrastructure so we don't duplicate effords. [09:02] and if you have patches that you think apply to us too, just make sure I see them, so i can get upstream approval and include at some point. [09:15] asac: this is the one we have alot of with pthread_mutex_unlock_* http://librarian.launchpad.net/6488411/Stacktrace [09:15] from bug 76608 [09:15] Malone bug 76608 in firefox "Crash when opening a bookmark via del.ico.us" [High,Needs info] https://launchpad.net/bugs/76608 [09:15] oops no [09:15] bug 77222 [09:15] Malone bug 77222 in firefox "crash from viewing java-applet containign page runescape.com on a low memory machine" [High,Needs info] https://launchpad.net/bugs/77222 [09:16] 77308 also [09:21] hmm [09:24] bug 76608 is [09:24] Malone bug 76608 in firefox "Crash when opening a bookmark via del.ico.us" [High,Needs info] https://launchpad.net/bugs/76608 [09:24] thats what i said too. not real sure what the mutex is but alot of bugs have it [09:25] @g_timeout_dispatch @nsAppShell::Run [09:25] bug 77222 is: [09:25] Malone bug 77222 in firefox "crash from viewing java-applet containign page runescape.com on a low memory machine" [High,Needs info] https://launchpad.net/bugs/77222 === asac waiting for lp [09:25] lp is slow as crap here [09:25] AlexLatchford: you still here? [09:26] Dimal's is same [09:26] im leaning towards bug 84716 to be more orca than fx [09:26] Malone bug 84716 in firefox "firefox crashes, screen divides after applying orca screen reader" [High,Needs info] https://launchpad.net/bugs/84716 [09:26] elpitagorico's is [09:26] @DocumentViewerImpl::Destroy [09:26] for now [09:27] @g_timeout_dispatch @nsAppShell::Run??? same this as nsAppShellrun? [09:27] no ... this is something new [09:27] just add those two to summary [09:27] and name it master of that crash [09:27] k [09:27] [@g_timeout_dispatch] [ ...] [09:27] i think 77222 should be used for elpitagorico's issue [09:28] e.g. [@DocumentViewerImpl::Destroy] [09:28] [@nsPluginInstanceOwner::Init@ [09:28] ^^ add that to 77222 as well [09:28] [@nsPluginInstanceOwner::Init] [09:28] of course [09:28] so 77222: [@DocumentViewerImpl::Destroy] [@nsPluginInstanceOwner::Init] :-D [09:29] so dont name it master? or still do [09:30] bug 77222 is as follows [09:30] Malone bug 77222 in firefox "[@DocumentViewerImpl::Destroy] [@nsPluginInstanceOwner::Init] " [High,Needs info] https://launchpad.net/bugs/77222 [09:30] sure master [09:30] k [09:31] always master if we have no other master for that [09:31] and move master to confirm [09:31] confirmed state i mean [09:31] k [09:31] not mt-confirm [09:31] mt-upstream is tag [09:31] should i report one for dimal or is he part of this bug? [09:32] drop a note that dimal is a duplicate from the other crash ... but that we use this report for elpit...'s crash [09:32] you can subscribe dimal to the other [09:32] as a servie [09:32] dupe of what crash? you said his was a new one i thought [09:32] no elpitagorico's is new [09:33] dimal is dupe of the first bug you mentioned [09:33] bug 76608 [09:33] Malone bug 76608 in firefox "Crash when opening a bookmark via del.ico.us" [High,Needs info] https://launchpad.net/bugs/76608 [09:33] or? [09:33] maybe verify that his stacktrace really has the timoeout issue [09:33] k [09:33] bug 76608 is master for [09:33] [@g_timeout_dispatch] [@nsAppShell::Run] [09:33] k [09:45] asac: what do you want to do with bug 85857. you said in bug to mark as dupe of filepicker if he didnt respond [09:45] Malone bug 85857 in firefox "firefox crashes when attempting to save video links" [High,Needs info] https://launchpad.net/bugs/85857 [09:50] y go ahead [09:50] close or dupe [09:51] whatever gives more karma :) [09:55] lol neither anymore [09:59] is bug 86362 a masterbug? [09:59] Malone bug 86362 in firefox "firefox crash [@gtk_xtbin_new] " [High,Needs info] https://launchpad.net/bugs/86362 [10:00] lp down [10:00] internal error 500 [10:00] ah [10:00] yes [10:01] but please [10:01] use [10:01] [@gtk_xtbin_new] [@nsPluginNativeWindowGtk2::CallSetWindow] [@nsObjectFrame::InstantiatePlugin] [10:02] thanks [10:02] k [10:02] please assign to me and move to confirmed stage mark mt-upstream ... and try to find duplicates :) [10:02] this looks interesting ;) [10:03] as i have worked a good bunch on plugin code because of the restyle_issues [10:03] whch we now will resolve on totem side [10:04] ok time for me to get ready to pick aunt up from work be back later or tomorrow [10:04] ty [10:04] bye [10:04] yw bye [10:05] i move it back to needs info as we definitly should try to get some testcase from hopefully some duplicate reports [10:05] guess has to to with flash plugin ... but probably a mozilla problem anyways [10:05] cu tomorrow === dfarning [n=dfarning@69-179-3-108.dyn.centurytel.net] has joined #ubuntu-mozillateam [10:23] council mail sent. === hjmf [n=hjmf@140.Red-217-125-227.dynamicIP.rima-tde.net] has joined #ubuntu-mozillateam [10:34] gnomefreak: yea [10:36] anyone else not receiving any ubuntu lists mail? [10:38] just got one [10:51] i guess i get them [10:52] though load has never been really high on lists i am subscribed to [10:52] of yes ... ubuntu-bugs ... i am still getting some mails for that list ... i unsubscribed 4 days ago or so [10:53] anyone have an idea how to list the number of installable packages? [10:57] installable? [10:57] hmm [10:57] grep in Packages.gz ? [10:57] 20818 according to Synaptic === Admiral_Chicago returns to doc work [10:57] yes probably you can do [10:57] that [10:57] :) [10:58] there has to be a CLI to do it. i hate GUIs for installing packages [10:59] yes probably grep in Packages.gz [10:59] should be somewhere in /var/... [11:00] maybe there is a higher level CLI program ... but have no idea [11:00] i'd like to know how many are in main specifically, then universe [11:02] e.g. [11:02] grep -c ^Package: /var/lib/apt/lists/de.archive.ubuntu.com_ubuntu_dists_edgy-updates_main_binary-amd64_Packages [11:02] should do the trick [11:02] Admiral_Chicago: just use the right Packages file [11:03] asac, are the retraces looking better? [11:03] which ones? [11:03] in general? or some specific? [11:03] well in general is -retrace meeting your need better? [11:04] hmmm [11:04] that didnot sound positive;( [11:04] can't tell ... luckily usually i only see good results :) [11:04] so i cannot say ... ask gnomefreak and hjmf who do most of retraces [11:04] from your perspective what still need work [11:04] definitly a backtrace db [11:04] i'll follow up with them [11:05] asac: i'll keep write that down [11:05] that automatically matches duplicates [11:05] and shows you all bug reporter messages on one page [11:05] so you might identify how to track an issue down (e.g. extract a testcase) [11:05] dfarning: further ... privacy issues [11:06] people should either be warned that report might contain private data [11:06] or original reports should go over https to some trusted maschine that automatically retraces [11:06] imo it would be best to do retraces right when report is captured [11:07] so on user maschine befor he submits [11:07] Linspire and guadalinux also had the same conserns [11:07] argument against symbolization on user maschine was a bandwidth thing [11:08] but at least for firefox, the core dump is probably more data than all dbgsym packages [11:08] the main problem with doing the retrace on the reporters machine is the hug number of dl needed [11:08] hmm [11:08] not that much i guess [11:08] setup a proper cache then it will at max be double packages then normal [11:08] whereas -dbgsym packages are smaller than the normal one [11:09] of course releasing in ~pitti on people.ubuntu.com would not be feasible [11:09] should go on mirrors [11:09] pitti repo is getting huge [11:09] yes [11:09] as we ask him to retain stuff [11:10] how much percentage of mirror size has it? [11:10] that would not be needed [11:10] hmmm [11:10] if triagers see the retrace are there still privacy issues [11:10] yes ... but user can read retrace and look (in normal case) [11:10] so its not as critical [11:10] the core dump contains all [11:11] stacktrace is just a tiny fraction [11:11] was wonder how much of the problem will go away when retrace on handled in the data center [11:11] don't know [11:11] i still don't see this happen [11:11] but who knows [11:12] martin claims he is close;) [11:12] to what? [11:12] automatically retracing? [11:12] i hope so [11:12] :) [11:12] getting retraces on service [11:12] That guy is great [11:13] i think we should expect some disrupting happenings in the beginning :) [11:13] but i guess they will work out nicely [11:13] New service rollouts are always perfect on linux;) [11:13] next step would be to add data to trace db instead of bts [11:13] its only bloat [11:13] we can then pick top-crashers and open bugs to track them on our own [11:14] I think that is farther away [11:14] still debate over necessity of crash db [11:14] no one else seem to be getting hit as hard as firefox;( [11:14] for packages with huge amount of different crashes like firefox [11:14] its important [11:14] other might not care [11:15] if they just get hit by a flood of duplicates [11:15] of one or two issues [11:15] yeah ... thats why we are lead users [11:15] and we are here to make launchpad the best service in world [11:15] i think a good crash db is the right way [11:15] darn right [11:16] can be provided as service to downstream [11:16] to easily get the big picture [11:16] and more input for rare crashes [11:16] agree [11:17] at best that crash db gets a read-only integration to talkback as well :) [11:17] but in the long run upstream releases will probably die [11:17] with distribution package installs already much higher than official downloads [11:17] I you don't mind I will log off and summarize your ideas, and see who we can get to buy in. [11:17] dfarning: please wait [11:18] oh sit more [11:18] i am preparing a report to launchpad lead [11:18] on request by mark [11:18] what is that [11:18] so maybe don't get things running one by one [11:18] s/sit/shit/ [11:18] we should find all things we need and put them into one document [11:18] then we can send one mail which will get highest attention [11:18] to those that can decide [11:19] for mt related needs/wants [11:20] yes [11:20] its [11:20] mark things we as heavy load users can provide valuable input on how to improve things [11:20] s/things/thinks/ [11:21] is that to elliot or matthew? [11:21] i don't remember [11:21] i have to look up [11:21] in mail [11:21] its been a few weeks [11:21] :) [11:22] ar you going to get a chance to work on it it the next few days? [11:22] you can help ... we can setup a wiki where we aggregate what we need [11:23] dfarning: you can try to get people to convince that they need a crash db [11:23] anyway [11:23] ;) [11:23] if it works through normal channels fine :) [11:24] but as you said that people appear somehoe against this [11:24] i thought it would be better to push through other channels [11:24] any ... summarizing my ideas is good :) [11:24] not against...just can't figure out how to make it work easily [11:24] what? [11:24] ah [11:24] ok [11:25] yes [11:25] the crash db [11:25] it requires resources [11:25] of course [11:25] to many man hours [11:25] Ok i will sumarrize your thought tonight and post them on a wiki by tommorow [11:26] exactly ... so lets summarize the reasoning and why its important and how it help downstream collaboration [11:26] to empasize our position [11:26] this is a ball I would like to get rolling [11:26] thats good [11:26] ty [11:26] yeah but we need make the ball a high quality one with decent weight :) [11:27] I'll try but Alex may need to check my grammer;( [11:28] hehe [11:28] bye [11:28] name it braindump page about malone improvements [11:28] :) [11:28] so no grammar is needed [11:28] bye [11:32] fast work on the ML