[00:09] <Laney> pitti: regarding lpi, it would be better to drop the BDs on libmono-2.0-dev and mono-gmcs entirely
[02:13] <TheMuso> RAOF: Just reading the merge changelog entry for mesa confirms that specialists need to be handling that part of our system. :p I am sure others think that about audio etc.
[02:13] <TheMuso> Thats one big lot of changes we carry.
[02:15] <RAOF> TheMuso: There are fewer changes conceptually than appear there.  But yeah, we've got quite a lot of changes!
[05:31] <GunnarHj> robert_ancell: Hi Robert, Have you had a chance to look at the suggestions at https://launchpad.net/bugs/793366 ?
[05:31] <ubot2> Ubuntu bug 793366 in lightdm "Sets $LANG to invalid value "de"" [Undecided,In progress]
[05:32] <robert_ancell> GunnarHj, Hi thanks for that.  I've had a quick look.  I'm just trying to get 0.4.0 out the door, and then it's my top priority for 0.4.1
[05:34] <GunnarHj> robert_ancell: Ok, then I know. Let me know when you are ready to talk about it. Thanks!
[05:37] <robert_ancell> GunnarHj, will do
[05:38] <pitti_> Good morning
[05:40] <TheMuso> Morning pitti.
[05:53] <lifeless> bryce: http://launchpad.net/ubuntu/oneiric - see the diffs section
[05:53] <lifeless> https://launchpad.net/ubuntu/oneiric/+localpackagediffs
[06:10] <bryce> lifeless, sweet
[06:11] <bryce> lifeless, 'Add comment'... interesting
[06:33] <robert_ancell> RAOF, aha, I think I worked out why my unit tests don't work in a pbuilder...  xcb/xlib tries to connect over TCP/IP first right?  Any ideas how to make something running in a pbuilder definitely run my local X server and not connect outside of the pbuilder?
[06:35] <RAOF> robert_ancell: I think that if you've got DISPLAY set appropriately (ie: to “:0”) xlib should be connecting locally before trying TCP/IP?
[06:35]  * RAOF goes code diving.
[06:36] <robert_ancell> it looks like it's using the xauth and connecting to my main xserver
[06:40] <RAOF> Hm.  You could also try DISPLAY set to “unix:0”.
[06:44] <robert_ancell> RAOF, I think the problem is while pbuilder uses a chroot, the chroot is not used for unix sockets.  So it always connects to the host socket
[06:45] <RAOF> Well, another option would be to start xvfb on :99 or somesuch?
[06:45] <robert_ancell> yes, that works.  So it prefers the host sockets, and falls back to local ones?  It's very weird
[06:47] <robert_ancell> oh, no there will be a table in the kernel where the names of each socket are, and that name will be taken by the host first
[06:54] <RAOF> I think the latter is correct, yes.
[08:24] <seb128> hey
[08:28] <pitti> bonjour Monsieur Bacher
[08:31] <pitti> hm, is there any CLI way to determine the default value of a gsettings key?
[08:32] <seb128> hey pitti, how are you?
[08:32] <pitti> I'm great, thanks!
[08:32] <pitti> had a challenging training last night, was a bit harder than usual to get out of bed :)
[08:32] <seb128> not sure about the default value
[08:32] <seb128> you can ask on #gnome-hackers
[08:32] <seb128> desrt should know ;-)
[08:33] <pitti> ok, thanks
[08:33]  * pitti checks the GLib API -- using GI would be fine
[08:34] <pitti> hm, seems not
[08:34] <pitti> ok, plan B then
[08:37] <seb128> pitti, get out of bed at 5am is difficult, training or not ;-)
[08:37] <pitti> hey, it's 6 am!
[08:37] <seb128> lol
[08:37] <seb128> same difference :p
[08:37] <pitti> yeah..
[08:39] <seb128> I'm on the late evening side nowadays but 6am would still be at least one hour too early for me ;-)
[08:39] <seb128> robert_ancell, hey
[08:39] <robert_ancell> seb128, hello
[08:40] <seb128> robert_ancell, how is that new lightdm version coming? do you need testing on the current vcs code?
[08:40] <robert_ancell> seb128, I'm fighting pbuilder to run the unit tests
[08:40] <seb128> robert_ancell, btw I read your meeting logs and set up oneiric retracers yesterday
[08:40] <robert_ancell> seb128, that will be a huge help
[08:40] <seb128> usually they are not that useful for GNOME that early in the cycle because we are too busy packaging to look at those bugs
[08:41] <seb128> but it's true that for new product or things we are actively hacking on they are useful
[08:41] <seb128> robert_ancell, sorry that it took a while
[08:41] <robert_ancell> np
[08:43] <seb128> pitti, btw do you want bugs about things that take apport down in the bug description formatting?
[08:43] <pitti> seb128: yes, at least as a place to discuss them
[08:44] <pitti> I wonder what's better, silently ignoring them or stopping on them to fix the bugs
[08:44] <seb128> pitti, like
[08:44] <seb128> "/usr/lib/python2.7/dist-packages/apport/crashdb_impl/launchpad.py", line
[08:44] <seb128>  751, in _subscribe_triaging_team
[08:44] <pitti> best might be to send email about the bugs and go on, I guess
[08:44] <pitti> oh, please bug me for those, yes
[08:44] <seb128> it was doing that yesterday one a bug where the \n got eaten after the previous line
[08:44] <seb128> so the Distro..what next to another field rather to be on its line
[08:45] <seb128> what->was
[08:45] <seb128> pitti, ok, thanks
[08:47] <rodrigo_> morning
[08:48] <seb128> hey rodrigo_, how are you?
[08:48] <seb128> hum
[08:48] <seb128> how do I set a package on hold? echo "binary hold" | dpkg --set-selection?
[08:48] <seb128> selections
[08:48] <seb128> or is there a better way?
[08:50] <seb128> that seems to do it, let's keep that
[08:55] <pitti> oh, I didn't know about that
[08:55] <pitti> seb128: I usually use apt pinning
[08:55] <pitti> seb128: for the retracer chroots?
[08:55] <rodrigo_> hi seb128, pitti
[08:56] <pitti> hey rodrigo_
[08:56] <seb128> pitti, yes, to pin down python-httplib2 to a working version
[08:56] <seb128> pitti, well, that's easier to do a one line command that to remember the pinning syntax and values to use :p
[08:56] <pitti> right, I just didn't know about it
[08:58] <seb128> learning every day ;-)
[08:58] <seb128> I used before but I had to google to find it back :p
[09:02] <seb128> robert_ancell, don't forget to make lightdm read .profile before rolling a new tarball :p
[09:03] <robert_ancell> seb128, yeah yeah.  Actually thats in the ubuntu package
[09:03] <seb128> robert_ancell, btw is there any process that is likely to have private infos in its gdb dumps?
[09:03] <seb128> robert_ancell, just to know if I need to be careful about making lightdm bugs public
[09:04] <robert_ancell> seb128, yes, they may contain passwords so don't make public until backtraced (and then should still check if is in trace)
[09:04] <seb128> robert_ancell, ok, I don't make bugs public before retracing in any case
[09:05] <seb128> robert_ancell, bug #795686 just got a duplicate
[09:05] <ubot2> Launchpad bug 795686 in lightdm "lightdm crashed with SIGSEGV in g_closure_invoke()" [Medium,New] https://launchpad.net/bugs/795686
[09:05] <seb128>  xserver_get_server_type (server=0x0) at xserver.c:100
[09:05] <seb128> that's all from recent retracing
[09:06] <robert_ancell> seb128, I think it's fixed in 0.4.0
[09:06] <seb128> ok
[09:12] <seb128> chrisccoulson, hey
[09:12] <seb128> chrisccoulson, rodrigo_: could one of you have a look to bug #797947
[09:12] <ubot2> Launchpad bug 797947 in gnome-settings-daemon "gnome-settings-daemon crashes frequently with X protocol error" [Undecided,New] https://launchpad.net/bugs/797947
[09:12] <rodrigo_> seb128, looking
[09:12] <seb128> slangasek got a stacktrace but I've the feeling it's useless because the libxklavier handler traps the real error or something
[09:13] <seb128> chrisccoulson knows better about the libxklavier issue than me I forgot the details
[09:13] <chrisccoulson> hi seb128, how are you?
[09:13] <seb128> but I think those usually are not libxklavier bug, it's just trapping the error
[09:13] <seb128> chrisccoulson, I'm fine thanks, what about you?
[09:13] <seb128> can we turn that libxklavier handler off or something?
[09:14] <LLStarks> ricotz, gnome-shell is making my laptop cry. how do i force notifications for critically low battery situations?
[09:14] <bryce> seb128, sounds like we should
[09:14] <chrisccoulson> unfortunately, the stack isn't much use there - the actual error code would be interesting (that's usually printed in the error message when it quits, and it should be on the stack as well)
[09:16] <seb128> chrisccoulson, can you remind me why the stack is hijacked by libxklavier? was there anything we could patch to avoid that and get the actual errors?
[09:16] <RAOF> LLStarks: I think you'd need to get gnome-power-manager to actually work.
[09:17] <chrisccoulson> seb128, it sets it's own error handler, but it needs to do that so it can catch errors that it legitimately creates
[09:17] <seb128> chrisccoulson, so we could have a version without that in a ppa that users could install to get the real stacktrace of their non libxklavier issues?
[09:17] <seb128> chrisccoulson, rodrigo_: the actual error he gets is
[09:17] <seb128> "The error was 'BadMatch (invalid parameter attributes)'.
[09:17] <seb128>   (Details: serial 102079 error_code 8 request_code 2 minor_code 0)"
[09:18] <seb128> he said he usually gets it once a day on workspace switching
[09:18] <rodrigo_> ugh, those are usually on the X stack, right?
[09:19] <chrisccoulson> request code 2 is ChangeWindowAttributes, which doesn't match what is in the stack. so the actual error occurred earlier on :)
[09:19] <chrisccoulson> i think it would be useful to see the stack with --sync
[09:19] <seb128> chrisccoulson, I hate those
[09:19] <chrisccoulson> heh :)
[09:19] <rodrigo_> yeah
[09:20] <seb128> rodrigo_, no, usually they turn to be issues on the client side
[09:20] <seb128> chrisccoulson tracked a few of those back then when he still had time for desktop work ;-)
[09:21] <seb128> chrisccoulson, can you comment on the bug asking what you need?
[09:21] <seb128> chrisccoulson, would rebuilding libxklavier without the signal handler help?
[09:22] <seb128> it seems that handler gets in the way most of the time, it turns out that those issues are often not libxklavier ones :p
[09:27] <LLStarks> raof: as if the low-capacity warnings weren't depressing enough. thanks though.
[09:38]  * pitti -> dentist, bbl
[09:51] <seb128> oh
[09:52] <seb128> I just discovered evolution-settings
[09:54] <seb128> it's quite nice, you just enter your email and password, it figures all the account settings for you
[09:54] <seb128> servers, etc
[09:55] <rodrigo_> seb128, but the UI is horrible, or it was, haven't run the 3.0 version
[09:55]  * rodrigo_ runs it
[09:55] <rodrigo_> yes, as horrible as it was :)
[09:56] <seb128> right, but the "new" dialog is just nice
[09:59] <seb128> i.e just having to enter your email and having all the server details figured for you
[10:03] <seb128> rodrigo_, ok, mcrha fixed the "wrong time is displayed in the meeting reminder dialogs" ;-)
[10:03] <seb128> it was a typo in a gconf key name
[10:03] <rodrigo_> seb128, yes, that's very nice, what I don't like is the main UI, the list of accounts
[10:03] <seb128> it was not seeing that the system tz is used and reading the gconf value
[10:04] <seb128> rodrigo_, right, I was not suggesting the dialog is nice, just the "add an account" part
[10:04] <seb128> it should be the first run dialog imho :p
[10:04] <seb128> just enter your email and password and we done
[10:04] <seb128> we->be
[10:08] <rodrigo_> seb128, yes
[10:21] <rodrigo_> need to run some errands, bbiab
[10:30] <jasoncwarner> morning EU folks.
[10:32] <seb128> jasoncwarner, evening .au ;-)
[10:33] <jasoncwarner> hey seb128
[10:33] <seb128> jasoncwarner, how are you?
[10:33] <jasoncwarner> so, uh, I think I, like, screwed up my machine?
[10:33] <seb128> again?
[10:33] <jasoncwarner> ;)
[10:33] <seb128> what did you do this time? ;-)
[10:34] <jasoncwarner> I just updated and when I rebooted it put me into Unity-2d with no option to go back to Unity
[10:34] <jasoncwarner> I'm thinking my machine now thinks I don't have the necassary hardware to run it? I'm nvidia on that test machine
[10:34] <jasoncwarner> (this is oneiric, fyi)
[10:35] <seb128> jasoncwarner, right, didrocks mentioned that linux 3 screwed nvidia yesterday or the day before
[10:35] <jasoncwarner> gah!
[10:35] <jasoncwarner> ok... so I'm just in a waiting period now until that gets sorted? or is there something I need to do to get it fixed?
[10:35] <seb128> jasoncwarner, check with tseliot he made nvidia updates yesterday
[10:35] <seb128> jasoncwarner, otherwise didrock's workaround was to boot the previous kernel
[10:36] <jasoncwarner> seb128: but...but...but...3 is newer than "previous" kernel...it has to be better?
[10:36] <tseliot> jasoncwarner: can you boot in recovery mode?
[10:37] <bryce> jasoncwarner, not really a matter of better... if the kernel ABI changes, nvidia has to be rebuilt else it won't interface with the kernel properly
[10:37] <jasoncwarner> tseliot: I can boot, and I boot into unity-2d...I'll check recovery mode when I go back upstairs (test machine is not right next to me right nwo...non-ideal physical layout :( )
[10:37] <seb128> jasoncwarner, it's clearly better, it's getting ride of that boring 3d, soon you will be back in real command line ;-)
[10:38] <tseliot> jasoncwarner: you could control you machine with ssh ;)
[10:38] <seb128> jasoncwarner, having to take stairs to switch between computers seems good physical exercise at least :p
[10:38] <tseliot> hehe
[10:39] <jasoncwarner> seb128: tis true, though, if you've seen me lately, how could one think I need _more_ excercise?! (as a gentle reminder to seb128, 2012 objectives are being written this week...respond with care :) )
[10:40] <jasoncwarner> tseliot, seb128 mentioned that you rebuilt nvidia drivers yesterday or so? can I pull those down somewhere?
[10:41] <seb128> jasoncwarner, DOH ;-) (indeed!=
[10:41] <tseliot> jasoncwarner: just make sure that you have nvidia-current 275.09.07 and the linux-headers for your kernel
[10:41] <tseliot> jasoncwarner: that would be a first step. Then I'd like to see the X log, dmesg and the output of dkms status
[10:42] <jasoncwarner> ok...let me go upstairs..be back in a bit..thanks
[10:50] <jibel> jasoncwarner, there is bug 798007 today with mesa and nvidia, even with the latest nvidia you'll fallback to 2d.
[10:50] <ubot2> Launchpad bug 798007 in mesa "[Oneiric] Latest mesa (7.10.3) breaks 3D with nvidia-current" [High,Incomplete] https://launchpad.net/bugs/798007
[10:52] <seb128> oh, so it's RAOF breaking things!
[10:55] <alex3f> hello, any vala god here?
[10:56] <seb128> try #vala on irc.gnome.org
[10:56] <seb128> chrisccoulson, nice, your accountsservice patch has already been uploaded to debian
[10:56] <seb128> ups
[10:56] <seb128> rodrigo_, ^
[10:57] <alex3f> thanks seb128
[10:58] <seb128> alex3f, yw
[10:59] <mvo> alex3f: hey! what are you up to with vala? just curious?
[11:00] <seb128> oh, a mvo, hey mvo ;-)
[11:00] <mvo> hey seb128
[11:00] <alex3f> hi mvo :) I'm still stuck at PackageKit + gi + GPtrArray + pygobject :(
[11:01] <alex3f> and I wanted to write the same code I'm running in python, but in vala
[11:01] <pitti> hey jasoncwarner
[11:01] <alex3f> to see if the problem isn't inside PackageKit instead of gobject-introspection
[11:01] <mvo> alex3f: aha, ok. good luck, your branch is *still* on my high importance todolist, but today I will finally review/merge, I'm sure
[11:01] <mvo> alex3f: *nod*
[11:02] <alex3f> np, after the merge, I'll bring the other two left things
[11:02] <mvo> \o/
[11:02] <alex3f> haven't got the time either *nod*
[11:03] <seb128> pitti, wb
[11:05] <tseliot> jasoncwarner: what jibel said is correct. So, as a quick fix, I guess you can downgrade mesa
[11:16] <seb128> pitti, do you know what happened to the daily iso yesterday?
[11:16] <seb128> where is the extra space use coming from?
[11:17] <seb128> there daily-live doesn't have isos from < 15 to diff the manifest lists
[11:17] <rodrigo_> seb128, my or chrisccoulson's patch?
[11:17] <seb128> rodrigo_, yours
[11:17] <soren> seb128: https://lists.ubuntu.com/archives/ubuntu-devel/2011-June/033495.html perhaps?
[11:17] <rodrigo_> ah ok
[11:17] <rodrigo_> seb128, can you sync it then?
[11:17] <LLStarks> seb128, hybrid iso prep work?
[11:17] <seb128> rodrigo_, yes
[11:17] <seb128> LLStarks, soren: that email said it would take an extra meg
[11:18] <seb128> or did I misread it?
[11:18] <soren> seb128: No, you're right.
[11:18] <LLStarks> 1MB. still contributing though.
[11:19] <seb128> right, though we go from 710 to 720mb there
[11:19] <soren> seb128: Ah, and that would only be starting today.
[11:19] <soren> seb128: And from yesterday->today, it grew 1 MB.
[11:19] <seb128> it's something else
[11:19] <soren> Yeah.
[11:19] <pitti> seb128: I wonder myself -- today we dropped tomboy and a bunch of libs, and yet it didn't shrink
[11:20] <pitti> it even grew by 1 MB or so
[11:20] <seb128> pitti, no we didn't
[11:20] <seb128> pitti, tomboy etc are still in the current build
[11:20] <pitti> ??
[11:20] <seb128> well tomboy is in the manifest
[11:20] <ogra_> pitti, you uploaded to late for the iso build
[11:20] <pitti> ah, darn
[11:20] <seb128> $ grep tomboy oneiric-desktop-i386.manifest
[11:20] <seb128> tomboy	1.6.1-0ubuntu4
[11:20] <seb128> pitti, ^
[11:20] <soren> seb128: We still have the build logs, though.
[11:20]  * ogra_ was also just looking for tomboy in his manifests 
[11:21] <seb128> next build I guess
[11:21] <pitti> I did that first thing in the morning
[11:21] <pitti> https://launchpad.net/ubuntu/+source/ubuntu-meta/1.229
[11:21] <LLStarks> speaking of the hybrid iso... will zsync work fine?
[11:21] <pitti> no, the manifest does have 1.229
[11:21] <ogra_> weird
[11:22] <seb128> not so weird, didrocks ran into a similar case recently
[11:23] <pitti> I can't find it in germinate either
[11:23] <soren> There's a whole bunch of perl things on the CD now that weren't there two days ago.
[11:23] <seb128> pitti, cjwatson had an explanation the other day
[11:23] <soren> ...and autoconf and automake..
[11:23] <seb128> I think it's wrong timing issue
[11:24] <pitti> seb128: I'll try a rebuild then
[11:24] <seb128> like the lifefs build still had outdated datas or something
[11:24] <pitti> soren: uh
[11:24] <pitti> soren: there's also some 5 MB of new mono bits on it
[11:24] <soren> pitti: Really? didn't spot that yet.
[11:24] <seb128> well those were the 700 to 710 mb though
[11:24] <seb128> that's something new
[11:24] <seb128> soren, can you pastebin the diff?
[11:25]  * pitti sighs -- 25 MB growth in just a few days, after all the hard work of getting it from 730 to 698
[11:25] <soren> A whole bunch of erlang stuff was added.
[11:25] <pitti> oh, couchdb?
[11:25] <soren> seb128: I'm working on making it more readable.
[11:25] <seb128> soren, thanks
[11:25] <pitti> desktopcouch is back
[11:25] <soren> desktopcouch!
[11:25] <soren> Heh :)
[11:26] <pitti> for xdiagnose
[11:26] <seb128> desktopcouch is on the CD
[11:26] <seb128> bah
[11:26] <pitti> whcih also pulls in python-distutils-extra, and toolchain bits
[11:26] <pitti> xdiagnose                        | xdiagnose                        | x11-common (Recommends)                  | Bryce Harrington <bryce@ubuntu.com>
[11:26] <seb128> bryce, !!! ;-)
[11:27] <pitti> bryce: ^ could this not use desktopcouch?
[11:27] <soren> There we go.
[11:27] <pitti> bryce: also, I guess the python-distutils-extra dependency is unnecessary? (it's a build time tool)
[11:27] <pitti> oh, also uses python-gtk2
[11:28] <seb128> could be tjaalton's fault, he did the recent xorg upload ;-)
[11:29] <pitti> http://paste.ubuntu.com/627891/
[11:29] <pitti> seb128: I have a feeling that xdiagnose actually came from us, not from Debian
[11:29] <pitti> above pastebin is the delta from alpha-1 to today's daily
[11:29] <seb128> +  [ Bryce Harrington ]
[11:29] <seb128> +  * apport/source_xorg.py:
[11:29] <seb128> +    - Move Failsafe-X out of the xorg package to xdiagnose
[11:29] <seb128> +xorg (1:7.6+7ubuntu1) oneiric; urgency=low
[11:29] <seb128> +
[11:29] <seb128>  
[11:30] <seb128> I guess
[11:31] <pitti> hm, that delta doesn't have the xorg bits yet
[11:31] <pitti> I suppose the alternate was built before that got published?
[11:32] <seb128> pitti, that was uploaded on tuesday
[11:32] <seb128> so that would be weird
[11:32] <pitti> apt-get source xdiagnose -> no trace of couch there, hmm
[11:32] <soren> http://paste.ubuntu.com/627892/
[11:33] <soren> If you scroll down to line ~1700 or thereabouts..
[11:33] <soren> You see the stuff getting downloaded. Scroll down to see where the gaps are to see what was only downloaded now, but not two days ago.
[11:33] <soren> I've cheated a tiny bit (removed a few lines here and there to make things line up), but it's mostly accurate.
[11:34] <pitti> seb128: oh, xdiagnose 0.3 FTBFSed
[11:34]  * pitti looks to fix
[11:36] <seb128> soren, the perl stack is pulled in by python-distutils-extra it seems
[11:36] <pitti> I'll get that fixed, too
[11:36] <seb128> it's all down to the xorg issue
[11:36] <soren> seb128: Yup.
[11:36] <tjaalton> seb128: ah, so xdiagnose pulls a lot of stuff?
[11:36] <tjaalton> meh
[11:37] <pitti> tjaalton: it's all just an error, not required
[11:37] <tjaalton> pitti: cool
[11:37] <pitti> it doesn't even need pysupport/dh_python, there are no python modules
[11:37] <RAOF> tseliot: Yeah, you sneakily uploaded a new non-multiarched nvidia-current while I wasn't looking. :)  I've updated the Breaks, and I'll fix the armel build, and upload.
[11:38] <seb128> soren, thanks for the pastebin dual column thing ;-) but yeah, it's all down to one issue it seems
[11:38] <seb128> so let's wait for pitti to fix it and trigger a new iso build later in the day
[11:39] <tjaalton> pitti: the new xorg upload should actually save a few kb since -video-all pulls in fewer drivers now :)
[11:39] <soren> seb128: Sure thing. I was in the mood for a bit of detective work, apparently :)
[11:39] <seb128> ;-)
[11:39] <tseliot> RAOF: yes, thanks. I'll make sure nvidia and fglrx are ready soon so that we won't have to worry about this any more
[11:40] <pitti> bryce: I push my changes to lp:ubuntu/xdiagnose; is that ok?
[11:40] <RAOF> tseliot: The Breaks: will be unversioned this time; once we know what versions of the packages support multiarch we can stick the appropriate versioning on there.
[11:40] <pitti> uploaded 0.4
[11:40] <seb128> pitti, danke
[11:42] <tseliot> RAOF: right, as you explained on launchpad. It's a sensible choice, so that we don't have to rebuild mesa every time
[11:42] <seb128> rodrigo_, did you plan to fix other issues in accountsservices or do you need feedback from kees on your comments?
[11:43] <rodrigo_> seb128, I have a patch for upstream, about the -- thing Kees comments on, should be pushing it as soon as mclasen approves it
[11:44] <rodrigo_> seb128, apart from that, yes, need feedback from Kees
[11:44] <seb128> ok
[11:44] <seb128> rodrigo_, can you add a pointer to your patch and reassign to kees, setting as New?
[11:44] <seb128> not sure if he will notice comments otherwise
[11:45] <seb128> ok, lunch time
[11:45] <seb128> bbl
[11:45] <rodrigo_> seb128, yes, as soon as I push it, since mclasen told me it looked ok yesterday
[11:45] <seb128> rodrigo_, thanks
[11:45] <rodrigo_> seb128, just needed some more testing, which I've done today
[11:48] <dpm> pitti, chrisccoulson, a bunch of Natty langpacks + Firefoxes have been tested -> https://wiki.ubuntu.com/Translations/LanguagePackUpdatesQA - We don't have feedback for all languages, but as discussed, we need to upload them all to make sure FF appears translated. This is just a heads up that the testing period from the translations side is over, and that the langpacks can be uploaded
[11:52] <chrisccoulson> dpm - ok, thanks. they need to wait for the firefox release though
[11:52] <dpm> chrisccoulson, yeah, yeah, this was just a fyi that langpacks are ready to go
[11:52] <chrisccoulson> dpm - thanks :)
[11:52] <pitti> dpm: ah, thanks; so I guess we can wait a little longer until ffox is ready
[11:53] <chrisccoulson> i'm glad things have gone smoothly :)
[11:53] <dpm> chrisccoulson, np :) do you know roughly when the FF release is planned?
[11:53]  * pitti does another xdiagnose upload to actually make the package work
[11:54] <chrisccoulson> dpm - it's meant to be june 21st, i'm not sure if that will slip yet as they did 2 new beta's this week
[11:54] <dpm> chrisccoulson, ok, thanks
[11:54] <chrisccoulson> so, it looks like they've done their release build already
[11:55] <chrisccoulson> so i'd imagine we're still on for the 21st
[12:02]  * pitti ports xdiagnose to pygi while he is at it, and the project is still small
[12:07] <pitti> bryce: FYI, I ported xdiagnose from obsolete pygtk2 to PyGI with GTK3, and pushed to ubuntu:xdiagnose; but this doesn't build right now, I need to fix python-distutils-extra first (which I'll do now)
[12:14] <mpt> mvo, hi, I'm getting a blank grey window whenever I launch USC 4.0.3. Do you have time to help fix it? :-)
[12:15] <mvo> mpt: wehh - does ps afx show another running s-c that is for some reason sstale?
[12:16] <mpt> mvo, no, just the one
[12:17] <mpt> 21074 ?        Sl     5:34 /usr/bin/python /usr/bin/software-center
[12:17] <mvo> mpt: and if you kill that (kill 21074 on the terminal)
[12:17] <mvo> ?
[12:17] <mpt> mvo, when running it from a terminal I get the grey window, but the terminal command returns, which seems odd
[12:17] <mpt> mvo, killing that process closes the window
[12:18] <mpt> oh, and now relaunching it works fine
[12:18] <mpt> weird
[12:21] <mvo> mpt: yeah, so the problem is that one software-center was stuck for some reason (would be nice if you could mail me .cache/software-center/softwarecenter.log)
[12:21] <mvo> mpt: but it had a dbus server still running, so the other s-c tried to contact the dbus server of the hanging ne and exited
[12:26] <mpt> mvo, logs sent
[12:27] <cjwatson> LLStarks: zsync should continue to work just fine
[12:27] <cjwatson> pitti: have you folks debugged the CD size growth problems I saw in scrollback, or is there more to do?
[12:28] <seb128> cjwatson, it's debugged
[12:28] <seb128> cjwatson, should be fixed or will once things build
[12:28] <cjwatson> ok
[12:28] <pitti> cjwatson: the ones for the perl and couchdb/erlang bits, yes
[12:28] <pitti> cjwatson: not yet the mono growth
[12:29] <seb128> do we have the manifests from previous week somewhere?
[12:29] <seb128> just to diff what got pull off and in with the updates
[12:30] <seb128> well I guess diffing with alpha1 could work
[12:30] <seb128> it's just easier to work on a smaller diff
[12:35] <cjwatson> seb128: you might be able to find them by going to http://{cardamom,kapok}.buildd/~buildd/LiveCD/oneiric/ubuntu/ from a DC machine
[12:35] <cjwatson> depends how long ago
[12:35] <seb128> cjwatson, ok, thanks
[12:35] <seb128> cjwatson, should be around a week or less
[12:35] <cjwatson> seb128: also, the build logs have enough information to reverse-engineer the manifest, more or less
[12:36] <cjwatson> http://people.canonical.com/~ubuntu-archive/livefs-build-logs/oneiric/ubuntu/
[12:36] <cjwatson> we should probably log that properly somewhere
[12:37] <pitti> cjwatson, seb128: also, diff to alpha-1 is not too hard to read, I think: http://paste.ubuntu.com/627891/
[12:38] <pitti> (that's not a live .manifest diff, though, but an alternate; but it's more actionable)
[12:40] <pitti> ssl.SSLError: [Errno 185090050] _ssl.c:340: error:0B084002:x509 certificate routines:X509_load_cert_crl_file:system lib
[12:40] <pitti> oha
[12:40] <pitti> seb128: I just got that from lp-project-upload
[12:40] <pitti> seb128: wasn't that the one you got in the retracers as well?
[12:40] <pitti> httplib2 downgrade?
[12:41] <seb128> pitti, yes
[12:41] <seb128> pitti, downgrade python-httplib2 to the natty version
[12:42] <pitti> thanks
[12:42] <seb128> yw
[12:42] <pitti> that helped
[12:46] <pitti> bryce: FYI, p-distutils-extra fixed, so ubuntu:xdiagnose bzr head is good to go
[12:47] <seb128> go pitti go
[12:47] <seb128> pitti, once those are built can you do an iso spin?
[12:47] <pitti> pygified GTK3 xdiagnose, here you come!
[12:48] <pitti> seb128: the xdiagnose package with the dependencies fix is already published
[12:48] <pitti> so I'll start one in a few minues, yes
[12:48] <seb128> \o/
[12:48] <seb128> pitti, thanks
[12:48] <pitti> I wanted to do the GI port as a separate upload
[12:50] <seb128> cjwatson, is there a way to chroot in a daily-live iso?
[12:50] <seb128> (I'm trying to see if I can automate rdepends calls from a script)
[12:51] <cjwatson> well, you can loop-mount the ISO and then loop-mount casper/filesystem.squashfs?
[12:52] <cjwatson> if you have fuse privileges on the relevant system you might even be able to do that without root using grub-mount :-)
[12:52] <cjwatson> pitti: can you wait for parted 2.3-6ubuntu1 before spinning new ISOs, please?
[12:53] <cjwatson> might as well have a system that's vaguely installable
[12:57] <seb128> cjwatson, thanks, that works fine ;-)
[12:58] <seb128> (doing loop mounting, I didn't try grub-mount)
[12:58] <seb128> try grub-mount next just to see ;-)
[12:59] <pitti> cjwatson: sure
[13:00] <pitti> so, in an hour
[13:00] <pitti> sounds like lunch break :)
[13:00] <seb128> enjoy
[13:02] <cjwatson> seb128: it's not entirely POSIX-compatible, but it's fine for read-only work
[13:02] <cjwatson> (well, it never will be entirely POSIX, given that it will never support writing ...)
[13:02] <seb128> cjwatson, I just want an easy way to do rdepends list for gconf, gtk2 and some other things on the CD image
[13:03] <seb128> so read only is fine ;-)
[13:21]  * rodrigo_ -> lunch
[13:33] <fta2> hi, after an upgrade+reboot, i ended up with unity-2d
[13:34] <fta2> oh, unity_support_test crashed
[13:34] <fta2> known already?
[13:34] <seb128> fta2, nvidia?
[13:34] <fta2> yes
[13:34] <seb128> yes, known
[13:35] <fta2> ok, good
[13:35] <fta2> well, sort of
[14:17] <pitti> seb128: FYI, building new ubuntu alternate/desktop images now
[14:17] <seb128> pitti, thanks
[14:25] <sandy|lurk> seb128: howdy, just heard the news about Tomboy on the CD
[14:25] <seb128> sandy|lurk, hey
[14:26] <sandy|lurk> seb128: looked a bit, only issue appears to be that the gconf property editors library has some widgets (that we don't use) that depend on gnome-sharp and bring all that stuff in
[14:26] <sandy|lurk> seb128: so we can either just copy the widgets we use into Tomboy source, or see if the gconf-sharp maintainer will just remove that stuff and do a new release
[14:26] <seb128> sandy|lurk, right, gconfpeditor is in libgnome2.24-cil which brings the whole old gnome stack in
[14:26] <sandy|lurk> seb128: is there a timeframe that would make this really convenient for you?
[14:26] <sandy|lurk> or are we already dropped from the CD so it doesn't matter when we do it? :-P
[14:27] <seb128> sandy|lurk, you can't really remove the depends, it would break the api compability
[14:28] <seb128> sandy|lurk, there is no decision taken about dropping tomboy from the CD once it's ported to new apis
[14:28] <sandy|lurk> seb128: I guarantee you that no existing app uses the gnome-sharp-dependent peditors
[14:28] <sandy|lurk> but yeah, we'll just bundle, it is a tiny amount of code
[14:28] <sandy|lurk> seb128: sorry, I didn't understand that last bit
[14:29] <sandy|lurk> I mean, we can get rid of those dependencies without even porting to gsettings
[14:29] <sandy|lurk> and then just port to gsettings when the mono bindings are stable/released
[14:29] <sandy|lurk> since you guys are continuing to ship gconf
[14:30] <seb128> sandy|lurk, the main issue is that it brings libgnome, ui, bonobo, etc in now so yeah use gconf rather than gconfpeditor would be nice
[14:31] <seb128> but I though rodrigo checked with you previous cycle and that you said there was no plan to port to gconf, but rather to gsettings directly when it will have bindings...speaking of which do you know when mono will get gsettings bindings?
[14:32] <sandy|lurk> seb128: I believe knocte on the banshee team is planning to have that by the end of the cycle
[14:32] <seb128> sandy|lurk, sorry, I meant that we didn't decide to drop tomboy (yet), if it stops pulling old libs in we can put it back
[14:32] <sandy|lurk> but if it's not released, and they bundle or something, we wouldn't want to be stuck doing the asme
[14:32] <sandy|lurk> great :-)
[14:32] <sandy|lurk> we'll fix asap, hen
[14:33] <sandy|lurk> gtg, baby calling
[14:33] <seb128> sandy|lurk, we might have other discussions during the cycle to drop mono from the CD though since one options that would bring us the CD space we need (having 2 GTK stacks and some other things put us out of budget)
[14:33] <seb128> sandy|lurk, but that's nothing done and that will be only if we find no other way to solve the issues we have
[14:34] <sandy|lurk> :-(
[14:34] <seb128> sandy|lurk, thanks for checking with us on the tomboy situation ;-)
[14:35] <seb128> sandy|lurk, well I'm pretty sure there will be quite some push back on dropping mono if we suggest it so that's not done, it would not be the first cycle where it's suggested and doesn't happen so let's see
[14:41] <chrisccoulson> heh, is deja dup trying to frighten me in to backing up my files?
[14:41] <chrisccoulson> "In the case of a disaster, you would be able to recover them from that backup"
[14:41] <chrisccoulson> :)
[14:41] <seb128> yeah, if you don't opt-in mterry will make sure a disaster happens to your laptop at the rally ;-)
[14:43] <mterry> chrisccoulson, exactly.  :)  You hit the new "tell non technical users about backups" feature.  Should have only shown after a month from updating to 19.2 though...
[14:43] <seb128> deja-dup apparently backuped my datas yesterday morning, I didn't notice anything out of the notify-osd bubble to say that it finished doing a backup
[14:43] <mterry> seb128, good...?
[14:43] <seb128> mterry, yes, that's exactly what I'm waiting from a backuper, just be quiet and do the job ;-)
[14:44] <mterry> seb128, wait until you've successfully restored to say it did it's job ;)  not that I expect something to go wrong, but that's the crux of the biscuit
[14:45] <seb128> mterry, I just wish it was telling me somewhere when he last backup-ed things with success
[14:45] <mterry> seb128, it does, go to the preference screen
[14:45] <seb128> hum
[14:45] <seb128> I did
[14:45] <seb128> g-c-c using 100%cpu now
[14:45] <mterry> The overview page should have a line "Last backup:"
[14:45] <seb128> indeed
[14:46] <mterry> seb128, you get that too?  I was wondering what was going on
[14:46] <mterry> seb128, so did your "indeed" mean that you now see the "Last backup:" line?
[14:46] <seb128> yes
[14:46] <seb128> it says "today"
[14:47] <mterry> seb128, awesome.  I assume the g-c-c issue is due to the gtk3 bump...
[14:47] <seb128> it must have been this morning and not yesterday I got the notification, I was not sure ;-)
[14:47] <seb128> mterry, it does eat cpu when switching between categories
[14:47] <mterry> seb128, I get it eating cpu just sitting on a preference screen too
[14:47] <mterry> bad enough that compiz blacks it out
[14:48] <seb128> #6  0x0040a357 in icon_info_ensure_scale_and_pixbuf (icon_info=0xb2814308,
[14:48] <seb128> hum
[14:48] <seb128> I'm wondering if there is some icon it's busy scaling or something
[14:49] <chrisccoulson> the evolution messaging indicator only shows a count for the main inbox doesn't it?
[14:49] <seb128> chrisccoulson, correct
[14:49] <chrisccoulson> seb128, i'm just wondering what to do for thunderbird
[14:49] <seb128> mterry, yeah, seems gtk related, either theme or icons
[14:50] <seb128> chrisccoulson, check the spec or with mpt perhaps?
[14:51] <chrisccoulson> seb128 - the spec says - name should be set to to the name of the mailbox. If (and only if) there is more than one mailbox with the same name, the mail program should disambiguate them using the account name if possible, e.g. “Inbox (Home)” vs. “Inbox (Yoyodyne)"
[14:51] <chrisccoulson> which is how m_conley has already done it
[14:51] <chrisccoulson> but i'm thinking that if we only show a count for the inbox, then having "Inbox" in the menu seems a little redundant
[14:52] <seb128> the screenshot shows other boxes on the wiki though
[14:52] <chrisccoulson> mpt ^^ :)
[14:52] <seb128> "one message source item for each mailbox that contains new messages concerning you"
[14:52] <seb128> says the wiki
[14:53] <seb128> with a maximum of 6
[14:53] <chrisccoulson> ok, so it seems that evolution is not compliant with the spec :)
[14:53] <seb128> so I guess it should display the folder and count for folders with messages
[14:53] <seb128> seems not
[14:54] <chrisccoulson> i think thunderbird does the right thing then ;)
[14:54] <m_conley> points! :D
[14:54] <chrisccoulson> heh :)
[14:56] <seb128> well done guys ;-)
[14:59] <mpt> chrisccoulson, it depends whether you are able to get new-messages counts for individual Thunderbird folders. If you can, show them as separate items. If you can't, show a single count.
[15:00] <chrisccoulson> mpt - ah, ok. thanks
[15:01] <chrisccoulson> shouldn't it be "if you can't, then fix it so you can"? ;)
[15:01] <seb128> well, evo does neither of those
[15:01] <seb128> it shows a single count but which is the inbox one
[15:01] <seb128> not the unreads count
[15:11] <pitti> seb128, cjwatson: http://cdimage.ubuntu.com/daily-live/20110616.1/ -> back to the previous 709 MB, yay
[15:11] <seb128> \o/
[15:12] <pitti> that's still 10 MB more than we had a couple of days ago :/
[15:12] <seb128> -libgnome2-0	2.32.1-0ubuntu3
[15:12] <seb128> -libgnome2.24-cil	2.24.2-0ubuntu1
[15:12] <seb128> -libgnomecanvas2-0	2.30.3-0ubuntu1
[15:12] <seb128> -libgnomecanvas2-common	2.30.3-0ubuntu1
[15:12] <seb128> -libgnomeui-0	2.24.5-0ubuntu1
[15:12] <seb128> -libgnomeui-common	2.24.5-0ubuntu1
[15:12] <seb128> \o/
[15:12] <mterry> yay
[15:13] <seb128> -libbonobo2-0	2.32.1-0ubuntu1
[15:13] <seb128> -libbonobo2-common	2.32.1-0ubuntu1
[15:13] <seb128> -libbonoboui2-0	2.24.5-0ubuntu1
[15:13] <pitti> oh, and tomboy and old libs are gone now, and it still didn't shrink
[15:13] <pitti> so something else must have grown again, too
[15:13] <seb128> pitti, no, they are small
[15:13] <seb128> it's like a 1mb win which is what the iso format switch used
[15:13] <pitti> it seems cruft piles up faster than we can take it away :/
[15:13] <pitti> ah, that'd be the alignment, yes
[15:14] <pitti> but tomboy alone is already 0.5 MB
[15:15] <dobey> pitti: rhythmbox plz :)
[15:15] <pitti> butyeah, the rest is small
[15:15] <pitti> dobey++
[15:15] <seb128> pitti, right, but those libs are some ten kbs
[15:15] <pitti> I guess unseeding gbrainy is no biggue
[15:15] <pitti> biggie
[15:15] <seb128> it's not no
[15:18] <pitti> so for banshee, who should we ask about this?
[15:19] <pitti> i. e. who were the persons who advocated it for maverick/natty in the first place?
[15:19] <pitti> I remember jcastro
[15:20] <Laney> this is fast going from 'we can bring this back when you do the porting' to 'lets remove mono'
[15:20] <rodrigo_> yes, jcastro was the biggest advocate :)
[15:21] <pitti> Laney: mono itself would be a nice side effect of course, but my bigger concern is actually to get a GNOME 3 music player
[15:21] <pitti> (well, and I love RB)
[15:21] <pitti> but I don't want to make this a personal preference
[15:21] <Laney> you've spoken to upstream about their gtk3 plans?
[15:22] <chrisccoulson> i like banshee
[15:22] <chrisccoulson> but i would also like space for thunderbird :/
[15:22] <Laney> they said just today that it's hoped for this cycle
[15:22] <pitti> we had a discussion about it some weeks ago, and there was apparently some progress with providing GI support for mono
[15:22] <pitti> which would unblock the migration for banshee, tomboy, and all the other apps
[15:22] <pitti> I haven't spoken to them since then
[15:24] <Laney> 16/06 14:09:53 <knocte> sandy: migrating to gsettings is in the todo list of the bug to port to gtk3, hopefully will be finished by 2.2 (sept)
[15:24] <seb128> Laney, well the issue is rather down to "would having rb and thunderbird" better than what we have now
[15:24] <seb128> if we want thunderbird on we will need to make space
[15:24] <seb128> we will need to make space without that
[15:25] <seb128> and mono is one of the only things we could drop
[15:25] <Laney> if there's nothing anyone can do then just come out and say it
[15:25] <seb128> it would be unpleasant but better ideas are welcome
[15:25] <pitti> well, the question should be which music player is better
[15:25] <Laney> it doesn't sound like quality is the primary consideration
[15:25] <seb128> pitti, we decided on that previous cycle and that's why we switched
[15:25] <Laney> but space
[15:25] <pitti> we wouldn't want a worse music player to get a different email client
[15:26] <pitti> I'm not saying that RB would be worse; I don't personally think it is
[15:26] <pitti> but we shouldn't just discuss that in terms of space
[15:26] <seb128> Laney, yeah, it's not down to purely merit reasons, we need CD space :-(
[15:26] <pitti> otherwise we'd ship abiword and not LibO
[15:27] <seb128> well some people think the thunderbird brand and quality would be a strong value for Ubuntu
[15:27] <seb128> I've no strong opinion either way
[15:29] <seb128> Laney, btw is somebody looking at why the new mono is taking an extra 5mb on the CD?
[15:29] <Laney> i didn't know it was
[15:29] <Laney> what grew?
[15:29] <seb128> I tried to have a look but out of noticing it has some new binaries I've no clue about I don't know why
[15:29] <seb128> Laney, http://paste.ubuntu.com/627891/
[15:29] <seb128> new binaries
[15:30] <seb128> libmono-corlib4.0-cil (1.0 MB)
[15:30] <seb128> libmono-system4.0-cil (0.7 MB)
[15:30] <seb128> libmono-system-xml4.0-cil (0.4 MB)
[15:30] <Laney> oh we probably have a dual 2.0/4.0 stack
[15:30] <seb128> libmono-csharp4.0-cil (0.4 MB)
[15:30] <Laney> http://people.canonical.com/~ubuntu-archive/transitions/mono.html
[15:30] <seb128> libmono-security4.0-cil (0.1 MB)
[15:30] <Laney> stuff needs rebuilding to get it from 2.0 → 4.0
[15:30] <Laney> directhex is handling it
[15:31] <seb128> ok
[15:31] <rodrigo_> is mono-introspect the project for bringing the new introspection bindings?
[15:31] <seb128> so that should autosort itself over rebuilds?
[15:31] <seb128> pitti, ^ well at least that's something
[15:31] <Laney> the 2.0 stuff should fall off
[15:31] <seb128> great
[15:31] <seb128> Laney, thanks
[15:32] <pitti> ah, thanks for the heads-up
[15:32] <Laney> do rebuilds if you want, but start with core stuff first
[15:32] <Laney> mono → libraries → apps
[15:32] <pitti> so it's more or less an ABI transition
[15:32] <Laney> everything in main should be without issue
[15:32] <Laney> http://wiki.debian.org/Teams/DebianMonoGroup/Mono210TransitionTODO
[15:32] <sandy|lurk> should Oneiric alpha 1 work in vmware or vbox? do I get some 2D environment?
[15:32] <Laney> probably best to coordinate with directhex before doing any rebuilds though
[15:32] <pitti> i. e. "apt-cache rdepends libmono-corlib2.0-cil" shoudl be empty at some point?
[15:33] <Laney> yeah
[15:33] <Laney> it's a transition from CLR 2.0 to CLR 4.0
[15:34] <seb128> sandy|lurk, not sure, it will fallback to unity-2d but it has some issues, you might be better trying a daily
[15:34] <seb128> sandy|lurk, http://cdimage.ubuntu.com/daily-live/
[15:34] <rodrigo_> hey sandy|lurk
[15:35] <seb128> has->had
[15:35] <sandy|lurk> thanks seb128
[15:35] <seb128> yw
[15:35] <rodrigo_> sandy|lurk, is mono-introspect the project for bringing the new introspection bindings?
[15:35] <sandy|lurk> hi rodrigo_
[15:35] <sandy|lurk> rodrigo_: I don't know
[15:35] <sandy|lurk> sorry, I'm totally out of the loop
[15:35] <rodrigo_> sandy|lurk, and if so, is the github repo the correct one?
[15:35] <rodrigo_> sandy|lurk, ah, ok, didn't get any answer from alan
[15:35] <sandy|lurk> rodrigo_: the guys in #banshee (on gimpnet) are pretty on top of this, it seems
[15:35] <broder> sandy|lurk: vmware doesn't support passing through the opengl support needed for unity, but vbox should if you install the guest tools
[15:35] <Laney> try knocte
[15:35] <sandy|lurk> maybe knocte knows?
[15:35] <Laney> or more generally #banshee
[15:36] <broder> sandy|lurk: (might need the non-open guest tools)
[15:36] <sandy|lurk> broder: not a problem, I'm actually in OS X for work right now
[15:36] <sandy|lurk> thanks
[15:36] <rodrigo_> sandy|lurk, ok, trying
[15:36]  * Laney covers his eyes
[15:38] <seb128> \o/ the retracers natty and oneiric queues are empty
[15:40] <pitti> nice!
[15:41] <rodrigo_> hmm, https://github.com/mono/gtk-sharp seems to have support for 3.0, included gio
[15:43] <cyphermox> seb128: dunno, I tried yesterday's daily (today seems to be missing amd64), and lightdm or session startup has issues
[15:43] <cyphermox> sandy|lurk: rodrigo_: ^
[15:43] <seb128> how so?
[15:44] <seb128> it doesn't autologin but doing enter should work?
[15:44] <cyphermox> after you login in lightdm, you get thrown back to the text cnsole
[15:44] <pitti> cyphermox: did you select ubuntu-2d?
[15:44] <cyphermox> isn't there a password?
[15:44] <pitti> cyphermox: or tried on real iron?
[15:44] <pitti> cyphermox: it's empty, just press enter
[15:44] <cyphermox> pitti: iron
[15:44] <rodrigo_> cyphermox, gnome-session crashing maybe?
[15:44] <cyphermox> heh. maybe that's what I did wrong, I was convinced the password was "ubuntu"
[15:45] <cyphermox> but yeah, gnome-session was crashing in some way even if I did startx after
[15:45] <cyphermox> I ended up adding ubiquity to .xinitrc and startx again ;)
[15:45] <charlie-tca> user = ubuntu, password = ENTER
[15:45] <charlie-tca> hit ENTER, that is
[15:45] <cyphermox> yeah ;)
[15:59] <fta> mvo, hi, what exactly are those "short read on buffer copy for backend dpkg-deb" errors about?
[16:00] <jibel> cyphermox, I can confirm what you said re lightdm login on live cd. If the user enters a password he's dropped to a console. nice
[16:00] <cyphermox> jibel: well, the password *is* wrong ;)
[16:01] <jibel> cyphermox, sure, but that's not a  reason to punish the user with a console only mode.
[16:01] <cyphermox> jibel: indeed
[16:10] <cyphermox> jibel: are you using today's image?
[16:10] <jibel> cyphermox, yes
[16:10] <cyphermox> ok
[16:11] <cyphermox> jibel: are you able to partition?
[16:11] <jibel> cyphermox, 20110616.1
[16:11] <jibel> cyphermox, haven't tried, the default test uses the whole drive
[16:12] <jibel> cyphermox, anyway the default partitioning scheme works fine.
[16:12] <cyphermox> jibel: that's what I'm trying to do too, but with the 20110615 image because 16 and 16.1 don't have amd64
[16:13] <jibel> cyphermox, the fix for the partman is on 20110616.1
[16:13] <cyphermox> ah!
[16:31] <pitti> hm, is it just me, or is empathy jabber quite busted? I receive notifications, but the chat window just greys out and uses 100% CPU once you try to send something
[16:31] <pitti> and it doesn't display conversations
[16:31] <pitti> kenvandine: ^ is that related to the telepathy-indicator bits by chance?
[16:32] <kenvandine> ugh
[16:32] <kenvandine> shouldn't be... but perhaps
[16:32] <kenvandine> actually no
[16:32] <kenvandine> it couldn't cause the chat window to grey out
[16:33] <pitti> ok
[16:33] <pitti> well, if it works for other people, I'll some more debugging
[16:33] <kenvandine> i haven't restarted since updating today...
[16:34] <pitti> it's not new from today, it started a couple of days ago
[16:34] <kenvandine> oh, interesting
[16:35] <kenvandine> not sure... i am actually running empathy 3.1.2 now, which i think is still in depwait on the new folks to get out of binNEW
[16:38] <pitti> NEWed
[16:40] <kenvandine> pitti, thx :)
[16:46] <rodrigo_> ugh, toothache is starting to be unbearable, bbl
[16:48] <pitti> rodrigo_: get well soon!
[16:48]  * pitti sympathizes with rodrigo_, was at the dentist today as well
[16:48] <pitti> scary people!
[17:01] <mvo> I do the vte merge now if nobody minds
[17:01] <pitti> thanks
[17:15] <seb128> hum
[17:15] <seb128> stupid question, but can a source v1 package use a .tar.bz2 orig?
[17:15] <seb128> it's ignoring the .orig.tar.bz2 and doing a native source build
[17:16] <Laney> no, gz only
[17:16] <seb128> bah
[17:17] <seb128> thanks
[17:18] <pitti> seb128: what's wrong with 3.0 (quilt)?
[17:19] <seb128> pitti, I'm doing the unity update and it's full source in vcs
[17:19] <pitti> seb128: bzr, bzr bd-do/uscan will automatically create a .gz from the .bz2, but that's not what we want, i guess
[17:19] <seb128> oh and also I think whatever dx is using for their daily builds didn't like source v3
[17:19] <seb128> hudson?
[17:20] <pitti> ah
[17:20] <seb128> well anyway I will tar xjf; tar czf
[17:20] <pitti> I assumed it was GNOME now not releasing tar.gz any more
[17:20] <pitti> gzip -cd tar.gz | bzip2 -9 > tar.bz2 should do, no reason to regenerate the .tar
[17:20] <pitti> but anyway
[17:20] <seb128> I guess that's what didrocks does usually
[17:20] <pitti> if DX wants orig.tar.gz, why don't they release tar.gz?
[17:21] <seb128> I think DX doesn't care about the format
[17:21] <seb128> it's didrocks who does the packaging
[17:21] <pitti> dinner, back for TB meeting
[17:21] <seb128> but since he's offline I will just do that update and sort it with him later
[17:21] <seb128> pitti, see you
[17:54] <LLStarks> seb128, as per the discussion last night. the erlang, python dist, and couch stuff is gone again, right?
[17:56] <seb128> LLStarks, hum, I was not sure yesterday for a discussion about that, we investigated this afternoon though and fixed it yes
[17:58] <LLStarks> hehe timezones. thanks.
[18:04] <seb128> ok, new unity uploaded to oneiric
[18:04] <seb128> there is a launcher autohide bug though
[18:04] <seb128> bug #798318
[18:04] <ubot2> Launchpad bug 798318 in unity "launcher autohidding is failing with 3.8.16" [High,Confirmed] https://launchpad.net/bugs/798318
[18:04] <seb128> so I've not uploaded as a sru yet
[18:04] <seb128> but I've done a natty upload to https://launchpad.net/~ubuntu-desktop/+archive/ppa
[18:05] <seb128> if people want to test it
[18:05] <seb128> dx is working on a fix for the issue and if no other bug is raised on oneiric we might get the sru done tomorrow
[18:09] <LLStarks> will do. this is for sru2, right?
[18:10] <seb128> yes
[18:10] <seb128> what is the ppa is the sru candidate
[18:10] <seb128> since I've found the bug I pointed before I didn't bother uploading for SRU, we will need a patch for it so waiting on that
[18:11] <seb128> so testing is welcome to make sure there are no other bug ;-)
[18:13] <LLStarks> kinda sad that unatty needs such aggressive SRU fixes, but that's a 26 week dev cycle for ya
[18:33] <dobey> sad because natty got firefox 5.0 as an sru? :)
[18:33] <broder> i don't think there's anything sad about SRUs
[18:34] <dobey> broder: only if you're a developer trying to get certain updates in :)
[18:35] <broder> dobey: no, i think SRUs are great as an end user
[18:35] <broder> and i think they're great for anybody who's not crazy enough to run dev releases (which is almost everybody)
[18:36] <micahg> dobey: no, it will be a security update...
[18:36] <micahg> dobey: the security team has the right to use proposed for extended testing and I will be taking advantage of that
[18:39] <dobey> micahg: ah, i guess that's why i got it then. didn't see where it came from exactly. but alas
[18:39] <micahg> dobey: it's only in -proposed at the moment (at least it better be :))
[18:39] <dobey> broder: yes, but as a developer trying to get certain chanes into SRU, it can be a hassle. :)
[18:40] <dobey> micahg: right, i'm pretty sure i have -proposed enabled and just forgot about it :)
[19:04] <pitti> please someone say that they can read me
[19:04] <micahg> pitti: I can read you :)
[19:04]  * pitti haven't had a TB meeting yet where nobody at all turned up
[19:04] <pitti> micahg: thanks :)
[19:08] <chrisccoulson> pitti - i can't read you ;)
[19:09]  * pitti ^5s chrisccoulson
[19:09] <chrisccoulson> heh :)
[19:39] <bryce> pitti, awesome, thanks!
[19:39] <pitti> hey bryce, good morning
[19:39] <pitti> bryce: later I noticed that there's an lp:xdiagnose branch which looks like being the packaging branch
[19:40] <pitti> I didn't see it at first, as there's no Vcs-Bzr:
[19:40] <pitti> bryce: do you rather want to use this instead? I could replay the commits into that, and propose a merge (I can't commit to lp:xdiagnose)
[19:40] <bryce> pitti, yeah I should add that
[19:42] <bryce> pitti, it's both the main branch and packaging, I haven't split them out (perhaps they should?)
[19:42] <pitti> bryce: if you split it, then we can just as well use the standard ubuntu:xdiagnose branch, I guess?
[19:43] <pitti> bryce: but right now it is versioned as ubuntu native, so splitting the branch sounds too complicated to me; but it's your baby, set it up as you like
[19:46] <bryce> pitti, yeah let's keep it simple.  I can give you commit access to lp:xdiagnose
[19:47] <bryce> (I think...)
[19:49] <bryce> pitti, actually, yeah just propose a merge, that's probably easiest
[20:02] <pitti> bryce: done, https://code.launchpad.net/~pitti/xdiagnose/oneiric/+merge/64886
[20:03] <pitti> bryce: perhaps you can pull from lp:~pitti/xdiagnose/oneiric instead of merging, to retain a clean history
[20:03] <bryce> pitti, ok
[20:06] <bryce> pitti, thanks for converting to dh7 btw, that was on my todo list today :-)
[20:06] <pitti> bryce: no problem, it was quite easy, and actually required to make the package work
[20:06] <pitti> before it didn't install any of the upstream parts
[20:06] <pitti> it's much easier now
[20:07] <pitti> just a boilerplate standard python 4-line debian/rules
[20:07] <pitti> TTFN, have a nice evening everyone!
[20:07] <kenvandine> good night pitti
[20:09] <bryce> pitti, night!
[20:14] <cyphermox> hey bryce, i saw your email about the diffs between packages earlier, really nice :)
[20:19] <bryce> cyphermox, thanks
[20:33] <cyphermox> oh yay, finally got nm-applet in more than one user at the same time.
[20:37] <broder> ooooh
[21:18] <cjwatson> looking at bug 797669
[21:18] <ubot2> Launchpad bug 797669 in casper "No autologin on live session with lightdm" [High,Triaged] https://launchpad.net/bugs/797669
[21:18] <cjwatson> seb128 says that the conffile will be /etc/lightdm/lightdm.conf in the next update (it's currently /etc/lightdm.conf)
[21:18] <cjwatson> I don't want to have to keep moving this around in casper and other bits of the installer - I'd rather wait for the location to settle and then use that
[21:19] <cjwatson> when's that next update going to be?
[22:21] <mterry> is empathy chat broken for anyone else?
[22:31] <TheMuso> cjwatson: Robert said he plans updating this week, so likely uploaded today Australian EST.
[22:33] <cyphermox> mterry: yes, empathy is broken majorly for me, too
[22:33] <mterry> cyphermox, ever since the gtk3 update
[22:33] <cyphermox> I try to type, it hangs; I kill chat windows, it eventually somewhat unfreezes and starts showing e.g. notifications
[22:35] <cyphermox> ahh, thanks for closing the nm task on the 0.9 API bug
[22:40] <cjwatson> TheMuso: OK, that's soon enough I guess then
[23:25] <TheMuso> kenvandine: Just a heads up, it seems that services/Makefile is missing from configure.ac in your new libgwibber. I'd send a patch, but its so trivial that its quicker to let you know about it.
[23:26] <TheMuso> However, I can send a merge proposal/patch.