[00:19] <meebey> .oO( Smuxi uses 2 minutes interval )
[00:21] <TheMuso> /c/c
[02:44] <kenvandine> high... i think low :)
[02:44] <kenvandine> considering facebook and twitter rate limiting stuff
[02:44] <RAOF> Which is per app-key, right?
[02:46] <kenvandine> yes
[02:46] <kenvandine> well, facebook is
[02:46] <kenvandine> twitter sucks less :)
[02:46] <RAOF> Apart from the oauth fun? :)
[02:47] <kenvandine> yeah
[02:47] <kenvandine> but at least twitter throttles the user that is abusing it... not everyone... SUCK
[02:50] <hallyn> upgraded my maverick laptop this afternoon, now gdm says it can't load nvidia module.  known problem?
[02:51] <hallyn> (probably should ask on #ubuntu-kernel, but figured i have to start somewhere)
[02:51] <hallyn> (tried to submit a bug, but elinks brings me to a page sayingn launchpad is broken)
[02:54] <RAOF> hallyn: That problem is not known to me, but you'll need to provide some hardware details before I can say something useful about your problem.
[02:57] <hallyn> RAOF: nvidia GT218 (GeForce 310M) rev a2
[02:58] <RAOF> Ok, so it's not that we don't have an nvidia driver for your card that supports Xserver 1.9, then.
[02:58] <RAOF> Loggities?  /var/log/Xorg.0.log and /var/log/dkms.log are nice :)
[02:59] <hallyn> RAOF: yeah, i submitted a bug that should have those, but actually i suspect it used the wrong logs
[02:59] <cyphermox> kenvandine, could you review / sponsor an update to vte?
[02:59] <RAOF> Feel like pointing me at that bug? :)
[02:59] <hallyn> that is, i'm booted into the previous kernel right now, so gdm/:0.log.0 probably is from THIS kernel's failure
[02:59] <hallyn> RAOF: i'd love to, still waiting for the email confirming it
[02:59] <RAOF> Yeah.
[03:00] <hallyn> i'll try to attach the correct logs, but am having to use elinks for this...
[03:00] <RAOF> But /var/log/Xorg.0.log.old is probably the right thing, and /var/log/dkms.log should still apply.
[03:00] <hallyn> i have no /var/log/dkm*
[03:01] <hallyn> RAOF: pastebin.com/c8fhjSaZ
[03:01] <hallyn> that's Xorg.0.log.old
[03:01]  * hallyn kisses pastebinit
[03:02] <hallyn> RAOF: bug is 655446
[03:02] <RAOF> bug #655446
[03:02] <ubot2> Launchpad bug 655446 in xorg (Ubuntu) "Xorg won't start (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/655446
[03:04] <RAOF> Does it work if you boot into the 2.6.35-22-generic kernel?
[03:05] <RAOF> Because you *do* have an nvidia kernel module for 2.6.35-22-generic, but not for 2.6.35-20-generic
[03:05] <hallyn> RAOF: no, that's the one that gives me a useless blank screen so i can't even drop to terminal
[03:06] <hallyn> RAOF: at least 2.6.35-20-generic gives me a console :)
[03:06] <RAOF> So, next question: is your chip actually supported by the nvidia drivers we have…
[03:07] <hallyn> RAOF: it used to work until i upgraded today
[03:07] <hallyn> RAOF: it did not work under lucid (had to use vesa)
[03:08] <RAOF> When did you last update?
[03:09] <RAOF> Rather: my guess is that the 260 driver update, uploaded on the 4th, probably is your problem.
[03:09] <hallyn> looks like oct 2
[03:09] <hallyn> yup
[03:09] <hallyn> that would fit
[03:09] <RAOF> Care to download the previous nvidia-current package from Launchpad and give it a whirl?
[03:10] <hallyn> sure - where/how do i get it?
[03:10] <RAOF> Not that we're likely to be able to *do* much about this, but it'd be good to know what the problem is.
[03:10] <hallyn> (or should i pin the package somehow?)
[03:10] <RAOF> http://launchpad.net/ubuntu/+source/nvidia-graphics-drivers - there are links to where you can find all the previous versions.
[03:10] <RAOF> Like so:
[03:11] <RAOF> https://edge.launchpad.net/ubuntu/maverick/+source/nvidia-graphics-drivers - has a list of all the previous versions in Maverick.  Following one to the last 256.53 package…
[03:11] <RAOF> Takes you here: https://edge.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/256.53-0ubuntu3 where there's a link to the amd64 and i386 builds.
[03:12] <RAOF> Going to the amd64 build page here: https://edge.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/256.53-0ubuntu3/+build/1973339 there are all the binary .debs produced, which you can download and install.
[03:13] <hallyn> that's the prevoius version?
[03:13] <RAOF> (Basically you should only need to care about the nvidia-current deb)
[03:13] <RAOF> Yup.  That's the 256.53 driver version.
[03:18] <hallyn> RAOF: just curious, how did an upgrade of nvidia drivers fit into feature freeze?  serious bugfixes in there?
[03:19]  * hallyn rebooting
[03:19] <RAOF> Probably.
[03:19] <RAOF> It certainly claims to fix quite a major performance regression in text rendering.
[03:21] <hallyn> RAOF: downgrade worked, i'm back in X
[03:22] <RAOF> Now, finally, upgrade again and see if it's still broken?  It might be nice to ssh in and grab dmesg when it's frozen if you can.
[03:23] <RAOF> Ok.  Looks like that *is* a known issue; just not known by me :)
[03:26] <RAOF> In fact, it seems like you may be the lucky owner of a VPCF11 laptop, which seems to be the only one having problems!
[03:26] <Sarvatt> whoa, weird timing
[03:27] <RAOF> hallyn: http://www.nvnews.net/vbulletin/showthread.php?t=155218
[03:27] <Sarvatt> There's a bug filed on panel detection problems on some VAIO laptops, so hopefully that's the same issue and it'll be fixed in a future release. For future reference, the bug number is #681330.
[03:28]  * Sarvatt wonders where bug #681330 is
[03:28] <ubot2> Sarvatt: Error: Bug #681330 not found.
[03:28] <RAOF> Although that's not *quite* the same as your error.
[03:29] <Sarvatt> that vaio F series is hell, remind me not to buy one! touchpads aren't working on VPC F13's because of the screwed up pnp names in the bios too
[03:30] <Sarvatt> hallyn: 256.xx works without a CustomEDID section on yours?
[03:30] <Sarvatt> hallyn: is yours a quad core?
[03:31] <Sarvatt> the dual cores are optimus
[03:32] <Sarvatt> just thinking the only way yours would have worked without a CustomEDID is if it was a quad since mobile quad's dont have optimus
[03:32] <hallyn> quad-core graphics chip?  how do i find out?
[03:32] <Sarvatt> quad core CPU
[03:32] <Sarvatt> is it an i7 xxxqm?
[03:32] <hallyn> well, 8 cores with hyperthreading
[03:32] <hallyn> yup
[03:33] <Sarvatt> yep, makes sense then
[03:34] <Sarvatt> that model specifically is broken on 260.xx right now, and just extra broken on the dual cores :(
[03:34] <hallyn> (really is hould stick with vesa driver...  all i need for wmii)
[03:34] <hallyn> RAOF: re-upgrade in progress
[03:34] <RAOF> That sounds like it may want to be release-noted
[03:35] <hallyn> Sarvatt: btw, i know i spent a lot of time in lucid trying to get CustomEDID stuff working, but not sure i needed it in maverick (and it never worked in lucid)
[03:35] <hallyn> and i can't recall where it got set
[03:36] <TheMuso> RAOF: Ah I was wondering why GUI performance especially in gnome-terminal was sluggish recently. Did a fresh install the other day, so am on nouveau atm, but must try the nvidia drivers again...
[03:36] <Sarvatt> you shouldn't need it, it's just for people with dual core variants because they have both intel and nvidia GPU's
[03:36] <hallyn> ah
[03:36] <RAOF> TheMuso: Yeah.
[03:36] <RAOF> Hm.  We're not testing final ISOs at this point, it seems?
[03:36] <Sarvatt> friday isn't it?
[03:36] <TheMuso> But things are going to be going into lockdown very very soon.
[03:37] <TheMuso> They have to get archive stuff done, which takes a while afaik, as well as mirrors.
[03:40] <hallyn> RAOF: after upgrade, it again failed, and i can't ssh into it (times out - and i dn't use network-manager...)
[03:40] <RAOF> Yay!
[03:40] <RAOF> Anyway, looks like you've found your solution.
[03:40] <hallyn> back after re-downgrade and 2 more reboots...
[03:40] <hallyn> sigh
[03:40] <hallyn> RAOF: thanks!
[03:52] <cyphermox> RAOF, hi
[03:53] <RAOF> cyphermox: Ho!
[03:53] <cyphermox> I can't find the wiki page for the remote X stuff with wifi on the command line, do you remember what it is ?
[03:53] <cyphermox> (I wanted to update it with nmcli info)
[03:53] <RAOF> Oh, thanks!
[03:55] <RAOF> Ok.  So, I should also link that page more prominantly, so that people can actually find it!
[03:55] <cyphermox> hehe
[03:56] <RAOF> https://wiki.ubuntu.com/X/Debugging/WirelessWithoutX
[03:56] <cyphermox> ah! awesome
[03:56] <cyphermox> I was so close too >.<
[03:57] <TheMuso> Poor conman users.
[03:58]  * RAOF hasn't seen the rationale for using that over writing a network-manager indicator :/
[03:58] <Sarvatt> hallyn: does nouveau work?
[03:59] <hallyn> Sarvatt: it didn't.  haven't' tried since lucid
[03:59] <RAOF> Sarvatt: That's fermi-class hardware, right?
[03:59] <Sarvatt> nope
[03:59] <RAOF> Oh, well, then it might :)
[03:59] <RAOF> You may even have reasonable 3D performance!
[03:59] <Sarvatt> it should work in maverick
[03:59] <TheMuso> RAOF: I remember hearing one somewhere, but can't remember details/where I heard it.
[04:00] <hallyn> hm, wirelesswithout x doesn't mention /etc/network/interfaces or wicd?
[04:00] <hallyn> i take it that's by design?
[04:00] <RAOF> You're welcome to add those in; I just added the common cases.
[04:00] <hallyn> ok, wasn't sure if you wanted to stick to 'recommended' methods
[04:01] <RAOF> No, you're welcome to add extra versions, as long as NM is at the top.
[04:01] <RAOF> (Because it covers almost everybody, and is really easy)
[04:10] <cyphermox> TheMuso, in fact, I added the little connman stuff I could from memory since I can't test it on this system
[04:12] <cyphermox> hallyn, I think it might be better to just link to other pages that already cover such stuff at some point
[04:13] <hallyn> RAOF: cool, i actually didn't know network manager had cli now.
[04:14] <RAOF> hallyn: That was cyphermox, actually.
[04:14] <cyphermox> hallyn, new in maverick ;)
[04:14] <hallyn> cyphermox: yeah, true
[04:14] <hallyn> (about the linking)
[04:14] <cyphermox> I wish you could create connections from there too, but I guess it's going to come to it
[04:15] <cyphermox> for natty I'll try to write some code so that's possible... aside from looking at having indicator-network do useful stuff with both NM and connman as backends
[04:15] <hallyn> ppl keep mentioning connman, haven't looked at it yet
[04:16] <cyphermox> hallyn, it's pretty nice on UNE. still kind of bare bones for the UI, but there's lots of work being done both there and in features upstream
[04:43]  * cyphermox -> S3
[07:05] <pitti> Good morning
[07:41] <kenvandine> good morning pitti
[07:44] <pitti> hey kenvandine, how are you? you're up late
[07:44] <pitti> that's a bad sign :)
[07:44] <kenvandine> getting sleepy :)
[07:44] <kenvandine> trying to make facebook happy
[07:45] <kenvandine> i think i might have figured out what is killing gwibber's allocation
[07:45]  * kenvandine is getting really sick of facebook mysteries
[08:07] <didrocks> good morning
[08:08] <Cimi> hi didier
[08:13] <didrocks> hey andrea, how are you?
[08:20] <Cimi> tired :D
[08:20] <Cimi> and it's 9 o clock
[08:20] <Cimi> not good :D
[08:29] <didrocks> :)
[08:59] <seb128> hello!
[08:59] <pitti> bonjour seb128
[08:59] <pitti> hey didrocks
[08:59] <seb128> hey pitti
[08:59] <didrocks> hey pitti, lut seb128
[08:59] <seb128> lut didrocks
[08:59] <seb128> how are you?
[08:59] <didrocks> I'm fine, thanks! ready for a testing day :)
[08:59] <didrocks> and you?
[09:01] <Cimi> hi seb
[09:02] <seb128> hey Cimi
[09:02] <seb128> didrocks, I'm fine thanks
[09:18] <didrocks> some people are reporting that evolution-indicator is broken on amd64, I unfortunatly don't have 64 bits machines to confirm :/
[09:18] <didrocks> bug #651933
[09:18] <seb128> how broken?
[09:18] <ubot2> didrocks: Bug 651933 on http://launchpad.net/bugs/651933 is private
[09:18] <seb128> I don't have amd64 installs either
[09:18] <seb128> I only use i386 there
[09:19] <seb128> but we probably have amd64 users on the channel
[09:19] <didrocks> seb128: like, no green icon when receving an email
[09:19] <seb128> is that limited to evolution?
[09:19] <seb128> ie do they get green icons for empathy messages for example?
[09:20] <didrocks> I'll ask on the bug report, it's not clear from the comments
[09:20] <mvo> I have a 64bit instlal, but don't use evo
[09:20] <mvo> can I still help?
[09:21] <didrocks> mvo: do you use empathy? :)
[09:21] <mvo> *cough
[09:21] <mvo> *
[09:21] <seb128> be careful as well with the evolution issue, I think it counts only emails in the inbox
[09:21] <seb128> mvo, do you use pidgin with the message indicator?
[09:21] <seb128> mvo, do you ever seen the envelop icon going green? ;-)
[09:21] <didrocks> yeah, only emails on the inbox. Not sure how to interpret "a new mail in inbox" from the reporter (is it his real inbox? :))
[09:22] <seb128> you can ask from a sceenshot and if there is a non 0 count in the indicator
[09:22] <mvo> I don't know, I don't look much at this menu
[09:22] <mvo> but I have started empathy now
[09:23] <seb128> mvo, you are not online?
[09:23] <seb128> or maybe I don't have you in my list
[09:24] <seb128> didrocks, well to be honest I never saw the indicator turn green for emails there
[09:24] <seb128> but I move most of my emails in subfolders on the server
[09:24] <seb128> on imap
[09:25] <didrocks> seb128: I got it when it's in my inbox
[09:25] <didrocks> (on imap)
[09:25] <seb128> when it arrives and evolution is not focussed only right?
[09:25] <seb128> or does it count unread email?
[09:25] <didrocks> right
[09:25] <seb128> like if you mark an email unread now does the indicator turn green?
[09:25] <didrocks> no, incoming emails only, when evolution isn't focussed
[09:25] <didrocks> when you click on evolution, whatever you do, it's reset to 0
[09:25] <seb128> ok, I don't think I ever do that, I go and click send&receive every now and then
[09:26] <didrocks> (which isn't a great experience IMHO)
[09:27] <seb128> mvo, did you connect to jabber?
[09:27] <mvo> seb128: it imported my data twice
[09:27] <mvo> seb128: now I'm connecting, sorry, that confused me a bit
[09:28] <mvo> my indicator is doing somehting
[09:28] <seb128> it's turning green?
[09:28] <seb128> do you have a seb128 line in it?
[09:28] <nisshh> mvo, it's indicating something?
[09:29] <mvo> seb128: yes
[09:29] <seb128> mvo, ok great, so it's not broken for everybody on amd64
[09:29] <seb128> mvo, thanks for testing
[09:30] <didrocks> thanks mvo :)
[09:31] <didrocks> so, it's either the users not knowing the limitation of evolution-indicator or there is a real bug on amd64
[09:32] <seb128> didrocks, I would say the user doesn't know how it work or desactivated the option in the evolution preferences
[09:32] <seb128> or uninstalled evolution-indicator
[09:32] <chrisccoulson> yay, another stick of RAM arrived at my house this morning \o/
[09:32] <chrisccoulson> good morning everyone
[09:32] <seb128> hey chrisccoulson
[09:32] <seb128> chrisccoulson: you will be able to start a RAM selling business rsn
[09:32] <seb128> if you keep this way ;-)
[09:33] <chrisccoulson> heh :-)
[09:33] <didrocks> well, they are giving the version in the bug report, so, I won't assume they remove it (and 2 people are confirming it on amd64)
[09:33] <didrocks> we'll see, I'll add a comment once launchpad is up again
[09:34] <seb128> didrocks, launchpad is back
[09:34] <didrocks> yeah, commenting :)
[09:35] <seb128> did you have to register again as well?
[09:39] <didrocks> yes
[09:40] <didrocks> hum, I can't branch…
[09:41] <didrocks> it's ok now
[09:46] <chrisccoulson> yay, it works \o/
[10:30] <seb128> chrisccoulson, how much ram do you have now?
[10:30] <chrisccoulson> seb128 - 4GB
[10:30] <seb128> what did you do with the sticks you couldn't use?
[10:31] <chrisccoulson> i've just got the extra sticks sitting on my desk now
[10:31] <chrisccoulson> will put them on ebay later ;)
[11:06] <nicolask> hi, anybody having problems of nautilus not working(not responding) after upgrade to rc Ubuntu 10.10?
[11:13] <seb128> mvo, hey
[11:13] <seb128> bug #655231
[11:13] <ubot2> Launchpad bug 655231 in update-notifier (Ubuntu) "should build without using GTK deprecations (affects: 1) (heat: 6)" [Wishlist,Confirmed] https://launchpad.net/bugs/655231
[11:13] <seb128> in case you didn't notice ;-)
[11:14] <mvo> seb128: that is merged already, no?
[11:14] <seb128> mvo, oh right, you just didn't update the bug status, doing that now
[11:14] <seb128> mvo, sorry for the noise
[11:14] <mvo> no problem
[11:15] <mvo> bug #655132 looks like something for you
[11:15] <ubot2> Launchpad bug 655132 in brasero (Ubuntu) "package libbrasero-media1 2.32.0-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/lib/brasero/plugins/libbrasero-audio2cue.so', which is also in package brasero 0:2.30.2-0ubuntu1 (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/655132
[11:15] <seb128> urg
[11:16] <seb128> didrocks, ^ do you think you could check on this one?
[11:16] <didrocks> seb128: sure
[11:16] <seb128> thanks
[11:48] <didrocks> seb128: ok, just had a look at brasero. Do you think it should be a 0 day SRU (as it's just for updates and people rely more on archives that CD I guess) or should we get it in final?
[11:48] <seb128> didrocks, you can try to upload now
[11:48] <seb128> seems they are not rolling isos yet
[11:48] <didrocks> seb128: ok, doing then
[11:48] <didrocks> thanks
[11:49] <seb128> didrocks, thank you!
[11:50] <seb128> rickspencer3, hey
[12:12] <rickspencer3> hi seb128
[12:16] <didrocks> hey rickspencer3
[12:16] <rickspencer3> hi didrocks\
[12:17] <chrisccoulson> hi rickspencer3
[12:17] <rickspencer3> hey chrisccoulson
[12:17] <rickspencer3> how is everybody?
[12:17] <rickspencer3> what's the work on the street?
[12:20] <didrocks> … working :) anything special, maverick looks very good. Preparing the first salve of SRU (and new Quickly released btw :))
[13:11] <cyphermox> hi
[13:11] <cyphermox> I have a branch ready for bug 621927, but launchpad isn't cooperating ;)
[13:11] <ubot2> Launchpad bug 621927 in xfce4-terminal (Ubuntu) (and 8 other projects) "Embedded Terminal Emulator isn't giving a TERM variable (affects: 68) (dups: 16) (heat: 364)" [Undecided,New] https://launchpad.net/bugs/621927
[13:13] <cyphermox> ah, chrisccoulson, I wanted to ask you about your opinion on this ^ essentially I'm setting TERM if it's unset as the terminals get initialize, so that should fix starting lxterminal, etc. from the menus. couldn't see an adverse effect on synaptic either
[13:15] <chrisccoulson> cyphermox, i'm not sure, i'd need to try and figure out how this is meant to work first
[13:18] <mvo> cyphermox: synpatic will set a TERM itself, so that should be fine
[13:19] <mvo> cyphermox: how is the synaptic port going btw?
[13:21] <chrisccoulson> i wish my keyboard would notify me when it's batteries are low
[13:21] <chrisccoulson> having the keyboard die suddenly can be quite surprising!
[13:23] <cyphermox> mvo, half-way done maybe
[13:25] <cyphermox> chrisccoulson, I've seen in one place qense mentioning apps using libvte should set TERM, but libvte is already messing around with TERM a lot. perhaps it really should be not touching it at all, or touching it, either way setting the emulation should translate in setting TERM as well to let cli apps know what emulation is used
[13:28] <mvo> cyphermox: don't hesitate to push a half-done branch
[13:28] <cyphermox> I will shortly, most likely
[13:29] <cyphermox> plan today is head to the office in a couple of minutes to work on this and look at a NM/resolv.conf bug someone is having
[13:29] <cyphermox> lp is still scanning the branch :/
[13:40] <mterry> seb128, another good gtk3 migration flag: -DGTK_DISABLE_SINGLE_INCLUDES
[13:41] <seb128> mterry, oh right ;-)
[13:41] <seb128> I've opened a bunch of extra bugs today
[13:41] <mterry> seb128, I saw, I'm going through
[13:44] <seb128> is there somebody with upload rights to universe who want to work on bug #654392?
[13:44] <ubot2> Launchpad bug 654392 in tracker (Ubuntu) (and 1 other project) "package deskbar-applet 2.30.0-0ubuntu1 failed to install/upgrade: trying to overwrite directory '/usr/lib/deskbar-applet/deskbar-applet' in package libdeskbar-tracker 0.6.95-1ubuntu6 with nondirectory (affects: 8) (dups: 7) (heat: 66)" [High,Triaged] https://launchpad.net/bugs/654392
[13:46] <hallyn> is https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia/Nouveau still the right way in maverick to try out nouveau if i'm currently using nvidia drivers?
[13:46] <seb128> hallyn, hey, try asking on #ubuntu-x
[13:46] <hallyn> doh
[13:46] <hallyn> thanks
[13:46] <seb128> np ;-)
[13:49] <bilalakhtar> seb128: yes I can work on that
[13:49] <seb128> bilalakhtar, thanks
[13:49] <seb128> bilalakhtar, could you assign the bug to yourself to make sure nobody else start working on it?
[13:49] <seb128> mvo, ^
[13:50] <bilalakhtar> seb128: okay, well, does this thing affect both packages?"
[13:50] <seb128> bilalakhtar, cf #ubuntu-devel
[13:51] <bilalakhtar> seb128: seen
[13:52] <mvo> seb128, bilalakhtar: given that libdeskbar-tracker is not build anymore it seems like the simpletst solution is to just add a conflict to ensure the package gets removed on upgrade
[13:52] <bilalakhtar> Thanks mvo , will do just that
[13:53] <chrisccoulson> bilalakhtar, it shouldn't require any tracker changes
[13:54] <bilalakhtar> chrisccoulson: yes, just realised that, un-assigning myself and invalid-ing it
[13:59] <seb128> kenvandine, hey
[13:59] <bilalakhtar> seb128: This is a desktop package. I guess I will need to get the change in the bzr branch as well, right?
[14:00] <seb128> bilalakhtar, no, just drop the vcs in control if there is one
[14:00] <seb128> it's there from the time deskbar-applet was in the default installation
[14:00] <seb128> it doesn't make sense now that's it's in universe
[14:00] <bilalakhtar> seb128: ah, yeah, I will
[14:01] <seb128> bilalakhtar, thanks
[14:01] <bilalakhtar> seb128: you're welcome
[14:01] <seb128> mterry, is libdbusmenu one of those libraries that will need to be built with gtk2 and gtk3? I guess so?
[14:01] <seb128> mterry, do you want to work on that while you are on it?
[14:02] <mterry> seb128, yup, am doing so now  :)  adding --with-gtk=2 or 3
[14:02] <seb128> great
[14:08] <seb128> rickspencer3, wb
[14:09] <seb128> rickspencer3, sorry I was at lunch when you replied before, no concerning issues with maverick it seems
[14:14] <bilalakhtar> mvo, seb128: Uploaded, now waiting for an AA to approve it
[14:14] <seb128> bilalakhtar, thanks
[14:15] <bilalakhtar> seb128: you're welcome, after all, my aim is to be an ubuntu-desktop'er!
[14:15] <seb128> ;-)
[14:15] <kenvandine> hey seb128
[14:15] <seb128> kenvandine, how are you?
[14:15] <kenvandine> tired... and you? :)
[14:16] <seb128> I'm fine thanks
[14:16] <seb128> kenvandine, you do filter out bugs you are directly subscribed to right?
[14:16] <kenvandine> yes
[14:16] <seb128> kenvandine, I've subscribed you and ted to some indicator-me bugs
[14:16]  * kenvandine looks
[14:16] <seb128> would be nice if you could comment on those when you have some time
[14:16] <seb128> thanks
[14:19] <kenvandine> will do
[14:21] <kenvandine> seb128, bug 634957 , we had left that against indicator-applet because tedg wants a more generic way to fix it
[14:21] <ubot2> Launchpad bug 634957 in indicator-applet (Ubuntu) (and 1 other project) "Messaging menu not grabbing gwibber tray icon quickly enough (affects: 1) (heat: 6)" [Low,Invalid] https://launchpad.net/bugs/634957
[14:23] <kenvandine> ted wants to investigate fixing it somewhere in the indicator stack
[14:23] <seb128> kenvandine, ok, feel free to reopen adding a comment then
[14:23] <kenvandine> i am
[14:23] <seb128> it was not clear from it
[14:23] <seb128> well the applet seems wrong
[14:23] <kenvandine> yeah... well he should have commented on the bug :)
[14:23] <kenvandine> yeah, probably libindicate
[14:23] <seb128> can you reassign as well?
[14:23] <seb128> I'm trying to clean the applet list to not be a collection of bugs for other part of the stack
[14:23] <kenvandine> yeah
[14:24] <seb128> thanks
[14:24] <kenvandine> i know their bugs are a mess
[14:36] <chrisccoulson> hmmm, we're making firefox crash somehow :/
[14:36] <chrisccoulson> http://crash-stats.mozilla.com/report/index/3b7f5056-23ad-48a1-9c27-655422101006
[14:36] <chrisccoulson> all from ubuntu users
[14:38] <seb128> chrisccoulson, well at least it shows the crash submitting works ;-)
[14:39] <chrisccoulson> seb128 - yeah, unfortunately the stack traces aren't useful due to another bug on the mozilla side
[14:39] <chrisccoulson> but, i can recreate the crash anyway
[14:39] <chrisccoulson> it seems all the reporters are running maverick
[14:39] <seb128> you can recreate it? how?
[14:41] <seb128> chrisccoulson, where do you see the stacktrace or duplicates?
[14:41] <chrisccoulson> seb128 - just visiting code.google.com/webfonts ;)
[14:42] <seb128> I don't think I want to crash my browser :p
[14:42] <chrisccoulson> seb128 - if you click the "Comments" tab, it shows a list of people who left comments, with a link to their reports
[14:42] <seb128> where does it crash? in which function I mean
[14:42] <chrisccoulson> not sure yet, i'm just about to run it through GDB
[14:43] <seb128> ok, they all have it crashing on the same website
[14:45] <kenvandine> chrisccoulson, i got 2 crashes on our stackexchange site too
[14:45] <chrisccoulson> kenvandine, you mean that you got the browser to crash as well?
[14:45] <chrisccoulson> did you submit those crash reports?
[14:45] <kenvandine> yeah, and yes
[14:46] <chrisccoulson> could i have the crash ID?
[14:46] <kenvandine> i think it was last weekend
[14:46] <chrisccoulson> about:crashes
[14:46] <kenvandine> one sec
[14:46] <kenvandine> doh!
[14:46] <kenvandine> No crash reports have been submitted.
[14:46] <chrisccoulson> lol
[14:46] <kenvandine> i chose to submit them...
[14:46] <chrisccoulson> hmmm, that's strange
[14:46] <kenvandine> but then my browser just restarted...
[14:46] <chrisccoulson> you haven't cleaned anything in your profile have you?
[14:47] <kenvandine> i had thought it was fishy that it doesn't ask me anything
[14:47] <kenvandine> oh... actually it might have crashed in a VM
[14:47]  * kenvandine can't remember anymore
[14:47] <chrisccoulson> ah :)
[14:48] <kenvandine> and i trash my VMs every monday :/
[14:48] <kenvandine> i think it was on voting on answers
[14:48] <kenvandine> happened twice in the same day, i think saturday
[15:08] <cyphermox> so it looks like LP isn't ready to scan my branch yet... could someone review/merge https://code.edge.launchpad.net/~mathieu-tl/vte/lp621927 to lp:~ubuntu-desktop/vte/ubuntu ? This is to fix bug 621927
[15:08] <ubot2> Launchpad bug 621927 in xfce4-terminal (Ubuntu) (and 8 other projects) "Embedded Terminal Emulator isn't giving a TERM variable (affects: 68) (dups: 16) (heat: 364)" [Undecided,New] https://launchpad.net/bugs/621927
[15:15] <mdeslaur> pitti: ha! just noticed your GPG key contains your picture! :)
[15:16] <seb128> hey cyphermox
[15:16] <cyphermox> hey seb128
[15:16] <seb128> chrisccoulson, mvo: ^ could you review the fix cyphermox worked on?
[15:16] <seb128> you know the code a bit
[15:17] <cyphermox> I'd gladly make a merge request but the branch isn't scanned yet... otherwise I can make a debdiff
[15:17] <pitti> mdeslaur: yeah, wanted to play with that, and it's easy to sign if you know me :)
[15:17] <seb128> I guess people can still get it and locally diff?
[15:17] <cyphermox> seb128, yeah
[15:17] <seb128> should be alright then
[15:18] <mdeslaur> pitti: darn, now I have to import your picture into my fake pitti gpg key :)
[15:18] <pitti> happy gimping
[15:20] <mvo> seb128: sure, once I can get a diff from it
[15:20] <seb128> mvo, well you can checkout and diff locally
[15:20] <seb128> it seems launchpad is having issues
[15:22] <cyphermox> seb128, db python upgrade or something, apparently
[15:30] <mterry> mdeslaur, I share your frustration with the annoying upgrade treadmill of faking pitti's identity
[15:30] <mdeslaur> mterry: lol :)
[15:30] <pitti> guess why I renewed my key
[15:31] <pitti> so that you now have 4096 bits to crack instead of 1024
[15:31] <mdeslaur> pitti: yeah, I had to update my trojaned windows distributed cracking screensaver
[16:13] <mvo> cyphermox: the patch for vte looks good
[16:15] <cyphermox> mvo: cool
[16:16] <cyphermox> mvo: I wish it was better, but looking at the vte code I don't quite agree with how it's been done in general, but the changes I'd make are much bigger than this ;)
[16:22] <mvo> cyphermox: heh :) no worries, vte is "interessting", thats for sure
[16:26] <cyphermox> hehe yeah ;)
[16:28] <cyphermox> mvo: btw, in progress branch for synaptic: lp:~mathieu-tl/synaptic/porting-to-gtkbuilder
[16:29] <chrisccoulson> i'm finding pango quite "interesting" too ;)
[16:31] <cyphermox> I haven't had a "chance" to touch pango yet ;)
[16:31] <mvo> cyphermox: cool
[16:56] <OwaisL> w
[16:56] <OwaisL> w.h
[18:13] <njin> ara: already in rebuild 201006.1 ?
[18:13] <ara> njin, it was a problem with the build itself, not with bugs
[18:13] <njin> ops 20101006.1
[18:14] <njin> ok for me work
[18:14] <njin> ara:thanks
[18:37] <didrocks> sport + dinner, bb in an hour or so
[18:39] <chrisccoulson> now it's time to see if the extra 2GB of RAM makes a difference with a firefox build
[18:41] <seb128> didrocks, sport?
[18:41] <seb128> didrocks, you? ;-)
[18:41] <seb128> mvo, nice catch for this gconf upgrade issue
[18:46] <mvo> seb128: I just commited a fix
[18:46] <mvo> seb128: could you double check the branch please?
[18:46] <mvo> seb128: jibel deserves all the credit, I just did the easy fixing :)
[18:47] <mvo> seb128: commited it to bzr+ssh://bazaar.launchpad.net/~ubuntu-desktop/gconf/ubuntu/
[18:47] <mvo> seb128: if it looks ok, just upload or I will do it when I'm back (in ~45min or so)
[18:48] <seb128> mvo, seems fine to me
[19:01] <njin> ara: the tracker is closed
[19:20] <kenvandine> seb128, your going to set launchpad on fire today!
[19:21] <jcastro> seb128: I think he's doing all the work tedg hasn't been doing
[19:30] <kenvandine> hehehe
[19:30] <seb128> kenvandine, right, what jcastro said
[19:31] <seb128> kenvandine, sorry you got subscribed to indicator bugs as well but since dx seems to need to be pushed to work on things... ;-)
[19:32]  * kenvandine will help nag them :)
[19:39] <seb128> kenvandine, thanks ;-)
[19:44] <mterry> seb128, https://code.launchpad.net/~mterry/indicator-appmenu/deprecations/+merge/37777
[19:44] <seb128> tedg, bratsche: ^
[19:46] <seb128> mterry, great ;-)
[19:46] <tedg> Woot, a single function!  That's better than I thought we'd be :)
[19:46] <tedg> Thanks mterry!
[19:46] <mterry> tedg, yeah, that was an easy one  :)
[19:47] <seb128> seems we will get the indicator stack cleaned before UDS
[19:47] <seb128> mterry, great work ;-)
[19:48] <mterry> thx
[19:48] <seb128> mterry, let me know if have other things you would work on or would prefer to start work on python with gir or something
[19:48] <seb128> I sort of tried to set tasks which allow us to work on maverick without needing gtk3 or new packages until UDS
[19:48] <mterry> seb128, I've been doing a few other things too.  Like writing vala-dep-scanner (https://launchpad.net/vala-dep-scanner) for the quickly vala template.  :)
[19:49] <seb128> mterry, excellent ;-)
[19:49] <seb128> mterry, well feel free to pick in anything you think is useful
[19:49] <mterry> seb128, yeah.  I've been chomping at the bit to do the gtk3 conversion though.  This deprecation work leaves me feeling incomplete.  :)
[19:49] <seb128> I'm setting those gnome3 clean tasks as a todolist for those who want
[19:49] <seb128> but I'm not opposed to people to pick on other tasks
[19:50]  * mterry waits for natty to open
[19:50] <seb128> mterry, we need to port things to gsettings as well
[19:50] <seb128> if you like that better
[19:50] <mterry> seb128, oh yeah...  guh, that's like real work.  :)  I recently did deja-dup, so I am a bit familiar.  I could give it a go.  Have you started tagging such bugs?
[19:51] <seb128> mterry, otherwise feel free to start on desktop merges locally or to get gtk3 from debian pkg-gnome svn and start updating libindicate, etc for multi builds
[19:51] <seb128> mterry, no, I did the gtk3 ones today, I will start on the gsettings one tomorrow
[19:51] <seb128> mterry, by time you wake up I will have a list you can use to pick tasks for those
[19:51] <seb128> ;-)
[19:52] <seb128> we need to maintain a tasklist somewhere
[19:52] <mterry> k.  still plenty of deprecation work in the meantime
[19:52] <seb128> we have several porting lists now, the versions in the title, merges and, gtk3 builds
[19:52] <seb128> well maybe I should try to get gtk3 in a ppa
[19:52] <seb128> then we start updating GNOME libs to do gtk2 and gtk3 builds
[19:53] <seb128> we should work with debian on that though to make sure they take the same packaging
[19:53] <seb128> I'm not sure if we should have 2 sources
[19:53] <seb128> or 2 builds from the same source
[19:54] <mterry> seb128, I've seen packages build twice from the same source.  It didn't seem too complicated
[19:54] <cdbs> Have GNOME upstreams began their migration to gtk3?
[19:54] <mterry> cdbs, yeah, this week was 2.91.0 tarballs, which *should* use gtk3
[19:55] <cdbs> mterry: ah
[19:56] <seb128> mterry, right, multi build is not really hard
[19:56] <seb128> we do in a few packages
[19:56] <seb128> I guess it depends if libs have a build time choice for the gtk to use
[19:57] <seb128> or if one serie is using gtk2 and the new one gtk3, in which case they are different sources
[19:58] <seb128> well my gut feeling is that we should stay in porting tasks for this week until maverick
[19:58] <seb128> then let's see when next distro open and we can start on merges from debian and updates
[19:59] <mterry> seb128, https://code.launchpad.net/~mterry/indicator-messages/deprecation/+merge/37778
[19:59] <seb128> another easy one? ;-)
[19:59] <mterry> yar
[19:59] <seb128> hum annoying that launchpad diff are still broken
[20:00] <mterry> seb128, oh, it will show up, just takes a sec
[20:00] <mterry> or at least that was true earlier today
[20:00] <mterry> recent breakage?
[20:00] <seb128> it seems they break things during the downtime earlier today
[20:00] <seb128> but that was before you were up so if it worked for you they probably fixed it
[20:01] <seb128> https://code.launchpad.net/~mterry/indicator-appmenu/deprecations/+merge/37777 is still not done though
[20:01] <seb128> well rather it failed it seems
[20:01] <mterry> hrm, yeah
[20:01] <seb128> it might be broken until tomorrow's downtime for the remaining update they have to do
[20:02] <didrocks> seb128: how insulting!!! :-)
[20:02] <didrocks> but fair ;)
[20:02] <seb128> didrocks, ;-)
[20:03] <seb128> slomo_, what is missing for gtk3 in debian?
[20:11] <didrocks> mterry: also, if you want to begin some Quickly works, I have suggestion of stuff that will be planned for next cycle too :-) (like refactoring the ubuntu-application code, or adding testsuite, or adding the Quickly pluginto gedit :))
[20:12] <mterry> didrocks, yeah, I've been meaning to sit down and look at a test suite
[20:12] <didrocks> that would be awesome :)
[20:12] <mterry> didrocks, seb128 just has all this fun work to do
[20:12] <didrocks> sure, I was just wondering if you just lacked of Quickly tasks or if seb128 was stealing you :p
[20:13] <seb128> mterry, well fell free to select yourself tasks you think you should work on
[20:13] <seb128> I think there is no hurry right now
[20:13] <mterry> yar
[20:13] <didrocks> (kidding of course on stealing :-))
[20:16] <seb128> mterry, speaking of which, are you interest in maintaining glade
[20:16] <seb128> ups
[20:16] <seb128> glade3, anjuta stack, gedit
[20:17] <slomo_> seb128: same as last time... copyright file, making sure that everything is built correctly and put into the correct binary packages and dpkg-diverts for debian/gtk-config.1 and debian/update-icon-caches
[20:18] <mterry> seb128, I could.  It's not something I dreamed of as a kid, but I suppose that speaks more to my lack of imagination than anything.
[20:18] <seb128> slomo_, do you plan to have any time in the next weeks to finish that?
[20:18] <seb128> mterry, is there anything you dreamed of as a kid that match our team tasks? ;-)
[20:18] <didrocks> (porting to gtk3) :-)
[20:19] <mterry> seb128, don't make me feel bad for being a dumb kid
[20:19] <seb128> if the tasks match what people want it's better ;-)
[20:19] <slomo_> seb128: not really, i'm very busy at the moment... maybe i find some time for it but don't wait for me to do it :)
[20:19] <seb128> slomo_, ok, I might pick the current packaging and put in a ppa to see how it goes
[20:19] <cyphermox> mterry, that probably makes me a very weird kid, dreaming of maintaining network-manager ;D
[20:20] <mterry> seb128, but sure, I can take on glade
[20:20] <mterry> cyphermox, :)
[20:20] <slomo_> seb128: should be fine after adding the diversions, the main thing that keeps me from finishing the package is the copyright file
[20:21] <seb128> slomo_, I'm not sure I care about the diversions, nobody is going to remove gtk2 any time
[20:21] <seb128> so I can just make gtk3 not ship them for now
[20:21] <seb128> it would allow people to get started on doing multi build for the others libs ;-)
[20:21] <seb128> gnome-desktop etc
[20:21] <slomo_> seb128: then you have to make sure that gtk3 depends on gtk2 for that update script ;)
[20:22] <seb128> well I just want a ppa people can use for porting
[20:22] <seb128> so it can be a bit broken
[20:23] <seb128> but as said I don't see anybody removing gtk2 in the next years
[20:23] <seb128> or next year
[20:23] <seb128> ;-)
[20:23] <jcastro> even motif is still around, so don't sweat it
[20:35] <seb128> mterry, when you start on a bug could you set the ubuntu task in progress?
[20:35] <seb128> ^ others as well
[20:35] <seb128> this way we can spot easily in https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=gnome3-gtk3 what is being worked
[20:35] <seb128> this list or similar ones ;-)
[20:35] <mterry> seb128, yeah...  OK.  I wasn't working on the ubuntu side of those bugs, but I understand why it's convenient
[20:36] <mterry> not that I was setting the upstream task to in progress either...
[20:36] <seb128> well we often abuse the ubuntu task status
[20:37] <seb128> like we set it to fix commited when the fix lands in the upstream vcs
[20:37] <seb128> it makes easier to notice what will be fixed in the next upload or has a fix to backport
[21:20]  * didrocks waves goodnight
[21:20] <fagan> night didrocks
[21:21] <didrocks> night fagan
[21:21] <fagan> oh oh oh bon nuit is better :)
[21:21] <didrocks> almost: "bonne nuit" :)
[21:21] <fagan> hehe damn so close
[21:22] <fagan> im better at speaking it than spelling it
[21:34] <chrisccoulson> well, i might have to think of some more blueprints for natty :/
[21:35] <seb128> chrisccoulson, don't overwork yourself
[21:35] <seb128> chrisccoulson, which ones are you thinking about currently?
[21:35] <chrisccoulson> seb128 - i already created 3 - with the firefox-4 transition likely to take up most of my time
[21:36] <chrisccoulson> but i've nearly done one of them ;)
[21:36] <micahg> chrisccoulson: do you think I should readd my apport blueprint from last cycle, I still have the notes
[21:37] <chrisccoulson> micahg - yeah, can do
[21:37] <seb128> chrisccoulson, which ones?
[21:37] <seb128> chrisccoulson, you will probably be enough to do with the new firefox, cleaning fonts and some GNOME tasks
[21:38] <chrisccoulson> seb128 - other-desktop-n-thunderbird-messaging-indicator, other-desktop-n-firefox-4 and other-desktop-n-firefox-pgo-builds
[21:38] <chrisccoulson> the latter one will probably be done before we go to UDS
[21:39] <micahg> chrisccoulson: do you mind if I send a message to the -devel list about the Mozilla team's sessions to get them on the radar?
[21:39] <chrisccoulson> micahg - yeah, that's ok
[21:40] <micahg> chrisccoulson: what do you think of TB on top of xul?
[21:44] <chrisccoulson> micahg - i'm not sure. can thunderbird actually build with libxul?
[21:44] <micahg> chrisccoulson: not yet, it's in progress though
[21:44] <chrisccoulson> seb128 - rick also created a thunderbird one - appselection-n-thunderbird-on-ubuntu
[21:45] <chrisccoulson> i guess we could just use the one blueprint though
[21:45] <seb128> chrisccoulson, I guess that's about the default email client
[21:46] <chrisccoulson> seb128 - yeah, i'm not too sure about the scope of that
[21:55] <chrisccoulson> seb128 - the extra 2 GB of RAM really makes a difference
[21:56] <chrisccoulson> i can actually use my laptop whilst doing a large build now :)
[21:56] <kklimonda> chrisccoulson: how much do you have?
[21:56] <seb128> chrisccoulson, great
[21:56] <chrisccoulson> kklimonda, 4GB now
[21:57] <kklimonda> chrisccoulson: man, you were working on Firefox with only 2GB before? How did you cope? Do you have a second computer to do anything when Firefox is building? ;)
[21:57] <chrisccoulson> kklimonda, it was a struggle
[21:57] <seb128> enough work for today, night everybody
[21:57] <chrisccoulson> 'night seb128
[22:01] <JanC> several years ago I have built firefox on a Compaq Armada Pentium MMX with 64 MiB RAM a couple of times, and I could still surf the net while doing that, so 2 GiB should be plenty  ;)
[22:02] <JanC> (okay, it took hours to build...)
[23:08] <zyga> is it just me or is copy-paste broken when you are running unity?
[23:08] <zyga> to be precise
[23:08] <zyga> copy-paste from non gnome-terminal to gnome-terminal
[23:09] <zyga> for me, the only method that works is <select in firefox> <rightclick> <copy> <rightclick in gnome terminal> <paste>
[23:09] <zyga> no keyboard shortcuts work
[23:09] <zyga> doing the same operation from the menu also does not work
[23:19] <devildante> !bugs | zyga
[23:20] <zyga> devildante, eh, ok :-P
[23:20] <zyga> devildante, I know you are right
[23:20] <devildante> haha
[23:20] <zyga> devildante, I just wanted to rule out something specific to my setup while working past midnight trying to get my stuff done
[23:21] <devildante> ah
[23:21] <devildante> okay, then, bye all :)