[00:06] seems those 'events suppressed' are what's making the sound crappy /w alsa [00:52] E: module-hal-detect.c: D-Bus error while parsing HAL data: org.freedesktop.Hal.NoSuchProperty: No property info.capabilities on device with id /org/freedesktop/Hal/devices/usb_device_45e_29_noserial [00:52] E: module-hal-detect.c: D-Bus error while parsing HAL data: org.freedesktop.Hal.NoSuchProperty: No property info.capabilities on device with id /org/freedesktop/Hal/devices/usb_device_45e_29_noserial_if0 [09:45] fta: my guess is that its ppp ... need your /etc/ppp/options and the command line arguments for pppd you see in syslog [10:03] fta: so lets create thunderbird-3.1.head ;) [10:04] I don't think we should build that yet daily ... but well; if its just a matter of adding a line to your build config, just do that i would say [10:09] asac, http://paste.ubuntu.com/115742/ [10:11] asac, https://edge.launchpad.net/~ubuntu-mozilla-daily/+archive/ppa [10:11] fta: and the command line? (it was cut off in the log paste you gave me) [10:11] tb3 needs a better nss in hardy/intrepid [10:12] asac, NetworkManager: [1234114356.551458] nm_ppp_manager_start(): Command line: /usr/sbin/pppd nodetach lock nodefaultroute ttyUSB0 noipdefault usepeerdns lcp-echo-failure 0 lcp-echo-interval 0 ipparam /org/freedesktop/NetworkManager/PPP/0 plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so [10:12] same for both [10:12] ..SIMs [10:14] hmmmmmm [10:15] asac, i guess you're not getting the error logs of the daily ppa, right? [10:23] fta: seems not ... hmm [10:23] was the last meeting in september? [10:24] cant find anything to subscribe [10:24] gnomefreak: probably yes. [10:24] ok im gona clear adgenda and fix link in topic [10:26] what are we doing with NCommander's Membership request? [10:27] gnomefreak: drop it [10:27] or ping him [10:27] gnomefreak: he probably is on -motu or -devel [10:27] ok [10:29] asac, this is a problem then (the logs) [10:29] yeah [10:31] fta: asked on #launchpad === gnomefreak changed the topic of #ubuntu-mozillateam to: Welcome to the Ubuntu Mozilla Team: | Mailing List: ubuntu-mozillateam@lists.ubuntu.com | Please help Mozilla QA tracker: http://tinyurl.com/6yo6g7 | Next meeting TBA, if you would like add a topic for the next meeting please add it to the agenda. The agenda is available at: http://tinyurl.com/2ekzoq. [10:42] we really need tinyurl back in repos [11:02] * gnomefreak goes for smoke since nothing is working atm. [11:03] eheh gnomefreak... smoking is bad [11:03] you should _want_ to stop [11:36] ok now i can go for smoke and coffee and maybe breakfast ;) [11:39] fta: filed a bug [11:39] fta: 327134 [11:39] bug 327134 [11:39] Launchpad bug 327134 in soyuz "add support to subscribe to PPA uploads/build failures" [Undecided,New] https://launchpad.net/bugs/327134 [11:44] Hello, why is the xulrunner package not synch'ed with Debian ? [11:44] I see xulrunner & xulrunner-1.9 source packages in Ubuntu [11:44] I see xulrunner (1.8) & xulrunner-1.9 source packages in Ubuntu [11:45] while the xulrunner in Debian (testing & unstable) is 1.9 [11:57] AnAnt_: because xulrunner in debian is a mess ;) [11:58] asac: ok, I have a problem, I need the libmozjs 1.9 [11:58] asac: yet it does not exist in Ubuntu [11:58] none of our packages are synced from debian normall we push ours to debian at lease some of them [11:58] AnAnt_: yes. thats intentional. libmozjs is not a first-class lib as there are no ABI/API guarnatees upstream [11:58] ok back to morning break [11:59] we will work on improving that together with upstream [12:00] asac: well, is that the reason that in Debian libmozjs 1.9 is libmozjs1d (not 0d as in 1.8) ? [12:01] AnAnt_: no. thats ok if it was underlined by an official upstream policy; the problem is that there is even no guarantee that 1.9.0.7 will have no ABI breakage over 1.9.0.6 [12:01] so debian tries to track ABI/API (like you said with libmozjs1d ...), but nobody has a plan what happens if a security update breaks it [12:02] i think its unlikely that this happens, but we have to stay hard so upstream starts thinking about proper ABI procedures for mozjs [12:02] AnAnt_: didnt we talk about all this before? [12:03] asac: we did ? [12:03] asac: we talked about firefox plugins before [12:03] asac: extensions that is [12:04] so, Debian guys weren't hard about that matter, right ? [12:05] AnAnt_: yes. its most likely ok. but not suitable for our main archive [12:05] AnAnt_: also if we do that we break upstream binary compatibility too [12:05] which debian doesnt care about either [12:06] e.g. stuff build against debian mozjs wont work with upstream builds or anywhere else [12:06] AnAnt_: so the goal is that upstrea mozjs gets proper so version and ABI/API policy [12:06] once thats there we will make mozjs a standalone packjage [12:07] AnAnt_: which app needs mozjs? [12:07] AnAnt_: if its for universe you can use the approach google-gadgets took -> e.g. use a glue [12:07] asac: elinks (for javascript support) [12:07] but thats not suitable for main [12:07] asac: it's a special build that I do by myself [12:08] asac: neither the debian nor ubuntu packages of elinks enable javascript support [12:08] AnAnt_: i would suggest that you robb the google-gadget glue code ... in that way your builds will work on all distros that have a proper xulrunner build [12:08] asac: what do you mean by "use a glue" ? [12:08] AnAnt_: look in google-gadgets [12:08] and what they do [12:09] AnAnt_: http://paste.ubuntu.com/116019/ [12:09] thats in google-gadgets. you need to steal them, build and link them statically against your stuff and maybe adjust the codec [12:10] well ... most likely [12:10] if you are not a developer you need to ask upstream about that [12:10] steal them ? [12:10] isn't it GPL ? [12:10] or so [12:10] look at the files. stealing == copying [12:11] ok [12:11] (without breaching licensing of course)= [12:12] in this case, I won't need to get mozjs 1.9 ? [12:15] AnAnt_: you need to depend on xulrunner-1.9 then ... yes. [12:16] huh ? [12:16] oh, ok [12:36] AnAnt_: http://identi.ca/notice/2208082 ... hope we get a solution for jaunty+1 [12:48] asac: i got to thinking about patch in SM2. if i edit it in /mozilla/ it wont apply. i'm fairly sure we cant edit it in our debian/patches dir. and if so autoconf will fail(i think) is there an easy way around this? [12:50] gnomefreak: sorry ... let me fix [12:50] ok [12:52] gnomefreak: ok committed ... rev 192 [12:53] thanks. damn that was fast [12:55] gnomefreak: i had it fixed here ... just forgot to committ on friday [12:55] ah [12:55] it was just a strip-leve thing in the patch [13:28] ok gonna let it build ill be back to check on it in a bit. [13:46] asac: thanks for the help, I decided that the glue would be too much, so I fixed the upstream code to be compatible with mozjs 1.8 (I just had to comment a single line) [14:07] AnAnt: well 1.8 will die now ;) [14:08] it has to be removed from #jaunty [14:08] actually should already have happened in intrepid [14:16] asac: ping [14:17] is there a wiki page I can bookmark [14:17] to know EXACLY how to debug NM connection time outs? [14:21] https://wiki.ubuntu.com/DebuggingNetworkManager is this it? [14:36] BUGabundo: yes but that doesnt/cannot give you infos on all [14:38] bug 214366 [14:38] Launchpad bug 214366 in mozilla-thunderbird "Can't delete a folder if Trash already contains a folder of the same name" [Low,Confirmed] https://launchpad.net/bugs/214366 [15:02] what the hell i cant put upstream tb bug on LP bug [15:02] what link should i be using? [15:02] asac: feel free to fix tb3, otherwise, it will keep failing everyday [15:03] gnomefreak, you can't, it's not in the repo yet [15:03] fta2: tb 2 is [15:03] oh, thought you meant tb3 [15:03] nm [15:03] cant link to upstream bug report [15:04] fta2: do you use .head for all ? [15:05] ok that did it :) [15:05] asac, yes, fix head, the bot will catch it [15:06] asac, you wont see the daily bump in .head, it's in .daily [15:08] asac: mark the bug you forwarded upstream from bug 214366 since mozilla bug 66763 was already reported [15:08] Launchpad bug 214366 in thunderbird "Can't delete a folder if Trash already contains a folder of the same name" [Low,Triaged] https://launchpad.net/bugs/214366 [15:08] Mozilla bug 66763 in Backend "Deleting a folder fails when there is already a folder with the same name in Trash" [Normal,New] http://bugzilla.mozilla.org/show_bug.cgi?id=66763 [15:08] s/from/as a dupe/ [15:10] i cant mark dupes upstream [15:11] fta2: yeah. but i guess the build failure is not new on hardy/intrepid ... so .head will do [15:11] yes [15:11] well, b1 worked [15:11] hm, maybe not, my ppa has a fresh nspr/nss couple [15:15] yeah. probably [15:15] i will commit the fix [15:15] just want to get the proper orig ;) [15:23] get it from the daily ppa [15:24] Why is Firefox 3.0.6 in the jaunty archives and in the bazaar branches for Intrepid and Hardy but not in their archives (as in security) yet? [15:24] Anywhere I can get it? [15:25] (without building it myself from the bazaar branches) [15:25] Or is the security problems fixed in 3.0.6 not relevant for Ubuntu? [15:26] (Sorry if I sound inpolite, English is not my first language) [15:30] sveinung: please help ou ttesting [15:30] sveinung: we have a security preview archive [15:30] where can I help? [15:31] add that to your sources and keep it ... when you have issues you should always escalate here [15:31] sveinung: https://edge.launchpad.net/~ubuntu-mozilla-security/+archive [15:31] sveinung: take that ... add that to sources.list [15:31] asac: thank you [15:31] sveinung: there is also a testplan [15:31] sveinung: if you could run that it would be grate [15:31] link? [15:32] * asac looks [15:32] sveinung: https://wiki.ubuntu.com/MozillaTeam/QA [15:50] i fucking hate LP [15:53] is ther eno upstream info for seamonkey? only thing i get is chatzilla when i change it to seamonkey it gives me our package [15:54] gnomefreak: maybe [15:54] let me check [15:54] for some reason its not letting me mark it upstream [15:54] bug 327214 is the problem one [15:54] Launchpad bug 327214 in seamonkey "seamonkey does not support gpg signing" [Undecided,New] https://launchpad.net/bugs/327214 [15:55] fta2: can you hand over seamonkey maintainer ship to mozillateam :) ... and update the package info ;) so the bugs get automatically a good upstream target [15:55] ah thatsd why [15:55] i needed to report another bug but cant recall on what :( [15:56] good news SM2 is still building :) [16:00] * gnomefreak wonders what i have to do to get upstream duplicate powers [16:01] asac, I just changed the maintainer [16:04] thanks [16:04] still no way to do it [16:05] if i add Seamonkey it doesnt give me upstream option [16:05] gnomefreak: ok i think it should work now [16:05] try again [16:06] nope [16:06] got it [16:06] took a littl etime for it to change [16:08] ok off to wait for build to finish its freezing me up too much [16:12] fta2: I just figured out what caused the firefox 3.1b3 instant segfault on my machine [16:13] fta2: I had a pacakge named "libxul-dev" installed. after removing that it works fine, currently running 3.1 from the daily ppa [16:13] hm, so the pkg-config files were mixed up [16:15] asac, how come your tb3 patch will help? it will move to dep-wait, that's it. or did I miss something? [16:15] asac: I did step 1 to 10 on the testplan on Firefox 3.0.6. Since I don't use GNOME I can't do step 11. I also tested the plugin Gnash on youtube, and VLC on Wikimedia commons. Gnash on Youtube worked, VLC worked for a time once without finishing and once crashing Firefox [16:15] except that all worked [16:17] sveinung: ok. so is vlc a regression? [16:17] or did you get those with 3.0.5 too? [16:17] fta2: yes you missed something ;) [16:17] fta2: i touched rules not control [16:17] hence, "soft-depends" like i named it in changelog [16:17] asac: I think I also had it in 3.0.5 [16:18] sveinung: thats ok then. we are mostly intersted in regressions [16:18] thats the focus of all the -security testing [16:18] sveinung: are you running hardy? [16:18] or intrepid? [16:18] anyone know how to get the from address of a selected message? [16:18] asac: Intrepid [16:19] asac: do you have a min? [16:20] BUGabundo: ask ... and i will decide ;) [16:20] i have to run to post-office as my tax declaration had missing parts which are now overdue [16:21] will run in 5 minutes after this security stuff has finished and i can give it a quick test [16:21] eheh [16:21] just need guidelines on how to debug NM [16:21] https://wiki.kubuntu.org/DebuggingNetworkManager [16:21] been reading this [16:22] I'm at Tokamak, and the eduroam here is not connecting [16:22] with PPA NM [16:22] now a friend arrived [16:22] and can't connect either with interpid [16:22] thought you might want fresh logs [16:22] from ibex and jaunt [16:22] BUGabundo: what type of accesspoint is that? [16:22] a b g n? [16:22] and yes, I know u want new bugs for jaunty to new reports [16:23] let me check nm-tools [16:23] well nm-tools doesnt show if you are not connected i presume [16:23] ah [16:23] check whether iwconfig gives a hint [16:23] when associated [16:23] so if I can't connect (or at least autenticate) [16:23] how can I know? [16:24] what is that wpa-psk ? or -eap? [16:24] eduroam: Infra, 00:1C:C5:7B:14:D0, Freq 2412 MHz, Rate 54 Mb/s, Strength 51 WPA WPA2 Enterprise [16:25] BUGabundo: manually wpasupp works? [16:25] let me ask my friend [16:25] and chipset also [16:25] kill NM first? [16:25] intel iwl 3945 [16:26] kill NM first? [16:26] BUGabundo: for manually? sure [16:26] kill NM and wpa [16:26] ok [16:27] wpa_suplicant -i ipw bla bla? [16:28] BUGabundo: on that chipset for some disable_hw_scan=1 helps as module parameter [16:28] where is that? [16:28] BUGabundo: read the wpasupplicant README.modes.gz [16:28] ok [16:30] BUGabundo: add the option from above to /etc/modprobe.d/options for your chipset [16:30] ok have to run now [16:31] bye [16:32] anyone know the overlay in thunderbird for viewing a message [16:32] i am trying to extract the from/to/subject of the currently selected message [16:48] asac: what is your user name on bugzilla? [16:49] * gnomefreak finally figured out how to follow you [16:56] im going to lunch. Sm 2 succeeded will push it after lunch to PPA. [16:56] also does tb support hotmail, yahoo and friends? === asac_ is now known as asac [17:47] gnomefreak: asac at jwsdot.com [17:50] thanks [18:14] cant push unreleased to PPA :( [18:14] fixing than pushing than off for a bit maybe take this afternoon and spend with amily [18:20] fta: oh also if you want ppp debugging (probably one of the causes) add "debug" to /etc/ppp/options [19:18] fta: hey, can you push your updates from now on into the "debian" branch for gwibber instead of "packaging"? [19:18] fta: for gwibber I mean [19:18] jcastro, do you mean *.packaging is dead now? [19:19] i use it for the daily builds [19:19] I didn't know you were making daily builds! [19:20] jcastro, https://edge.launchpad.net/~gwibber-daily/+archive/ppa [19:21] oh dude, neat! [19:21] fta: if you push your changes into just "debian" then I'll make builds like weekly or something based off of it [19:22] where is that branch? [19:22] i need to see if my bot is able to use it [19:22] lp:~gwibber-team/gwibber/debian [19:22] fta: you have all this automated? [19:23] yes, i'm not crazy ;) [19:23] got all that up someplace? [19:23] WANT. [19:23] same as https://edge.launchpad.net/~ubuntu-mozilla-daily/+archive/ppa [19:25] i'm tired of updating my own ppa, and i'm good at scripting so here we are [19:26] fta: have you chatted with james_w at all? He wants to do this as part of distributed development [19:27] jcastro, hm, it's flat, my bot is not able to use it as it is [19:27] jcastro, over gwibber, yes, when he announced he was writting a spec about the same thing [19:27] yeah, I'm still drafting it :-) [19:27] ah, he's here. :p [19:28] I was going to chat to you when I had something ready to look at [19:28] ok I just wanted to make sure you were both aware of each other [19:28] it sounds more and more like you've already done it all though :-) [19:28] i had the daily PPA in mind for a long time, even before PPA ever existed, even before i joined ubuntu [19:29] well, i have two scripts doing all the work, with a few requirements [19:30] i would think that our scripts are as of now quite tailored to the way we do maintain branches and how our get-orig-source is implemented [19:31] i need a package maintained in bzr, and if it's not native, it should have a get-orig-source target that knows how to fetch and name a fresh tarball, and it should be mergeable with bzr bd --merge [19:32] that's all about it [19:32] fta: ok. so what is next is probably a quick "probe if something new exists" [19:32] it does that too [19:33] so you dont need to pull full sources in case there is no fresher tarball [19:33] right [19:33] fta: is that probe quick? is that available as a separate "functioN" ? [19:33] no [19:33] no function or not quick? ;) [19:33] ? [19:34] not separate and in fact, it's still pulling the sources, preferably from a local branch, before it realizes there's no new snapshot available [19:35] yet, it still checks for updates in the packaging branch [19:35] fta: yeah. i think when thats fixed without pulling sources we could ask james_w to provide hooks so we can plug-in your logic at some point in his "full ubuntu" thing [19:35] so the debian branch from jcastro doesn't fit, it doesn't work for the bzr bd --merge step [19:36] james_w: in your plans: do you have a quick-probe for new stage? or are you using "get latest" and then check whether thats newer than existing? [19:36] asac, not sure, my stuff is half in shell, half in perl.. I think james_w wants 100% python or something [19:37] asac: don't know [19:37] https://code.edge.launchpad.net/~fta/+junk/ppa-scripts [19:37] james_w: can you comment on that? do you need everything to be reimplemented in python? [19:38] preferably [19:38] so preferably != mandatory ;) [19:38] it will be useful to have access to bzrlib for one thing [19:38] (you can ignore build-ppa.pl for now, it's not used by the bot) [19:38] well, it's mandatory I guess [19:38] yeah, i figured that out a long time ago, lp = python [19:39] thanks for the scripts though, I'll look at how they work [19:39] james_w: is it realistically that we get mozilla daily builds within a year? [19:40] that's up to you guys, or someone else [19:40] now that we have our own, i dont really think its urgent ;) [19:40] I'm not going to maintain them [19:41] james_w, don't bother reading the code, i plan to write a small spec when i can find so time [19:41] cool [19:41] james_w: ok different viewpoint: when will the framework land so someone could start to impelement the mozilla backend parts etc. [19:41] ? [19:42] it's a spec for jaunty [19:42] k [19:43] james_w: well. the spec reads "proof of concept" ;) [19:44] i would think mozilla wouldnt be part of that ;) [19:45] still drafting [19:45] https://blueprints.edge.launchpad.net/ubuntu/+spec/daily-upstream-builds-poc [19:45] asac, from UDS: https://wiki.ubuntu.com/UDSJaunty/Report/Foundations (look for "Daily Upstream Builds POC") [19:46] "For 9.04, we will do a simple proof of concept with a small number (approx. 5) of upstream projects." [19:46] yeah. so a year seems not that too far away [19:47] "however the projects we choose will also depend on the anticipated difficulty in implementation" :) the mozilla packages are probably on the difficult side [19:47] especially considering that things that involve launchpad often take ages to sink in [19:47] yeah, that's why i finally decided to start with my own bot [19:48] and my own server [19:49] i will be limited by disk space if i start doing archives, not by bandwidth [19:49] nor by cpu, unless i add a lot more packages [19:51] for ff and xul, i think it's good enough, for tb (and sm, sb, chromium, ..) it needs more work as sources come for several vcs, my local branch feature is not enough [20:07] ok resurrected from swap o rama [20:07] reset button pushed [20:08] where/when did you quit? [20:24] fta: i have everything in my irssi [20:24] just couldnt answer ;) [20:25] i disabled swap now [20:25] rather want OOM kills [20:31] my desktop experience has never been so bad [20:33] asac, tb3.1 means forking the tb3 branch [20:34] it's the same comm-central, by different xul [20:34] moz1.9.1 for tb3 and moz-central for tb3.1 [20:46] fta: hmm. sounds like thats not the final setup [20:47] fta: lets wait until upstream has forked comm-central or something [20:47] fta: if its the same comm-central, how do you get the 3.1? thought that client.py just gets whatever is right for that branch [20:47] they said they want their nightly based on moz-central [20:47] mozilla bug 469835 [20:47] Mozilla bug 469835 in Build Config "Change version number to 3.1a1pre for Thunderbird comm-central+mozilla-central builds" [Normal,Resolved: fixed] http://bugzilla.mozilla.org/show_bug.cgi?id=469835 [20:48] there's an ugly hack in there: version.txt vs version-191.txt [20:48] so it's easy for me to use in mozclient .conf [20:55] hmm [20:55] ok [20:55] i dont care much then for 3.1 ... i guess 3.1 will take 4 years ;) [20:56] by then, I'll be using what? [20:56] 5.2 ? [20:56] lol [20:56] only $DEITY knows that [21:02] gwibber crashed, again [21:07] now, i can't connect anymore [21:08] LOL [21:08] for me, its identica [21:09] it won't connect [21:09] jaiku and tw are fine [21:09] oh, good, i'm not alone then [21:09] but it was just now [21:09] in the last 2 hours [21:09] maybe something is bad on identica servers [21:09] altough XMPP works [21:09] identichat and gwiber don't [21:09] humm API change? [21:21] i doubt it [21:21] identi.ca is just under high load imo [21:21] but #gwibber crashing isnt really good imo ;) [21:22] lots of my Apps crash [21:22] when I have HUGE IO [21:22] pidgin, gwibber, kmail, blablalbla [21:22] bad coding I guess [21:23] I should file bugs against that, but it would fall under wish bugs or something [21:24] that's also my view of bugs in lp, they won't move unless you move them yourself. sad [21:25] yeah [21:25] if I really care for a bug, I have to nag the QA team or the mantainers [21:26] and I really hate to nag ppl [21:26] _as you have found from what I do here on the # _ [21:28] errr ... "Microsoft's decision to limit Windows 7 Starter Edition to running only three concurrent applications" [21:29] reminds me of windows 2 :) [21:29] crazy [21:29] ROFL [21:29] i mean i thought windows 7 could really be a good thing and compete with ubuntu [21:29] but now that i read this ;) [21:30] * asac wonders how users feel when the first dialog pops up stating: "ETOOMANYAPPSRUNNING: select which one to kill: firefox, word, skype" [21:30] or icq + skype ;) [21:31] http://en.wikipedia.org/wiki/File:Windows_2.0.png [21:31] the firefox/IE -> done [21:31] now open word -> ETOOMANYAPPS [21:31] or even chrome: open 3rd tab -> two many processes running ;) [21:31] i think now i get why windows 7 will be less resource hungry and better suitable for netbooks ,) [21:32] its similar to thought we had for the classmate PC and restricting ffox to just have 3 tabs ;) [21:32] because 4 tabs would cause the system to lock down due to mem consumption [21:32] amazing [21:32] http://en.wikipedia.org/wiki/Windows_1.0 => that's LTS ! Release date: November 1985, Unsupported as of December 31, 2001 [21:33] heh [21:33] depends on what "support means" ;) [21:33] most likely "hey, i have windows 1 and have this problem; A: please upgrade to windows 2" [21:34] now its "hey, i have windows 1 and have this problem; a: we dont support windows 1 anymore (hangs up)"! [21:34] http://www.pcpro.co.uk/news/246859/windows-7-a-nonstarter-on-netbooks.html [21:35] "Microsoft says the restriction is designed to ensure that users get the best possible performance from limited netbook hardware." [21:35] hah [21:35] just like i said for the classmate [21:35] just that MS is either incompetent or pretending [21:35] more likely, "hold on, we're sending you a sales squad by jet" [21:35] probably ... but only if you have more thatn 100 installs i guess ;) [21:50] * asac dancing [21:50]