[01:43] finally managed to get my Unity 3D working for the first time in almost a week, I think clearing ~/.cache was the trick [01:51] jbicha, that is weird [01:51] yeah, too bad I used rm -r and not just mv [01:52] kenvandine: resurrected your contacts mir [01:53] thx! [02:36] TheMuso: are you around? [03:01] jbicha: Luke tells me that the answer is “no” :) [03:02] Apparently Telstra's decided that it doesn't want to provide internet, even from a mobile. [03:19] oh ok, I was just looking for someone interested in uploading vte3 [03:20] Ok I have limited connectivity now. [03:21] jbicha: I am around now. [05:11] Good morning [05:12] chrisccoulson: awesome! [05:12] chrisccoulson: does the same apply to Tbird as well? [05:21] dobey: bug 939173 - looks like sso-client is now trying to use qt? [05:21] Launchpad bug 939173 in ubuntu-sso-client "ubuntu-sso-login crashed with ImportError in start_setup(): No module named qt" [High,Confirmed] https://launchpad.net/bugs/939173 [05:21] I thought that only affected the control center [05:27] DBO thumper hey guys... this bug here: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/936818 ROAF saw this same thing on Intel, I saw it on nvidia...looks like it isn't just nvidia driver thing... any other thoughts? [05:27] Launchpad bug 936818 in compiz "Visual Corruption on Desktop" [High,New] [05:30] jasoncwarner_: Good afternoon... Hope you weren't kep offline too long today, and I hope you didn't miss anything important. :) [05:31] TheMuso: telstra down? I ended up tethering for a bit today...wondered what was up [05:31] jasoncwarner_: So you are not on Telstra for mobile? Yes, down so badly that it took out a large chunk of internet usage around the country. === m_conley is now known as m_conley_away [05:32] TheMuso: I am on telstra mobile...weird... [05:32] I'm back up now with both....how long were you down? [05:33] jasoncwarner_: About 40 minutes or there abouts, couldn't even get a connectin on my mobile... Adn the closest place where I could have used wifi was using Telstra also... [05:41] jasoncwarner_: I wish we had more info on it [05:42] thumper: I think we were hoping ti was driver related, but clearly not anymore. So probably somewhere in nux/unity/compiz? (manager steps out now ;) ) DBO mentioned something about FBO but I'll let him speak to that. [05:42] jasoncwarner_: is it exactly the same behaviour? [05:42] I'm on intel and not seen any corruption [05:43] * thumper goes to make dinner [05:43] thumper: RAOF says it even has the same black defect in the white bar...so I would say yeah, close enough for government work [05:43] bbl [05:43] :) [05:44] thumper: I've seen it exactly once - yesterday. It went away with a restart. I've not seen it before or since. It does look very much like that effect, though. === tjaalton_ is now known as tjaalton [07:13] good morning [07:13] bonjour didrocks [07:14] good morning pitti, didrocks, jasoncwarner_ [07:14] hey rickspencer3 q [07:14] hey pitti, rickspencer3 [07:15] hey pitti, sure, shoot [07:15] hey rickspencer3 [07:15] good morning jasoncwarner_ [07:15] morning didrocks [07:16] didrocks: hey, you get my emails (don't you love waking up to me in your inbox? ) [07:17] jasoncwarner_: one sec, just connecting and already 3 PM :/ [07:21] jasoncwarner_: so, on bug #926859 [07:21] Launchpad bug 926859 in nux "llvmpipe software rendering needs blacklisting in unity-support-test" [High,Triaged] https://launchpad.net/bugs/926859 [07:21] jasoncwarner_: I can do it [07:23] jasoncwarner_: for bug #936818, I added the tag [07:23] Launchpad bug 936818 in compiz-core "Visual Corruption on Desktop" [High,Fix committed] https://launchpad.net/bugs/936818 [07:23] jasoncwarner_: I can add it to the spreadsheet in a new section for the priority [07:24] thanks, didrocks ! [07:25] yw :) [07:27] didrocks, hey [07:28] didrocks, I was just merging the new ibus support code into unity, and it cant found 'ibus-1.0' [07:29] good morning bschaefer [07:29] didrocks, I thought "libibus-1.0-dev" had been added [07:29] bschaefer: nux or unity? [07:29] they both need it [07:29] for the "it" [07:29] ah [07:29] jay told me only nux will need it [07:29] https://code.launchpad.net/~unity-team/unity/unity.text-entry-im/+merge/94305 [07:29] and that the API isn't leaked [07:29] in unity [07:30] hmm well unity will need it until we redo TextEntry using the pimpl idiom [07:31] bschaefer: it shouldn't work like that then [07:31] bschaefer: nux .pc file should require ibus in that case [07:31] and remove the dep check in unity [07:31] then, with that, I'll make the nux -dev to ibus -dev [07:32] I spent 1h to explain that to your team last week :/ [07:32] didrocks, it didn't seem to get back to me :( [07:33] bschaefer: I'm fixing nux a little [07:33] bschaefer: no worry, as thumper is making is to no leak, you will need to remove the ibus check on unity and be done once nux is merged [07:34] didrocks, right now the TextEntry.h is including the ibus.h which is why the dep check was there for unity [07:34] it* [07:34] didrocks, the nux part just merged a little bit ago [07:35] bschaefer: TextEntry.h is part of nux, isn't it? [07:35] didrocks, yeah [07:35] bschaefer: so yeah, it's not how you do it in that case [07:35] (if thumper wasn't fixing the leak) [07:35] what you do in that case, is: [07:35] your nux.pc file is requiring ibus-1.0 [07:36] yes [07:36] then, seeing that, the nux-dev package will dep on the ibus-dev package [07:36] so, when you include nux from unity [07:36] you don't need to check for ibus [07:36] hmm I thought I had tried that, then it complained about no ibus.h found [07:36] as the nux.pc check will make unity checking for ibus.pc [07:37] bschaefer: it's how it works for all FLOSS project, so you probably did something wrong : [07:37] :) [07:37] didrocks, most likely ;) [07:37] but yeah, the reason here is "there is no magical reason unity dev should read the nux .h files to know that a dep is missing" ;) [07:37] so Tim is fixing the leak, you don't need to do that [07:38] didrocks, it is still good to learn! [07:38] you can push an additional revision that removes the ibus check in unity though [07:38] bschaefer: yeah, it's pretty simple once you know it :) [07:40] didrocks, thanks! [07:40] thumper, thank you too, for being up and working still [08:31] good morning everyone [08:33] chrisccoulson, g'day [08:33] hi bryceh, how are you? [08:33] chrisccoulson, good, you? [08:34] bryceh, yeah, not too bad thanks. i feel like this week has been much more productive than last :) [08:35] good, yeah been crazy amounts of bugs here on the X side, but got through a ton [08:43] pitti - when does the freeze come in to effect? [08:43] chrisccoulson: I think today at 2100 UTC [08:44] the last mad dash :) [08:44] pitti - ah, cool. thanks. i've got new builds of firefox and thunderbird, but i'm trying to hold out until i've got mozilla approval for making the changes for hyphenation [08:44] and i don't want to do 2 uploads :) [08:58] hey [08:59] bonjour seb128 [08:59] hey pitti, wie gehts? [08:59] gut, danke! [09:00] kenvandine, go to bed! [09:01] seb128, soon:) [09:01] it's not a proper hour to upload video lenses :p [09:01] or anything else ;-) [09:01] seb128, damn your quick :) [09:01] kenvandine, tb is efficient [09:01] * kenvandine ignores that [09:01] kenvandine, joke aside I was just opening my mailed and looking at -changes, good timing ;-) [09:01] * kenvandine also really dislikes evolution now too [09:05] wow kenvandine me thinks you should be sleeping [09:05] salut seb128 [09:05] jasoncwarner_, i did tell you i was going to be like an hour ago :) [09:05] lut didrocks, ca va [09:05] hey jasoncwarner_ [09:05] i had two more things to finish... done now though [09:05] * jasoncwarner_ notes how often I see someone saying "good night" and "good morning" [09:06] kenvandine: ah...well, get to sleep ;) [09:06] video lens updated, time to crash :) [09:06] see you guys in a couple hours! [09:06] kenvandine, 'night [09:07] seb128: ça va, le rush dès la première minute, mais ça va :) [09:08] jasoncwarner_, good night. And good morning! [09:08] didrocks, there is a reason I don't start my IRC first thing in the morning ;-) [09:08] bryceh: seriously! you too! [09:08] seb128: yeah, I tried to get that too, but was trapped this morning :) [09:09] didrocks, ;-) [09:09] wow, it's busy in here this morning [09:09] that happens even to the bests! [09:09] chrisccoulson, hey, how are you? [09:10] seb128, yeah, pretty good thanks. and you? [09:10] chrisccoulson, smashed a plug first thing this morning? ;-) [09:10] I'm good thanks [09:10] seb128, oh, not this morning. my foot is still throbbing though [09:10] and i still have a hole in my toe :( [09:10] :-( [09:12] chrisccoulson: the doctor didn't stitch the toe together? [09:13] pitti - oh, i've not been to see a doctor. they wouldn't do that anyway, they'd just send me to an A+E department [09:13] i'm sure it'll heal :) [09:13] uh? [09:14] A+E? [09:14] aren't you worried about infections? [09:14] heh, i hadn't thought of that ;) [09:16] chrisccoulson, what happened? [09:16] bryceh, i stepped on to the pins of an electrical plug on the floor, when i got out of bed a couple of mornings ago [09:16] and one of them penetrated my foot ;) [09:16] but i also broke the plug [09:17] ah, ouch. yeah, tetanus shot time === tkamppeter_ is now known as tkamppeter [09:22] sorry, didn't mean to kill the conversation, so to speak. [09:25] bryceh: I hope he's running head over heels to a doctor! [09:26] indeed! [09:29] lol [09:30] not sure a doctor would do much for a cut [09:31] you can clean that with antiseptics yourself [09:31] well I guess different people have different habits, I would probably not run to a doctor either for that ;-) [09:33] seb128, suppose it matters how deep it is [09:33] I probably would when I coudl see my foot's inside from a larger hole [09:33] and GB power plugs are insanely big [09:33] seb128, still throbbing after 3-4 days might suggest infection [09:34] /join #ubuntu-doctors [09:34] well it matters if they need to close it and clean it in a better way yeah [09:34] pitti, or -> move to actual work :p [09:34] pitti, thanks again for the help on updates btw [09:34] seb128: I am currently uploading 821 packages; how many do you? :-) [09:35] pitti, I'm not going to pick that gauntlet [09:35] ;-) [09:35] * pitti hugs seb128, my pleasure [09:35] * seb128 hugs pitti [09:35] damn [09:35] you are 1 bug ahead again [09:35] hehe [09:35] go, seb128, go! [09:35] ;-) [09:35] I know why seb128 wanted to do the GNOME's update completly himself :) [09:35] my goal was to break the 200 mark this cycle [09:36] that would be a new personal record [09:36] I know, didrocks can only laugh at trivial numbers like this [09:36] * didrocks has an army to work for him :) [09:36] oh, nice, Debian updated libgphoto2 yesterday, I just wanted to do that myself [09:37] didrocks, in fact I think pitti scored more bug closing from that GNOME update round than me :p [09:37] didrocks: and yet the hud keeps popping up when I don't want it :) [09:37] but it's only fair from the stack of updates he did ;-) [09:37] seb128: oh? I think it was about 5 or so [09:37] seb128: damn! :) [09:37] pitti: yeah, I just want to have enough people opening duplicate [09:38] and closing them all, so that I can +100 on the bug number [09:38] pitti, yeah, I think I got between 3 and 5, g-c-c and g-s-d took me a whole afternoon to rebase and clean our patches and closed 1 bug we had [09:38] [09:38] pitti: more seriously, this is a compiz and unity patch, it's #1 on the priority list [09:38] didrocks: yes, I know; I was just kidding you [09:38] https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuMtju1x8UoEdDNCT1U5MlVodjIwNGJPdnU5YVltVmc#gid=1 [09:38] see, it's #1, no kidding :) [09:39] didrocks: I guess the real scope of the bug is larger than just alt+f4 [09:39] pitti, btw the 200 mark is a joke, you should aim for 300 seeing where we stand with stil like 5 weeks of bug fixing [09:39] we can do it! [09:39] pitti: yeah, I just didn't change the bug title [09:39] ;-) [09:39] seb128: well, I never got to 200 before, so this was my goal at the start of the cycle [09:39] pitti: it's basically if you key + something, compiz please please please ignore "key" tap [09:40] seb128: so, I think we don't need the metacity update, there is the gsettings stuff we don't want and the other fixes are not relevant IMHO [09:40] yes, I often get it with switching workspaces or terminal tabs [09:40] didrocks, ok [09:40] pitti: so switching ws on the way to change to Shift + Super + arrows [09:40] didrocks, what about the lim merge request from sam, does that needs to land before lim in compiz? [09:40] seb128: no, both are independant from what I was told [09:40] it will just be deactivated [09:41] didrocks: sorry, shift+super+something will break my hand [09:41] didrocks, well, for feature parity for 2d I guess we will need to land it? [09:41] didrocks: ctrl+alt is very convenient (keys are next to each other) [09:41] pitti: agreed, and moving a window will be Super + alt + arrows [09:41] didrocks, is lim planed to land before beta1 still? [09:41] seb128: no, see the desktop meeting, no release before beta1 :) [09:41] didrocks, heya good morning! [09:41] seb128: yeah, they will land at the same time, hopefully (still need work on the 2d side) [09:42] hey bryceh [09:42] bryceh: good morn… night! :) [09:42] didrocks, are you aware of bugs 933322 / 931967? [09:42] Launchpad bug 933322 in xserver-xorg-video-ati "LightDM graphic corruption with ati and nvidia" [Undecided,Confirmed] https://launchpad.net/bugs/933322 [09:42] lightdm? :) [09:43] I don't really work on it, but looking :) [09:43] didrocks, possibly they're dupes, we're not sure yet. We *think* they're not unity bugs but not 100% certain. Also think they're not X or driver bugs, but not 100% certain. And we're not 100% certain they're lightdm either but that's the best guess so far. [09:43] bryceh, btw, I "like" how you put that wacom g-s-d bug that 1 user with specific hardware ran into on the wiki meeting page and didn't mention any of the xserver bug ten of unity users are running into ;-) [09:44] can't repro on -intel [09:44] in the "Notable bugs this week:" [09:44] bryceh, I've nothing against being finger pointed for stuff we broke but I think that summary is not fair [09:44] seb128, yes but were any of those ten of unity users Pete Graner? ;-) [09:44] heh ;-) [09:45] bryceh: it doesn't seem to be particularly linked to unity as people reports the same in GS, isn't it? [09:45] seb128, anyway, certainly wasn't trying to point fingers, sorry if it came off that way! :-( [09:45] bryceh, well I would rank xorg segfault and closing your session several times a time over "g-s-d doesn't start when a specific wacom device is plugged leading to a weird looking but working desktop" [09:45] several times a "day" [09:46] bryceh, no worry, I just think you overranked that wacom issue to be fair, putting it at the top of the weeky is a bit much, it has bitten 1 user and it doesn't break the session just g-s-c [09:46] g-s-d [09:47] didrocks, right, and I can reproduce the one on -ati logging into gnome classic (no effects) which is why I'm doubting unity. But kinda running out of ideas so am seeing if anyone has more clue than I on it. [09:47] (anyway, moving on) [09:47] seb128, sorry it upset you! [09:48] bryceh: hum, I don't have any ATI around, but gnome classic (no effects) have compisoted enabled, maybe try metacity without any compositing? [09:48] bryceh, oh it doesn't upset me, I just think it has been overanked over other issues, I've a list of bug that collect dups every day though :-( [09:49] bryceh, sorry for complaining, I got back to work (I just noticed that it was on the wiki because didrocks pointed to the page for the "no local menu in beta" info) [09:49] seb128, to be honest at the time I added it, a couple people had asked about it, and at the time it sounded fairly bad. But mainly I was just penciling it in hoping you'd notice and follow up on it. [09:49] bryceh, yeah, fair enough, and thanks for making sure it got raised ;-) [09:49] seb128, also I guess I was thinking maybe the status report would be a good way to track bugs that are known issues but that we're not going to fix ASAP, that non-desktop people might run into [09:50] upstream is looking at it [09:50] but maybe that's not such a great idea, I dunno [09:50] I'm certainly full of many not so great ideas [09:50] bryceh, well, I think it's a good idea, but I would think the synaptic, xorg and mesa issue are fairly common and should be there as well then ;-) [09:50] didrocks, oh I assumed "no effects" implies no compositing? [09:51] seb128, right totally agreed, those are well worth adding [09:51] bryceh: I guess there are some, need to check on gconf, not 100% sure [09:51] actually, wait, I know the synaptic and mesa issues, what's the xorg issue? [09:52] bryceh, the WriteToClient thing [09:53] bryceh, but I didn't follow much, just read the discussion with the dx guys the other day [09:53] ah right, that actually turned out to be nvidia 295.10 specific and is already fixed [09:54] oh, good news ;-) [09:55] bryceh, well anyway sorry if that seemed ranting, I find weird to find 2 GNOME bugs there and nobody's else bugs, it filled like a bit people were finger pointing on others issue but not listing theirs ;-) [09:55] filled->felt [09:56] seb128, really the only reason I listed those two was because they were originally reported against X as X bugs, and they ended up not X bugs but sounded like a lot of people would hit them. I'll continue listing such bugs but will also try to remember to list the currently hitting X-and-really-is-X bugs as well. Guess I overlook those since I'm actively working on them. Would love it if you did similarly on the gnome [09:56] side. [09:56] seb128, also you may have better insight into X bugs that people are hitting a lot, so don't be shy about flagging them if you think they're getting hit a lot. That'll actually help me and chris focus on solving them. [09:57] bryceh, yeah, I like the "list known issue" idea, maybe having a separate section for those would be better though [10:05] good morning people :) [10:05] hey czajkowski, how are you? [10:05] good thanks getting into this workign from home lark [10:05] :) [10:05] you didn't before? [10:05] nope never [10:06] hey czajkowski [10:07] pitti: if you have some minutes, can you please cheat with those build priority: https://launchpad.net/~ubuntu-desktop/+archive/ppa/+packages -> compiz, c-p-m, metacity ? [10:09] didrocks: done [10:09] pitti: thanks a lot, and sorry to bother you :) [10:09] didrocks: no worries [10:13] seb128, alright here you go, my quick brain dump - https://wiki.ubuntu.com/DesktopTeam/Meeting/2012-02-28 [10:14] bryceh, thanks, will try to do something similar to desktop as well [10:14] bryceh, you put it in "agenda" btw, maybe add a "known issues" section? [10:16] seb128, feel free to edit [10:16] right, it's a wiki ! [10:16] ;-) [10:17] RAOF, ^^ if I missed any X bugs worth mentioning, please add === Chipaca` is now known as Chipaca [10:30] hmm, with the most recent update all fonts in my panel (unity-2d) got a colour blur around them .... and my notification bg color seems to be a dark green [10:35] ogra_, I haven't heard of that bug. Might be something unity2d related. Check your /var/log/dpkg.log and downgrade as makes sense until you find the faulty component. [10:36] note that i'm on arm ... and use a tegra2 driver ... i guess i should first disable that bit and see if its the driver [10:36] i would have guessed for a Qt issue, but that wouldnt explain the green notification bubbles (which look really weird btw) [10:37] pitti: yeha! all reportbuilder deps seem to be there now! MIR galore, brace for impact. [10:37] Sweetshark: yes, I poked them last night/this morning [10:37] Sweetshark: note that most of them were in main before and thus don't need a MIR [10:38] Sweetshark: we only need the libexttextcat thingy you already filied [10:38] Sweetshark: is this related in any way to libtextcat (which is already in main)? [10:39] sorry, it's in universe [10:39] but was in main in natty/oneriric [10:41] there are a ot left for MIR [10:41] if we would upload again today (just for MIRs and reportbuilder) would that abort the running arm builds? [10:42] no, builds are never aborted [10:42] but their builds might fail to upload [10:42] due to the obsolete version [10:42] so I'd rather wait until armhf has built [10:43] yes. [10:43] Sweetshark: does https://launchpad.net/ubuntu/+source/libreoffice/1:3.5.0-1ubuntu2/+build/3230659 provide any indication how far it is? [10:44] pitti: its in sd (star draw=impress, thats rather far up the build) [10:45] but sd/sw (writer)/sc (calc) are the major beasts, so they are still to be done. [10:46] sw alone is ~1/12 of compile time ... [10:47] pitti: is there any way to find out how big the buildlog is on the buildd by now? [10:47] not with mere layman powers [10:52] comparing it to the amd64 log and filtering for compiles, it is roughly at 88% (assuming that the ARM make used the same build order, which it does not have to, but likely does) [10:53] OTOH the sw/sd/sc compiles will take longer because they have bazillion of includes. [10:53] the only way to be sure is once it is finished, we have a log and a total time to comare against. [10:54] :/ === soren_ is now known as soren === cking_ is now known as cking [11:39] again, xorg crashing on toomanywrite :/ [11:56] didrocks, ?? [12:06] bryceh: I'm getting the issue since oneiric: when there are too many write on my disk, X crashes [12:17] didrocks, install my https://launchpad.net/~ubuntu-x-swat/+archive/mesa-8.0.1 [12:17] bryceh: mesa? I have a nvidia card [12:17] hrm [12:18] didrocks, 295.20? [12:18] bryceh: yeah, I got it since oneiric [12:18] and I'm on the latest [12:19] odd, dunno. Filed bug#? [12:19] * bryceh EOD + Bed. g'nite. [12:20] bryceh: sleep well! [12:20] I think I filed more than once, but can file another one with latest crash :) [12:28] didrocks, soo ... we need to talk, i got an overview about the gles stuff yesterday .... [12:28] didrocks, seemingly what linaro produced will be an 1.9MB patch file .... plus 4-500k for compiz-plugins-main [12:29] ogra_: ok, does it follow the requirement from the email thread? [12:30] what thread exactly ? (i have like ten open for that topic) [12:30] same here, and I have 2 people pinging me everyday about it :/ [12:30] it's so confusing [12:30] i dont think it ships tests etc [12:30] and I lost so much time on it [12:31] who pinged you ? [12:31] jay, david… [12:31] it should all be run over my table [12:31] hmm [12:31] so, the patch which don't ship tests [12:31] they are in #define armel? [12:31] #ifdef sorry [12:31] anyway, i dont think 1.9M is acceptable, but i also dont want to lose the work that was been done over thelast months [12:32] what's your proposal then? [12:32] no, thats the compiz part, its a patch that should only be applied if DEB_BUILS_HOST is arm [12:32] during package build [12:32] ok, some people come back telling it was finally on #ifdef [12:32] well, seems they *can* clean it up, they just didnt have the time yet [12:32] * didrocks *sigh* [12:33] the end result should be more like 500k or so [12:33] ok, and that's the compiz part only applied on armel build, isn't it? [12:34] the question is, regarding the beta, should we apply it now and wait for getting it updated until release or should we wait for the cleaned up patch and ask for freeze exceptions etc [12:34] right, that was the plan [12:34] but it will make your diff-gz horrid for a while if we apply it now ... [12:34] bryceh: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/939470 when you wake up and it's retraced [12:34] didrocks: Error: bug 939470 not found [12:34] and indeed it would need your agreement (as well as skaet's) [12:35] ogra_: well, anyway, there is a FFe request to do, do you have any ETA for them to make the patch cleaned up? [12:35] they promised me "before release" [12:35] with me pushing for asap indeed [12:35] well, "before release" it really vague [12:35] you can open a FFe [12:36] alf should be able to give a very rough ETA [12:36] and discuss with the release team when it's the last dadte [12:36] date* [12:36] k [12:36] ogra_: also, I want to be clear [12:36] will do (first talking to kate though) [12:36] if compiz is FTBFS on armel, that won't prevent me to pushing a compiz fix [12:36] right [12:36] then, they will have to fix their patch promptly [12:36] if not done and the armel image is broken for few days [12:37] just ignore it and blame me or linaro (cant blame ubuntu-arm anymore, it dissolved) [12:37] I'll revert the patch to make the armel image working [12:37] ogra_: heh, blaming you? with pleasure :) [12:37] * didrocks hugs ogra_ [12:37] * ogra_ hugs didrocks [12:37] ok, seems we are in agreement then :) [12:37] hope that will lift the confusion on all those threads! [12:37] right, let me try to catch kate first though [12:37] yeah, keep me posted [12:37] yeah, i dislike doing it by mail at all [12:38] +1 [12:38] we should just have quick ad-hoc IRC meetings so everyone is in the loop and can react immediately [12:38] agreed, once you discussed it with kate, maybe you can arrange that? [12:38] but seems thats not how linaro works :) [12:38] i will try [12:39] sweet :) [12:41] ogra_: didrocks: Keep in mind that, as I mentioned yesterday, even the cleaned up patch is estimated around 400KB for compiz-core and around 300K for compiz-plugins-main [12:41] yes, buts thats a lot smalled than x.xMB [12:41] :) [12:41] yeah :) === MacSlow is now known as MacSlow|lunch [13:00] I'm the beta tech release manager [13:00] Sweetshark: libreoffice here needs looked into toot sweet [13:01] hmm, no robert, if anyone sees him tell him the lighdm needs cleaned up there [13:03] Riddell, what is the issue with lightdm? [13:04] oh sorry, forgot link [13:04] http://people.canonical.com/~ubuntu-archive/nbs.html [13:04] NBS is all [13:04] Riddell, no lightdm there [13:04] seb128: "lightdm-gtk-greeter" [13:04] Riddell, lightdm-gtk-greeter is a standalone source now that needs to be taken care of by the derivatives that need it [13:05] robert_ancell said several time he wrote it as a demo greeter and has no intention to spend efforts on it [13:05] that's why he made a different project,source for it this cycle [13:05] seb128: that's fine. I'll just delete it then [13:05]