[06:57] <pitti> Good morning
[07:03] <didrocks> good morning pitti
[07:43] <TheMuso> Hey pitti.
[08:47] <seb128> hello there
[08:49] <chrisccoulson> hello everyone
[08:50] <pitti> hey chrisccoulson, good morning seb128
[08:50] <seb128> hey chrisccoulson pitti
[08:51] <seb128> how are you?
[08:51] <pitti> chrisccoulson: btw, are you still looking for things to fix? bug 389322 is making a lot of people unhappy
[08:51] <pitti> this needs a backport of the yahoo bits to hardy
[08:52] <chrisccoulson> hey pitti / seb128
[08:52] <seb128> those u-d-d discussions are annoying
[08:52] <chrisccoulson> pitti - i can take a look at that, but i don't know the pidgin code all that well
[08:52] <chrisccoulson> i might be able to figure it out though:)
[08:53] <Laney> that stuff was really annoying to backport to hardy when i looked at it
[08:53] <seb128> "don't ship karmic it's not ready, there is some graphical things some users don't like and dvd playing doesn't work perfectly in totem yet"
[08:53] <seb128> yeah, right...
[08:54] <chrisccoulson> seb128 - i saw that one too
[08:54] <chrisccoulson> and the replies to digest's are annoying too
[08:54] <huats> morning everyone
[08:57] <seb128> hey huats
[08:57] <huats> hey seb128
[08:57] <huats> how are you
[08:57] <huats> ?
[08:57] <huats> busy busy busy I imagine
[08:57] <huats> :)
[08:57] <seb128> bit tired and waiting for karmic
[08:57] <seb128> you?
[08:57] <huats> bit tired too
[08:58] <huats> and otherwise could be worst
[08:58] <huats> still waiting...
[08:58] <didrocks> lut seb128, hey chrisccoulson
[08:58] <huats> and very busy with the company
[08:58] <seb128> lut  didrocks
[08:58] <huats> (which is great I agree)
[08:58] <seb128> huats, ok, good luck, business is good for you now?
[08:58] <huats> seb128, starts to be good
[08:59] <chrisccoulson> hey didrocks
[08:59] <huats> need to see if it is just the end of the year
[08:59] <huats> or if it will be like this early next year
[08:59] <huats> but the nov/dec are just madness :)
[09:06] <chrisccoulson> hello huats
[09:11] <huats> hey chrisccoulson
[09:14] <seb128> I need to get used to see rickspencer3 so early there
[09:14] <seb128> I need to get used to see rickspencer3 so early there
[09:14] <seb128> hey rickspencer3
[09:14] <rickspencer3> hi seb128
[09:14] <rickspencer3> :)
[09:16] <pitti> hey rickspencer3
[09:19] <rickspencer3> hi pitti
[09:35] <rickspencer3> jono, http://news.bbc.co.uk/1/hi/technology/8326264.stm
[09:39] <asac> nice
[09:39] <rickspencer3> good morning asac
[09:40] <asac> morning rick ;)
[09:40] <asac> how is the london weather?
[09:40] <davmor2> rickspencer3: It's great isn't it, it's almost like a review :)
[09:40] <rickspencer3> asac, rainy, chilly ... so pretty normal
[09:40] <rickspencer3> davmor2, yeah, pretty cool
[09:41] <davmor2> rickspencer3: sorry for a second I thought that was the weather report for London :D
[09:42] <rickspencer3> pitti, good news wrt to the empathy patch
[09:42]  * rickspencer3 crosses fingers
[09:43] <pitti> rickspencer3: wrt. my report, or did you hear other positive ones?
[09:43] <rickspencer3> your report
[09:53] <asac> pitti: can we remove firefox-3.0 from the archive completely? or is it ok to have it superseded in universe?
[09:55] <asac> i have opened bug 461782
[09:55] <pitti> asac: checking
[09:57] <pitti> asac: done, bug updated; thanks!
[09:57] <asac> too bad that bfilter still rdepends on xulrunner-1.9 ... i think without that we could get rid of that too
[09:57] <asac> pitti: thanks could you chcek if bfilter is really the last that still requires 1.9?
[09:58] <pitti> asac: hm, I commented on that one yesterday, and there were a fair number of rdepends still (I copied checkrdepends)
[09:58] <asac> really=
[09:58] <asac> ?
[09:58] <asac> what bug was that ;)
[09:58]  * asac searches
[10:00] <asac> pitti: sure that was xulrunner-1.9 bug?
[10:00] <asac> we fixed two more rdepends yesterdayy
[10:01] <pitti> asac: bug 456191
[10:01] <asac> hmm
[10:01] <asac> fix released ... thats why i didnt find it
[10:02] <asac> mozilla-helix-player -> fixed in archive
[10:02] <asac> ok
[10:02] <asac> then nevermind
[10:02] <asac> we went through what we found in Sources/Pakcages three times
[10:03] <asac> sugar-hulahop is also fixed
[10:04] <asac> pitti: google-gadgets is build dep xulrunner-dev | xulrunner-1.9-dev
[10:04] <asac> thats ok
[10:09] <seb128> pitti, do you know where the bugs about floppy drives being listed in devicekit-disks when there is none should go?
[10:09] <pitti> seb128: usually that's a kernel bug (detecting an fd if there is none)
[10:09] <seb128> pitti, I reassigned 2 of those to devicekit-disks now
[10:09] <pitti> asac: there might be some false positives on the list due to alternative b-deps, yes
[10:09] <pitti> seb128: ok, will look
[10:10] <seb128> should I move them to linux? what log would you need?
[10:10] <pitti> seb128: dmesg and lspci, I think
[10:10] <seb128> ok thanks
[10:10] <seb128> I will ask for those
[10:10] <asac> pitti: updated
[10:10] <asac> pitti: the bug
[10:10] <pitti> "udevadm info --export-db" can't hurt either, I think
[10:10] <asac> its just bfilter
[10:10] <pitti> asac: ah, the rest is alternative deps?
[10:10] <asac> https://bugs.edge.launchpad.net/ubuntu/+source/xulrunner-1.9/+bug/456191/comments/2
[10:10] <asac> pitti: yes
[10:11] <asac> pitti: let me double check the ones i said "fixed in archive" ... aka mozilla-helix-player
[10:11] <asac> and python-hulahop
[10:14] <pitti> asac: reopened, and sub'ed; please followup on the bug, will look in an hour
[10:14] <pitti> I'm off for a bit for a doctor appointment
[10:15] <asac> tx
[10:29] <seb128> 2 hours to go through night bug emails
[10:30] <asac> seb128: how long was that night ... 3 hours :-P?
[10:30]  * seb128 slaps asac
[10:31] <seb128> asac, that's not because you are slow that we all are there!
[10:31] <asac> hehe
[10:31] <asac> seb128: i rather ment it the other way around
[10:31] <asac> e.g. 3 hours sleep -> 2 hours bugs
[10:32] <asac> e.g. too many mails
[10:32] <seb128> right too many emails that was my point
[10:32] <seb128> 2 hours in the morning is crazy
[10:32] <seb128> usually it takes me half an hour
[10:32] <asac> yeah but would be even crazier if you just slept 3 hours
[10:32] <asac> i am quite openly saying that i cannot read all bug mail
[10:32] <asac> i can either do bugmail 100% of time
[10:33] <asac> or try to just spot the important ones :/
[10:33] <seb128> to be fair I had a long night break
[10:33] <seb128> ie I stopped at 7pm yesterday until 9am today
[10:33] <asac> haha
[10:33] <asac> thats efficient then
[10:33] <asac> or maybe means hat karmic is in good shape
[10:34] <seb128> well I just read quickly through desktop bugs
[10:34] <seb128> I want to spot things for sru-ing
[10:35] <asac> yeah
[10:35] <asac> me too
[10:35] <asac> i will start doing 100% bugwork the next few days
[10:35] <seb128> I'm find a better balance this cycle between spending too much time on bugs or overlooking those
[10:35] <seb128> I try to read quickly through
[10:35] <seb128> use greasemonly a lot to quickly close duplicates etc
[10:35] <seb128> and milestone other things
[10:36] <seb128> what I really want now is a "I don't care about your bug" button
[10:36] <seb128> which takes the bug off the buglist or something
[10:36] <asac> yeah
[10:36] <asac> i thought about that too
[10:36] <seb128> there is ton of valid wishlist I don't care about and we will never work on
[10:36] <seb128> or corner issues
[10:37] <asac> seb128: you could create a black-sheep account and then filter bugs out that have that user subscrbied
[10:37] <seb128> like "I get this issue after tweaking those 6 compiz options and those 3 gconf keys"
[10:37] <seb128> I could as well use tags...
[10:37] <seb128> no need of a fake account
[10:37] <asac> hmm
[10:37] <seb128> seb-dont-care
[10:38] <asac> yeah but tags can be removed by others
[10:38] <seb128> seb-dont-care-about-this-stupid-bug
[10:38] <asac> while others cannot unsubscribe someone
[10:38] <asac> ;)
[10:38] <seb128> right
[10:38] <asac> so if you want a dead sink ... use accounts
[10:38] <asac> but you ar eright. tags are probably good
[10:38] <seb128> yeah I think tags would be good enough
[10:39] <seb128> ok, done with bug triage now, let's do some iso testing
[10:39] <seb128> brb
[10:39] <asac> oh iso testing
[10:39] <asac> ... much neglected this cycle ... *cough*
[10:39]  * asac gets an iso image for usb key test
[11:00] <asac> do we know what happened to meeting time now that we are out of summer time in europe?
[11:01] <davmor2> asac: the meetings are still utc no?
[11:02] <asac> idk ;)
[11:02] <soren> What is the blessed way to run stuff as root from .desktop files nowadays?
[11:02] <asac> i only know that it was always confusing ;)
[11:03] <soren> ...for something that does not natively support policykit, of course.
[11:03] <asac> soren: i think the idea is policykit
[11:03] <asac> and if not, there is only the good old way
[11:05] <soren> asac: And what is that? gksudo? gksu? Something else that I've forgotten about?
[11:08] <asac> gksudo
[11:08] <asac> but only 90% sure
[11:08] <asac> we dont have that many apps that need root ... mvo ?
[11:18]  * asac checks iso
[11:25] <mvo> asac: no, not that many.
[11:25] <mvo> asac: still some though
[11:25] <asac_empathy> mvo: they use gksudo?
[11:25] <mvo> yes
[11:25] <mvo> well, gksu
[11:25] <mvo> and we default to sudo mode there
[11:25] <asac_empathy> soren: see above
[11:26]  * soren nods
[11:26] <soren> mvo, asac_empathy: Thanks.
[11:39] <pitti> asac, seb128: FWIW, I gave up trying to read all bug mail from all packages I'm interested in; it just doesn't work :-(
[11:39] <seb128> pitti, you are interested in too many thing?
[11:40] <seb128> things
[11:40] <pitti> at least I now don't need to have a bad conscience any more about not reading hal bugs at all :)
[11:40] <pitti> it was one of those packages which get all kinds of weird sh*t
[11:41] <seb128> right
[11:42] <mvo> asac: I have a somewhat unusual kvm setup here, but there NM tells me my wired device is not managed. however it is added by something to /etc/network/interfaces
[11:42] <mvo> asac: eh, nevermind
[11:42] <mvo> asac: strange setup
[11:42] <seb128> pitti, I don't find hard to read bugs, it's usually like a 1 hour a day job
[11:42] <seb128> and I do stock reply on quite some to count one hour a day
[11:43] <pitti> seb128: I guess that's just enough to browse through and pick out the nasty ones?
[11:43]  * mvo discovered with delight that qemu can do stuff like "pci_add auto nic model=e1000"
[11:43] <pitti> seb128: (which is fine; it's by and large what I do as well)
[11:43] <pitti> seb128: I usually browse through the web ui list for new bugs, though
[11:43] <seb128> pitti, yes, I'm not interested in reply to every issue users can have there
[11:43] <seb128> I just want to know about things that should be milestoned or srued
[11:43] <pitti> I'm not subscribed to apport/devicekit-disks/jockey/etc.; I just individually subscribe to the ones where I ask for more info
[11:44] <pitti> seb128: sounds fine; just ensure it doesn't ruin your mental health :)
[11:44] <seb128> don't worry ;-)
[11:45] <seb128> I also like to know what bugs are really active on launchpad
[11:45] <seb128> those are usually things users care about too
[11:45] <pitti> asac: ok, so want me to remove bfilter, too?
[11:45] <seb128> I would use the web ui if I had a I don't care button to filter things out of the bug lists
[11:47] <pitti> seb128: yeah, I guess that's a little different for my workflow; for apport, I look at all the new ones and set them to incomplete (and subscribe) or triaged, or close the ones I fixed in the meamtime
[11:47] <pitti> same for dk-disks
[11:47] <pitti> but I'm upstream for both of those, so it's a little different
[11:48] <seb128> the issue with that is that once a bug is triaged you sort of ignore it
[11:48] <seb128> it could get a thousand duplicate you would not notice
[11:48] <seb128> or comments rather
[11:52] <asac> pitti: yes. it hasnt seen any upstream release for ages
[11:52] <asac> and for the sake of getting the security nightmare out i think its worthwhile to drop
[11:53] <asac> mvo: figured what added something to interfaces?
[11:54] <asac> mvo: did you get my offer to fix apt yesterday ;)
[11:54] <asac> mvo: i wanted to factor out the "is_valid_filename_char" ... as it seems to be done in various places (and for preferences.d there is no "." allowed)
[11:55] <asac> so a) do you want that ... b) where to put such general utility funcs?
[11:55] <pitti> asac: want me to blacklist it as well? it was removed from debian testing, but not from sid
[11:55] <mvo> asac: contrib/strutil.cc or contrib/fileutil.cc
[11:55] <mvo> asac: probably the former
[11:55] <mvo> asac: good idea!
[11:55] <asac> pitti: afaik debian has xul 1.9.1 ... so if a new upload happens in debian it will probably for that 1.9.1 port
[11:56] <pitti> asac: right, debian has a "xulrunner" package and that's 1.9.1
[11:56] <pitti> ok, not blacklisting then
[11:56] <mvo> asac: I can do it between upgrade tests too if you want
[11:56] <pitti> asac: hah, bfilter never actually built
[11:56] <asac> mvo: no ... i want to submit at least one merge in my life ;)
[11:56] <mvo> ahah
[11:56] <mvo> ok
[11:56] <mvo> :)
[11:56] <asac> pitti: yes. because the js api changed
[11:57] <pitti> *flush*
[11:57] <asac> it uses JS_..BranchCallback which wes dropped without any valid replacement
[12:19] <pitti> seb128: minor request: can you please subscribe me to bugs, not assign?
[12:19] <pitti> seb128: I want to avoid having all the incomplete ones on my +assignedbugs page
[12:19] <pitti> I'm subscribed, so I'll timely respond to them either way
[12:19] <seb128> pitti, ok will do, sorry about though I was not sure which one were reaching you nowadays
[12:19] <pitti> seb128: no need to be sorry, no problem
[12:19] <pitti> seb128: they both reach me
[12:19] <seb128> ok
[12:20] <seb128> noted
[12:20]  * seb128 hugs pitti
[12:20] <pitti> merci! *hug*
[12:20] <seb128> pitti, and let me know if I should stop subscribing you to those keyboard and eject issues
[12:20] <pitti> seb128: oh, please continue to do so
[12:20] <pitti> it seems that several people are affected by this "Multiple layouts in /etc/default/console-setup" issue
[12:21] <seb128> I think you know how to debug those bugs since you worked on some of this changes
[12:21] <seb128> yes
[12:21] <pitti> no idea where it comes from, but it's easy to set manually and thus not hard to fix
[12:21] <seb128> right, I was wondering if the installer can set several in some cases too
[12:21] <seb128> I see that you replied on the upstream bug about stopping to define cdrom entries in fstab too
[12:22] <seb128> seems it's leading to quite some issues
[12:22] <seb128> it also leads to have nautilus not refreshing it's view on eject
[12:23] <pitti> yeah, cdrom in fstab is 3v1l
[12:23] <pitti> I just keep telling people to remove those
[12:23]  * pitti cd kitchen && lunch
[12:24]  * seb128 just back from lunch
[12:24] <seb128> pitti, enjoy
[12:27] <kenvandine> seb128, hey
[12:27] <seb128> hello kenvandine
[12:27] <seb128> how are you?
[12:27] <kenvandine> seb128, your last change to empathy, adding the symbols
[12:28] <seb128> yes?
[12:28] <kenvandine> breaks building it
[12:28] <kenvandine> not sure what is up
[12:28] <kenvandine> obviously it built for the archive
[12:28] <seb128> https://edge.launchpad.net/ubuntu/+source/empathy/2.28.1-1ubuntu1
[12:28] <seb128> right
[12:28] <kenvandine> but doesn't build locally, in pbuilder or in my ppa
[12:28] <kenvandine> i had to remove those
[12:28] <seb128> you already said you didn't have the symbols in your build log
[12:28] <kenvandine> yeah
[12:28] <seb128> weird
[12:28]  * asac lunch and errands bbiw
[12:29] <seb128> are those conditional to some build option?
[12:29] <kenvandine> i had to remove them to build it in my ppa
[12:29] <kenvandine> dunno
[12:29] <kenvandine> i have looked to closely
[12:30] <kenvandine> i do have the leak fix built into a ppa and asked folks to test
[12:30] <seb128> excellent
[12:32] <seb128> kenvandine, dunno about the symbol issue though
[12:52] <seb128> kenvandine, do you track bug #450290 too?
[12:52] <seb128> kenvandine, it got another duplicate today
[12:52] <kenvandine> yeah
[12:53] <kenvandine> so about that one... do we have a way of looking for libs that haven't been updated properly?
[12:53] <seb128> what do you mean?
[12:54] <kenvandine> like a failed update, leaving around old files
[12:54] <kenvandine> that's kind of what they were suggesting was the case
[12:54] <seb128> urg
[12:54] <seb128> which file would create an issue and why?
[12:55] <kenvandine> not sure, but notice he re-installed and it worked fro him
[12:55] <kenvandine> for
[12:55] <seb128> that's weird
[12:55] <seb128> I would rather say it's a coincidence
[12:57] <kenvandine> yeah, this is one i know i had re-produced and confirmed fixing
[12:58] <kenvandine> or maybe the transition between versions wasn't great
[12:59] <kenvandine> doubt that would be it actually
[12:59] <kenvandine> this is from empathy itself, not libempathy
[13:02] <seb128> kenvandine, not sure if bug #459274 is the same
[13:03] <chrisccoulson> kenvandine - you sure that crash is not from libempathy?
[13:03] <chrisccoulson> it starts because empathy_contact_list_get_monitor returns a NULL pointer
[13:03] <chrisccoulson> and that then gets passed to g_signal_connect, which will make it crash
[13:04] <chrisccoulson> frame 2 of the stack trace:
[13:04] <chrisccoulson> monitor = (EmpathyContactMonitor *) 0x0
[13:04] <kenvandine> chrisccoulson, could be
[13:22] <pitti> seb128: do you know if bug 381116  is the same as bug 428884? I. e. does totem use g-screensaver --poke ?
[13:22] <chrisccoulson> i might have overlooked something really stupid here, but to me, it seems like EmpathyTpContactList doesn't implement get_monitor, which would make empathy_contact_list_get_monitor return NULL and trigger this crash
[13:23] <chrisccoulson> but i've only had a quick look, i should be doing work really
[13:23] <chrisccoulson> kenvandine^^
[13:24] <Zdra> chrisccoulson, to me the whole concept of EmpathyContactMonitor is wrong. I have no idea why we added that
[13:24]  * pitti updates https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[13:24] <pitti> rickspencer3: ^ FYI
[13:24] <seb128> pitti, I don't think it's the same issue
[13:24]  * asac lurks on releasestatus
[13:25]  * pitti removes obsolete and confusing commentary from there, please reload
[13:25] <chrisccoulson> Zdra - yeah, I don't know the empathy code too well, so I can't really have a well-informed opinion ;)
[13:26] <chrisccoulson>  I just had a quick look because of a crash some users are seeing
[13:26] <chrisccoulson> pitti - totem (correctly) uses the gnome-session inhibit interface
[13:26] <chrisccoulson> like VLC should do ;)
[13:26] <pitti> right, I figured
[13:26] <kenvandine> pitti, btw jcastro seems to be getting that crash with the leak fix version... so perhaps you are just lucky
[13:26] <pitti> which made me wonder why the totem one is "fix committed"
[13:26] <pitti> kenvandine: entirely possible
[13:27] <chrisccoulson> Zdra - http://launchpadlibrarian.net/33599139/Stacktrace.txt is the crash I just took a quick look at
[13:27] <kenvandine> pitti, good news is he can very easily trigger it
[13:27] <seb128> pitti, the bug watch points to "web browser plugin doesn't inhibit screensaver"
[13:27] <seb128> pitti, which is fixed in 2.28.2
[13:27] <kenvandine> basically during a chat, he closes the chat window and then starts a new chat via the contact list
[13:27] <kenvandine> and it crashes
[13:27] <pitti> seb128: ah; but it would still fail because of 428884
[13:27] <seb128> pitti, so there is probably a mix of different issues there
[13:28] <pitti> kenvandine: sounds familiar
[13:28] <Zdra> chrisccoulson, drop the libindicator patch ?
[13:28] <seb128> pitti, no, I think totem use the gnome-session api
[13:28] <Zdra> chrisccoulson, must be related to that, I never say such crash in upstream
[13:28] <chrisccoulson> that's not really an option for me at the moment, as I'm at work, and I can't trigger the crash ;)
[13:28] <pitti> seb128: ah, so it's not affected by the --poke thing?
[13:29] <seb128> Zdra, could you stop making such comments every day?
[13:29] <seb128> pitti, I don't think so but should be confirmed
[13:29] <seb128> Zdra, I could suggest drop empathy which would be almost as constructive
[13:34] <asac> jcastro: how do you reproduce the empathy crash?
[13:38] <asac> for me empathy works ;)
[13:40] <seb128> pitti, I can't confirm the totem issue there
[13:40] <seb128> pitti, I just tried it inhibit correctly screen
[13:40] <chrisccoulson> WFM too
[13:40] <kenvandine> asac, here is what he is doing
[13:40] <kenvandine> he is chatting with me and closes the chat window
[13:40] <kenvandine> then immediately goes to the contact list and double clicks on me to start a new chat
[13:41] <kenvandine> and it crashes almost every time
[13:41] <asac> hmm
[13:41] <kenvandine> empathy:ERROR:empathy-tp-chat.c:1391:empathy_tp_chat_acknowledge_message: assertion failed: (m != NULL)
[13:41] <kenvandine> i can't reproduce that
[13:41] <asac> kenvandine: jabber?
[13:41] <kenvandine> yes
[13:41] <asac> i guess empathy doesnt support gpg ?
[13:41] <kenvandine> upstream thinks it was a leak, which was clearly there
[13:41]  * asac wonders if he can migrate there
[13:41] <kenvandine> i fixed that
[13:42] <asac> yeah i remember that discussion
[13:42] <kenvandine> pitti was getting the crash pretty frequently
[13:42] <kenvandine> with the leak fixed, it hasn't crashed for him
[13:43] <jcastro> asac: I just close a window and then initiate a conversation
[13:43] <asac> yeah
[13:43] <asac> thanks
[13:44] <jcastro> asac: so never when I respond to someone, only when I start up a conversation
[13:44] <kenvandine> no
[13:44] <seb128> kenvandine, want to do the 2.28.1.1 sru?
[13:44] <cassidy> you should really ship empathy 2.28.1.1
[13:44] <cassidy> I fixed a lof of nasty bugs
[13:45] <seb128> cassidy, right, it's on my "to sru" list ;-)
[13:45] <seb128> kenvandine, I was about to do it now let me know if you prefer to do it
[13:45] <asac> kenvandine: where is the leak fixed version?
[13:45] <kenvandine> seb128, let me...
[13:45] <seb128> pitti, ^ do you think it's fine to fix libindicate and update in the same update?
[13:45] <asac> i assume it didnt end up in karmic?
[13:45] <kenvandine> in my empathy ppa
[13:46] <seb128> pitti, ^ do you think it's fine to fix libindicate and update the version in the same update?
[13:46] <pitti> seb128: sure, if the other changes are SRU compliant
[13:46] <asac> kenvandine: have a .dsc?
[13:46] <kenvandine> asac, one sec
[13:46] <seb128> pitti, yes it's a bug fix only GNOME update
[13:46] <pitti> seb128: my opinion didn't change in the last 1.5 seconds :-)
[13:46] <asac> thx i can check too ... but inet is slow ;)
[13:46] <pitti> j/k
[13:46] <seb128> pitti, I added some words to clarify the "update in the same update" ;-)
[13:46] <seb128> kenvandine, ok
[13:47] <kenvandine> asac, https://edge.launchpad.net/~ken-vandine/+archive/empathy/+packages
[13:47] <kenvandine> you can grab the source there
[13:47] <kenvandine> or debs
[13:47] <asac> heh. thatts not a .dsc, but thanks. let me grab it
[13:47] <kenvandine> asac, there is a .dsc there :)
[13:47] <asac> https://edge.launchpad.net/~ken-vandine/+archive/empathy/+files/empathy_2.28.1-1ubuntu1+r64.dsc
[13:49] <asac> ok out for a bit testing stuff
[13:49] <asac> NM et al
[14:07] <seb128> urg
[14:08] <seb128> rickspencer3's reminding landed in my launchpad bugsbox
[14:12] <pitti> l
[14:12] <seb128> pitti, s
[14:12] <pitti> -EFOCUS, sorry
[14:14] <seb128> pitti, is it worth trying current iso or will we get a respin?
[14:14] <pitti> seb128: we'll get a respin very soon for an ubiquity fix
[14:14] <pitti> seb128: (OEM installer with encrypted home dirs)
[14:14] <pitti> but "trying" for testing is always appreciated
[14:15] <seb128> ok
[14:15] <seb128> let me try the "reinstall but don't wipe user dir" on my netbook
[14:26] <chrisccoulson> wow, i'm going to have to do a hardy install later
[14:26] <chrisccoulson> that's going to seem ancient ;)
[14:40] <pitti> chrisccoulson: for pidgin? back when I did security updates, a mere chroot was more than enough for that..
[14:42] <pedro_> could anybody reproduce bug 404351 ?
[14:42] <pedro_> i still don't managed to reproduce it here, it's getting a lot of dups and there's no easy way to reproduce it besides just login in
[14:43] <seb128> no
[14:43] <pedro_> we're still missing a good backtrace there though :-/
[14:43]  * pedro_ kicks nautilus
[14:43] <seb128> I expect it's a crash at session closing
[14:43] <seb128> ie it's a non issue
[14:43] <seb128> we just don't know how to filter those automatically
[14:45] <pedro_> right i was thinking it was as session closing, because of the exit() function there, but the comments said it's at login, so i'm a bit lost
[14:45] <pedro_> s/as/on
[14:46] <seb128> pedro_, well, you close the session, nautilus crashes, when will you see apport?
[14:47] <pedro_> seb128, good point
[14:54] <kenvandine> cassidy, just noticed something about bug 408530
[14:54] <kenvandine> cassidy, it was originally filed against 2.26.1 which didn't have the libindicate patch
[14:55] <Zdra> kenvandine, the crash happens if EmpathyChat object is leaked. We fixed another bug in upstream that had that same issue
[14:55] <kenvandine> ok, the leak was real for sure
[14:55] <kenvandine> and my fix did work for jcastro and pitti went quite a while without a crash but just got one
[14:55] <jcastro> I am still not crashed!
[14:56] <kenvandine> :)
[14:56] <kenvandine> and jcastro could reproduce it very easily
[15:03] <chrisccoulson> pitti - is bug 454487 ok for a SRU?
[15:03] <chrisccoulson> stgraber has already tested the patch and confirms it works
[15:03] <chrisccoulson> (the patch is in my PPA currently, but i will prepare a debdiff later)
[15:06] <seb128> chrisccoulson, seems a good sru candidate indeed
[15:06] <chrisccoulson> cool, thanks!
[15:07] <pitti> chrisccoulson: sounds fine; how intrusive is it?
[15:07] <pitti> chrisccoulson: i. e. regression potential for normal local usage?
[15:07] <chrisccoulson> pitti - the patch is here: http://launchpadlibrarian.net/34294574/gnome-desktop_1%3A2.28.1-0ubuntu2_1%3A2.28.1-0ubuntu3~chrisccoulson1.diff.gz
[15:08] <chrisccoulson> it just traps X errors when calling XRRGetScreenResources
[15:08] <chrisccoulson> under these circumstances, the xrandr plugin would be disabled
[15:09] <pitti> chrisccoulson: seems fine
[15:09] <chrisccoulson> thanks, i'll prepare a debdiff for that later
[15:12] <pitti> seb128: still planning/doing that test install on your netbook?
[15:12] <seb128> pitti, yes, I'm writting iso to usb key right now
[15:12] <pitti> seb128: the "keep old files" is broken right now unfortunately
[15:12] <seb128> pitti, want me to try something?
[15:12] <pitti> seb128: it doesn't clean up /var and /usr
[15:13] <seb128> oh ok
[15:13] <pitti> seb128: would be great if you could postpone that; I think we'll have new images in some 2 hours
[15:13] <pitti> and then we need to test that mode
[15:13] <seb128> ok
[15:13] <seb128> thanks for letting me know
[15:14] <pitti> nice timing
[15:14] <pitti> cjwatson just found it
[15:16] <hggdh> seb128: it ends up that there was a hard limit of 100 cache pages for SQLite in Evo. A patch has just been commited upstream for 2.28 and trunk
[15:16] <seb128> hggdh, did anybody notice a different with other cache values?
[15:17] <hggdh> I had 3 responses from my query to evolution-hackers, all positive. This will only make a difference on large folders.db
[15:17] <hggdh> no negative responses
[15:17] <seb128> right, I'm just wondering how much difference it makes
[15:17] <seb128> rather curious than discussion the change being correct
[15:18] <hggdh> we have not yet tested different cache sizes. The default is 2000, but I am not sure if I have a large enough DB to make a difference if I increase it
[15:18] <seb128> hggdh, pedro_: there is a zillion e-d-s crash bugs on launchpad btw
[15:18] <hggdh> what we did was simply take out the hard limit of 100 pages
[15:18] <seb128> it's new from this cycle, lot of random dbus crashes
[15:18] <seb128> not sure if there should all be dupped from one bug or something
[15:18] <seb128> hggdh, ok thanks
[15:19] <hggdh> seb128: will look at the EDS crashes
[15:19] <seb128> hggdh, I guess that will go with the next evolution update or sru in karmic
[15:19] <seb128> hggdh, thanks
[15:19] <pedro_> i'll take a look into that
[15:19] <hggdh> I agree
[15:19] <seb128> pedro_, thanks too
[15:19] <hggdh> seb128: depending on results, we might want to consider a SRU to Jaunty
[15:20] <hggdh> er, backporting the fix
[15:20] <seb128> right
[15:20] <seb128> though I doubt many user will care about jaunty after karmic
[15:20] <seb128> it's not a lts
[15:21] <hggdh> oh, yes. Forgot, sorry
[15:25] <kenvandine> seb128, building empathy 2.28.1.1 i get this:
[15:25] <kenvandine> - empathy_location_manager_dup_singleton@Base 2.28.1-1ubuntu1
[15:25] <kenvandine> - empathy_location_manager_get_type@Base 2.28.1-1ubuntu1
[15:25] <kenvandine> +#MISSING: 2.28.1.1-1ubuntu1# empathy_location_manager_dup_singleton@Base 2.28.1-1ubuntu1
[15:25] <kenvandine> +#MISSING: 2.28.1.1-1ubuntu1# empathy_location_manager_get_type@Base 2.28.1-1ubuntu1
[15:26] <kenvandine> which is the ones you added, should i push as is and let you try to reproduce that?
[15:26] <seb128> yes please
[15:27] <kenvandine> pushed
[15:40] <seb128> kenvandine, building, I will let you know in a minute
[15:41] <seb128> kenvandine, do you still plan to update the changelog? you dropped half of the NEWS summary apparently and you can probably close some bugs too
[15:45] <kenvandine> seb128, they are dupes from 2.28.1
[15:45] <seb128> kenvandine, oh ok
[15:45] <seb128> kenvandine, empathy builds fine there
[15:46] <kenvandine> so weird
[15:46] <kenvandine> i had the same build failure in the ppa
[15:46] <seb128> what arch do you use?
[15:46] <kenvandine> locally it was x86
[15:46] <kenvandine> the ppa failed for all the arches
[15:46] <seb128> $ nm -D debian/libempathy-gtk28/usr/lib/libempathy-gtk.so.28 | grep empathy_location_manager_get_type
[15:46] <seb128> 00049b20 T empathy_location_manager_get_type
[15:47] <seb128> in the build dir
[15:47]  * kenvandine does the same
[15:47] <sailor> wie kan mij helpen, please
[15:47] <seb128> sailor, #ubuntu
[15:47] <kenvandine> seb128, returns nothing
[15:47] <seb128> kenvandine, ok, so for some reason the symbol is not in the lib for you
[15:48] <sailor> mijn ubuntu os crasht denk dat het met ATI catalyst driver te maken heeft
[15:48] <sailor> wie kan mij helpen?
[15:49] <seb128> sailor, it's an english speaking channel
[15:49] <seb128> sailor, try #ubuntu or #ubuntu-<locale> for user questions
[15:49] <sailor> Okay sorry
[15:50] <pitti> sailor: #ubuntu-nl exists
[15:50] <sailor> you can not help me?
[15:50] <seb128> no
[15:50] <sailor> #ubuntu
[15:53] <kenvandine> seb128, i bet you have libchamplain and geoclue installed
[15:53] <kenvandine> seb128, look at config.log, you are building it with location awareness
[15:53] <seb128> kenvandine, no
[15:53] <seb128> $ dpkg -l | grep libchamplain
[15:53] <seb128> $
[15:54] <seb128> libgeoclue is installed though
[15:54] <kenvandine> oh... yeah i think that is enough
[15:54] <kenvandine> libgeoclue-dev?
[15:54] <seb128> yes
[15:54] <seb128> weird that it did build in the official archive though
[15:54] <kenvandine> yeah
[15:55] <kenvandine> very weird
[15:55] <seb128> I'm dropping those now
[15:55] <seb128> and adding some bug reference in the changelog
[15:55] <kenvandine> thx
[16:15] <Riddell> rickspencer3: when is the meeting today?
[16:23] <pitti> well, the wiki page says 1630 UTC, so it should be an hour earlier than last week (with DST being gone)?
[16:25] <asac> i would think so
[16:25] <kenvandine> so in 5m right?
[16:26] <asac> at least if we follow the calendar
[16:26] <asac> hmm
[16:26] <asac> according to calendar its 6:30 ... still
[16:26] <bryce_> morning
[16:26] <asac> i would prefer 5:30 if everyone is here ;)
[16:27] <asac> ... feel a bit tired today
[16:27] <seb128> the meeting should be in one hour no?
[16:27] <asac> no ;)
[16:27] <asac> hehe
[16:27] <kenvandine> 3m
[16:27] <bryce_> rick is in london this week, fwiw
[16:27] <asac> no. the question was in 3 minutes or in 1h
[16:27] <seb128> 1h
[16:28] <seb128> we usually keep european time no?
[16:28] <asac> last time there was disagreement of calendar and wiki we said wiki
[16:28] <asac> is the proper source for time info
[16:28] <kenvandine> should be 1630 UTC right?
[16:28] <asac> that says in 2m
[16:28] <seb128> no, 1730UTC
[16:28] <pitti> seb128: our wiki page says UTC..
[16:28] <asac>  i think it should be 1730 in future
[16:28] <seb128> usually we kept constant european hours
[16:28] <asac> question is if we should use 1630 this time
[16:29] <pitti> hm; I hoped we'd get it a little earler, but oh well :)
[16:29] <seb128> 1730 collide with my weekly call with rick
[16:29] <asac> as wiki is the public source for the time
[16:29] <asac> i prefer 1630 ... so on pitti's side
[16:29] <asac> seb128: that feels like fixable
[16:29] <pitti> I'm fine with either, though; if 1730 UTC causes fewer conflicts, let's keep it
[16:29] <seb128> asac, it's fixable either way yes
[16:29] <asac> yeah
[16:30] <seb128> I just said that until now we mostly kept constant utc times
[16:30] <asac> i am fine with both ... just would like to follow wiki today :-P
[16:30] <seb128> brb
[16:31] <seb128> re
[16:31] <seb128> I'm there for the meeting if it's now
[16:31] <rickspencer3> it's now?
[16:32] <asac> wiki says so ;)
[16:32] <rickspencer3> my calendar says in one hour
[16:32] <asac> calendar not
[16:32] <seb128> rickspencer3, we were arguing over it
[16:32] <seb128> rickspencer3, I said one hour but other say now
[16:32] <rickspencer3> whatever
[16:32] <asac> i would prefer to follow wiki if everyone is here
[16:32] <seb128> we have the issue every dst ;-)
[16:32] <rickspencer3> I think Google Calendar is confused with different time zones
[16:32] <awe> +1
[16:32] <ccheney> heh
[16:32] <rickspencer3> ok, let's go
[16:32] <ArneGoetje> please stick to UTC, makes things easier :)
[16:32] <kenvandine> ok
[16:32] <asac> very good
[16:33] <rickspencer3> ArneGoetje, asac, ccheney,
[16:33] <ArneGoetje> rickspencer3: here
[16:33] <rickspencer3> pitti, seb128, br
[16:33] <rickspencer3> bryce_,
[16:33] <rickspencer3> Riddell,
[16:33]  * bryce_ waves
[16:33] <ccheney> here
[16:33] <asac> 20-char column mode ;)?
[16:33] <pitti> o/
[16:33]  * pedro_ waves
[16:33]  * awe waves for my last desktop meeting
[16:33]  * asac waves
[16:33] <Riddell> hi
[16:33] <rickspencer3> no till?
[16:34] <rickspencer3> https://wiki.ubuntu.com/DesktopTeam/Meeting/2009-10-27
[16:34] <asac> awe: 6 month is way too short :(
[16:34] <rickspencer3> awe's last team meeting?
[16:34] <rickspencer3> :'(
[16:34] <awe> well, i'm not disappearing completely...
[16:34] <kenvandine> :)
[16:34] <rickspencer3> hi kenvandine
[16:34] <kenvandine> awe, we'll still drink with you at UDS :)
[16:34] <pitti> awe: thanks for your work in our team; was a pleasure
[16:34] <asac> for sure
[16:35] <rickspencer3> ditto
[16:35] <awe> thanks for having me.  i have a much better appreciation of what you all do.  ;)
[16:35] <rickspencer3> ready for the agenda?
[16:35] <pitti> ccheney: likewise, will you return to desktop full time next week?
[16:36] <rickspencer3> pitti, ccheney the answer is "yes" ;)
[16:36] <ccheney> pitti: yes, pretty much been that way for the past two weeks to get OOo under control
[16:37] <rickspencer3> pitti, the first two agenda items were yours
[16:37] <rickspencer3> do you want to take it away?
[16:37] <rickspencer3>     * Check your bugs for things which should be SRUed
[16:37] <rickspencer3>     * Think about your personal lucid goals/wishlist until next week
[16:37] <pitti> they pretty much speak for themselves
[16:37] <pitti> so, for SRU bugs
[16:38] <pitti> I updated https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus today
[16:38] <pitti> and it seems there's not that much which needs urgent post-RC fixing
[16:38] <pitti> but if you have something, please go ahead and turn your bugs into SRU bugs (justification, subscribe ubuntu-sru)
[16:38] <pitti> and please already upload
[16:38] <pitti> karmic-proposed is open for upload
[16:38] <rickspencer3> what about the empathy crasher?
[16:38] <pitti> I'll review/accept those right after release
[16:38] <seb128> uploaded one minute ago now
[16:39] <seb128> I'm doing the paper work for the empathy update
[16:39] <pitti> rickspencer3: the patch seems to make it better, but it still happens
[16:39] <seb128> kenvandine did the actual update
[16:39] <pitti> the original crash predates the indicator patch
[16:39] <seb128> pitti, oh, you got it again?
[16:39] <rickspencer3> right
[16:39] <seb128> pitti, the original crash was fixed upstream
[16:39] <kenvandine> rickspencer3, jcastro could consistently reproduce the bug and my patch fixed it for him
[16:39] <pitti> seb128: once so far
[16:39] <rickspencer3> so I saw kenvandine's comment on the bug
[16:39] <asac> i think we should check a day or two if we can find the full fix for empathy
[16:39] <kenvandine> but pitti did hit the crash one more time
[16:39] <rickspencer3> ok, that's good, at lease one crasher is solved
[16:39] <asac> unless folks say its fixed.
[16:39] <pitti> seb128: oh, I didn't try the new release yet, just the patch
[16:39] <seb128> pitti, no, I mean before karmic
[16:40] <seb128> what leads to the crash is a leak
[16:40] <pitti> anyway, just wanted to point out the procedure for SRU
[16:40] <kenvandine> there might be other leaks that cause the same problem
[16:40] <seb128> there was one in upstream code which has been fixed
[16:40] <seb128> and the libindicate has some others
[16:40] <seb128> we need to find maybe yet another codepath leaking
[16:40] <pitti> seb128: our patch + new upstream version together might well fix it
[16:40] <rickspencer3> k
[16:40] <asac> kenvandine: i looked at the patch and wondered why you didnt do the g_signal_connect_data thing to free the cb_data ?
[16:40] <pitti> the other piece:
[16:40] <pitti> asac: let's continue the details after meeting, shall we?
[16:40] <asac> sure
[16:41] <asac> go ahead
[16:41] <pitti> I guess on Friday we'll all chill out and do something easy, like catch up on mail and something
[16:41]  * seb128 is taking a vac day again
[16:41] <rickspencer3> are there other SRUable bugs that should be on our ReleaseStatus page?
[16:41] <asac> i will hopefully do holiday ;)
[16:41] <pitti> but for meeting next week I'm curious about everyone's ideas for lucid
[16:41] <pitti> no fine-grained plans, just some rough ideas what you would like to work on
[16:42] <rickspencer3> pitti, I have discussed with many folks 1-1 about Lucid
[16:42] <seb128> lowering the number of rough edges
[16:42] <pitti> so that we can start putting together an UDS agenda
[16:42]  * ccheney will be leaving this weekend for OOoCon
[16:42] <seb128> ie tackling annoying issues
[16:42] <pitti> rickspencer3: oh, great
[16:42] <seb128> as we did in hardy
[16:42] <rickspencer3> but not everyone
[16:42] <seb128> do we need a real project ?
[16:42] <rickspencer3> seb128, not necessarily
[16:42] <seb128> or using extra time to polish what we have is one?
[16:42] <pitti> so, I thought it'd be nice to sit together and throw our main focus areas into the pot to get a first idea about what we'll work on
[16:43] <asac> for karmic?
[16:43] <seb128> there is many bugs around for a while that I would like time to work on
[16:43] <rickspencer3> one thing I want is for people to get to work on something that they are passionate about at least onto a list of consideration
[16:43] <pitti> seb128: that's great
[16:43] <rickspencer3> seb128, if you are passionate about polish, that's fine
[16:43] <seb128> good
[16:43] <seb128> thanks guys ;-)
[16:43] <bryce_> rickspencer3, there is one kind of bad bug that might be worth an sru
[16:43] <rickspencer3> pitti, when should we start putting in blueprints?
[16:43] <pitti> seb128: I personally think it's good for people to have at least one pet project and not doing bug fixing all the time, but of course it's up to you :)
[16:44] <rickspencer3> oops
[16:44] <bryce_> rickspencer3, if you put a typo into your xorg.conf it locks up your system with the screen blinking
[16:44] <rickspencer3> uh
[16:44] <pitti> rickspencer3: can we do that on our 1-1 call next Wednesday, after the meeting?
[16:44] <pitti> rickspencer3: at least start on it?
[16:44] <rickspencer3> pitti, sure
[16:44] <pitti> bryce_: that sounds like a good SRU fix
[16:44] <bryce_> rickspencer3, seems to be some interaction between gdm and upstart
[16:45] <pitti> rickspencer3: [done with my two bits]
[16:45] <bryce_> pitti, there is already a bug about it filed against gdm
[16:45] <bryce_> pitti, ok I'll mark it as a release bug
[16:45] <seb128> it's a gdm issue, it keeps retrying
[16:45] <pitti> bryce_: thanks
[16:45] <seb128> the old gdm has a retry counter
[16:45] <bryce_> seb128, actually, gdm does give up after 5 tries
[16:45] <seb128> oh, nice
[16:46] <bryce_> seb128, but then upstart restarts gdm
[16:46] <seb128> so there is a misleading bug open
[16:46] <pitti> ah, bugger
[16:46] <seb128> ah, I see
[16:46] <rickspencer3> hehe
[16:46] <pitti> I don't think it ever should, TBH
[16:46] <bryce_> it blinks *really* fast, it's kind of cool
[16:46] <rickspencer3> bryce_, is there a bug # for those of us watching from home?
[16:46] <rickspencer3> (or the office in this case)
[16:46] <bryce_> bug 441638
[16:47] <rickspencer3> bryce_, thanks for the heads up, moving on ...
[16:47] <bryce_> it's easy to reproduce, just "echo 'foo' >> /etc/X11/xorg.conf" and reboot
[16:47] <rickspencer3> this seems rather bad
[16:47] <rickspencer3> that bug I mean
[16:48] <rickspencer3> speaking of which ...
[16:48] <rickspencer3> next item is release notes
[16:48] <rickspencer3> I just wanted to say "don't forget about release notes" ;)
[16:48] <pitti> ^ for documenting major bug workarounds, etc.
[16:48] <pitti> https://wiki.ubuntu.com/KarmicKoala/ReleaseNotes
[16:49] <rickspencer3> pitti, may I ask people to seek guidance from you if you have questions?
[16:49] <pitti> and if you want to do last-minute "new features" documentation, use https://wiki.ubuntu.com/KarmicKoala/TechnicalOverview
[16:49] <pitti> right; best is to come to #u-release and discuss it first
[16:49] <rickspencer3> k
[16:49] <rickspencer3> I have one last item not on the agend
[16:50] <rickspencer3> as you may know, I am sitting in the office in Milbank right now
[16:50] <pitti> rickspencer3: (agenda: add meeting time, please)
[16:50] <rickspencer3> the excitement here about Karmic is palpable
[16:50] <pitti> ♪ let's do the karmic dance ♫
[16:50] <and471> hehe
[16:50] <awe> w00t
[16:50] <and471> mac_v: I have been starting to create a humanity theme for claws mail :-)
[16:51] <pitti> /msg rickspencer3 the fridge is usually filled well with beer, FYI :)
[16:52] <seb128> rickspencer3, how is karmic looking from milbank comments?
[16:52] <pitti> I bet everyone is bugging you about fixing their laptop :)
[16:52] <seb128> rickspencer3, not too many people complaining about things broken around? ;-)
[16:52] <rickspencer3> ok, so I wish I could tell all you folks how much excitement there is about the release, and how muh people here appreciate your efforts
[16:52] <and471> mpt: I just saw your latest tweet and I happened to be looking at that an hour previously :-)
[16:53] <rickspencer3> it's the opposite
[16:53] <and471> mpt: I never thought something I contributed to would be on the front page of BBC :-)
[16:53] <rickspencer3> seems that we are on the cusp of something big, and people are really happy
[16:53] <rickspencer3> and471, exactly, well put! ;)
[16:53] <rickspencer3> ok, so pitti had one last agenda item
[16:53] <rickspencer3> pitti, go ahead
[16:53] <pitti> there was some confusion about the  meeting time
[16:54] <pitti> our wiki says 1630 UTC, and fridge (?) adapted that to non-DST
[16:54] <pitti> so we need to decide whether we want to stick to UTC (always) or move with DST (keeping in mind that we'll move the southern hemisphere by 2 hours then)
[16:54] <and471> rickspencer3: an image on OMGUbuntu puts it even better :-) http://lh5.ggpht.com/_FJH0hYZmVtc/SubSNrGcgxI/AAAAAAAAEGY/B9c6LRaPt58/image_thumb%5B4%5D.png?imgmax=800
[16:54] <rickspencer3> pitti, this happens whenever the clocks  change
[16:55] <ArneGoetje> to hell with DST! ;)
[16:55]  * kenvandine thinks we should follow UTC
[16:55] <pitti> ArneGoetje++
[16:55] <rickspencer3> pitti, may I ask you to make a recommendation and we can all stick to it?
[16:55] <kenvandine> seems less confusing
[16:55] <mac_v> and471: hi... mail icons? as in reply/forward and so on?
[16:55] <awe> pitti, the fridge is UTC and is correct
[16:55] <pitti> rickspencer3: I think we should just keep it at 1630 UTC all the time, unless it causes too many conflicts, but I do'nt have a firm opinion
[16:55] <rickspencer3> ((keep in mind no matter what we decide, I will end up confused ;) )
[16:55] <asac> ++
[16:55] <ArneGoetje> ++
[16:56] <asac> i am for constant UTC
[16:56] <kenvandine> rickspencer3, it's that pointy hair
[16:56] <rickspencer3> okay, it's pitti's call, and seems to be consensus
[16:56] <and471> mac_v: yup, so claws mail doesn't using the gtk icon theme, so all of the icons have to be packaged seperately (ie. reply forward) but also I have created some panel icons in the greyscale style
[16:56] <pitti> rickspencer3: well, it's really a team decision
[16:56] <mac_v> and471: you've got the worst timing in the world ;p
[16:56] <rickspencer3> so 1630 UTC, but kenvandine will have to ping me and remind me next week ;)
[16:56] <seb128> rickspencer3, we need to rediscuss our weekly call slot then ;-)
[16:56] <pitti> does anyone have objections against 1630 UTC?
[16:56] <kenvandine> hehe
[16:56] <rickspencer3> seb128, okay
[16:56]  * ccheney likes it being set to UTC regardless of actual time that is decided on
[16:56] <kenvandine> rickspencer3, our clocks didn't change yet :)
[16:56] <mac_v> and471: just uploaded those icons yesterday ;p
[16:56] <and471> mac_v: hehe
[16:56] <rickspencer3> kenvandine, exactly, so I will be confused again next week
[16:57] <and471> mac_v: are they on the branch
[16:57] <pitti> I maintain tzdata and know how often DST rules change (ugh)
[16:57] <kenvandine> rickspencer3, oh right... it is this sunday :)
[16:57] <rickspencer3> pitti, seems the team agrees with you
[16:57] <bryce_> is it currently 1730?
[16:57] <pitti> bryce_: 1657 UTC now
[16:57] <rickspencer3> lol
[16:57] <bryce_> pitti, no, is the meeting time set to 1730 currently?
[16:57]  * kenvandine wishes google calendar could remember that :)
[16:58] <ccheney> bryce_: 1630
[16:58] <pitti> bryce_: no, our wiki has always said "1630 UTC"
[16:58] <bryce_> ok
[16:58] <rickspencer3> ok, let's wrap this up on a high note though
[16:58] <pitti> ACTION: pitti to add a permanent record of this to the wiki
[16:58] <rickspencer3> Karmic is an epic, but epic release
[16:58] <rickspencer3> I hope everyone is very very proud of their contributions, and excited about the future
[16:59] <seb128> \o/
[16:59] <pitti> karmic's new features plus the polish/bug fixes in lucid -> awesome
[16:59] <asac> yes. i used todays live usb image and karmic is a great release.
[16:59] <pitti> great job everyone
[16:59] <chrisccoulson> :)
[17:00] <asac> not enough sleep again, but you now see that it pays off ... and i am sure most users will think the same :)
[17:00] <pitti> chrisccoulson: thanks so much for your hard work, too!
[17:00] <rickspencer3> chrisccoulson, thanks for your great contributions, Amaranth, didrocks, dtchen (too may others to mention)
[17:00] <chrisccoulson> pitti / rickspencer3 - you're wecome
[17:00] <seb128> chrisccoulson, thanks, you really did rocking work this cycle
[17:01] <chrisccoulson> thanks:)
[17:01] <seb128> same for didrocks and some others ;-)
[17:01] <rickspencer3> any other business?
[17:01] <pitti> so, let's get this out of the door, sleep, have a great weekend, and then think about new goodness
[17:02] <seb128> do we know when lucid will open btw?
[17:02]  * kenvandine keeps trying to re-install karmic x86_64 on this laptop, but keep getting derailed into empathy debugging
[17:02] <kenvandine> :)
[17:02] <asac> seb128: not before we release ;)
[17:03] <seb128> asac, hey no hurry anyway
[17:03] <asac> or are you asking for upload queue? i would like to have it already too
[17:03] <seb128> I usually spend a week or two on srus
[17:03] <asac> ack
[17:03] <pitti> seb128: I guess a day or two after release, but as usual it will start frozen for the toolchain bootstrap
[17:03]  * Amaranth is sad to not have any more updates every day :)
[17:03] <asac> hehe
[17:04] <rickspencer3> hi tkamppeter
[17:04] <pitti> last thing, we need to re-roll iso images
[17:04] <bryce_> Amaranth, there's always xorg-edgers if you get desperate
[17:05] <pitti> helping out with testing appreciated
[17:05] <rickspencer3> pitti, ack, thanks
[17:05] <pitti> thanks everyone
[17:05] <seb128> pitti, do we know when new images will be there?
[17:05] <rickspencer3> hmm
[17:05] <Amaranth> bryce_: I need my usermode mode setting so no
[17:05] <bryce_> thanks
[17:05] <rickspencer3> is anyone going to overlap with the Eastern Edition?
[17:05] <pitti> seb128: order of an hour
[17:05] <rickspencer3> I just realized that I'm going to miss that
[17:05] <seb128> ok
[17:05] <rickspencer3> awe ?
[17:05] <seb128> rickspencer3, I don't think so, nothing urgent to do now so I will stop working not too late
[17:06] <awe> ?
[17:06] <awe> rickspencer3, sure, i can attend...
[17:06] <asac> rickspencer3: the riverbank has wifi in the lobby ;)
[17:06] <seb128> lol
[17:06] <seb128> asac, I think you just got volunteered thanks to your comment ;-)
[17:06] <asac> ... or bar
[17:06]  * seb128 runs
[17:06] <rickspencer3> awe, well, just let them know to look at the log ;)
[17:06] <rickspencer3> TheMuso ^ no Eastern Edition
[17:06] <awe> ok
[17:07] <rickspencer3> thanks awe <3
[17:07] <asac> i am not sure... but i might really be around, but i could crash so i dont want to commit to that if possible
[17:07] <seb128> asac, I was joking
[17:07] <asac> hehe
[17:07] <asac> good ;)
[17:07]  * seb128 hugs asac
[17:07]  * asac hugs seb128 
[17:07] <seb128> you should get some well deserved sleep too
[17:07]  * seb128 plans to do that
[17:07] <seb128> or maybe I will let some installs running while I watch tv or something
[17:07] <asac> yeah ... i reduced the daily dose of caffeine already ;)
[17:10] <jcastro> kenvandine: still 0 crashes so far, it's never gone this long!
[17:10] <kenvandine> woot woot
[17:14] <ccheney> jcastro: have you seen the weird resume failures on your x200?
[17:14] <jcastro> ccheney: not lately no
[17:14] <ccheney> jcastro: ok
[17:14] <jcastro> ccheney: want me to test?
[17:14] <ccheney> jcastro: i think maybe its more a case of really slow resume because i was getting them but then started waiting longer before power cycling
[17:14] <jcastro> ccheney: just one time ubuntuone crashes on resume, so I filed a bug about that
[17:15] <ccheney> oh i mean my system would not come back from resume at all
[17:15] <jcastro> oh wow, I've never seen that
[17:15] <ccheney> but i tested a bit more and it seems to just sometimes take a long (> 10s) time to resume
[17:15] <jcastro> that's odd
[17:15] <ccheney> with the suspend light just blinking
[17:16] <jcastro> I don't think I've ever had a failure like that the entire time I've had it
[17:16] <ccheney> if i manage to make it happen without actually resuming again i'll file a bug
[17:16] <jcastro> when my thing fails it's suspend that breaks
[17:16] <ccheney> ah
[17:19] <tkamppeter> hi rickspencer3
[17:21] <dtchen> jcastro: / ccheney: what sort of suspend/resume failures?
[17:21] <asac> kenvandine: so connect_data vs. just connect ... how is that supposed to work?
[17:22] <kenvandine> asac, i am not sure... i have a patch that uses connect_data but it doesn't do what i expected
[17:22] <kenvandine> so i didn't push that yet
[17:22] <asac> kenvandine: whats the wrong behaviour?
[17:22] <jcastro> dtchen: I've been fine for most of the cycle, haven't had a problem in a while. ccheney's the broken one. :p
[17:22] <kenvandine> i had tried to get tedg to look at it yesterday but i guess he was busy
[17:22] <kenvandine> asac, well i am sure i am just doing it wrong :)
[17:22] <asac> kenvandine: was that on top of what you have atm? or a replacement patch?
[17:23] <kenvandine> on top of
[17:23] <asac> kenvandine: good. ... so i would think using connect_data and using the notification_free thing as callback might work. but i assume you did that?
[17:23] <kenvandine> that is what i did
[17:23] <asac> and what didnt work?
[17:23] <kenvandine> it is never calling free_notification_data
[17:23] <asac> ;)
[17:24] <asac> is that chat-window object finalized/disposed?
[17:24] <kenvandine> let me paste it... one sec
[17:24] <kenvandine> it should be
[17:26] <kenvandine> http://pastebin.ubuntu.com/302956/
[17:26] <kenvandine> asac, ^^
[17:27] <kenvandine> i commented out the call to free_notification_data in chat_window_indicator_activate_cb because it was causing an error in the unref
[17:27] <kenvandine> so i thought it was working
[17:27] <asac> kenvandine: and you see the Finalize DBG output?
[17:27] <kenvandine> but that debug message never gets printed
[17:28] <Laney> what if it wasn't?
[17:28] <Laney> what if it wasn't?
[17:28] <Laney> [A
[17:28] <Laney> [A
[17:28] <Laney> ooer
[17:28] <Laney> excuse me
[17:28] <asac> huh?
[17:28] <tedg> kenvandine: Why don't you just put "cb_data" in the private struct, and then unref it when the whole object dies?
[17:28] <Laney> accidental input
[17:30] <kenvandine> maybe it is getting called, just not when i think it should
[17:30] <kenvandine> tedg, i hadn't considered that
[17:31] <asac> first i would check if the window ever gets finalized
[17:32] <asac> anyway out for a few
[17:35] <didrocks> thanks everyone (just got my new passeport \o/)
[17:35] <mac_v> hmmm ,.. anyone know how... [In nautilus side pane ] to place nautilus bookmarks on top and the rest of the filesystem and trash below?
[18:43] <pitti> new ubuntu desktop images up for testing
[18:53] <chrisccoulson> pitti - where are the images?
[18:53] <chrisccoulson> (that might sound like a silly question) ;)
[18:54] <davmor2> chrisccoulson: On the t'interweb :)
[18:54] <chrisccoulson> davmor2 - really? ;)
[18:54] <chrisccoulson> at cdimages?
[18:54] <chrisccoulson> are they the latest ones?
[18:54] <davmor2> http://cdimages.ubuntu.com/daily-live/current/
[18:55] <chrisccoulson> excellent, thanks:)
[19:45] <jcastro> is the gwibber auto-url-shortener broken for anyone else?
[19:45] <pitti> re
[19:45] <pitti> chrisccoulson: what davmor2 said
[19:46] <chrisccoulson> pitti - thanks
[19:46] <chrisccoulson> i probably should have known that ;)
[20:24] <seb128> pitti, thanks for taking over the gdm respawn bug
[20:24] <seb128> pitti, do you know if isos are good to test now?
[20:24] <pitti> np
[20:24] <pitti> seb128: yes, they are
[20:24] <seb128> ok good
[20:24] <pitti> currently writing my usb stick
[20:24]  * seb128 rsync
[20:24] <pitti> I'm off for the next hour for reinstalling my box
[20:39] <chrisccoulson> heh, i suspect the archives are going to grind to a halt on release day
[20:40]  * chrisccoulson must make sure his pbuilder is up to date
[20:45] <seb128> chrisccoulson, better to use mirrors yes
[20:46] <seb128> the archive.ubuntu.com speed is already slow for a week now
[20:47] <kenvandine> jcastro, do you have any specific url shortener selected?
[20:47] <chrisccoulson> yeah, it is pretty slow now. i suppose that using a mirror is not so bad when packages aren't being updated as quickly. the mirrors won't be out of date by as much then
[20:53] <chrisccoulson> woah, hardy pidgin with the yahoo fix built first time
[20:53] <chrisccoulson> i must have done something wrong
[20:54] <seb128> lol
[21:07] <seb128> mclasen, hey, did you send you default location gnome-panel patch somewhere?
[21:07] <seb128> I'm trying to find the corresponding upstream bug
[21:09] <mclasen> seb128: default location ? thats just our panel config setting 'Boston' in gconf...
[21:09] <jcastro> kenvandine: anyone I choose doesn't work
[21:09] <seb128> mclasen, seems a good idea since the default can be by locale
[21:09] <seb128> mclasen, any reason that shouldn't be done upstream too?
[21:09] <mclasen> seb128: really, I want someone to finally finish the geoclue patch
[21:09] <jcastro> chrisccoulson: use a caching proxy (I just blogged about it if you want to check it out)
[21:10] <mclasen> seb128: I can give you the bug for _that_ if you like :-)
[21:10] <seb128> no, I know the one about that
[21:10] <seb128> somebody pointed to the change you have for order notify area icon
[21:10] <seb128> so I looked at your other changes and that one seems useful too
[21:10] <seb128> but right having geoloc working would be nice
[21:10] <seb128> thanks
[21:11] <jcastro> kenvandine: just had 2 crashers back to back. :-/
[21:12] <kenvandine> jcastro, i have another patch for you to test :)
[21:14] <chrisccoulson> jcastro - thanks for the tip:)
[21:18] <seb128> mclasen, hum, an any reason you didn't add your change for the notification area order to https://bugzilla.gnome.org/show_bug.cgi?id=531282?
[21:18] <seb128> mclasen, the change you have seems quite different of the current upstream suggested change
[21:19] <mclasen> seb128: that bug simply did not come up. I am pretty sure I put my patch in a different bug
[21:20] <mclasen> also 'allow to arrange icons' is pretty different from 'hardcoded standard order'
[21:20] <mclasen> seb128: my patch is a straight backport of  a gnome-shell patch
[21:20] <seb128> mclasen, right, it's in your .spec, thanks, I think the issue is the same though
[21:21] <mclasen> https://bugzilla.gnome.org/show_bug.cgi?id=583115
[21:21] <seb128> vuntz, ^ do you plan to do patches review soon? ;-)
[21:21] <seb128> there is quite some patches in bugzilla that would be nice to get upstream
[21:22] <seb128> though I guess upstream might not be much interested in GNOME 2.30 uses gnome-shell
[21:22] <seb128> still would be nice to have for distros that still use gnome-panel
[21:35] <TheMuso> Yay, wiki is down.
[21:35] <TheMuso> Hrm now it works.
[21:55] <chrisccoulson> wow, i can't believe how dated hardy feels now
[21:57] <charlie-tca> I'll second that
[21:57] <chrisccoulson> it just goes to show how far along karmic has come:)
[22:00] <TheMuso> I'll third that.
[22:00] <bryce_> chrisccoulson, judging from the amount of ubu-jealousy/ubu-hate I'm getting from the more fedora-oriented xorg folks, we must be doing pretty well this release ;-)
[22:01] <TheMuso> heh
[22:01] <chrisccoulson> heh, do you normally get a lot of abuse then?
[22:02] <bryce_> yeah, off and on.  it's notched up a bit more than usual lately tho
[22:02] <chrisccoulson> that's a shame:(
[22:03] <TheMuso> Shame that.
[22:03] <bryce_> what's funny is most of the stuff they've been harping on have been due to upstream changes
[22:04] <chrisccoulson> what sort of stuff do they talk about?
[22:04] <bryce_> ah, issues caused by the new gdm was the most recent
[22:05] <chrisccoulson> yeah, gdm has caused us a few issues
[22:05] <bryce_> also ubuntuone stuff, I guess they think "personal cloud" sounds silly
[22:05] <chrisccoulson> but some of those issues shouldn't be new to other distro's that have been using the new version for several cycles now
[22:06] <chrisccoulson> i haven't made much use of ubuntu one yet. i suppose that i probably will if i get myself a netbook
[22:06] <chrisccoulson> thats a good excuse to buy one:)
[22:06] <bryce_> I tried it when it first came out, but the icon would not stop being animated so I finally turned it off
[22:06] <chrisccoulson> i don't think it's animated anymore
[22:07] <bryce_> I was going to set up something for baby photos for the grandparents, but they're all on hardy so no ubuone there
[22:07] <bryce_> facebook has suited the bill sufficiently so far
[22:07] <chrisccoulson> it's maybe time to upgrade them ;)
[22:08] <bryce_> yeah...
[22:08] <chrisccoulson> you have a baby?
[22:08] <bryce_> yep, name's Dutch, 6 weeks old
[22:08] <chrisccoulson> excellent:)
[22:08] <chrisccoulson> i will do at some point soon, if she hurries up!
[22:12] <bryce_> chrisccoulson, http://bryceharrington.org/drupal/dutch-announce
[22:24] <TheMuso> t/c