=== bjf is now known as bjf[afk] === fta_ is now known as fta [07:03] Good morning [07:10] good morning [07:10] Morning didrocks, pitti. [07:11] hey TheMuso [07:11] bonjour didrocks [07:11] hey TheMuso, how are you? [07:11] didrocks: Well thanks, yourself? [07:11] guten morgen pitti [07:11] TheMuso: I'm fine, thanks :-) [07:37] pitti: the separate "SRU bug" for empathy was because for the first, we didn't intend to include the patch debian/patches/91_git_fix_small_font.patch fixing the other bug (remember, I asked you to reject it) [07:41] didrocks: right, that's fine [08:09] morning [08:09] bonjour huats [08:09] comment vas-tu? [08:10] hello pitti [08:10] I am fine thanks ! way too busy with my company + baby [08:10] but fine :) [08:10] what about you pitti ? [08:11] I'm great, thanks; looking forward to the weekend, we'll go tenting [08:11] it'll get ~ 32 degrees, what better to do than swimming and idling on the beach :) [08:12] pitti, sounfs terrific indeed ! [08:14] salut huats [08:14] hello didrocks [08:28] seb128, nope, never heard of it [08:29] hey cassidy [08:29] ok [08:29] it's reproductible ? [08:31] I've not tried yet, will do that now [08:31] seb128: thanks for the evo fix btw [08:32] didrocks, np [08:32] cassidy: seb128: I tried on 2.30.1.1 and gtalk on a fresh box, can't reproduce [08:32] didrocks, ok, thanks [08:33] yw [08:33] IIRC I didn't touch this wizard in the last stable release so I'd be surprised that's a regression [08:33] but we never know [08:34] (also I clearly remember to have setup a new account for 2.30.2, so not reproduceable in the new -proposed version) [08:35] "- note that even if I get the "Please enter personal details" page, no matter if I selected the "I don't want to enable this feature for now", the apply button is grayed when I enter nothing and empathy, in the meawhile is connecting the account. Consequently, I can just hit "cancel"" [08:35] didrocks, that's buggy [08:35] cassidy, ^ [08:36] yeah, that's buggy, but the account is added, it's not totally broken as the bug report is telling [08:36] didrocks, that might be the issue the user is having [08:36] well it's not obvious for the user the account is added still [08:36] that's still weird, it used to work fine [08:36] hum, I didn't understand that. I was thinking he told "I can't add my acount" [08:36] didrocks, did you observe that as well ? [08:36] account* [08:36] cassidy: yeah, this quote is mine :-) [08:36] ah ok :) [08:36] didrocks, well "I can't finish the wizard" is easy to map to "I can't add my account" [08:37] didrocks, can you fw this issue upstream please? [08:37] cassidy: sure [08:37] should check in .2, I don't remember if I had that [08:38] seb128: you still see that the account is connected before hiting "cancel", so I think the user would have noticed [08:38] didrocks, I think you give lot of credits to users ;-) [08:39] seb128: maybe, I'm too optimistic, indeed ^^ [08:39] quite some users are really focussed on the dialog they interact with and will not notice other changes on screen [08:39] let me confirm with .2 [08:39] so if they fail to complete the wizard they will perceive the configuration to have failed [08:39] right, that makes sense [08:42] didrocks, it's working for me in .2 [08:42] let me try .1.1 [08:43] seb128: in .2, I don't have the proposal of "not adding more detail info" [08:44] the page to add infos on local accounts has a checkbox "don't use that" [08:44] yeah, and then on next screen, I can check "I don't want to enable this feature for now" and hit apply [08:44] so it's fixed [08:44] yeah, the UI is different [08:44] cassidy, ^ seems to be alright in .2 [08:44] I'm trying 1.1 just to check the difference [08:45] I'd be surprised that matters [08:45] seb128: you should see 3 options on the account creation screen, one being basically being "skip enter personal detail screen" [08:49] didrocks, works the same way in 1.1 [08:49] the dialog has "do you want to configure another account" [08:49] seb128: yeah, but in previous dialog you had another option [08:49] if you let it on no you get the local dialog info screen where you can check the "don't enter infos" === zyga is now known as zyga_away [08:50] let me check again, I was maybe not awake :-) [08:50] I'm pretty sure to have exactly what was writtent on the bug report [08:56] seb128: I don't understand, I don't get the same thing here. But contrary to have a new box, I removed previous account. I wonder if that can have an influence [08:58] it might [08:59] I did try by removing .mission-control and stopping mission-control-5 then restarting empathy [09:11] mvo, do you have any idea when this stuff will start being worked on (or has it already started?) https://wiki.ubuntu.com/SoftwareUpdateHandling [09:13] dear aptd please stop crashing [09:13] seb128: do you have a backtrace? [09:14] and471: work on the glade stuff in the update-settings is started, but it needs some love to software-properties [09:14] mvo, will get you one, apport keeps triggering every time I use update-manager in maverick since I reenabled apport there [09:14] and471: so that s-p gets a dbus backend and can run as the user [09:14] and471: most(?) of this should be possible today with aptdaemon [09:14] mvo, what language will both be in? [09:15] and471: python [09:15] mvo, :) [09:15] mvo, where can I start? [09:15] and471: the right question ;) porting software-properties is certainly a good start [09:16] mvo, I am not experienced in the backend apt stuff [09:16] mvo, but could I start ont he frontend [09:16] and471: fagan was doing some work on the glade side, best to coordinate with him [09:17] mvo, using the gtkbuilder framework for software-center? [09:17] mvo, simplebuilderapp [09:17] mvo, or whatever it was called [09:17] mvo, cool [09:17] and471: yeah [09:17] mvo, well I shall have a look :) [09:17] mvo, goota go now, giving all my books back after exams :D [09:17] *gotta [09:17] mvo, see ya [09:17] see you [09:22] self._emit_acquire_item(item) [09:22] File "/usr/lib/python2.6/dist-packages/aptdaemon/progress.py", line 119, in _emit_acquire_item [09:22] elif item.owner.status == apt_pkg.AcquireItem.STAT_FAILED: [09:22] AttributeError: type object 'apt_pkg.AcquireItem' has no attribute 'STAT_FAILED' [09:22] Traceback (most recent call last): [09:22] mvo, ^ [09:22] seb128: thanks, that looks like a bug in python-apt, I work on it [09:22] mvo, thanks, want it in launchpad? [09:25] seb128: no thanks, I fix it right here [09:26] mvo, you rock, thanks [09:30] seb128: fix uploaded, let me know [09:30] mvo, ;-) [09:30] I will [09:31] pitti, \o/ no directfb ;-) [09:31] seb128: muhaha! [09:32] seb128: btw, did you see that mail about "live cd optimization" from the other day on -devel (or -discuss)? [09:32] could be interesting to hook optipng and the svg optimization stuff into our build scripts [09:32] that was some weeks ago? [09:32] yes [09:32] the one which suggested changing images quality and sort of things? [09:32] 21.05.10 02:35 Louis Simard LiveCD optimisations [09:32] no, not quality [09:32] right [09:34] pitti, sorry I though that things like optipng were changing the image [09:35] but right some of the ideas might be worth investigating [09:35] well, they do, but only the encoding, not the quality; png is lossless [09:35] he claims an 11 MB size reduction, which is quite amazing === victorp_isaway is now known as victorp === lifeless_ is now known as lifeless [09:52] mvo, if fagan comes on IRC, can you tell him I want to speak to him === almaisan-away is now known as al-maisan === victorp is now known as victorp_isaway === lifeless_ is now known as lifeless [10:27] didrocks, cassidy: comments on bug #597556 seems to confirm what didrocks suggested [10:27] Launchpad bug 597556 in empathy (Ubuntu) "Cannot complete Empathy add account wizard (affects: 2) (heat: 12)" [Low,New] https://launchpad.net/bugs/597556 [10:28] it doesn't happen with clean profiles but with ones where accounts have been tweaked [10:28] so seems some user configurations could be causing the issue [10:37] ouch, sun-java6 is a 160MB tarball :( === victorp_isaway is now known as victorp === zyga_away is now known as zyga === lifeless_ is now known as lifeless === lifeless_ is now known as lifeless === lifeless_ is now known as lifeless === MacSlow is now known as MacSlow|lunch === ara_ is now known as ara === lifeless_ is now known as lifeless === MacSlow|lunch is now known as MacSlow [14:15] seb128: re: the clean up translations break , that simple bug had stalled since no one pinged the docs team , and now we are worried about translations after i pinged them :( [14:15] break translations in the sense , that the translations might not benefit from the change? [14:17] vish, right, since we will not pull the new upstream versions we will not get the translations from GNOME so it will need to be translated in rosetta or other locales will see an english string [14:17] vish, you can guess than with enough warning 75% of translations team will get it done [14:18] vish, so basically you drop translations in some languages which don't have active ubuntu translators and create work for other teams [14:18] seb128: lets hope and get that in quicker , that they catch it and gets translated :) [14:18] vish, so you ask yourself if that's really worth the effort and breaking the strings in some translations [14:19] :s [14:19] I tend to think that wording changes are not worth having the string useless in some locales because they will get the english versions and they don't read english [14:21] seb128: silly Q: cant we pull the translations from upstream for those strings? [14:21] we can [14:22] it just requires patching files by hand [14:23] vish, being one hundred or so [14:23] vish, then tracking every upstream change to those [14:23] hm.. [14:23] vish, so we can but it has real cost [14:23] I'm really wondering if changing a word is really worth the efforts [14:24] seb128: oh well , your call . I'd hoped it can make it. [14:24] it can [14:24] it's just costy [14:25] we could fix some code bugs during the same time [14:25] yeah :( [14:25] so it's a tradeoff on what we want to get in [14:25] ie I could backport some of the location bar fixes rather than the string change for the same effort [14:25] hehe :) [14:28] * vish tries to find mdc to get some location bar fixes ;) [14:35] seb128: so , https://bugs.launchpad.net/hundredpapercuts/+bug/503330 , would be tough to get in M too? [14:35] Launchpad bug 503330 in nautilus (Ubuntu) (and 2 other projects) "In the file operation dialog, the file count and the size count change in opposite direction. (affects: 1) (heat: 21)" [Low,Triaged] [14:36] the sentence needs changing there [14:37] because upstream is considering an easy fix for the time being , for us , if its not going to make it , we can fix it properly [14:38] vish, right [14:39] vish, I'm still pondering trying to get the new nautilus in maverick there is lot of nice things there [14:39] cool , so we can fix it properly itself [14:39] yeah :D === asac_ is now known as asac [15:17] lamalex: hi , any progress on https://bugzilla.gnome.org/show_bug.cgi?id=585914 ? or is it only banshee these days ;p [15:17] Gnome bug 585914 in Notifications "Notification icon must be clicked before user can see new messages" [Normal,New] [15:18] bye everyone, have a nice weekend! [15:18] vish: the empathy guys finished the job. I had planned on testing but it requires a much newer glib and I don't feel like completely destabilizing my system [15:18] lamalex: i thought so too , but why isnt the bug closed? looks like the depends was closed [15:18] or rather they did the back work of making the status icon a proper approver [15:19] ah right [15:19] i dont know if they fixed their behavior or not [15:19] like I said, I wanted to test [15:19] cool.. [15:19] but they use gsettings and all of the fancy new glib features [15:21] does maverick have glib 2.25? [15:22] packages.ubuntu.com is being weird or else I'd check myself [15:23] not sure , i'm still on lucid too [15:25] vish: I'm asking in #empathy :P they'll know [15:25] heh [15:26] lamalex: if you keep saying empathy a fews times here too , some of those folks might answer ;) [empathy highlights fwiw ;p] [15:26] haha [15:27] 10:26 it's not yet fixed but I'll probably fix it soon as we all have the pieces in place now [15:28] you could have ask me directly :p [15:31] I didn't realize you were in here [15:31] lamalex: told ya some of them hide here ;) === bjf[afk] is now known as bjf === fta_ is now known as fta [16:18] didrocks: is the newest unity supposed to decrease mutter's CPU usage at all? [16:18] LaserJock: not what I know of, just some optimization on places, why? [16:33] uuid.getnode() doesn't play nicely at all with threading [16:38] didrocks: I get a fairly higher load average in Unity than the old UNE [16:38] didrocks: and it looks to be mostly in mutter (i.e. mutter is the #1 process in CPU usage for the most part) [16:38] LaserJock: so, it's not supposed to decrease, but rather increasing :) [16:39] LaserJock: yeah, mutter can be guilty I guess [16:39] LaserJock: you can try running mutter without unity too [16:39] like in the GNOME session: mutter --replace [16:41] didrocks: also mutter is taking a whole lot of RAM [16:41] LaserJock: mutter is quite young too. I think it'll be better with time as it was for compiz [16:41] 135MB RES, which is the highest consuming process [16:42] sure sure, but this targeted for netbook right? ;-) [16:43] LaserJock: right, but my evolution which is also on my netbook takes more :-) [16:44] it think those bugs will be fixed in near futur, now it's more feature development than bug/ressources fixing [16:44] in any case, you should have a look at mutter --replace in GNOME session [16:44] and see how much RAM it's taking [16:44] if there is a huge difference, unity can be guilty [16:44] k [16:45] well, I can't imagine using evo on a netbook so maybe my standards a too high :-) [16:46] does evo express use less ram than regular evo? [16:47] lamalex: didn't benchmarked that, there is less elements drawned, so maybe [16:47] seems like une should ship evo express, since it's you know - for netbooks [16:49] LaserJock, thats why we use webmail in the low spec netbook images (i.e. arm) [16:49] as well as weboffice [16:49] yeah [16:49] lamalex: it's already the plan, discussed at UDS and tracker as A3 item [16:49] I can't imagine actually using a desktop client for email anymore [16:50] dropping evo gave us 60MB free space on the image :) [16:50] dropping OO.o another 150 :) [16:51] sweet [16:52] my problem now is bad network connections [16:52] everything is online so with spotty internet, things can be frustrating :-) [16:53] not the case when I triage my email on plane for instance :-) [16:53] well [16:53] assuming you can actually get your email client up and see anything [16:53] which is working well for me [16:53] TBird and Evo have always had such horrible UI for me on the netbook [16:54] hopefully with this new Evo Express it'll be worth a shot maybe === MacSlow is now known as MacSlow|break [16:58] LaserJock: you should try it, it's good [16:58] LaserJock: add --express on maverick [16:58] and -c [16:59] lamalex: did you got some time to have a shot on the notification vs empty list thing for banshee? [16:59] didrocks: not yet, I've been focusing on udev [16:59] we're REALLY close to finishing [17:00] lamalex: sure :-) that's way more important [17:00] lamalex: awesome :) [17:00] lamalex: are there still some remaining tricks? [17:00] yeah, just trying to track down audiocd support [17:00] once that is up (and it's pretty close I think) we'll have a fully working hal-less banshee [17:01] yeah, I saw about android detection too, congrats :) [17:01] didrocks: I'm not sure I'm up for maverick yet. I only have one computer (my netbook) and it's also my work computer [17:02] LaserJock: you can just give it a shot in testdrive or in a live :-) [17:03] didrocks: lol, testdrive? I can't imagine that working well on my Atom N270 [17:04] but yeah, maybe I'll grab an image and try it off a USB stick [17:04] LaserJock: on atom, yeah, not the best platform for virtualization :) [17:05] I really need to find a machine to run KVM, just so I can say I've tried it [17:06] heh [17:11] didrocks: oh, did the unity bzr branches move somewhere? I'm using ~canonical-dx-team/unity/trunk/ but I haven't seen any updates [17:12] LaserJock: it's ~unity-team/unity/trunk now [17:12] I told you we will fix it :-) [17:13] ah, great, but the PPA is still at ~canonical-dx-team? [17:14] yeah, it's just a ppa for people waiting to test, not a big deal (and moving the ppa after the advertisement we made is not a good choice) [17:14] sure, just checking [17:14] some of the newer atoms have v [17:14] vt === cking is now known as cking-afk [17:41] pedro_, great work on the gstreamer bugs ;-) [17:41] seb128, thanks!. they way too many old ones there, time to do some clean up ;-) [17:41] indeed [17:42] I guess that's true on other components as well ;-) [17:42] do you have scripts to do that? or just stock replies and browsing bug lists? [17:43] i went trough the bug lists to review the bugs then i pass the number to an script for adding the response/status [17:43] ok [17:43] i don't trust the scripts for doing all automatically, one could miss some important info [17:44] yeah, same here [17:44] like 'the bug is no longer an issue' or things like that [17:44] I tend to use stock replies rather than a script though [17:44] but you get to wait on launchpad to commit the change [17:45] well if you have tabs and go the next one that's usually ok ;-) [17:47] yeah, for normal triage that's ok i think, but for a few bugs i prefer to add it with an script, that way i don't get piss when getting the launchpad oops or timeouts :-P === fta__ is now known as fta === al-maisan is now known as almaisan-away