[00:00] thats one of th reasons why we currently think about how to best reorganize stuff [00:01] ok [00:01] i want to stop the inflationary team creation... but also inflationary ppa creation [00:01] let me know if I can help [00:01] thats why we need to carefully thinka bout the key services we want to provide outside the main archive [00:01] and reduce them to a minimum [00:11] i think my laptop battery just got a bad hit [00:11] jumped down from 65% to 5% and then went off ;) [00:11] ehehehe [00:26] fta: There? [00:30] fta: Just an FYI, if it didn't catch your eye, but the thunderbird daily builds are failing b/c of one of the patches no longer directly compatible with the source. And the version currently published is broken in the sense that it doesn't work at all (atleast for me) [00:45] * micahg was wondering why FF3.5 was so slow, it turned out my cpu was stuck at 500mHz [07:38] ping asac bug 365965 [07:38] Launchpad bug 365965 in ubufox "Firefox3.5 recommends ubufox but should suggest ubufox" [Undecided,Triaged] https://launchpad.net/bugs/365965 [07:39] Here's the response I wrote: http://pastebin.ubuntu.com/210954/ === ripps_ is now known as ripps === asac_ is now known as asac [10:29] gnomefreak seems to be back ;)< [11:14] gandi: hey [11:14] hi [11:15] gandi: do you have some time today or tomorrow to explain to me how the trees in the l10-mozilla repo are structured? [11:15] asac: in a few hours, sure :) [11:16] gandi: i tried to look at them to see what needs to be done to fix our export [11:16] gandi: but the layour looks rather random to me ;) [11:16] gandi: cool [11:16] i will ping you this afternoon then ;) [11:16] mozilla 496683 [11:16] Mozilla bug 496683 in Build Config "Organize removed-files.in, make it not suck" [Normal,Resolved: fixed] http://bugzilla.mozilla.org/show_bug.cgi?id=496683 [11:16] gandi: also, did you talk to the "ro" translators? [11:16] gandi: (do you remember what this was about at all or should i send a mail?) [11:17] asac: I did ask them [11:17] but was out of time to have a full chat, I'll do this this week [11:17] asac, http://hg.mozilla.org/comm-central/rev/27b3a0d2aa23 [11:17] gandi: cool. no hurry. [11:18] nice [11:18] fta2: does that mean our testsuite works now? [11:18] eh? it's what makes tb3 ftbfs [11:19] it's too big of a change, i don't have time for this right now, feel free to have a look [11:19] fta2: oh [11:19] fta2: yes. thats on my list for ... _now_ ;) [11:20] several people already reported that ftbfs [11:21] shhhh you dont see me, i can barely see you :) [11:22] fta2: ok i updated the -daily PPA description telling them to contact our mailing list or this channel to report issues [11:22] https://edge.launchpad.net/~ubuntu-mozilla-daily/+archive/ppa [11:22] gandi: hiiiiii [11:22] oop [11:22] gnomefreak: ^^ [11:22] ;) [11:22] gnomefreak: good to h ave you back [11:23] it was just yesterday that i wondered: "hell, didnt gnomefreak say that he will most likely be back in jul - hope all went well" [11:23] :) im here for a bit with one eye closed and screen at some very very big res [11:23] asac: july 27th is next eye [11:23] gnomefreak: at least you can _see_ something. did the surgery go well in general? [11:24] asac: yep as expected [11:24] btw tbird-3 is borked [11:24] fta2: right [11:24] as is mozilla-devscripts [11:24] gnomefreak: right [11:24] ok good known [11:24] fta2: so you bumped snapshot on branch already good. [11:25] fta2: did you start on the patch? [11:25] e.g. is there something i should start with [11:25] asac, no, I just had a look [11:25] fta2: any hints, while the orig is downloading ;)? [11:25] or just diverged patch for now? [11:25] it seems they are doing what we need now [11:26] maybe our patch is no longer needed [11:26] ok i will check that [11:26] * gnomefreak smacks self [11:26] does anyone else experience severe focus problems? [11:26] (btw, the bot has a feature to bump the changelog) [11:26] fta2: you mean, on .head or on .daily? [11:27] * gnomefreak didnt put 2 and 2 together last night. m-d is lookijng in old place for upstream. sm moved since it is now synced with tbird [11:27] to update .head from the .daily [11:27] asac: focus? not like i can tell, but what do you mean [11:30] fta2: if thats what we want its easy enough to do manually (e.g. merge from .daily) [11:30] i think its ok actually [11:30] gnomefreak: well if i click somewhere its often not accepted [11:30] also sometimes i switch apps and i cannot type until i re-switch apps [11:31] etc. [11:31] fta2: when does it merge back? [11:31] when it fails? [11:32] i havent seen that yet [11:32] asac, what i meant is the changelog bump in .head is not manual. I was tired to have to visit .daily, edit .head, commit and push, just to change a version and a date. So it's automatic now. [11:33] asac, there's no merge back from .daily to .head, .daily is not supposed to contain any change, expect changelog and the tweaked deps in control [11:34] anyone on karmic have a working lower panel in gnome? running apps showing up? [11:35] trash is there but no running apps [11:35] asac, btw, o3d doesn't work here (nvidia x64). the plugin is loaded, but it doesn't render anything (and no error in the console, beside the usual canberra-gtk-module) [11:37] hmm [11:38] asac, http://paste.ubuntu.com/211182/ *sigh* [11:38] fta2: btw, why dont we build -enable-static for tbird? do you remember the reason? [11:38] yeah. looking at that [11:38] too [11:38] was the idea that we wanted to use the same build way xulrunner uses? [11:38] because we are not building ff statically either [11:39] yeah [11:39] thats what i thought [11:39] even before the split with xul [11:39] but ffox is a xulapp [11:39] right i remember [11:40] do as you wany ;) [11:40] want [11:40] let me fire off a normal build now after fixing the patches to see where we stand ;) [11:41] fta2: its a bit odd. there is no --enable-static/disable-static or --enable-shared, etc. in our rules [11:43] hmm. gwibber disappeared again. seems it crashes quite regularly now [11:45] for me, it's better, no crash in a week [11:45] hmm [11:46] but i dent less those days (i mean, even less than before), and it always crashed while i was writing [12:07] what is the panel addon called that has the open windows in it? example: open terminal now on lower panel it shows a button for terminal [12:08] gwibber seems again crashed [12:09] mines working ok other than a problem with ident [12:09] @firusvg i have given up on !firefox on linux .. my hopes lies with google chrome now [12:11] yay clearing the window works now and not sure what the extra tab is for now [12:16] asac: what version of gwibber? [12:25] gnomefreak: latest karmic [12:27] hmmm seems karmic has gotten the latest daily [12:27] 1.2.0~bzr346-0ubuntu1 [12:27] it works here no problems other than errrors on indent.ca retrieving [12:27] gnomefreak: yes. i uploaded that [12:28] but now - a few days later i get more and more crashes ;) [12:28] not sure why you are crashing unless it depends on mopnoi [12:28] mono [12:28] nope doesntr [12:29] doesnt [12:38] g/f thinks im crazy again. she over heard me asking the dog how to fix system [12:42] asac: we should look into getting SM2 into Karmic however im waiting for everything to be finished with eyes and having glasses before i dive into it again. a few patch problems last i looked but it is on b3 (should be finished or atleast very close by release [12:55] gnomefreak: sure. do you know whats the current status of sm2? [12:55] is it at least at beta? [12:55] asac: b3 [12:56] as for state its in eh not sure since i havent fixed the FTBFS in ~a month [12:56] one of our patches was conflickting [12:58] ok ;) [12:58] asac: one minute ill get you last failure [12:58] currently working on getting tbird 3 fixed [12:58] so based on that i might be easy to also fix sm [12:58] 2 [12:58] last known failure for SM2 http://launchpadlibrarian.net/27243867/buildlog_ubuntu-karmic-i386.seamonkey-2.0_2.0~b1~hg20090528r2718%2Bnobinonly-0ubuntu1.9.10_FAILEDTOBUILD.txt.gz [12:59] tbird bug here is that no boxes are showing up not sure if that is what you are working on or not [12:59] ok thanks [12:59] np [13:00] gnomefreak: that problem is a minimal nspr/nss version requirement [13:00] asac: have you started on the OO.o patch for mozilla? [13:00] e.g. you need to bump the minimal version for using --system-nspr/nss [13:00] asac: than maybe i fixed that in my branch [13:01] i have done that once already IIRC [13:01] * gnomefreak checks branch [13:01] https://code.edge.launchpad.net/~gnomefreak/seamonkey/ubuntu-2.x-9.10 [13:02] yep needed another bump damnit [13:02] gnomefreak: you need nspr dump i guess [13:03] >= 4.7.5 [13:03] ill update it while your on tbird [13:03] lets see what else is wrong if anything [13:03] USE_SYSTEM_NSPR := $(shell pkg-config --exists 'nspr >= 4.7'; a=$$?; if test $$a != 1; then echo 1; fi) [13:03] make that 4.7.5 [13:03] gnomefreak: or even 4.8 now on latest trunk i think [13:03] (which we dont even have packaged yet) [13:04] nss should be ok now [13:04] gnomefreak: try 4.7.5... but if it still fails on current karmic you need 4.8 there [13:04] k [13:05] we should really use the version that is on system instead of naming version [13:06] gnomefreak: no ... the version in rules is important [13:06] without that you cannot do builds on systems that dont have high enough version [13:06] so no backports etc. [13:06] just adjust it properly and all is fine and the package does the right thing [13:06] we dont backport most of our apps anyway [13:06] e.g. it uses system lib if its good enough [13:06] will do [13:06] gnomefreak: we backport everything [13:06] e.g. -daily ppa [13:07] ah thats right [13:07] has builds from hardy to karmic [13:07] based on the same branch [13:07] so its important that our packages just build everywhere [13:07] well i just closed a bug on backporting 3.5 for hardy. that is bad idea in system outside of PPA's IMHO [13:10] grrrrr org.freedesktop.devicekit.disks.filesystem-mount-system-internal no [13:10] udev-extras? [13:11] devicekit makes me think that [13:12] although by the sounds of it udev-extras was replaced by udev :( [13:32] gnomefreak: right. udev-extras is now gone again (at least libgudev moved to udev) [13:39] well its not mounting usb drives nor ejecting cd/dvds [13:42] Hello, isn't firefox-3.5 now final ? [13:43] if m-d uses hg clone http://hg.mozilla.org/comm-central/ mozilla why the hell would SM1 not work [13:43] why is Shiretoko codename still being used ? [13:44] looks to be final. are you sure you are not using 3.5.1 [13:44] its in umd repo [13:45] firefox-3.5 (3.5+nobinonly-0ubuntu0.9.04.1) [13:45] that one still uses Shiretoko [13:45] AnAnt: thats ok [13:46] https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-karmic-firefox-3.5 [13:46] i dont have 3.5 installed only .1 [13:46] in short: we only ship the default browser officially branded [13:46] jaunty default is ffox 3.0 [13:46] ok [13:46] karmic is still 3.0, but that will change as soon as the spec above gets implemened [13:47] * gnomefreak gone for a month and i miss all kinds of stuff [13:48] thanks [13:49] AnAnt: i hope i find time to announce how things go on my blog soon [13:51] * asac scared: asac@hector:~/ubuntu_bzr/thunderbird-3.0.head$ bzr st [13:51] Segmentation fault [13:55] either these changes are massive or m-d doesnt like me anymore [13:55] same place > 1 hour [13:56] tbird 3 fixed in branch [13:56] fta2: can you kick off a ubuntu2 for yesterdays daily? [13:56] tbird 3 [13:57] just in case they break something new :) ... so we get at least a good build today [13:57] that bug has happened a few times in tbird3 cycle [13:58] builders are idle ... so good time to kick this [13:58] at least the one i saw [13:58] gnomefreak: thats ok. its a normal to break stuff if new files dont get installed et al [13:58] but now we have static build which should be a bit better [13:58] ah it was all due to shared? [14:00] i faintly remember shared/static builds topic with upstream [14:00] asac, done [14:00] thx a bunch [14:03] ok something is wrong here :( i dont want 2.1 [14:03] i want 2.0b3 [14:03] seamonkey-2.0-2.1~a1~hg20090706r3013+nobinonly [14:04] anyone can tell me why m-d grabbed 2.1 instead of recent 2.0 [14:06] i dont mind working on 2.1 but would like to fix 2.0 first [14:10] ok so m-d grabs latest testing build for 2.0 fails to grab 1.1.17 and onkly grabs stable calendar [14:11] * gnomefreak needs to rest my head [14:11] letting 1.1.x go for a while to see if maybe its not dying [14:15] gnomefreak: i think that 2.0 probably moved to its own brtanch [14:15] so your md rules pull in 2.1 now [14:16] they should move the newest one to a new branch and leave old ones where they are. makes sense even outside of m-d [14:17] ok 1.1.17 seems to be working at least its connected and pulling in latest [14:18] * gnomefreak smoke while i think about how to tackel that or even if i have time before doctors appt. [14:26] ok today im wokring on 1.1.17 if it id done when i get home than i might start on 2.0 d rework [14:26] md even [14:30] mozilla 495057 [14:30] Error: Error getting Mozilla bug #495057: NotPermitted [14:31] asac: any idea why i am denied [14:31] theres no CVE number for this fix for some reason [14:42] ok gone for a while started SM1 build [14:50] gnomefreak: the bug is security sensitivbe [14:51] no need to check it [14:51] what info are you looking for [14:51] ? [14:54] i was hoping for a CVE but i used the MFSA 2009-33 [14:56] ok its building,, i need to get ready for dr appt. ill see you in a few hours [14:58] yeah one MFSA didnt have a CVE [14:58] checkout what i documented in icedove upload to debian [14:58] i think i left out the CVE for -33 [15:37] 75 Ns Jul 06 Martin Pitt (2.8K) Next karmic gdm upgrade WILL BREAK your system [15:37] fta2: gnomefreak: ^^ [15:39] asac: seems like a regression in the plasma-widget-network-manager cuz wicd connected just fine for me [15:40] eagles0513875: didnt i say that yesterday? [15:40] kick plasma .... long live nm-applet [15:40] asac: you wanted me to try and determine if it was a regression or not [15:41] im not even using the nm-applet cuz in hardy that wouldnt even work for me [15:41] im using wicd [15:41] eagles0513875: i wanted you to check nm-applet not wicd [15:41] ahhh if you would like ill do that now [15:41] or what did i say? [15:41] great [15:41] we want to know if its plasmas fault alone [15:41] i would htink yes [15:41] yes [15:42] and it is a regression cuz an older svn version that is in jaunty works just fine [15:42] yeah that would be the case then [15:42] eagles0513875: after verifying that nm-applet works fine you could check whether there is newer stuff in svn [15:42] ya but we know that since its working with wicd that the wifi card or kernel arent to blame [15:42] also you could try to downgrade to jaunty widget version and see if that helps [15:43] eagles0513875: no. testing with wicd is useless [15:43] even if wicd works it doesnt mean that kernel isnt broken [15:43] ok whats the exact name of the nm-applet package [15:43] wicd uses only the most basic features of the wifi kernel stack [15:43] so you cannot compare that [15:43] eagles0513875: network-manager-gnome [15:44] whats the difference between network-manager-gnome and just plain old network-manager [15:44] eagles0513875: network-manager is the daemon (the actualy manager) [15:44] gotcha [15:44] network-manager-gnome is the applet you can use to manage it [15:44] similar to what plasma should do if it gets ever finished [15:44] but i think that kde will move to lava- before they finish anything ;) [15:48] just kidding ;) [15:48] its just that kde folks always start new things without fixing the old stuff ;) [15:48] but i think thats the case everywhere [15:53] lol asac you cant make it any more obvious your a gnome user lol [15:54] i am pretty open minded [15:54] but i am suffering quite a lot seeing that knetworkmanager and frieds are always lacking behind [15:55] and nobody from the kubuntu team really taking a lead on that ;) [15:55] certain aspects of kde i love [15:55] if i knew programming really well i would [15:55] but im a novice programmer [15:55] i dont care about kde and gnome much ;) [15:55] just about NM [15:55] and FFocx [15:55] and other things of course ;) [15:55] let me try the gnoem nm [15:56] problem is that i begged so much in the past on kubuntu state of network managing and often got back "we dont really care" ;) [15:56] same for ffox integration in kde [15:56] i wanted to drive that, but answer i got when asking for info/help was "we dont care much because we have konqueror" ... which imo is dishonest to all users that use ffox [15:56] eagles0513875: yeah. ensure that plasma widget is killed [15:56] then start nm-applet [15:57] from the command line [15:57] i rebooted [15:57] and wicd removed it [15:57] but there is no lil widget or applet for the nm [15:57] well yeah. you need to get rid of wicd if you want to use NM anyway [15:57] from what i saw it removed it [15:57] well. wicd also removes network-manager [15:57] so you dont have network-manger at all now [15:58] kick wicd. install network-manager and network-manager-gnome ;) [15:58] i installed network-manager-gnome and as it was installing it it remove wicd [15:58] yeah [15:58] i have network-manager-gnome installed according to apt-cache policy [15:58] so you need to start nm-applet manually [15:58] kde folks forced me to not start applet on log-in if you are on kde [15:58] ;) [15:58] dont ask me why [15:58] thats strange [15:58] i would think that users that install nm-applet want to have it running [15:59] hehe so what do i type in network-manager-gnome [15:59] exactly [15:59] * asac considers to change that back and conflict with plasma-widget-network-manager [15:59] eagles0513875: nm-applet [15:59] thats what you type [15:59] sry for all these questions im so used to the widget working and not having to touch anything [15:59] #well here is a bug [15:59] if i start it from the command line the ctrl+c the applet disappears [16:00] ive seen some programs where i ctrl+c and it stays there [16:00] thats ok [16:00] ctrl+c is should kill processes [16:00] if process prevent that they must have a good reason [16:00] should i background it [16:01] eagles0513875: if you want to keep it running you could probably also start it using alt+f2 [16:01] coudl as well [16:01] e.g. whatever kde facility allows you to start commands [16:01] couldnt i use nm-applet & to bg it [16:01] eagles0513875: but for testing you can just keep the terminal open and keep it running there? [16:01] try it [16:01] i am [16:01] if its working fine. if its not, its not something we care about i guess ;) [16:02] usually it gets started on login [16:02] it seems to want me to setup a keyring which i dont want to [16:02] only if you want to debug stuff its started from terminal [16:02] eagles0513875: you need to in order to test it [16:02] you can delete the keyring later [16:02] it shouldnt be required though [16:02] eagles0513875: questionable. its a gnome app [16:02] you can create a system connection and set the passphrase there [16:03] then it wont use the keyring [16:03] not sure if NM allows you to get that far though [16:03] it was asking me to create a new keyring [16:03] it connects [16:04] good [16:04] maybe NM should default to making connections "system connections" [16:05] i will think about it and talk to nm developers [16:05] imo it would be great if we could make a less-gnome dependent app out of it [16:05] though kde folks probably wouldnt want it because its gtk ;) [16:06] i honestly dont care [16:07] kde 4.3 is nice and improving on performance but im impressed how zippy gnome is [16:08] yeah. i promissed to try kde ... but it didnt work because compiz/composition still doesnt work here on my GPU [16:09] jdstrand: there? [16:09] jdstrand: so the -proposed bits are verified and now we wonder whether you wanted us to first copy that to -updates [16:10] or directly to -security and from there to -updates [16:10] asac: I'll go to security [16:10] jdstrand: see -devel [16:10] jdstrand: pitti wants to know if you or he will do the roll out ;) [16:10] yeah, see -devel [16:10] ack [16:12] asac: intel gpu [16:14] yeah intel is probably working [16:14] been lucky with nvidia [16:14] but my intel system has only a tiny disk ;) [16:14] but that is a nasty bug i must say [16:14] i have ati [16:15] hehe why not install kubuntu onto a pen drive [16:15] actually one of the chips that i always get told that they work perfect [16:15] and use that as a persistent portable install [16:15] until i show them that compositing is still borken ;) [16:15] ati is a nightmare graphics wise [16:15] nvidia ftw [16:15] well. ati is not that bad actually [16:15] the free driver is improving and rocks on lots of chips nowadays [16:15] but not on mine :( [16:15] probably because it was a high-tech gamers card once ;) [16:16] man talking about gaming cards lol [16:16] if you want i wont even go there [16:25] asac: ty for your help man [16:28] eagles0513875: so you can live with the solution for now? can youplease file a bug against plasma-widget-network-manager so i can make it important and put it on release teams radar? [16:28] file it just on launchpad [16:28] or can you link me to the wpa bug that there was for jaunty [16:29] eagles0513875: its a regression in karmic, right? [16:29] eagles0513875: we should have a new bug then. [16:29] ya but there was a similar issue that was in jaunty where one couldnt connect to wpa encrypted wifi [16:34] yes. most likely [16:34] but open a new bug for the karmic problem unless you really thinkits the same still [16:39] i cant find the jaunty one so will open a new bug [16:43] ping asac [16:44] asac: https://bugs.launchpad.net/ubuntu/+source/plasma-widget-network-manager/+bug/396180 [16:44] Ubuntu bug 396180 in plasma-widget-network-manager "plasma-widget-network-manager regression with connectiong to wpa connections" [Undecided,New] [16:46] micahg: yep? [16:46] hope that bug helps some if any [16:47] asac: is that bug good enough for ya or you need more info [16:47] eagles0513875: can you attach the file i asked for (directly after reproducing) [16:48] i just aksed [16:48] it never showed up for me over here [16:48] asac: is this response ok: http://pastebin.ubuntu.com/210954/ for bug 365965 [16:48] Launchpad bug 365965 in ubufox "Firefox3.5 recommends ubufox but should suggest ubufox" [Undecided,Triaged] https://launchpad.net/bugs/365965 [16:48] last comment [16:48] let me check [16:48] didnt i comment on that bug already?` [16:49] wb gnomefreak [16:49] micahg: i think its a dejavu bug [16:50] the apturl is the problem [16:50] but i feel reluctant to remove a recommends [16:50] its recommended for ubuntu to have that [16:50] yes, I'm not worried about that part right now [16:50] asac: apologies if you did as im jumping back and forth between a bunch of stuff and soon have to leave [16:50]