[07:20] <didrocks> good morning
[07:38] <pitti> Good morning
[08:04] <pitti> BANZAI!
[08:04] <pitti> http://cdimage.ubuntu.com/daily/current/
[08:05] <pitti> i386/amd64 not oversized any more
[08:05] <pitti> OO.o helped to kill ~ 10 MB
[08:05]  * pitti dances around happily
[08:06] <micahg> pitti: BTW, libreoffice is in experimental
[08:06] <pitti> micahg: right, but I won't touch it, I'm afraid
[08:07] <pitti> micahg: we'll get a proper OO.o maintainer soon
[08:07] <pitti> it already took me half a week to get the current version building on natty..
[08:07] <micahg> pitti: wow, yeah, I just read the changelog, I hope the libreoffice build system ends up a little cleaner
[08:08] <pitti> micahg: so am I; doing patches-for-patches hurts a lot
[08:08] <pitti> micahg: well, I hope/think that most of the go-oo patches can make it into upstream libreoffice
[08:09] <pitti> and for the remaining ones we can hopefully just have a single set of patches which are directly applied to the build tree
[08:22] <didrocks> hey pitti!
[08:23] <didrocks> pitti: excelent :)
[08:23] <didrocks> pitti: oh really, we have an OO.o maintainer now? \o/
[08:24] <pitti> didrocks: not yet
[08:24] <pitti> didrocks: just a poor pitti who spend his nights sledgehammering on the current package :)
[08:24] <didrocks> pitti: hehe, yeah, I can imagine. I played that game for a week in August
[08:25] <didrocks> pitti: at least, I hope that me, documenting all changes in debian/changelog helped you
[08:25] <didrocks> (because most of the diff between debian and us wasn't documented…)
[08:42] <pitti> unfortunately http://cdimage.ubuntu.com/daily-live/20101213/ is still heavily oversized
[08:45] <didrocks> :/
[08:45] <didrocks> pitti: how was your week-end, btw?
[08:46]  * didrocks just finished a tedious 2 hours of week-end unity bug triaging :/
[08:46] <pitti> didrocks: went to visit my parents and cousins yesterday, for the ceremonial red cabbage cooking :)
[08:46] <pitti> (my father has an awesome recipe)
[08:46] <pitti> otherwise it was fairly quiet; some OO.o hacking, and some idling, I caught a bit of a cold
[08:46] <didrocks> oh nice!
[08:46] <didrocks> urgh
[08:46] <pitti> didrocks: last week I discovered http://www.dxx-rebirth.com/
[08:46] <didrocks> take care… not very surprising with this weather btw :)
[08:47] <pitti> that's a productivity killer :)
[08:47] <pitti> I loved Descent back in the DOS era
[08:47] <didrocks> oh, excellent! Yeah, you will kill my productivity as well :)
[08:47] <pitti> and now it runs amazingly well under Linux, and it looks 10 times better than back then due to full resolution
[08:47] <didrocks> I played that game too much :)
[08:48] <pitti> didrocks: I'm in level 9 in Ace mode now -- gee, they really give you a good beating at that difficulty
[08:48] <didrocks> pitti: they changed the difficulty level?
[08:48] <pitti> didrocks: no, I just didn't play Ace back then
[08:48] <pitti> didrocks: btw, if you want to build it, give me a ping; there's some tricks you have to do to get it to build
[08:49] <didrocks> pitti: oh sure, I'll. Probably after the holidays I guess (so in January) as I think I'll have to focus on housework first :)
[08:49] <didrocks> thanks :)
[08:50]  * pitti discovers 1.9 MB balooning of libgphoto2 and fixes
[08:50] <didrocks> 1.9 MB? what was the cause?
[08:52] <pitti> it accidentally ships the API docs in both the lib and the -dev package
[08:53] <didrocks> oh ok
[08:53] <pitti> I'm analyzing the iso-deb-size-compare result between maverick and current daily
[08:54] <pitti> and this one stuck out
[08:55] <didrocks> oh there is such a tool or did you hack a shell-script ourself (I did that when I tracked the oversize in UNE). I've always wondered why the manifest doesn't report the size
[09:00] <pitti> didrocks: I hacked it a few months ago
[09:00] <pitti> didrocks: it's in lp:ubuntu-archive-tools
[09:02] <didrocks> pitti: thanks I'm refreshing my branch then :)
[09:04] <htorque> didrocks, bug 688803
[09:04] <ubot2> Launchpad bug 688803 in unity (Ubuntu) (and 1 other project) "SIGSEGV in g_atomic_int_get (affects: 1) (heat: 6)" [Medium,Triaged] https://launchpad.net/bugs/688803
[09:04] <htorque> what's incomplete there (except the call in /usr/lib/libdbusmenu-glib.so.2)? i always thought if i get all function names i'm good to report?
[09:05] <didrocks> htorque: if you look, for some function, you ony have the prototype, not the values, not sure why, I was blaming missing dbgsym
[09:05] <didrocks> htorque: but in any case, it can be easily reproduced, hence the triaged :)
[09:07] <htorque> didrocks, oh, i see. will try again. :)
[09:07] <didrocks> htorque: thanks :)
[09:07] <didrocks> htorque: you know about the dbgsym and such, I guess?
[09:07] <didrocks> htorque: oh you build from trunk most of the time, scratch it :)
[09:07] <didrocks> (but not for bamf and glib I guess)
[09:17] <seb128> hey
[09:17] <pitti> hey seb128
[09:17] <seb128> hey pitti
[09:17] <seb128> how are you?
[09:17] <seb128> had a nice we?
[09:18] <pitti> seb128: have a bit of a sore throat, but weekend was nice, yes
[09:18] <pitti> seb128: I finally got OO.o to build \o/
[09:18] <seb128> oh, take care of you then
[09:18] <seb128> nice, so you are officially maintain it now? ;-)
[09:18]  * seb128 runs away from pitti
[09:18] <pitti> seb128: sorry, I didn't understand your last sentence; must be a temporary transmision glitch
[09:19] <didrocks> salut seb128, ça va?
[09:19] <seb128> lut didrocks
[09:20] <seb128> ouais et toi ?
[09:20] <didrocks> ça va bien :)
[09:21] <seb128> did the unity and indicators update land on friday?
[09:21] <seb128> did they work? ;-)
[09:21] <pitti> and we have current CD images again, finally
[09:22] <didrocks> seb128: unity landed and worked for me. Not sure about the indicators update
[09:23] <didrocks> seb128: seems that a lot of people got stuck in the dist-upgrade which removed the indicators
[09:23] <didrocks> so, I'm just apt-get upgrade now and then will try a dist-upgrade to see the current status
[09:25] <seb128> ok
[09:26] <htorque> didrocks, yeah, when testing trunk i always remove the -dbgsym packages to avoid conflicts. looks like i didn't reinstall them when testing this with the natty packages. :)
[09:27] <didrocks> htorque: ok :)
[09:43] <chrisccoulson> good morning everyone
[09:43] <seb128> hey chrisccoulson
[09:43] <pitti> hey chrisccoulson, how are you?
[09:43] <seb128> how are you?
[09:44] <chrisccoulson> good thanks, how are you?
[09:44] <seb128> I'm fine thanks
[09:46] <chrisccoulson> hmmm, unity doesn't work well when i dock my laptop :/
[09:46] <chrisccoulson> i have one black screen and one screen with half a shell on it ;)
[09:47] <didrocks> hey chrisccoulson
[09:47] <chrisccoulson> hi didrocks, how are you?
[09:47] <didrocks> chrisccoulson: yeah, multi-monitor isn't good for now
[09:47] <didrocks> chrisccoulson: I'm tired but fine, thanks :)
[09:48] <chrisccoulson> ah, restarting compiz fixes the issues :)
[09:48] <chrisccoulson> i now have 2 monitors back
[09:51] <didrocks> chrisccoulson: yeah, but the panel isn't at its best from the bug reports I see :)
[09:52] <chrisccoulson> didrocks - yeah, it spans both monitors and the menubar on the opposite monitor is a bit weird ;)
[09:52] <chrisccoulson> but i need to run unity now to hack on the ffox menubar :)
[09:52] <didrocks> chrisccoulson: there are already discussions on bugs about that :)
[09:53] <didrocks> chrisccoulson: hehe :) (I think you can also use the gnome-panel appmenu applet, but I won't discourage you using unity of course :p)
[09:54] <chrisccoulson> oh, i didn't realise that!
[09:57] <seb128> catching up on planet
[09:57] <seb128> chrisccoulson, nice appmenu firefox work ;-)
[09:58] <chrisccoulson> thanks :)
[09:58] <seb128> pitti, I think one reason to not preselect the gdm user as well was that selecting it starts the pam dialog
[09:58] <chrisccoulson> there's still quite a lot for me to do, and i need to get some missing features in to libdbusmenu this week too
[09:58] <chrisccoulson> but it's getting there!
[09:58] <seb128> there was some issues, timeout bugs, etc in the past about those
[09:58] <seb128> chrisccoulson, ;-)
[09:59] <pitti> seb128: I see; right, it needs to check for the auth method
[10:00] <seb128> well I don't say it's not doable but it would not be as trivial as activating the widget
[10:08] <pitti> didrocks: do you know what the real packaging bzr branch for unity-asset-pool is?
[10:08] <pitti> didrocks: https://code.launchpad.net/unity-asset-pool is not entirely clear, and the package doesn't have a vcs-bzr
[10:08] <didrocks> pitti: should be lp:~unity-team/unity-asset-pool/packaging
[10:08] <pitti> meh, -ECAN'TCOMMIT
[10:09] <pitti> didrocks: if I throw you a branch, could you pull it into that one?
[10:09] <didrocks> yeah, that's something which should be fixed, not sure that subscribing all core-dev to unity-team and getting spammed but all unity bugs is nice though :/
[10:10] <didrocks> pitti: sure, sorry for the extra work
[10:10] <pitti> didrocks: no problem
[10:10] <pitti> I also need to fix notify-osd, doesn't build in natty
[10:10] <pitti> but I think I still have upstream commit powers there
[10:10] <didrocks> hehe :)
[10:10] <seb128> didrocks, why do we need unity in the unity team vcs?
[10:10] <seb128> the packaging should use the standard lp:ubuntu
[10:11] <seb128> pitti, check with mirco, I think they fixed issues in trunk
[10:11] <seb128> pitti, would be nice to get a new tarball as well
[10:11] <didrocks> seb128: well, we set up like that at the beginning, but yeah, that should be pushed in lp:ubuntu. can do it
[10:11] <pitti> didrocks: I can do that as well, while I'm at it
[10:11] <pitti> didrocks: (u-a-p to lp:ubuntu/
[10:11] <didrocks> pitti: sure, please do :)
[10:11] <didrocks> I'll do the others
[10:11] <pitti> alrighty
[10:12] <pitti> didrocks: perhaps you can delete the branch from LP then
[10:12] <seb128> brb session restart
[10:12] <didrocks> pitti: seb128: the only thing is that for daily build, sometimes, I change the packaging in advance
[10:12] <didrocks> too late :)
[10:15] <mvo> chrisccoulson: hey, I got a mail from a guy with problems with the latest ff/tbird (from 2010-12-10) are you interessted in reports like tihs?
[10:16] <mvo> chrisccoulson: very little details unfortuantely
[10:16] <chrisccoulson> mvo - it depends on what the problem is ;)
[10:17] <chrisccoulson> we get quite a lot of different problems from single reporters which generally tend to either not be real bugs or problems with plugins or extensions, so i normally only look at problems that affect more than one person ;)
[10:20] <mvo> chrisccoulson: yeah, I figured that. fair enough
[10:20] <chrisccoulson> mvo - what details do you have though?
[10:21] <mvo> very little
[10:21] <mvo> http://paste.ubuntu.com/542986/
[10:21] <mvo> but I wanted to raise it just in case it affects more people
[10:21] <mvo> don't worry if its a single report
[10:22] <didrocks> seb128: the only thing about packaging in lp:ubuntu, is that for daily build, sometimes, I change the packaging in advance. But it's rare enough to be a corner case
[10:23] <seb128> didrocks, well, you can have unreleased commits in lp:ubuntu
[10:24] <didrocks> seb128: yeah, but basically, some commits are in advanced like updating the symbol files for symbols in next release
[10:24] <didrocks> but again, that's a corner case
[10:24] <didrocks> or maybe ~ubuntu-desktop will make more sense for that?
[10:24] <didrocks> pitti: ^^
[10:25] <pitti> didrocks: no, use lp:ubuntu/
[10:25] <pitti> didrocks: since ~ubuntu-desktop has upload rights for these packages, they can also commit there
[10:25] <pitti> it's all integrated into per-package uploader etc.
[10:25] <pitti> didrocks: and yes, it's totally fine (and encouraged) to commit stuff there without upload, same as with the old branches
[10:26] <pitti> it's still a bzr branch, after all
[10:26] <didrocks> ok, and for compiz? it has been ~compiz for some time already
[10:26] <pitti> mvo's and your call, I guess
[10:26] <pitti> I'm all for allowing people to commit when they can upload
[10:26] <pitti> otherwise it's quite a burden
[10:27] <seb128> well it's not an issue when you have a list set for the teams
[10:28] <seb128> like anybody with upload rights can commit to the ubuntudesktop vcs
[10:28] <pitti> seb128: I need to rebuild seahorse; want me to upgrade to 2.32 while I'm at it?
[10:28] <seb128> but the unity team has no mailing list so it would mail spam everybody
[10:28] <pitti> (we are at 2.91.2)
[10:28] <pitti> erm, ignore me
[10:29] <pitti> I read it backwards
[10:29] <seb128> ;-)
[10:29] <pitti> uscan FTL
[10:29] <seb128> we have 2.32
[10:29] <seb128> pitti, just curious why do you need to rebuild it? is there a list of "need rebuilds" we can help on?
[10:29] <pitti> seb128: optimize SVGs and PNGs
[10:30] <pitti> seb128: http://paste.ubuntu.com/542992/
[10:30] <pitti> seb128: I spent some time analyzing today's CDs
[10:30] <pitti> and this is my work list
[10:30] <pitti> I can finish SVGs/PNGs today, then this chapter is done :)
[10:31] <seb128> ok
[10:31] <seb128> those changes make me nervous btw
[10:31] <pitti> which?
[10:31] <seb128> having games excluded from the list seems a workaround
[10:32] <seb128> touching the images without knowing if the software rely on them being in a specific format
[10:32] <seb128> is that being done only on things on the CD? or anything using cdbs will get it?
[10:32] <pitti> anything right now (except games)
[10:32] <seb128> didrocks, ubuntu-desktop is a subteam of compiz
[10:32] <pitti> I haven't heard about problems with that yet, aside from this game
[10:33] <didrocks> seb128: should we rather do the same with unity + add a ML?
[10:33] <seb128> pitti, ok, well let's see but it makes me nervous a bit
[10:33] <didrocks> seb128: I don't really care, just if we can be consistent :)
[10:34] <seb128> didrocks, being consistent would be to move to lp:ubuntu
[10:34] <seb128> imho
[10:34] <seb128> well do we need a special team for unity?
[10:34] <seb128> seems you abuse the unity upstream team for packaging
[10:34] <seb128> didrocks, you could move it to the ubuntu-desktop team if you prefer
[10:34] <seb128> that would be better than the unity one to start
[10:35] <didrocks> seb128: I proposed that as well, but pitti is more in favor for lp:ubuntu/
[10:35] <didrocks> so let's do that way
[10:35] <seb128> well then you can as well as james_w to alias the lp:ubuntu location to it
[10:35] <seb128> that's what we do for dx sources
[10:35] <seb128> indicators
[10:35] <pitti> didrocks: ~branch is by and large ~ubuntu-desktop for desktop packages :)
[10:35] <seb128> well you need to ask james_w
[10:36] <pitti> meh, seems I'm not able to commit to notify-osd trunk any more
[10:36] <seb128> the autoimport source is not a derivative of the upstream vcs
[10:36] <didrocks> ok, will do that then, setting up a list and pushing under ~ubuntu-desktop
[10:36]  * pitti will do a MP
[10:36] <seb128> pitti, what error do you get? did you check the merge proposal for it?
[10:36] <seb128> it seems people were speaking about fixes for notify-osd last week
[10:36] <pitti> seb128: I only checked out trunk
[10:36] <pitti> seb128: usr/bin/ld.bfd.real: notify_osd-bubble.o: undefined reference to symbol 'XDeleteProperty'
[10:37] <pitti> it's a missing -lX11
[10:37] <pitti> seb128: will look at MPs
[10:38] <pitti> seb128: nope, nothing there; I'll do my own
[10:38] <seb128> pitti, https://wiki.ubuntu.com/RobSavoye/GoldFixes/notify-osd
[10:39] <seb128> pitti, Sarvatt_ was working on it last week according to my logs
[10:39] <pitti> ugh, most discoverable page ever :)
[10:39] <seb128> he uploaded a fixed version to a ppa apparently
[10:39] <pitti> Sarvatt_: do you have a local notify-osd branch for that?
[10:39] <seb128> pitti, maybe check with him to no dup work
[10:39] <pitti> seb128: ok, I'll shelve that until later then
[10:39] <pitti> seb128: thanks for pointing out
[10:39] <seb128> np
[10:40] <seb128> xorg-edgers has it
[10:41] <seb128> hum no, the upload there failed to build
[10:41] <seb128> I will let Sarvatt_ comment ;-)
[10:41] <pitti> right
[10:42] <pitti> not that urgent
[10:42] <seb128> in any case would be nice if macslow could roll a tarball
[10:42] <seb128> the trunk has some bug fixes as well
[10:42] <pitti> two or three, yes
[10:43] <pitti> perhaps he can do a MP review before, and get this fixed
[10:43] <pitti> since this requires autoconf changes
[10:52] <seb128> didrocks, speaking of unity spam, my unity box got some since last week ;-)
[10:53] <didrocks> seb128: yeah, I'm not eager of Monday morning because of that :-)
[10:53] <didrocks> seb128: btw, you restarted with the new version, isn't it?
[10:56] <seb128> didrocks, yes
[10:56] <seb128> why?
[10:57] <didrocks> seb128: just to know if everything's all right on upgrade (gnome-session and unity) :-)
[10:57] <didrocks> I had to remove the detection module on Friday evening, it was segfaulting for some people and finally they got to unity + gnome-panel
[10:59] <seb128> didrocks, in fact it's broken
[11:00] <seb128> well first I didn't dist-upgrade, I'm avoiding the python transition
[11:00] <seb128> so I upgraded unity and its depends
[11:00] <seb128> not gnome-session
[11:00] <seb128> but compiz crashes when I activate unity it seems now :-(
[11:00] <didrocks> seb128: oh ok
[11:00] <didrocks> hum?
[11:00] <seb128> (I had until turned off before you asked)
[11:00] <seb128> Initializing staticswitcher options...done
[11:01] <seb128> ** (process:3106): DEBUG: perf-logger.vala:62: shoop de whoop
[11:01] <seb128> and it seems to exit
[11:01] <didrocks> oh, you have the same issue than david
[11:01] <didrocks> weird, you both have it and with all the week-end spam, no report of an issue with latest unity
[11:01] <seb128> running "unity" works
[11:02] <seb128> hum no
[11:02] <didrocks> hum… it shouldn't :)
[11:02] <seb128> it just starts compiz
[11:02] <seb128> (I had unity turned off again in ccsm)
[11:02] <didrocks> and when starting unity, it stops?
[11:03] <didrocks> oh ok
[11:03] <didrocks> so you changed your unity profile
[11:03] <seb128> it's easier to debug with a wm working :p
[11:03] <didrocks> don't tell me! :-)
[11:03] <seb128> yes, I'm on my GNOME session
[11:03] <seb128> it's the standard compiz
[11:03] <seb128> I didn't touch ccsm out of activating unity
[11:04] <didrocks> ok, should be good then setting-wise
[11:04] <didrocks> not sure about the crash/exit
[11:04] <didrocks> I can just say that there is a similar report for a week
[11:24] <chrisccoulson> pitti - i'm just about to upload a lucid SRU for pidgin (bug 683076), but the patch is absolutely massive. do you want to take a look before i upload?
[11:24] <ubot2> Launchpad bug 683076 in pidgin (Ubuntu) "pidgin can no longer log in to ICQ (affects: 27) (heat: 372)" [Undecided,Confirmed] https://launchpad.net/bugs/683076
[11:26] <pitti> chrisccoulson: massive in size, or in how much code it touches?
[11:26] <pitti> chrisccoulson: weird, I thought the one for maverick was just changing certificates or so (due to the server move)
[11:27] <pitti> chrisccoulson: but if you tested it, please upload; easier to review from teh queue
[11:27] <chrisccoulson> pitti - are you thinking about the recent change for MSN? that was quite a small patch
[11:27] <pitti> chrisccoulson: I remember that
[11:28] <pitti> chrisccoulson: but I thought we also fixed ICQ in maverick-updates
[11:29] <chrisccoulson> pitti - yeah, i see that now. the maverick patch does look smaller, but it's more than changing a certificate
[11:29] <chrisccoulson> i'll take a look at that
[11:30] <seb128> the lucid diff seemed small enough
[11:30] <seb128> out of the guy who did the debdiff included the .orig in it
[11:32] <chrisccoulson> yeah, i just realised that ;)
[11:32] <chrisccoulson> d'oh!
[11:32] <seb128> hehe
[11:32] <chrisccoulson> so it's smaller than it looks ;)
[11:32] <seb128> so it's ok? ;-)
[11:32] <seb128> when you can check the upstream commit
[11:32] <seb128> it seemed mostly ok to me iirc
[12:20] <nessita> hello everyone
[12:27] <seb128> hey nessita
[12:27] <seb128> how are you?
[12:27] <seb128> hey rickspencer3
[12:28] <rickspencer3> hi seb128
[12:28] <nessita> hey seb128! pretty good, thanks. How about you?
[12:29] <seb128> I'm fine thanks
[12:29] <seb128> rickspencer3, how was the qa sprint? are you back on your side of the world?
[12:31] <rickspencer3> seb128, sprint was great, very productive, especially from the SRU testing perspsective
[12:31] <rickspencer3> and I'm in Seattle now, got here yesterday "afternoon", though my body clock is a bit screwy ;)
[12:32] <seb128> ok
[12:32] <seb128> rickspencer3, is there any summary of the sprint or its outcome somewhere?
[12:32] <seb128> or will someone write one?
[12:33] <rickspencer3> seb128, that can be done easily
[12:33] <rickspencer3> victorp kept it very well organized
[12:33] <rickspencer3> so he has index cards for each task started and completed
[12:34] <seb128> nice
[12:34] <seb128> I'm mostly curious to know if there anything we can pick up to improve what we do
[12:34] <seb128> like writing automatic testcases for SRU
[12:37] <rickspencer3> seb128, well, there are 3 kinds of testing that we covered
[12:38] <rickspencer3> 1. SRU certification testing
[12:38] <rickspencer3> so, if we are going to do an SRU, ensure that machines that certified to run Ubuntu in the Canonical cert lab stay that way
[12:38] <rickspencer3> 2. SRU regression testing
[12:38] <rickspencer3> try to make sure that a new kernel does not cause regressions, these are deeper tests, but on fewer machines
[12:39] <rickspencer3> 3. Desktop integration testing
[12:39] <rickspencer3> this is a set of daily tests to ensure that bugs and breakages are caught early
[12:39] <rickspencer3> I think we need more tests for #3
[12:39] <rickspencer3> seb128, was that the kind of thing you were wondering about?
[12:40] <seb128> rickspencer3, if we should encourage sru uploads to come with a test testing the issue being fixed with the update
[12:40] <seb128> so we increase our testing coverages for applications as well and make sure the things we fix have a test
[12:40] <rickspencer3> seb128, is that to verify that the fix works, or to ensure that there are no regressions in that area in the future?
[12:41] <seb128> both
[12:41] <rickspencer3> seb128, that makes a lot of sense
[12:41] <seb128> rather to make sure we test for this bug so it doesn't come back
[12:41] <rickspencer3> seb128, that counts for bugs on desktop apps too, right?
[12:42] <seb128> right, I was rather thinking about applications bugs
[12:42] <seb128> those are easier to test
[12:42] <rickspencer3> ah
[12:42] <rickspencer3> that would be sweet, yes
[12:42] <seb128> if we care enough about a bug to SRU a fix we should be careful it doesn't come back
[12:43] <rickspencer3> true
[12:44] <rickspencer3> seb128, so, I need to write this up ... for testing apps I am seeing there are basically 3 ways to go about it
[12:44] <rickspencer3> 1. unit tests that work through the gtk builder object
[12:44] <rickspencer3> 2. GUI tests that use the accessability layer
[12:44] <rickspencer3> 3. sikuli (sic?) tests that work by taking screenshots
[12:44] <rickspencer3> between the 3, I don't think there is anything that is "untestable"
[12:45] <rickspencer3> #2 has the advantage of being easy to write tests when there are async aspects to the test
[12:45] <rickspencer3> like, it's easy to test if signals and such are working, if threads returns, etc... (well compared to #1)
[12:46] <rickspencer3> so we discussed last week that we may move all of the mago tests to trial and testtools, and create a MagoTest class in testtools
[12:46] <rickspencer3> (to make it easier to write tests with the accessibility layer)

[12:46] <rickspencer3> :)
[12:48] <seb128> rickspencer3, I see, I guess having a small example of each cases on a page and pointing that page from the SRU documentation would be a start
[12:49] <seb128> like "you are encouraged to write a test for the bug you fix, see that page if you need examples"
[12:55] <rickspencer3> seb128, right, we'll get there, and soon, lots of good work going on
[12:56] <seb128> great
[12:57] <rickspencer3> seb128, is it safe for me to dist-upgrade today? is that Python 2.6->2.7 transition settled?
[12:57] <seb128> it should yes
[13:00] <seb128> tell us how it works for you ;-)
[13:00] <rickspencer3> haha
[13:00] <rickspencer3> well, if I disappear and don't come back, you'll have your answer
[13:00]  * rickspencer3 wants new launcher features
[13:08] <nisshh> rickspencer3, i have to get new hardware if i want to run Unity in 11.04 :(
[13:08] <rickspencer3> nisshh, :/
[13:08] <nisshh> and im broke, which doesnt exactly help :)
[13:08] <rickspencer3> nisshh, don't worry, seb128 will ensure that you get a great desktop experience with your current hardware
[13:09] <rickspencer3> you'll still be able to run 11.04, and you'll get all the same apps and capabilities, just a different shell
[13:09] <nisshh> rickspencer3, heh, well, i need to upgrade anyway, this is 8 year old hardware :)
[13:09] <rickspencer3> wow
[13:09] <nisshh> rickspencer3, but i want Unity... *goes and cries in the corner* :)
[13:10] <rickspencer3> hehe
[13:10] <nisshh> rickspencer3, yep, i have been running Ubuntu on a single core with 1GB of RAM :)
[13:11] <nisshh> once i get new hardware im going to run irssi in screen on this machine so im on irc 24/7
[13:12] <seb128> rickspencer3, what launcher features do you want?
[13:12] <nisshh> rickspencer3, is it unusual that compiz works on this machine with 10.04, but it says i cant run desktop effects in 11.04
[13:12] <seb128> I want a way to start the same software several times
[13:12] <seb128> I might be weird but I tend to open several firefox, I don't always use tabs in the running instance :p
[13:12] <nisshh> seb128, *raises hand* i would like to actually be able to run Unity :)
[13:13] <seb128> nisshh, desktop effect has not been updated for the new compiz
[13:13] <rickspencer3> seb128, I want the "start new instance of an app on the current workspace" feature
[13:14] <nisshh> seb128, yeah, i get the "your computer cannot run/use 3d acceleration" or whatever when i try to use Unity in 11.04
[13:14] <rickspencer3> so you can switch desktops, then use the launcher to create new instances instead of activating current instances
[13:14] <nisshh> yet i can run compiz fine on 10.10
[13:15] <seb128> nisshh, what videocard do you use?
[13:16] <seb128> rickspencer3, can we turn that to "let me start several instance of the same applications" so it fixes my issue as well? ;-)
[13:16] <seb128> rickspencer3, can we turn that to "let me start several instance of the same applications" so it fixes my issue as well? ;-)
[13:16] <nisshh> seb128, intel IGP on an 8 year old motherboard *waits for seb128 to wince* :)
[13:16] <seb128> ups
[13:16] <seb128> nisshh, can you use compiz without unity on natty?
[13:17] <rickspencer3> seb128, I think that's what the fix is
[13:17] <seb128> great
[13:17] <nisshh> seb128, no, i get that message when logging into Unity on natty and then i try and log into the classic desktop, but it doesnt like it
[13:17] <didrocks> rickspencer3: it's not, it was a debugging option that will be turned off next release
[13:17] <rickspencer3> by default, it will activate, but you can middle click or select "launch new instance" in the menu
[13:17] <rickspencer3> didrocks, oh?
[13:17] <rickspencer3> alex had it on in the sprint last week
[13:18] <rickspencer3> didrocks, I *neeeeed* this feature
[13:18] <rickspencer3> is it hard to turn on?
[13:19] <nisshh> i *may* be able to get my hands on a dual core with 6GB of RAM early next year though :)
[13:19] <nisshh> but it wont really be worth it
[13:19] <seb128> nisshh, weird, normal compiz should still work
[13:20] <seb128> didrocks, what is a debugging option?
[13:20] <seb128> the "start in a new windows"?
[13:20] <nisshh> seb128, yeah, it was odd, i couldnt log into the classic desktop, i cant remember why it wouldnt let me
[13:20] <nisshh> from memory it just refused to go past the login screen
[13:21] <seb128> that needs debugging I guess
[13:23] <seb128> urg, unity crashed
[13:23] <chrisccoulson> i can't run hamster in unity! :(
[13:24] <seb128> there is a bug about that
[13:24] <chrisccoulson> oh, that would be nice to have :)
[13:24] <chrisccoulson> i use it all the time normally, and today is the first day i'm using unity during my working day
[13:24] <chrisccoulson> i'm going to miss that quite quickly ;)
[13:25] <didrocks> ok, disconnected
[13:26] <didrocks> 14:17:55     didrocks | rickspencer3: I came in the middle of the discussion, but you are talking about the new entry menu, isn't i
[13:26] <seb128> didrocks, we are speaking about being able to run the same software several times
[13:26] <seb128> like middle click on the launcher icon or something
[13:26] <rickspencer3> didrocks, I have a bug logged on it
[13:26] <rickspencer3> the scenario is:
[13:26] <didrocks> seb128: yeah, it's still not decided
[13:26] <rickspencer3> 1. I have a web browser running on desktop 1
[13:26] <rickspencer3> I switch to desktop 2, I want to run another browser window there, but I can't
[13:26] <didrocks> rickspencer3: I know, I commented on it Friday after wrongly closing it with the menu entry
[13:27] <rickspencer3> didrocks, can you paste a link to the bug?
[13:27] <didrocks> (I reopened it IIRC)
[13:27] <seb128> my scenario is easier than that
[13:27] <seb128> "I want to be able to have 2 firefox runnings"
[13:27] <didrocks> rickspencer3: trying to get it, without unity or gnome-panel, it's hard :)
[13:27] <seb128> I don't always use tabs, sometimes it's easier to have 2 of those in the alt-tab cycle
[13:27] <seb128> or 2 on screen with different content
[13:27] <seb128> next to each others
[13:28] <rickspencer3> seb128, for me, it's the multiple desktops scenario
[13:28] <rickspencer3> not desktops, work spaces
[13:28] <seb128> in any cases I think we need to be able to run something several times
[13:28] <nisshh> seb128, this computer is so slow and useless, my net connection will load a page and be waiting for my gpu to render the page its that slow
[13:29] <chrisccoulson> isn't that what "Open New Window" does already, or did I miss something?
[13:29] <seb128> chrisccoulson,
 rickspencer3: it's not, it was a debugging option that will be turned off next release
[13:29] <chrisccoulson> urgh, that sucks :(
[13:29] <seb128> "#6  0x04cfdf00 in FavoriteStoreGSettings::RemoveFavorite(char const*) ()
[13:29] <seb128>    from /usr/lib/compiz/libunityshell.so
[13:29] <seb128> "
[13:29] <seb128> didrocks, ^ known crash?
[13:30] <didrocks> seb128: there is one on that, right
[13:30] <didrocks> retraced and all
[13:30] <seb128> ok great
[13:31] <seb128> it happens every time I try to unpin nautilus
[13:31] <didrocks> the bug report was: https://bugs.launchpad.net/bugs/656517
[13:31] <ubot2> Launchpad bug 656517 in unity (Ubuntu) (and 2 other projects) "launcher should allow to start several instances of an application (affects: 9) (dups: 1) (heat: 56)" [High,Triaged]
[13:59] <bcurtiswx_> seb128, i believe there's a mismatch between the GNOME3 PPA and natty with libgirepository-1.0-1
[13:59] <seb128> bcurtiswx_, it's likely yes
[14:00] <bcurtiswx_> i guess some packages are still looking for the one without the - and the one with the - is trying to replace it
[14:00] <seb128> I will fix that today
[14:00] <seb128> thanks for pointing it
[14:01] <bcurtiswx_> yw, i believe (after some tinkering and guessing) it's what stopping me from getting the newest GTK3 to test my empathy build on
[14:23] <hggdh> hey folks, I got my nm-applet using 1.3 GB of real memory
[14:23] <hggdh> would you like a bug for it?
[14:31] <mdeslaur> didrocks: I've just upgraded to natty, and when I log in to the unity session, I don't get any indicators...any ideas?
[14:32] <didrocks> mdeslaur: the indicators is a seperate issue, there was an ABI transition in it. Are they all installed on your system?
[14:32] <mdeslaur> didrocks: hey work in the classic desktop
[14:32] <didrocks> mdeslaur: are you up to date with each indicator component?
[14:32] <mdeslaur> didrocks: I just did a dist-upgrade now
[14:32] <didrocks> kenvandine: is the transition finished? ^
[14:35] <seb128> didrocks, it should
[14:36] <didrocks> mdeslaur: hum, you mean, you have all your indicators in the classic desktop and not in unity?
[14:36] <didrocks> mdeslaur: the top panel is blank?
[14:36] <mdeslaur> didrocks: yes, the classic desktop has all the indicators. In unity, the top panel is blank, except for the ubuntu menu on the left
[14:37] <didrocks> mdeslaur: it the unity-panel-service running for you?
[14:37] <bcurtiswx_> mdeslaur, when loading unity i have those warnings that say they want to disable things on the top bar.  did you get those and click "don't reload" ?
[14:37] <mdeslaur> didrocks: yes
[14:37] <mdeslaur> bcurtiswx: nope, no warning, nothing
[14:37] <didrocks> mdeslaur: can you try killing it and restart it, please?
[14:38] <mdeslaur> didrocks: sure...nothing happened
[14:38] <mdeslaur> didrocks: here are some logs: http://paste.ubuntu.com/543068/
[14:39] <seb128> mdeslaur, dpkg -l | grep indicat
[14:39] <mdeslaur> seb128: http://paste.ubuntu.com/543070/
[14:39] <seb128> mdeslaur, what architecture do you use?
[14:40] <didrocks> seb128: I'm wondering if unity shouldn't be rebuilt for the transition as well? (the service at least)
[14:41] <mdeslaur> seb128: amd64
[14:41] <seb128> didrocks, unity was built after the transition, remember I retried on friday
[14:41] <didrocks> seb128: oh you're right, it was delayed on Friday
[14:41] <seb128> mdeslaur, if you uninstall indicator-datetime
[14:41] <seb128> does it work?
[14:42] <seb128> kenvandine, indicate-datetime still depwait on geoclue
[14:42] <seb128> can we build without it?
[14:42] <didrocks> ok, indicator-datetime should be guilty then
[14:43] <mdeslaur> nope, doesn't work even with indicate-datetime uninstalled
[14:43] <seb128> what did you try?
[14:43] <seb128> or "how" did you try
[14:43] <mdeslaur> seb128: killing unity-panel-service and restarting it
[14:43] <seb128> can you compiz --replace?
[14:44] <seb128> restarting the service was not enough when I tried earlier
[14:44] <mdeslaur> seb128: ah! success :)
[14:44] <seb128> great
[14:44]  * mdeslaur now has applets :)
[14:44] <seb128> kenvandine, keeeeeeeeeeeenn
[14:44] <seb128> ;-)
[14:44] <mdeslaur> euh, indicators
[14:45] <kenvandine> hehe... i tested that
[14:45] <kenvandine> unity seemed fine without that rebuilt
[14:45] <kenvandine> which is confusing...
[14:45] <highvoltage> mdeslaur: you don't like indicators!?
[14:45] <seb128> kenvandine, still the current source is depwaiting
[14:45] <kenvandine> i know
[14:45] <seb128> can we build without geoclue?
[14:45] <seb128> is that an optional feature?
[14:46] <kenvandine> nope
[14:46] <seb128> :-(*
[14:46] <kenvandine> we would need to re-upload the old version
[14:46] <mdeslaur> highvoltage: of course I do, why wouldn't I like indicators?
[14:46] <kenvandine> but... it shouldn't be breaking anything
[14:46] <seb128> kenvandine, ok, what is blocking promotion?
[14:46] <seb128> did you ping pitti about that on friday?
[14:46] <highvoltage> mdeslaur: I don't want to get into that :)
[14:46] <seb128> kenvandine, http://paste.ubuntu.com/543068/
[14:47] <seb128> kenvandine, that's what mdeslaur had
[14:47] <kenvandine> let me look at the bug again, i think they said they wanted security to look
[14:47] <mdeslaur> highvoltage: I honestly do like indicators.
[14:48] <kenvandine> humm
[14:48] <seb128> kenvandine, can we build geoclue without ofono?
[14:48] <kenvandine> we would lose a package
[14:49] <seb128> one which is useful?
[14:49] <kenvandine> dunno, we would need to check with asac
[14:50] <Sarvatt_> nisshh: save something like this as /etc/X11/xorg.conf    http://paste.ubuntu.com/543076/
[14:50] <kenvandine> i am curious why it is failing for him though
[14:54] <cyphermox> does somebody have time to review and sponsor https://code.edge.launchpad.net/~mathieu-tl/xchat-gnome/update-to-0.26.2+git/+merge/43283 ?
[14:55] <cyphermox> seb128, ^ you had asked about updating xchat-gnome to git ;)
[14:56] <seb128> hey cyphermox
[14:56] <seb128> great, I will review and sponsor it
[14:56] <cyphermox> thanks
[14:56] <kenvandine> didrocks, unity panel is working for you with the updates right?
[14:57] <cyphermox> not sure if you really meant to update it up to git head, but the last commit there seemed useful enough
[14:57] <didrocks> kenvandine: I didn't update to the indicator transition
[14:57] <kenvandine> humm
[14:57] <didrocks> kenvandine: look at #ubuntu-devel, seems kirkland has the same issue
[14:57] <kenvandine> i tested it all on a pristine box with unity
[14:57] <didrocks> kenvandine: and I saw 2 bug reports with people complaining about it
[14:58] <didrocks> I was thinking the transition wasn't finished
[14:58] <kenvandine> ugh
[14:58] <kenvandine> i thought it was
[14:58] <kenvandine> my tested had included the updated indicator-datetime, but i reverted it and it still seems fine
[14:59] <didrocks> did you restart or logout?
[14:59] <kenvandine> restarted
[14:59] <kenvandine> a bunch of times now, and it is fine
[15:00] <kenvandine> humm... actually, it has unity built from my pbuilder, not the archive
[15:01] <pitti> jasoncwarner, seb128: FYI, I created an updated meeting template at https://wiki.ubuntu.com/DesktopTeam/NewMeetingTemplate
[15:01] <ari-tczew> hey folks, I need your help
[15:02] <seb128> pitti, thanks
[15:02] <ari-tczew> look on bug 688926
[15:02] <ubot2> Launchpad bug 688926 in unity-place-files (Ubuntu) (and 1 other project) "Update dependencies on zeitgeist-fts-extension (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/688926
[15:02] <seb128> pitti, kenvandine: ok we need to unblock that geoclue build
[15:02] <ari-tczew> however, I tried to built on natty chroot and it's FTBFS
[15:03] <seb128> the places need to be updates to the new unity
[15:03] <ari-tczew> didrocks: are you familiar with unity packages?
[15:03] <seb128> that's an alpha2 task
[15:03] <seb128> we could probably drop them from now
[15:03] <seb128> or just wait that upstream get them working
[15:03] <seb128> kenvandine, pitti: unity is broken on current natty
[15:04] <ari-tczew> not good, not good :(
[15:04] <kenvandine> seb128, hang on... testing something
[15:04] <seb128> what are the option?
[15:04] <didrocks> ari-tczew: yes
[15:04] <seb128> if we think ofono and geoclue will be fine can we just promote libgeoclue?
[15:04] <didrocks> ari-tczew: the places are for later, right
[15:04] <seb128> to get the new build in, we can sort the mir later
[15:07] <kenvandine> ugh, tested with the unity from the archive and the latest built indicator-datetime in natty and it works fine
[15:08] <kenvandine> seb128, getting it promoted would be good, i am just not sure that is the real problem
[15:08] <kenvandine> i really wish we could test unity in a VM...
[15:09] <seb128> kenvandine, how did you test?
[15:09] <seb128> kenvandine, do you have any error when running the panel service?
[15:09] <kenvandine> not from datetime
[15:09] <kenvandine> just one warning
[15:10] <kenvandine> ** (unity-panel-service:3977): WARNING **: Unable to find the file menu stock item
[15:10] <kenvandine> which happens between loading datetime and libme
[15:12] <kenvandine> the error looks more like it is related to DbusmenuClient
[15:12] <kenvandine> which comes from libdbusmenu-glib
[15:13] <seb128> weird
[15:13] <seb128> dpkg -l | grep indicator
[15:13] <seb128> can you pastbin that?
[15:14] <kenvandine> http://pastebin.ubuntu.com/543084/
[15:18] <seb128> kenvandine, hum, I don't spot anything obvious
[15:18] <kenvandine> yeah, seems sane to me
[15:18] <Sarvatt> seb128, pitti: sorry guys, I never got around to making notify-osd to build on natty, the bug I uploaded it to the PPA for was fixing incorrect rendering with newer pixman but newer pixman still isn't passing the test suite on the natty toolchain unless I it's build with -O1 or lower
[15:19] <kenvandine> i just ran through and re-installed everything specifying natty
[15:19] <kenvandine> to make sure none were locally built
[15:19] <seb128> kenvandine, well in any case we need the indicator rebuilt
[15:19] <kenvandine> and still works
[15:22] <pitti> Sarvatt: ok, so I'll try to fix the build error independently then
[15:35] <kenvandine> seb128, i am re-installing this test box to try to reproduce it
[15:35] <kenvandine> this is weird
[15:36] <seb128> what?
[15:36] <kenvandine> the unity panel problem
[15:37] <kenvandine> i now have no packages locally built and it still works
[15:38] <seb128> you restarted the service and compiz?
[15:38] <kenvandine> and rebooted
[15:38] <kenvandine> and re-installed all the packages
[15:38] <seb128> ok, so dunno
[15:38] <kenvandine> ted had said he didn't think all the indicators would need to be rebuilt, just appmenu-gtk and indicator-appmenu
[15:38] <seb128> do you still have the old libs around?
[15:38] <kenvandine> i don't think so...
[15:39] <didrocks> well, if fixed it as well for kirkland
[15:39] <seb128> did you see the pastebin before?
[15:39] <kenvandine> yeah
[15:39] <seb128> it worked for mdeslaur as well
[15:39] <kenvandine> so after just rebuilding the appmenu related stuff i still had problems getting the unity panel to load
[15:39] <kenvandine> which confused ted
[15:39] <kenvandine> so i rebuilt the indicators and that fixed it, which he though was weird
[15:39] <seb128> kenvandine, it was working in indicator-applet for me
[15:39] <seb128> but not in unity
[15:40] <kenvandine> but then when indicator-datetime was still held up i downgraded that and unity still worked
[15:40] <seb128> like my gnome-panel had all indicators
[15:40] <seb128> but the unity panel was empty
[15:40] <kenvandine> yeah, so unity doesn't seem very robust, if it fails to load any indicator they all fail
[15:41] <kenvandine> i'll file a bug about that, if ted didn't already
[15:41] <kenvandine> we could just upload indicator-datetime 0.1.90.is.really.0.0.6
[15:41] <kenvandine> :)
[15:42] <kenvandine> the quickest fix
[15:46] <seb128> or promote geoclue
[15:46] <kenvandine> yeah
[15:46] <seb128> dbarth, ^
[15:47] <kenvandine> i really wish the geoclue code in indicator-datetime was optional
[15:47] <kenvandine> but it is not... :/
[15:50] <dbarth> kenvandine: what's the issue, a hard dep on the geoclue lib?
[15:51] <kenvandine> kind of
[15:51] <kenvandine> deps for geoclue are still be reviewed by the security team
[15:51] <seb128> dbarth, your issue is that indicator-datetime needs a rebuild with the new libdbusmenu
[15:51] <kenvandine> and indicator-datetime is breaking unity
[15:51] <seb128> but it can't right now because geoclue and ofono needs to be promoted for that
[15:54] <dbarth> does that have anything to do with the new gdbus ports?
[15:54] <kenvandine> no
[15:55] <bcurtiswx_> ugh, evince now segfaults on me
[15:56] <bcurtiswx_> (evince:2223): Gtk-WARNING **: Failed to load type module: (null)
[15:56] <bcurtiswx_> that error repeated along with `menu_proxy_module_load': evince: undefined symbol: menu_proxy_module_load
[15:58] <dbarth> kenvandine: so why did that suddenly break?
[15:58] <dbarth> what should i do / ask for to unblock that situtation?
[15:58] <kenvandine> dbusmenu abi changes
[15:58] <dbarth> but that's for the new gdbus port then, isn't it?
[15:58] <kenvandine> no
[15:59] <dbarth> how come does the old version suddenly break apis?
[15:59] <dbarth> abis?
[15:59] <kenvandine> new version, prior to gdbus port
[15:59] <kenvandine> 0.3.90
[15:59] <dbarth> oh, when there were not enough funcitons left anymore
[15:59] <kenvandine> seems indicator-datetime is keeping unity-panel-service from loading indicators
[15:59] <kenvandine> without a rebuild
[16:01] <seb128> bcurtiswx_, is appmenu-gtk installed?
[16:01] <kenvandine> seb128, so did indicator-datetime work for you in the classic panel?
[16:01] <seb128> I didn't try
[16:01] <dbarth> i removed indicator-datetime here and it doesn't solve the problem
[16:01] <seb128> in fact my issue was that appmenu-gtk was not updated
[16:01] <seb128> dbarth, did you restart the service and compiz?
[16:01] <dbarth> but it was working when i was using gnome-panel earlier today
[16:01] <seb128> dbarth, compiz --replace
[16:02] <dbarth> that said, i've kept most packages from alpha-1
[16:02] <seb128> kenvandine, it just means unity is not robust to buggy indicator
[16:02] <seb128> dbarth, you need to update indicator-*
[16:02] <kenvandine> seb128, i am just wondering if it works in indicator-applet
[16:02] <seb128> dbarth, sudo apt-get remove libdbusmenu-glib
[16:02] <seb128> dbarth, sudo apt-get remove libdbusmenu-glib1
[16:02] <seb128> dbarth, don't do it but it will give you a list ;-)
[16:03] <dbarth> ahah
[16:03] <kenvandine> you should be able to leave  libdbusmenu-glib1
[16:03] <seb128> kenvandine, you can't remove it
[16:03] <dbarth> oops
[16:03] <dbarth> i see
[16:04] <seb128> kenvandine, evolution-indicator and xchat-indicator will need a rebuild
[16:04] <kenvandine> yeah
[16:04] <dbarth> but so again, explain me why an abi change from maverick is breaking packages *now*?
[16:04] <seb128> dbarth, the abi change landed friday
[16:04] <kenvandine> not maverick
[16:04] <kenvandine> thursday :)
[16:05] <dbarth> hmm
[16:05] <seb128> kenvandine, no, it was in NEW thursday :p
[16:05] <kenvandine> well, builds landed
[16:05] <kenvandine> friday
[16:05] <kenvandine> right
[16:05] <bcurtiswx_> seb128, yes
[16:05] <seb128> ;-)
[16:05] <kenvandine> ugh... now i can't do a fresh install
[16:05] <dbarth> hmm, let's switch to #ayatana to see with tedg
[16:05] <seb128> bcurtiswx_, you can unset UBUNTU_MENUPROXY
[16:06] <seb128> it's a workaround though
[16:06] <kenvandine> dbarth, he is gone until jan
[16:07] <bcurtiswx_> seb128, yes, doesn't stop the segfault though :( i think it will all be fixed once apt lets me upgrade to GTK 2.91.6
[16:09] <bcurtiswx_> if I have an app that deps on telepathy-python and that was just renamed to python-telepathy, will it still build or fail due to the name change
[16:09] <seb128> bcurtiswx_, it will likely needs to be rebuilt with a change
[16:10] <bcurtiswx_> seb128, OK thats telepathy-butterfly that i'm talking about.. right now it's synced so should It get that fix and an 0ubuntu1 tag ?
[16:10] <seb128> what issue do you have?
[16:10] <didrocks> pitti: do you have a branch for unity-asset-pool that is derived from ~unity-team/unity-asset-pool/packaging that I can push to ~ubuntu-destop ?
[16:11] <pitti> didrocks: I pushed to lp:ubuntu/unity-asset-pool
[16:11] <pitti> didrocks: I thought we wanted to move to that one?
[16:11] <seb128> pitti, no, as said it's a bit harder than that
[16:11] <seb128> we need james_w
[16:11] <bcurtiswx_> butterfly is at 0.5.14-1 in natty and upstream its 0.5.15 but it depends on telepathy-butterfly (so by what you said, I'll assume it would fail build)
[16:11] <pitti> didrocks: if not, I can apply the changes to the old branch, too
[16:11] <bcurtiswx_> eek
[16:12] <seb128> pitti, we don't want to use the autoimport vcs since they don't derivate from the upstream vcs
[16:12] <bcurtiswx_> telepathy-python **
[16:12] <pitti> seb128: ah, I see; the old problem
[16:12] <seb128> pitti, ie you can't bzr merge a revision
[16:12] <didrocks> pitti: right, it doesn't work with the merge-upstream workflow :)
[16:12] <seb128> pitti, so we want ~unity-team/unity-asset-pool/packaging to become the lp:ubuntu one
[16:12] <seb128> which james_w can do
[16:12] <didrocks> so, I'm pushing everything to ~ubuntu-desktop now
[16:12] <seb128> didrocks, thanks
[16:13] <pitti> didrocks: ok, so want me to apply my commits to that new branch?
[16:13] <didrocks> pitti: if you don't have that, I can reproduce your commits in the old branch, no worry
[16:13] <seb128> bcurtiswx_, doesn't seem that anybody changed the naming there?
[16:13] <didrocks> pitti: no worry, it was just in case you had it, will reproduce that then :)
[16:13] <pitti> didrocks: ok, thanks; I'm sorry for the misunderstanding; otherwise I had used that one right away
[16:13] <seb128> bcurtiswx_, can you ask on #telepathy if anybody plans to update to 0.5.15 in debian
[16:13] <bcurtiswx_> yes, will do
[16:13] <didrocks> pitti: no worry :) thanks a lot :)
[16:13] <pitti> didrocks: http://launchpadlibrarian.net/60583271/unity-asset-pool_0.8.18-0ubuntu1_0.8.18-0ubuntu2.diff.gz ?
[16:14] <pitti> didrocks: (the individual commits weren't that interesting, taking the full diff will do fine)
[16:14] <didrocks> pitti: ok, will do that then. Thanks!
[16:23] <bcurtiswx_> seb128, nvm about that, we do things right.  It's more me not knowing this yet.
[16:28] <bdrung> i have installed date-time idicator in my natty VM, but it isn't shown
[16:28] <bdrung> (using the classic gnome desktop)
[16:29] <pitti> bdrung: I don't know, but my gut feeling is that it hides itself on gnome-panel, as this has its own clock
[16:30] <bdrung> pitti: is there a way to enable it?
[16:30] <pitti> I don't know
[16:30] <seb128> no, it's just that it needs a rebuild
[16:30] <seb128> which is blocked on geoclue
[16:31] <seb128> indicator-applet "handles" that by not showing the indicator
[16:31] <seb128> where unity breaks
[16:33] <bdrung> my second issue is that the indicator-applet isn't shown (only one pixel white vertical line on the panel) after the recent update. only the session indicator-applet is shown.
[16:34] <jcastro> bdrung: that happened to me today too
[16:40] <kenvandine> seb128, didrocks: a fresh install from today's live image works
[16:40] <kenvandine> unity-panel that is
[16:40] <kenvandine> it must be a lib
[16:41] <kenvandine> didrocks, can you give me a dpkg -l
[16:41] <didrocks> kenvandine: hum, I'm not up-to-date here
[16:41] <kenvandine> humm
[16:41] <kenvandine> ok
[16:41] <didrocks> I didn't go through the indicator transition yet
[16:41] <kenvandine> ok
[16:41] <kenvandine> seb128, are you up-to-date now?
[16:42]  * kenvandine checks with kirkland
[16:42] <seb128> kenvandine, well indicators wise yes
[16:42] <seb128> but I've some hundred other updates pending
[16:43] <kenvandine> how about dbusmenu and libindicate?
[16:45] <seb128> kenvandine, http://paste.ubuntu.com/543126/
[16:46] <bcurtiswx_> seb128, telepathy-glib is in experimental
[16:50] <mpt> mvo, here's another report of the "ValueError: unknown locale: en_NG" in USC. <http://openubuntu.com/index.php/topic,269.msg29120.html>
[16:55] <Ng> mpt: it's awful that my locale doesn't exist!
[16:55] <kenvandine> seb128, in comparing the fresh install and kirkland's list, the only thing that differs is really the -dev packages
[16:55] <mpt> Ng, almost as awful as overeager nick highlighting
[16:56] <Ng> mpt: indeed!
[16:57] <mpt> (I'm glad there has been little activity on the MPT-Fusion driver front lately)
[16:58] <mpt> mvo, tremolux: I forgot to mention: Right now I'm sketching out different possibilities for bug 670403, so I'll have something for you and the Unity developers to discuss in the next few days.
[16:58] <ubot2> Launchpad bug 670403 in software-center (Ubuntu) (and 1 other project) "Recently installed applications should be easy to run (affects: 3) (dups: 1) (heat: 22)" [High,In progress] https://launchpad.net/bugs/670403
[16:59] <tremolux> mpt: ah, nice!  thanks
[17:05] <jcastro> kenvandine: I have no issues/agenda items for your meeting today
[17:05] <kenvandine> thx
[17:13] <chrisccoulson> hmmm, this is not nice - http://bazaar.launchpad.net/~chrisccoulson/globalmenu-extension/trunk/revision/15 ;)
[17:18] <didrocks> cyphermox: hey
[17:18] <didrocks> cyphermox: looking at your xchat work. NOCONFIGURE=1 ./autogen.sh;  <- you will need automake and such in the builder chroot in that case
[17:19] <kenvandine> seb128, indicator-datetime uploaded, but it broke for people upgrading but not on a clean install/live session
[17:19] <kenvandine> but i am grabbing some food now... bbl :)
[17:19] <didrocks> cyphermox: you should use autoreconf and dh-autoreconf rather
[17:19] <didrocks> see you kenvandine
[17:19] <seb128> kenvandine, enjoy
[17:20] <seb128> kenvandine, did you figure why it broke?
[17:20] <seb128> cyphermox, emerillon needs to be update to use the new libchamplain
[17:21] <seb128> updated, or patched or something ;-)
[17:21] <seb128> I'm pinging you because apparently you maintain it in debian as well
[17:22] <cyphermox> didrocks, yeah, I just added it, it was missing :)
[17:22] <cyphermox> ah wait, no that was another branch
[17:23] <cyphermox> didrocks, thanks for the hints
[17:23] <cyphermox> seb128, yup
[17:24] <didrocks> cyphermox: you're welcome :)
[17:24] <cyphermox> I'll look at both these when I come back from lunch :)
[17:25] <didrocks> cyphermox: enjoy !
[17:26] <cyphermox> bbl
[17:59] <mpt> Hi and471
[17:59] <and471> hey mpt
[18:01] <and471> mpt, sorry my connection went, flaky wifi...
[18:01] <bcurtiswx> <-- mpt has quit (Quit: Ex-Chat)  and471 has quit (Quit: Ex-Chat)
[18:02] <and471> haha
[18:02] <and471> guess we are on the same crappy wavelength :D
[18:17] <and471> bcurtiswx, I guess mpt gave up on me :)
[18:20] <bcurtiswx> and471, haha
[18:20] <bcurtiswx> maybe more serious connection issues :P
[19:35] <highvoltage> hi, has anyone from the desktop team had time to look at bug 683833?
[19:35] <ubot2> Launchpad bug 683833 in ubuntu-meta (Ubuntu) "Unity should be in recommends, not depends for ubuntu-desktop (affects: 1) (heat: 469)" [Medium,Confirmed] https://launchpad.net/bugs/683833
[21:16] <bcurtiswx> hmm, no unity
[21:17] <bcurtiswx> i workarounded a unset ubuntu_menuproxy  could that be the reason unity isn't showing any more?
[21:32] <bcurtiswx> kenvandine, is unity-panel-service a program? i dont see it at all
[21:32] <kenvandine>  in /usr/lib/unity/
[21:33] <kenvandine> it is a service
[21:33] <bcurtiswx> its not working on my comp :-\.  what should I do to debug ?
[21:37] <bcurtiswx> kenvandine, (unity-panel-service:2026): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_get_id: assertion `DBUSMENU_IS_MENUITEM(mi)' failed
[21:39] <kenvandine> what's not working?
[21:40] <bcurtiswx> any part of unity
[21:40] <kenvandine> killall unity-panel-service; /usr/lib/unity/unity-panel-service&
[21:40] <kenvandine> see what it spits out on the console
[21:42] <bcurtiswx> kenvandine, http://paste.ubuntu.com/543300/
[21:44] <kenvandine> bcurtiswx, and are you seeing a panel at all?
[21:44] <kenvandine> just empty?
[21:44] <bcurtiswx> nothing
[21:44] <kenvandine> so no panel at all?
[21:44] <bcurtiswx> none
[21:45] <kenvandine> but unity is running? you see the launcher?
[21:45] <bcurtiswx> no launcher
[21:45] <kenvandine> ah... so unity is probably not running
[21:45] <kenvandine> is compiz running?
[21:45] <bcurtiswx> yes
[21:45] <kenvandine> hey rickspencer3!
[21:45] <rickspencer3> hey kenvandine
[21:45] <rickspencer3> how is life?
[21:45] <kenvandine> bcurtiswx, do you have window decorations?
[21:46] <kenvandine> rickspencer3: can't complain, and you?
[21:46] <bcurtiswx> kenvandine, yes
[21:46] <rickspencer3> kenvandine, pretty jet laggy, but going well
[21:46] <kenvandine> rickspencer3: hehe :)
[21:46] <rickspencer3> I'm taking today off and working on the developers' manual
[21:46] <kenvandine> woot
[21:46] <rickspencer3> I've knocked off 3 chapter drafts already
[21:46] <kenvandine> bcurtiswx, and your sure the unity plugin is loaded?
[21:47] <bcurtiswx> kenvandine, how could I verify?
[21:47] <kenvandine> look in ccsm i guess
[21:47] <kenvandine> or in .xsession-errors maybe
[21:48] <bcurtiswx> kenvandine, ah. got it.. i know what happened
[21:49] <bcurtiswx> i had disabled the plugin, found out unity was running still on reboots so i kept it off
[21:49] <kenvandine> :)
[21:49] <bcurtiswx> todays updates must have noticed the plugin was off and acted correctly
[21:49] <bcurtiswx> so does this mean i hate when things run the way they're supposed to?
[21:50] <kenvandine> :)
[21:50] <kenvandine> bcurtiswx, so did enabling that fix it?
[22:04] <bcurtiswx> robert_ancell, hey :) got a min?
[22:05] <robert_ancell> bcurtiswx, sure
[22:06] <bcurtiswx> I noticed you opened a bug for empathy 2.91.3, idk what you've gotten done (maybe as much as I) but I had been working on https://code.launchpad.net/~bcurtiswx/ubuntu/natty/empathy/empathy-2.91.3 for a bit..
[22:07] <bcurtiswx> robert_ancell, ^^
[22:10] <robert_ancell> bcurtiswx, oh, np.  I'll leave it for you
[22:11] <robert_ancell> bcurtiswx, I'm looking here (http://people.canonical.com/~platform/desktop/versions.html) to see what still needs updating - if you're working on something open a bug report and add the tag "desktop-upgrade" and it will show up on this page
[22:12] <bcurtiswx> robert_ancell, ah, OK.  I will assign myself to that bug report.  Thanks for starting it.  Sorry for not following that
[22:14] <robert_ancell> bcurtiswx, it's not well documented :( Thanks though!
[23:11] <chrisccoulson> hmmm, no tedg today? i could do with him taking a look at https://code.launchpad.net/~chrisccoulson/dbusmenu/ffox-fixes :)
[23:26] <bcurtiswx> chrisccoulson, i was told hes out this week
[23:26]  * micahg thought he was off until the EOY
[23:26] <chrisccoulson> bcurtiswx, that's a shame, i wanted to get the ffox global menu stuff in before christmas ;)
[23:27] <bcurtiswx> could be EOY too
[23:29] <chrisccoulson> yeah, it is EOY
[23:29] <chrisccoulson> which is probably what i should be doing ;)


[07:09] <mborzecki> morning
[08:07] <pstolowski> morning
[08:07] <mvo> good morning pstolowski
[09:04] <mborzecki> heya
[11:10] <mup> PR snapd#11202 opened: Test initrd systemd configuration refactoring <Created by valentindavid> <https://github.com/snapcore/snapd/pull/11202>
[11:27] <mborzecki> mardy: hi, can you take a look at https://github.com/snapcore/snapd/pull/11176?
[11:27] <mup> PR #11176: tests/core/failover: verify failover handling with the kernel snap <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/11176>
[11:30] <mup> PR snapd#11198 closed: github: add spellcheck workflow <⛔ Blocked> <Skip spread> <Created by bboozzoo> <Closed by bboozzoo> <https://github.com/snapcore/snapd/pull/11198>
[15:46] <mup> PR snapd#11203 opened: tests/nested/manual/core20-to-core22: wait for device to be initialized before starting a remodel <Run nested> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/11203>
[16:21] <mup> PR snapd#11197 closed: build-aux/snap/snapcraft.yaml: use build-packages, don't fail dirty builds <Created by anonymouse64> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/11197>
[16:46] <mup> PR snapd#11204 opened: tests/lib/tools/tests.invariant: simplify check <Simple 😃> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/11204>
[17:16] <mup> PR snapd#11205 opened: o/devicestate: pick system from seed systems/ for preseeding <Preseeding 🍞> <Created by stolowski> <https://github.com/snapcore/snapd/pull/11205>
[19:57] <mup> PR snapcraft#3608 opened: many: rename snapcraft package to snapcraft_legacy <Created by cmatsuoka> <https://github.com/snapcore/snapcraft/pull/3608>


[07:55] <Hoober> sweet
[07:55] <Hoober> hi guys
[07:55] <Hoober> and girls
[07:56] <Hoober> well
[07:57] <Hoober> !help
[07:57] <ubot4> Please don't ask to ask a question, simply ask the question (all on ONE line and in the channel, so that others can read and follow it easily). If anyone knows the answer they will most likely reply. :-)
[07:57] <Hoober> !all
[07:57] <ubot4> Factoid 'all' not found
[07:57] <Hoober> !announce
[07:57] <ubot4> Factoid 'announce' not found
[07:57] <Hoober> !channel
[07:57] <ubot4> Factoid 'channel' not found
[07:57] <Hoober> !say
[07:57] <ubot4> Factoid 'say' not found
[07:57] <Hoober> !hoober ? ubot4
[07:57] <ubot4> Factoid 'hoober ? ubot4' not found


[18:16] <thumper> https://wiki.ubuntu.com/WorkItemsHowto
[19:25] <sidnei> rogpeppe2: https://bugs.launchpad.net/juju-core/+bug/1177937
[19:25] <_mup_> Bug #1177937: juju deploy --config with invalid yaml goes ahead and deploys the service anyway <juju-core:New> <https://launchpad.net/bugs/1177937>
[19:28] <kapil_> to the ghost of mgz..
[19:28] <kapil_> http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-types.html
[19:32] <sidnei> kapil_: https://bugs.launchpad.net/juju-core/+bug/1177937
[19:32] <_mup_> Bug #1177937: juju deploy --config with invalid yaml goes ahead and deploys the service anyway <juju-core:New> <https://launchpad.net/bugs/1177937>
[20:51] <danilos> dimitern, hi, I am missing a second LGTM for https://codereview.appspot.com/9011043/: care to take a look? :)
[20:51] <dimitern> danilos: sure, looking
[20:51] <danilos> dimitern, don't say "no", I'll throw something at you :)
[20:51] <danilos> dimitern, thanks
[21:05] <dimitern> danilos: you got it
[21:05] <danilos> dimitern, cheers
[22:52] <sidnei> https://bugs.launchpad.net/juju-core/+bug/1172895
[22:52] <_mup_> Bug #1172895: relation-list incompatibility with pyjuju: -r <juju-core:Fix Committed by fwereade> <https://launchpad.net/bugs/1172895>


[04:50] <Kilos> morning everyone
[19:07] <missk_> hello
[19:08] <missk_> i have a shell issue
[19:08] <missk_> i want to register a channel here
[19:08] <missk_> to start my free shell projedct
[19:08] <missk_> its only for jakarta peoples
[19:09] <missk_> but this channel is belongs to freenode staff
[19:09] <missk_> what can i do to registered this channel


[14:55] <TheLordOfTime> anyone know why the extras repository is offering a newer version of lintian than what's in raring?
[14:59] <jtaylor> some arb reason
[14:59] <jtaylor> according to what extras is supposed to be it should have not happened
[15:00] <TheLordOfTime> so someone screwed up?
[15:00] <TheLordOfTime> and that should've hit raring?
[15:00] <TheLordOfTime> s/raring/raring main/
[17:41] <ScottK> It's been removed and we're following up with the ARB.
[17:42] <TheLordOfTime> indeed.


[00:37] <akgraner> doctormo, ping - when you get a few minutes can you talk to me about creating logo's
[00:56] <doctormo> akgraner: Sure, what would you like to know?
[01:13] <akgraner> doctormo, if you will make one for me :-)
[01:14] <akgraner> or know someone who would like to
[01:14] <doctormo> akgraner: This would be for the Community Days?
[01:14] <akgraner> nope - News Team
[01:14] <akgraner> I need an updated newspaper
[01:15] <akgraner> and a fridge and an overall news team logo
[01:16] <akgraner> I am willing to learn to make them - but not sure it would be completed anytime soon
[01:17] <akgraner> and since you know all the art people I thought even if you couldn't do it yourself you could point me in the right direction
[01:17] <akgraner> or to the right person
[01:18] <akgraner> no hurry but thought since everything was getting updated might as well go for broke and look into logos as well
[01:25] <doctormo> akgraner: Perhaps we could post a message to the deviantArt group, newspapers shouldn't be too hard but I take it your sick of the tango newspaper icon?
[01:26] <akgraner> doctormo, not sick of it... was just hoping could get an updated one :-)
[01:27] <akgraner> that looks "lighter"  and cleaner
[01:28] <akgraner> I like the other one but one with the new ubuntu logo or something would be really awesome
[01:29] <doctormo> akgraner: Do you have a link tot he current one?
[01:29] <akgraner> and a fridge with those bubble things as magnets on the Fridge door or something would be cool
[01:29] <akgraner> doctormo, yep one sec and I'll get you the newspaper one
[01:30] <akgraner> doctormo, http://frylock.redvoodoo.org/~akgraner/newspaper-icon3.jpg
[01:30] <akgraner> I don't have a link to the Fridge icon
[02:29] <doctormo> Thanks akgraner, I'll think about the best people to get on it, there are a couple of other good icon people too I might know.
[02:30] <akgraner> doctormo, thank you so much!
[03:27] <jcastro> jono: do you still have that ultrathin system 76?
[03:27]  * jcastro is considering buying one
[03:30] <jono> jcastro, yep
[03:30] <jono> it is sweet
[03:31] <jono> keyboard is a little plasticy, but in general I like it
[03:31] <jcastro> how's the battery life?
[03:34] <jono> not bad
[03:34] <jono> but great
[03:34] <jono> right have to run
[03:34] <jono> biab
[04:28] <nigelbabu> JFo: I heard that there were a lot of funny stuff at SELF :)
[05:31] <nigelbabu> jono: hey!
[05:33] <jono> heya nigelbabu :)
[05:37] <nigelbabu> jono: when you get time to blog, can you add cleansweep to that list? some time this week perhaps?
[07:56] <dpm> good morning everyone!
[07:57] <jussi> morning dpm
[07:57] <dpm> hey jussi
[07:58] <dholbach> good morning
[07:59] <dpm> hey dholbach, morning!
[07:59] <dholbach> hey dpm
[08:15] <nigelbabu> morning jussi, dpm, dholbach :)
[08:15] <dpm> hey hey nigelbabu :)
[08:15] <dholbach> heya nigelbabu
[09:34] <czajkowski> aloha
[09:37] <dholbach> hi czajkowski
[09:37] <czajkowski> dholbach: ello how's things?
[09:38] <dholbach> good good - how 'bout you?
[09:40] <czajkowski> grand sitting in back garden reading
[09:40] <czajkowski> Summer is back
[09:41] <dpm> morning czajkowski :)
[09:41] <czajkowski> dpm: howdy
[09:43] <dpm> morning popey, did you have a chance to look into the e-mail about screencasts I sent you? I'm about to start recording one, so I may start assaulting you with questions soon :)
[10:16] <doctormo> Morning
[10:32] <nigelbabu> doctormo: morning!
[10:49] <popey> ah yes dpm !
[10:49]  * popey goes to find it
[10:51] <popey> dpm: its probably easier to have a skype/mumble chat at some point to be honest
[10:54] <dpm> popey, sure. Would you have time some time this week?
[10:54] <popey> yes
[10:58] <dpm> popey, cool, you can just send me an e-mail or PM with what time suits you best and we can have a chat. I'm generally away on Tue and Thu evenings, but apart from that, other times should be fine. For now I've got a question already, though. Do you know any good app for subtitles? I've heard of gnome-subtitles, but I've never actually used it
[11:00] <popey> yup, thats the one we have used
[11:01] <popey> works quite well, generates srt files which can be used on youtube and in totem
[11:01] <dpm> ah, cool
[11:01] <dpm> thanks
[11:01] <popey> https://wiki.ubuntu.com/ScreenCasts/Subtitles seen that?
[11:02] <popey> ah, no, not that one, subtitle-editor is the one people used iirc
[11:02] <dpm> ah, I missed that one. I had only read https://wiki.ubuntu.com/ScreenCasts
[11:02] <popey> https://wiki.ubuntu.com/ScreenCasts/Subtitles/SubtitleEditor
[11:02] <dpm> ah, right
[11:02] <popey> how to links at the bottom of that page
[11:02] <dpm> reading now
[11:05] <dpm> I must say the documentation of the screencasting team is brilliant, good work!
[11:06] <popey> really!?
[11:06] <popey> needs updating :)
[11:06] <popey> I stepped down from the screencast team, give someone else a chance :)
[11:06] <popey> I'm doing some screencasts for my mum at the moment, very short ones
[11:14] <dpm> I found it very good. All the info I found there has been very useful. Yeah, some parts might need updating, but that's the nature of our fast environment :)
[11:16] <popey> you're too kind :)
[11:21] <dpm> no, really, just being honest! :) Anyway, my virtual machine is up and running, let me give this a go.
[11:21] <popey> dpm: which software are you using to record?
[11:22] <dpm> I'm going to use gtkrecordmydesktop
[11:22] <popey> dpm: http://popey.com/blog/2009/08/25/getting-back-into-screencasting/ might be useful, especially the command line options for recordmydesktop
[11:22] <popey> cool
[11:23] <dpm> popey, ah, thanks
[11:49] <dholbach> popey, pleia2: cc meeting?
[11:49] <dholbach> (in 11m)
[11:51] <popey> ok
[11:52]  * dholbach hugs popey
[11:52]  * popey hugs dholbach
[11:53] <dholbach> :-)
[12:03] <duanedesign> popey: i did update the screencast how-to
[12:04] <popey> ah, excellent :)
[12:05] <duanedesign> ah, i see that would be /ScreencastTeam/RecordingScreencasts
[12:05] <duanedesign> i am now looking at /ScreenCasts
[12:06] <duanedesign> popey: I need to start developing a plan to build some 'buzz' around the team
[14:29] <dpm> popey, I've recorded a 1024x768, 8 min., no audio screencast (~54 MB) with gtk-recordmydesktop, then I've simply added a header to it with Pitivi and then I thought I'd render it (720x480, 29 fps, theora). Is it normal that it's going to take like 10 hours to do that, or has something gone horribly wrong?
[14:35] <popey> dpm: heh, welcome to video encoding :)
[14:36] <popey> dpm: it would be faster if you rendered out at 1024x768, as soon as you scale down (or indeed up) you're gonna chew up CPU cycles
[14:38] <dpm> popey, yeah, I'm doing that now, looks a lot better, but what surprised me is that the CPU load wasn't going up. It says 25 minutes now, let's see if it stays that way :)
[14:40] <popey> if the cpu load stays idle then chances are something is wrong
[14:40] <popey> video encoding will usually murder the system
[14:40] <popey> you're not doing this on a netbook are you? :D
[14:40] <dpm> no, and also not on a 286 or something like that :)
[14:41] <dpm> anyway, it looks good now, it's loading the CPU as there's no tomorrow, but the remaining time stays in the minutes range, which is good
[14:46] <popey> cool
[15:04] <dholbach> akgraner: heya - how are you doing?
[15:11] <dpm> popey, my first ever screencast has been rendered \o/. It's pretty much proof-of-concept, though. I'm going to play with subtitles now.
[15:12] <popey> yay!
[15:12] <dpm> :)
[15:12] <popey> dpm: what video format did you render out as in pitivi?
[15:12] <popey> ogv?
[15:12] <dpm> yeah, I just took the default
[15:12] <popey> cool
[15:15] <dpm> I think I read somewhere on the screencasts docs that mpeg was recommended instead as the master format. Is that still the case?
[15:15] <popey> not really, it was when we didnt have a video editor that understood ogv but now we do
[15:16] <dpm> ah, cool.
[15:18] <popey> dpm: what did you add to the front in pitivi? a title page?
[15:18] <dpm> yeah
[15:18] <popey> I've not done that in pitivi before
[15:18] <dpm> I created a 5 sec presentation with Impress with the title and recorded it
[15:19] <popey> hah, was about to say.. i used openoffice to do it :)
[15:19] <dpm> I read all your tricks on the docs! :)
[15:21] <popey> hah
[15:21] <dpm> One thing I haven't managed to get right is the recording area in gtk-recordmydesktop. I use a VM, and even selecting only the window, it shows a few pixels around, apart from the fact that the "do not capture the window decorations" option does not work for me. I think I'll have to resort to recording my real desktop
[15:22] <dpm> or swap to a hard drive with a pristine installation
[15:22] <popey> ah, no, you can do that if you use rmd on the command line
[15:22] <popey> you specify the x and y and width and height
[15:22] <popey> and move your window to that location
[15:22] <popey> its clunky but meh
[15:23] <popey> see that blog post earlier, i do it in there
[15:24] <dpm> ah yeah, I see the parameters now. What do you use to see the x, y location where you need to move the window to?.
[15:27] <popey> i do it the other way, set the x/y and width/height  and then move the window into that box
[15:28] <popey> so if you have the vm set to 1024x768, I would use...
[15:28] <dpm> oh, I see, once you've set it you see the square on the screen
[15:28] <popey> yes
[15:28] <popey> once
[15:28]  * dpm tries
[15:28] <popey> then once it's in the right place, kill rmd and run it again with --no-frame
[15:28] <popey> so you dont get the box on the screen
[15:29] <popey> because the box actually makes rmd less stable
[15:29] <dpm> cool, I'll try that, thanks
[15:29] <popey> np
[15:48] <dholbach> hola jono
[15:49] <jono> hey dholbach
[15:51] <nigelbabu> morning jono
[15:51] <nigelbabu> jono: feeling better?
[15:52] <jono> hey nigelbabu
[15:52] <jono> I am now
[15:52] <jono> finally :)
[15:53] <jono> dpm, call in 8?
[15:53] <dpm> hey jono, morning! yes, I'll be all set in 8
[15:53] <jono> dpm, perfect :)
[15:57] <dholbach> akgraner: just started UDW planning (you're CCed :-))
[15:58] <akgraner> dholbach, awesome - was going to ping you tomorrow about that
[15:58] <akgraner> you are always a step ahead of me :-)
[15:58] <dholbach> not really :)
[15:58] <akgraner> I am finally recovering from the weekend
[15:58] <akgraner> sigh
[15:59] <jono> greg-g, thanks so much for the blog
[15:59] <jono> greg-g, I just tweeted it :)
[15:59] <akgraner> I'll plug dates in my spreadsheet and get a calendar ready task list ready and start checking things off :-)
[15:59] <dpm> hey akgraner, how are you feeling?
[16:00] <akgraner> tired.. :-(  but I am resting so some things are taking a bit longer to complete, but all is well - Everyday above ground is a good day! :-)
[16:00] <dpm> :-)
[16:01] <jono> dpm, alright, logging in
[16:01] <dpm> okie dokie
[16:02] <jcastro> dholbach: I got one too!
[16:02]  * dholbach hugs jcastro
[16:02] <dpm> jono, I can hear you, but it seems there is a delay
[16:03] <jono> dpm, odd
[16:03] <jono> dpm, lets do skype
[16:03] <dpm> jono, yeah
[16:50] <cjohnston> mornin
[16:59] <dholbach> alright my friends - I call it a day
[16:59] <dholbach> see you tomorrow!
[17:40] <akgraner> here is a little something to brighten you all's day :-)  http://frylock.redvoodoo.org/~akgraner/P1000429.JPG
[17:42] <akgraner> oh and here is the one where she talks about me replacing her with jono
[17:42] <akgraner> http://frylock.redvoodoo.org/~akgraner/Becca%20at%20SELF/P1000439.JPG
[17:52] <popey> hehe
[17:56] <cjohnston> she looks so enthused
[18:01] <jcastro> oh god. LOL
[18:01] <jcastro> RT @homeworkprod: I heard relocating window buttons to the left side in #Ubuntu is to make room for a big #Vuvuzuela button on the right.
[18:08] <cjohnston> jcastro: time for a quick call?
[18:10] <jcastro> cjohnston: in about 5 to 10?
[18:10] <jcastro> cjohnston: waiting for the one part of the desktop team meeting I need to finish.
[18:10] <cjohnston> sure
[18:11] <cjohnston> PM can work also
[18:49] <czajkowski> feckin' priceless http://twitter.com/keybuk/status/16241144361
[19:03] <cjohnston> nice
[20:16] <jcastro> jono: can you send a mail to debian@ubuntu to see if I get it?
[20:16] <jcastro> jono: sorry I should have made it clear I was testing that for me, not you, heh
[20:17] <jono> done jcastro
[20:17] <jcastro> yeah! rock and roll, I am in business!
[20:18] <jcastro> jono: lucas is busy this week, so we've decided to tag team the debian list o items next week together
[20:18] <jcastro> but I managed to get one WI done today, I have 3 outstanding that should be closeable tomorrow
[20:19] <jono> cool :)
[20:19] <jono> thanks jcastro
[20:37] <doctormo> nigelb: hello?
[20:38] <cjohnston> hey doctormo
[20:49] <jcastro> jono: we have a call in ~12?
[20:49] <jcastro> jono: I don't have any agenda items
[21:05] <jono> jcastro, lets skip
[21:06] <jcastro> no complaints here!
[21:23] <jcastro> jono: there was one semi-urgent matter
[21:23] <jcastro> jono: I didn't know they were doing this: http://www.fathomevents.com/concertsandmusic/series/the_big_four.aspx
[21:23] <jcastro> that's next week
[21:24] <jcastro> I am having people scrambling to find tickets now, just an FYI
[21:24] <jono> wow
[21:24] <jcastro> I know! Live!
[21:24] <jcastro> We need burndown charts for this.
[21:24] <jono> is that just that one date?
[21:24] <jono> oh hang on
[21:24] <jono> thats a movie?
[21:25] <jono> a live show
[21:25] <jcastro> it's beamed live to theaters during the event
[21:25] <jono> sweet~
[21:25] <jcastro> which is in .eu somewhere
[21:51] <jono> jussi, ping?
[21:52] <jono> jussi, could you take a look at completing your action on https://blueprints.launchpad.net/ubuntu/+spec/community-m-process-improvements - thanks!
[21:53] <jono> jcastro, is sense's item on https://blueprints.launchpad.net/ubuntu/+spec/community-m-upstream-contacts still TODO?
[21:54] <jcastro> jono: I think it's DONE, but iirc the work item was to review the current roles and made sure they still made sense
[21:54] <jcastro> I can follow up with him on it
[21:55] <jono> jcastro,  if you could, thanks
[21:56] <jussi> jono: are the page links finalised now?
[21:57] <jono> jussi, many of them are already there
[21:57] <jono> I think we just need to start adding them
[21:57] <jono> see wiki.ubuntu.com/BuildingCommunity
[21:58] <jussi> jono: I dont mind doing it, just Id rather wait till the links are finalised so I dont need to go changing them all again.
[21:58] <jono> jussi, they will never change
[21:58] <jono> just added to
[21:58] <jcastro> jono: also, if you're looking for an easy WI, you can probably handle the one about mailing Trent Reznor. :p
[21:58] <jono> jcastro, lol
[21:58] <jussi> jono: right, no probs!
[21:58] <jono> will do
[21:58] <jono> jussi, thanks!
[22:05] <jussi> jono: are you still planning to run this? https://wiki.ubuntu.com/BuildingCommunity/CommunityQuestionTime
[22:05] <jussi> its very old :D
[22:06] <JFo> we're changing the name of that to "Fireside chats with Jono"
[22:06] <JFo> j/k
[22:06] <jono> jussi, I do that on Wednesday's but as a video chat
[22:06] <jono> will update it
[22:06] <jussi> :)
[22:07] <jussi> jono: Im thinking there will be problably 1-3 factoids to begin with, for the most frequent peices of knowledge needed. adding more is easy, if more are needed. Problem is, often the bot gets factoids added that could be useful, but they rarely/never get used, so they get culled.
[22:08] <jono> jussi, np
[22:28] <jcastro> JFo: http://www.murraytwins.com/blog/?p=72
[22:28] <jcastro> JFo: next time you're trudging through your lists can you see if this list now reflects what you expected it to?
[22:28] <jono> jcastro, can you do me a favor - set me up a redirect on https://wiki.ubuntu.com/UbuntuOpportunisticDeveloperWeek to go to https://wiki.ubuntu.com/UbuntuAppDeveloperWeek
[22:28] <jono> I always forget how to do those
[22:29] <jcastro> yep
[22:29] <jono> thanks
[22:29]  * JFo looks
[22:29] <JFo> jcastro, will do :)
[22:30] <jcastro> jono: done
[22:30] <jcastro> #REDIRECT UbuntuAppDeveloperWeek
[22:30] <jcastro> ^^ FYI
[22:32] <jono> jcastro, thanks
[22:35] <jono> jcastro, so on https://blueprints.edge.launchpad.net/ubuntu/+spec/community-m-patch-review-initiative I have "[jonobacon] speak with J. Castro re. upstream work and patch review: TODO"
[22:35] <jono> this was regarding how we best handle patches that should go upstream
[22:35] <jcastro> ok
[22:36] <jcastro> jono: don't we talk about that all the time?
[22:36] <jono> yeah, I think the action was about how specifically build awareness into Project Cleansweep
[22:36] <jono> tbh, I think it is better if you have the conversation with nigelbabu about this
[22:36] <jcastro> sore
[22:36] <jcastro> er, sure
[22:37] <jcastro> jono: why not DONE that one and add one for me?
[22:37] <jcastro> or just rename it to be mine
[22:39] <jono> jcastro, I will give it to you
[22:45] <akgraner> jono, just replied to your email - there is an attachment as well :-)
[22:50] <jono> thanks akgraner
[22:50] <akgraner> you'll have more early next week :-)
[22:53] <doctormo> jono: Did you know there are a couple of ubuntu stickers on the new IT Crowd series set?
[22:56] <jono> doctormo, really? cool!
[22:57] <doctormo> They're on the monitor and there is one in the background, really cool as there is also an EFF sticker and a The Register Vultcher... it's a tricked out geek pad now.


[06:28] <blkperl> slangasek: http://pastebin.com/7j10TkAx
[06:28] <blkperl> slangasek: this is after a apt-get build-deb collectd
[06:29] <blkperl> why doesn't build-deb get it?
[06:32] <slangasek> blkperl: apt-get build-dep looks at the package indices to figure out which build-dependencies to install, not the current package; so any time you change the build-dependencies, apt-get build-dep won't do what you want
[06:32] <slangasek> blkperl: you probably want 'sudo mk-build-deps -i -r' instead
[06:32] <blkperl> hrm
[06:32] <blkperl> k
[06:32] <blkperl> slangasek: anyways its builds fine on raring for me
[06:32] <blkperl> slangasek: https://code.launchpad.net/~blkperl/ubuntu/raring/collectd/merge-from-debian/+merge/140116
[06:32] <blkperl> what do?
[06:34] <slangasek> let me see if I can reproduce the build failure
[06:38] <blkperl> thanks!
[06:50] <slangasek> blkperl: package built for me in raring just fine, too
[06:51] <slangasek> blkperl: and jdstrand didn't say what the configure failure had been, so I guess it was transient
[06:53] <blkperl> slangasek: ummm ok....
[06:54] <blkperl> slangasek: it would be cool if a bzr push, automatically triggered a build in jenkins or something and then updated launchpad
[06:55] <slangasek> that would require an awful lot of jenkins :)
[06:56] <blkperl> slangasek: openstack seems pretty good at it :P
[06:56] <blkperl> there gerrit -> jenkins -> launchpad intergration is pretty impressive
[07:29] <slangasek> blkperl: merged and uploaded
[07:30] <blkperl> slangasek: woot!
[07:30] <blkperl> slangasek: thanks!
[07:30] <blkperl> slangasek++
[07:31] <blkperl> slangasek: now I have to figure out what to work on next
[07:31] <blkperl> slangasek: can I merge puppet 3.x into rariing?
[07:33]  * blkperl will have to come up with a list of things
[07:56] <blkperl> or bkerensa beat me to it
[07:57] <blkperl> bkerensa: looks like your branch isn't proposed for merging
[23:04] <bkerensa> <slangasek> [22:00:55] bkerensa: I suppose it would make sense for me to cook something like that up and make it permanently available, wouldn't it
[23:04] <bkerensa> slangasek: sure
[23:05] <bkerensa> blkperl: yeah I figured I would just merge puppet into a personal branch and not propose it
[23:05] <bkerensa> ;)


[07:23] <felix_> please help me!
[07:24] <felix_> tried to install java from repository
[07:24] <felix_> cant accept the License Agreement
[07:24] <felix_> can anyone help
[07:25] <felix_> used ubutuguide.org/wiki/Ubuntu_Edgy/
[07:33] <tashiro> felix_: Why don't you use java-package
[07:36] <felix_> just followed the advisory on this page
[07:36] <felix_> some package broke during installation
[07:37] <felix_> and i dont know how to repair
[07:38] <felix_> apt-get want to install sun-java5-jre and -bin
[07:38] <tashiro> Just use java-package
[07:39] <tashiro> It's the easiest way IMHO
[07:39] <felix_> but how could i tell apt-get to remove the broken packages
[07:40] <tashiro> use dpkg
[07:40] <felix_> can you give me the parameter
[07:40] <tashiro> dpkg -r <package name>
[07:41] <tashiro> And additional parameter depending on your problem
[07:41] <felix_> thank you
[11:03] <doko> tashiro: java-package is the wrong way. really. please do not recommend it.
[11:15] <ramses_> hi, I have a little question about java, I hope I'll get an answer here


[12:18] <cjwatson> wgrant: Is there a reason to kill the UPLOADING status from the TTBB case in https://code.launchpad.net/~wgrant/launchpad/buildd-manager-handoff/+merge/250246 ?  The tarball processing is potentially slow, so it's worth having an indication of what's going on, and I can't see how archiveuploader could end up processing something from a TTBJ.
[12:20] <wgrant> cjwatson: I guess I could restore that. But it'd better not often be too slow, since it blocks all of buildd-manager...
[12:21] <cjwatson> Indeed.