[00:08] white: can you reproduce that anywhere? [00:09] the security focus thing only mentions IE [00:09] oh below there is [00:09] not sure what it means :/ [00:12] white: if you can make something up for testing, feel free to [00:12] ,9 [01:01] asac: you're sure MFSA 2008-53 doesn't affect xulrunner? [08:50] white: yes. that and https://bugzilla.mozilla.org/show_bug.cgi?id=459906#c38 [08:50] Error: Error getting Mozilla bug #459906: NotPermitted [08:51] hmm ... without bugzilla account i cant show you ... but not important in this case. its sessionstore which is a browser/ feature (like i said above ;)) [08:54] good morning asac [08:56] BUGabundo: hey [08:57] white: even more its nothing 1.8.0 branch actually has ;) [08:57] (session restore was invented for ffox 2) [11:26] [reed]: trick needed: what kind of search flags do i have to set to see all bugs that have approval1.8.1.next* ? [11:26] [reed]: (e.g. i want ...next? and ..next+) ;) [12:22] [reed]: i think i have it. thanks [12:32] @time [12:32] Current time in Etc/UTC: January 12 2009, 12:32:52 - Next meeting: Server Team in 1 day === ubott2 is now known as ubottu [14:53] asac, how come my url has not be shortened in identi.ca? I used the web site directly. [14:54] and i selected one of the free services [14:59] fta2: the website only shortens when there is a need to shorten ;) [14:59] e.g. when your line would exceed 140 [16:18] oh [16:38] ff with an authenticated proxy is a nightmare. zillions of popups asking for a password *and* providing no reason [16:39] fta2: at startup right? [16:39] e.g. multiple tabs fighting for a proxy authentication ;)? [16:40] yep, and when each addon wants to check for update [16:41] there is a bug for that ... i am sure ,) [16:41] this is under xp but i guess it's the same on all arches [16:41] its even linked from launchpad ;9 [16:41] yes its known [16:41] i always thought that the "no reason" thing was due to our xul split [16:41] but seems its not [16:41] makes me happy [16:42] so ... transition done [16:42] lets see how many build failures will fall down on me now :( [16:43] how could we do the python xpcom transition? the current package comes from xul 1.8 [16:43] fta2: does anyone depend on python xpcom? [16:43] i need one from 1.9 or 1.9.1 for openkomodo [16:44] what is python xpcom? [16:44] the binding so you can run python components in-process of firefox/xulrunner? [16:44] i think so, right? [16:44] i guess so [16:44] fta2: atm it doesnt work, right? [16:45] e.g. we still get this python error in error console? [16:45] we disabled it in 1.9bsomething [16:45] fta2: well its still in there her: [16:45] well, maybe not [16:45] /usr/lib/xulrunner-1.9.0.5/components/libpyloader.so [16:45] /usr/lib/xulrunner-1.9.0.5/components/pyabout.py [16:46] /usr/lib/xulrunner-1.9.0.5/libpyxpcom.so [16:46] ... anyway. i think the problem is that libpyxpcom.so isnt found [16:46] so we need a glue fix here ... i guess [16:46] fta2: does the py xpcom code actually still exist in trunk? [16:50] if so, i know what to do [17:03] please fix it in 1.9.1 first, then I'll merge in 1.9.2 [17:03] i have to run [17:43] hello.. fta or asac around ? [17:45] super breakage with a clean install [17:45] nm-applet: error while loading shared libraries: libplds4.so.0d: cannot open shared object file: No such file or directory [17:45] FF3.0 broken... and a bunch of other packages.. [17:46] FF3.1 Ok but libplds4 ??? what package does it come from ? === asac_ is now known as asac [17:52] Well... found it and its Xulrunner as I can see... [17:52] a mess... [17:52] http://ubuntu.pastebin.com/m16a5b2f4 [19:45] fta: Hey, LaserJock wanted me to ping you re: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/269188 and a possible SRU for Hardy, would that be possible? [19:45] Ubuntu bug 269188 in nspr "Extreme slowness, "Firefox is already running" error for >3 users launching Firefox in LTSP environment" [Medium,Fix released] [19:46] asac, ^^ from plun, i guess you need to rebuild xul and nm-applet [19:46] Lns, iirc, it's just nss, not firefox, right? [19:46] fta: I guess so - nspr [19:47] yep, nspr, not nss. [19:47] I just saw the comment from "LP Janitor" that it was fixed in jaunty [19:47] I cant test it as all my sites are hardy [19:47] Lns, could you confirmed that it fixes the bug in jaunty before we start an SRU for hardy? [19:48] argh [19:48] not even a VM ? [19:48] no :( but im sure i can call on someone(s) to test [19:50] there's also my ppa, you can just dl the nspr debs for hardy, they have the fix [19:51] oh! [19:52] fta: url me :) [19:52] fta: if I used the packages from your PPA on Hardy and tested, would that be enough for an SRU request? [19:55] yes [19:55] * fta hopes asac will not complain :P [19:56] well i'll call on the LTSP/Edubuntu people I know to test as well so we dont do anything without verifying completely [20:00] Im going to reboot myself and then upgrade, i'll bb in a bit === rzr is now known as rZr [20:11] Lns, don't use my ppa completely, just my nspr so we know for sure it's it. [20:12] fta: ugh.. ok this is what i just updated: http://logicalnetworking.net/other/nsprupdate.png [20:12] good thing i got a screenie ;) [20:13] is that ok, or should i downgrade anything? [20:14] you got just that? [20:14] dpkg -l | grep fta [20:14] (i sign all my packages with ~ftaX) [20:15] libnspr4-0d libnss3-0d libnss3-1d libpng12-0 pastebinit is what i upgraded to just now [20:16] please downgrade at least nss. png and pastebinit are not important as they are unrelated [20:18] ok [20:31] fta: ok i think im good now, downgraded libnss stuff to 3.12.0.3-0ubuntu0.8.04.4 [20:31] but libnspr4-0d and libnspr4-dev are your ppa versions [20:32] good [20:33] and just locked libnss3-0d (and 1d) versions. i think thats it right? [20:34] it is [20:34] awesome, thanks fta - mucho appreciado! [20:37] hrm..locking versions in synaptic doesnt reflect in apt-get :( [20:39] fta, can i safely remove your PPA after upgrading nspr? [20:39] i cant recall some of the more involved apt situations [20:43] yep, no problem. [20:43] fta: thx === Jazzva_ is now known as Jazzva [21:47] fta: FYI, I've posted this wiki to the LTSP lists so people can test. Im hoping to get a lot of tests done and get back to you for an SRU asap. http://lns.wikidot.com/nsprupdate [21:48] Lns, ok [22:32] fta asac my FF3.1 lost most/all file asociation! [22:36] Lns: what is your plan? [22:39] fta: whats the issue for plun? [22:47] asac: ping [22:48] does alt+NUM work for you with FF? [22:49] hello.. fta or asac around ? [22:49] super breakage with a clean install [22:49] nm-applet: error while loading shared libraries: libplds4.so.0d: cannot open shared object file: No such file or directory [22:49] FF3.0 broken... and a bunch of other packages.. [22:49] FF3.1 Ok but libplds4 ??? what package does it come from ? [22:49] Well... found it and its Xulrunner as I can see... [22:49] a mess... [22:49] http://ubuntu.pastebin.com/m16a5b2f4 [22:49] asac, ^^ [22:49] @time [22:49] Current time in Etc/UTC: January 12 2009, 22:49:48 - Next meeting: Server Team in 17 hours 10 minutes [22:50] @time [22:50] Current time in Etc/UTC: January 12 2009, 22:50:09 - Next meeting: Server Team in 17 hours 9 minutes [22:50] asac: still having trouble with your ISP [22:50] yeah ;) [22:50] obviously [22:53] fta: what was the problem above? [22:54] asac, donno. you have all i have. [22:54] fta: sure but you lead the discussion ;) [22:54] hehe [22:54] ok i see ... so probably the entropy fix of nspr [22:55] mine is pidgin! keeps crashing [22:55] $ ldd /usr/lib/xulrunner-1.9.0.5/xulrunner-bin | grep plds4 [22:55] libplds4.so.0d => /usr/lib/libplds4.so.0d (0xb7f37000) [22:55] asac, .0d is still there? [22:55] fta: plun? i dont know what issues he has [22:55] fta: for me it sounds a bit like he has rotten old things [22:56] fta@ix:~ $ ldd /usr/lib/xulrunner-1.9.0.5/xulrunner-bin | grep plds4 [22:56] libplds4.so.0d => /usr/lib/libplds4.so.0d (0xb802d000) [22:56] that's mine [22:56] true [22:56] and i have: [22:56] $ ls -l /usr/lib/libplds4.so.0d [22:56] lrwxrwxrwx 1 root root 11 2009-01-11 13:59 /usr/lib/libplds4.so.0d -> libplds4.so [22:56] after the transition [22:57] oh, right [22:57] the relinking is done in maintainer scripts [22:57] maybe that failed for him? [22:57] oh [22:57] i think he tried to upgrade [22:57] that failed ... and the upgrade-abort case left him with bad links maybe? [22:57] let's see. i bet he started a thread [22:57] he said "super breakage with a clean install" btw [22:58] http://ubuntu.pastebin.com/m16a5b2f4 [22:58] thats his error message [22:58] you see what the root cause there is? [22:58] yeah [22:58] clean install [22:58] how? [22:58] ;) [22:59] the error is an upgrade error i guess [23:03] asac: my plan is to test fta's PPA nspr package for Hardy to see if my issue with >3 LTSP terminals launching a FF3 session doesnt lag due to lack of entropy [23:04] Lns: ok. let us know [23:04] asac: will do for sure [23:05] fta: why is there no single word about where the random thing was fixed? was that an upstrewam commit? [23:06] asac, it's in changelog, but it was indeed committed upstream, so no tweak in our packaging for that [23:06] Lns: you dont need to visit -testing to coordinate an SUR [23:06] you need to go through us ;) [23:06] anyway, if that package fixes it for you we probably need to do a backport of the patch [23:07] fta: right. i meant "why is there no single word in changelog about the where" ;) [23:07] fixed upstream: or something would have been nice ;) [23:07] but all fine [23:07] the bug has the upstream link [23:07] asac: ok, i know where you live (on irc) ;) [23:08] Lns: if you drop a confirm comment in bug and ask for hardy SRU i will probably see and do ti [23:08] e.g. nominate, backport, release [23:08] asac, it's the topmost entry, i thought it was obvious [23:09] asac: ok, cool. I'll do that after getting at least 2 hardy-based confirmations from either my own sites or me+other LTSPers [23:09] fta: sure [23:09] Lns: thanks [23:10] asac: np, thank you guys for the fix(es) :) much appreciated by all of us LTSP net admins [23:12] fta: found any thread from plun? you think he will come back? [23:12] nope, none [23:12] i guess he'll come back [23:12] hehe ;) [23:13] not sure ... maybe he is one of those that just reinstall ;) [23:13] # [23:13] Setting up xulrunner-1.9 (1.9.0.5+nobinonly-0ubuntu1) ... [23:13] # [23:13] /usr/lib/xulrunner-1.9.0.5/xulrunner-bin: error while loading shared libraries: libplds4.so.0d: cannot open shared object file: No such file or directory [23:14] # [23:14] dpkg: error processing xulrunner-1.9 (--configure): [23:14] fta: are we running anything in postinst? [23:15] hmm. --gre-version [23:15] fta: you really think that --gre-version is a good thing to do? [23:16] yes, works well [23:16] whhat is the problem? [23:16] not sure [23:16] have the feeling that postinst happens after links have been removed, but before they have been reinstantiated? [23:17] lol [23:17] did I do that? [23:17] --gre-version is not meant to be used in the xul package [23:17] fta: yes [23:17] it's for pkgs depending on xul [23:17] you use it there [23:17] damn [23:17] fta: but even on higher packages it could happen i think [23:18] maybe its the way i reshuffle stuff [23:18] i do half in preinst ... the other half in postinst [23:18] well, at postinst, xul should already work [23:19] no one complained with 1.9.1/2, it's the same code [23:19] fta: not if nspr postinst is run after it i think [23:19] hmm [23:19] right [23:19] it should [23:20] preinst moves stuff away [23:20] then unpack happens and all should be fine [23:20] only then .postinst stuff is called [23:21] fta: ok ... so postinst.in should get XUL_VERSION=@XUL_BRANCH@ i guess [23:21] (regardless of whether thats the issue at all) [23:21] fta: oh. [23:21] postinst.in of what ? xul ? [23:21] the --gre-version is in debian/xulrunner-1.9-gnome-support.postinst [23:21] also in debian/xulrunner-1.9.postinst.in [23:24] so the transition catched two bogus packages [23:24] seahorse-plugins and epiphany-extensions failed everywhere [23:25] hmm [23:25] http://launchpadlibrarian.net/21134821/buildlog_ubuntu-jaunty-lpia.epiphany-extensions_2.24.1-0ubuntu2_FAILEDTOBUILD.txt.gz [23:25] epiphany-browser-dev: Depends: epiphany-gecko (>= 2.24.1-1ubuntu4) but it is not going to be installed [23:25] why isnt that dependency wait? [23:28] probably a soyuz bug... given back to builders [23:30] asac: fta: !!! https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/269188/comments/18 =) =) =) [23:30] Ubuntu bug 269188 in nspr "Extreme slowness, "Firefox is already running" error for >3 users launching Firefox in LTSP environment" [Medium,Fix released] [23:31] That is soooo awesome =) [23:31] excellent [23:33] targetted bug [23:34] thanks asac [23:38] fta: does ~fta PPA already have native notifications? [23:38] for 1.9.2 [23:38] hm, no [23:39] next batch [23:39] k [23:39] i do that ~ twice a week [23:39] yeah. thought you already did it [23:40] (thats why) [23:48] upgrading to oo3 [23:49] yeah me too [23:49] 6.8Mb/s [23:49] fta: maybe you could just do a bzr bd --builder='debuild -S -sd' on current head and push it ;)? [23:49] i hope it will be faster soon, i just signed for an upgrade to 18Mbps [23:49] hehe [23:50] but arent 6.8M/s already more than 24? [23:50] asac, if you want it that hard, i can just push it, it's all automatic [23:50] Mbps [23:50] * asac is brave [23:51] Mbit/s not MByte/s [23:51] so ooo 3 looks exactly like 2.4 for me ;) [23:51] oh there is a zoom handle [23:51] thats nice [23:52] but has visual glitches ;) [23:52] darn, i was hoping they'd implement the ribbon bar =p~ [23:52] maybe they have [23:52] ;) [23:52] me looking at ooo is similar to my mom looking at ubuntu feisty vs. hardy ... "oh the background is different" ;) [23:53] haha [23:53] asac, did you test that your libnotify stuff at least builds ? [23:53] i love that about so many oss projects..even major revisions stick to their UI roots, which is really nice for the user [23:54] Ok, i'm off to test out the nspr fix - wish me luck! [23:55] well, still as ugly as before [23:57] fta: yes [23:57] fta: just push [23:57] fta: the code is already in current snapshot [23:57] just new packaging required [23:57] fta: i tested that it builds and that it works if -gnome-support is installed and that it falls back to "normal" when its not installed