=== bjf is now known as bjf[afk]
[03:10] <robert_ancell> TheMuso, I've uploaded a pygi package - are you able to "add it to the overrides"?
[03:23] <robert_ancell> I think that means it's in the new queue
[03:31] <TheMuso> robert_ancell: I am not an archive admin.
[03:33] <robert_ancell> TheMuso, where can I find the list of archive admins?
[03:34] <micahg> robert_ancell: https://wiki.ubuntu.com/ArchiveAdministration#Archive days
[03:36] <robert_ancell> TheMuso, thanks
[03:58] <TheMuso> robert_ancell: np
=== pgraner is now known as pgraner-afk
=== almaisan-away is now known as al-maisan
[07:54] <didrocks> good morning
[08:51] <baptistemm> helllo
[08:53] <didrocks> hey baptistemm, how are you?
[08:53] <baptistemm> ca va
[08:53] <seb128> hey didro
[08:53] <seb128> didrocks,
[08:53] <didrocks> salut seb128, ça va ?
[08:54] <seb128> oui, nickel, toi ?
[08:54] <baptistemm> just a little bit borred since 3 weeks, not a lit of will to do some ubuntu taks I wanted to do
[08:54] <didrocks> seb128: ça va, blackout internet (freebox ne se synchronisait plus) à partir de 22h, mais heureusement, ce matin, c'est réparé
[08:55] <didrocks> contacté le service technique dans une fenêtre javascript à partir du browser de mon portable en 3G :)
[08:55] <baptistemm> ca permet de faire un break l anuit: à)
[08:55] <didrocks> baptistemm: ouai, enfin tout de suite, c'était "comment je vais bosser demain ?" ;)
[09:23] <didrocks> baptistemm: I can't pair my bluetooth headset in maverick (when I click on "configure a new device" I get notice), any command line I can trigger to debug this?
[09:25] <baptistemm> You means the discovery doesn't list your device ?
[09:25] <baptistemm> -s
[09:28] <didrocks> baptistemm: the command line (hcitool) does, but not the indicator/applet (nothing happen when I click to configure)
[09:29] <didrocks> baptistemm: do you know where the local data are stored for bluetooth-applet? (the current paired-list)? Maybe an incompatible format as I kept my /home for reinstalling
[09:29] <didrocks> uncompatible*
[09:31] <baptistemm> didrocks, this is system-wide in /var/lib/bluetooth/xx:xx:xx:xx:xx/
[09:31] <baptistemm> sorry I'm on a call
[09:31] <didrocks> baptistemm: no pb, thanks a lot already, looking if I can get something :)
[09:37] <didrocks> baptistemm: ok, I got the dialog after removing what was on that directory the second time. I'll recheck later again with a clean config. Thanks for the help :)
[10:22] <didrocks> seb128: btw, I pushed mutter yesterday evening if you didn't notice
[10:23] <seb128> I did noticed
[10:23] <seb128> thanks
[10:26] <didrocks> you're welcome
[10:37] <seb128> hey chrisccoulson
[10:37] <seb128> how are you?
[10:37] <chrisccoulson> hey seb128, i'm good thanks. how are you?
[10:37] <seb128> I'm fine thanks
[10:39] <didrocks> good morning chrisccoulson
[10:39] <chrisccoulson> hey didrocks, how are you?
[10:40] <didrocks> chrisccoulson: I'm fine thanks :-)
[10:41] <didrocks> chrisccoulson: I hope soon some testing on your workaround for the panel corruption from ubuntu-fr users :)
[10:43] <seb128> what workaround?
[10:44] <chrisccoulson> didrocks - that didn't work ;)
[10:45] <didrocks> chrisccoulson: oh really? :-(
[10:45] <didrocks> seb128: it was unactivating gtk managing itself the sub X window
[10:45] <chrisccoulson> didrocks - yeah, i was just clutching at straws there - i tried it and didn't see the issue, so i asked other people to try it too
[10:46] <chrisccoulson> and they still got the issue
[10:46] <didrocks> (GDK_NATIVE_WINDOWS)
[10:46] <didrocks> ok
[10:46] <didrocks> and deactivating the lazy load of nm applet has been already tried too?
[10:47] <seb128> the bug has reported in karmic
[10:47] <seb128> which was not doing lazy loading
[10:47] <chrisccoulson> i'm not sure it's related to nm-applet really. i've seen the corruption on pretty much every applet
[10:47] <seb128> has been reported
[10:49] <didrocks> seb128: right, apparently it's just triggering it more often (from the bug report comment, didn't try it myself)
[10:49] <didrocks> but yeah, that's not the root cause
[10:49] <seb128> or we have higher number of users on the lts
[10:50] <seb128> it's really something we should fix but I'm not sure how to debug it
[10:51] <didrocks> yeah, tricky. I got it very often on my netbook (small screen size related?) but almost never on my laptop.
[10:51] <chrisccoulson> didrocks - i get it on my desktop too (with a 22" screen) ;)
[10:52] <didrocks> chrisccoulson: that's because you are a power user :-)
[10:52] <chrisccoulson> lol
[10:52] <didrocks> and it tries to be nice with you, like "debug me… please"
[10:52] <chrisccoulson> i need to attach the 22" screen to my laptop really, and give joanne the 20" screen
[10:52] <chrisccoulson> i wonder if she'll notice
[10:52] <seb128> lol
[10:52] <didrocks> :)
[10:53] <seb128> it's a risky move, she might notice and you might pay back ;-)
[10:53] <chrisccoulson> lol
[10:54] <didrocks> I had a look at 22" screens recently to buy one. But most of them have the same resolution than the one to my 17" laptop (1920x1200), so I'm not so motivated to change…
[10:54] <chrisccoulson> yeah, my 22" has the same resolution as the 20"
[10:54] <chrisccoulson> but it is easier to see things ;)
[10:54] <seb128> well it's still nicer for your eyes
[10:55] <seb128> I'm much less tired on a my desktop screen than on the laptop one
[10:56] <didrocks> seb128: yeah, I feel really tired during the evening when I look at subtitles and I can't read. So I'll change in any case, but only once I've moved to Lyon :)
[10:57] <didrocks> so for that, it makes sense if you tell me your eyes notice the difference
=== agateau___ is now known as agateau
[13:11] <aquarius> seb128, I want to add a gconf key from the music store RB plugin which directs u1ms:// URLs to Rhythmbox. debian/rhythmbox-ubuntuone-music-store.gconf-defaults can have "/desktop/gnome/url-handlers/u1ms/command	'rhythmbox "%s"'", but...do I have to add a schema somewhere else that creates that key?
[13:11] <seb128> aquarius, it's not required
=== al-maisan is now known as almaisan-away
[13:12] <seb128> it would give you descriptions for the key
[13:13] <aquarius> seb128, how does gconf know what type the key is? it guesses based on the value?
[13:14] <seb128> aquarius, you need to specify the type when you set it
[13:14] <seb128> the gconf-defaults system do it for you
[13:14] <aquarius> seb128, that's what I don't understand, though. The current debian/rhythmbox-ubuntuone-music-store.gconf-defaults has one line in it: /apps/rhythmbox/plugins/umusicstore/active	true
[13:14] <aquarius> which doesn't specify a type
[13:15] <seb128> true is a bollean
[13:15] <seb128> l->o
[13:15] <seb128> gconf-defaults try to be smart about that
[13:15] <aquarius> ah, so the gconf-defaults system looks at the value and works out what the type must be. cool. :)
[13:15] <seb128> yes
[13:16] <aquarius> right, then I shall add my two extra lines and it's all good. yay.
=== kenvandine_ is now known as kenvandine
[13:55] <ccheney> good morning
=== pgraner-afk is now known as pgraner
[14:03] <kenvandine> good morning ccheney
=== bjf[afk] is now known as bjf
[15:47] <seb128> aquarius, you might want to do your changes over maverick and not lucid
[15:48] <aquarius> ah crap did I just propose the packaging branch change against the lucid version?
[15:49] <aquarius> I am so stupid.
[15:49] <aquarius> kenvandine, sorry
[15:49] <aquarius> so I want to propose the merge against lp:ubuntu/maverick/rhythmbox-ubuntuone-music-store, yes, kenvandine?
[15:50] <aquarius> seb128, thanks :)
[15:51] <seb128> aquarius, you're welcome
[16:07] <kenvandine> seb128, the maverick branch doesn't exist, do i just push to that?
[16:08] <seb128> use lp:ubuntu/<source> it should work? or check with james_w
[16:08] <kenvandine> it doesn't
[16:08] <kenvandine> james_w, ^^
[16:08] <kenvandine> well, it does... but it looks like the lucid branch
[16:08] <kenvandine> actually it doesn't
[16:08] <kenvandine> bzr: ERROR: Invalid url supplied to transport: "lp:ubuntu/rhythmbox-ubuntuone-music-store": rhythmbox-ubuntuone-music-store in ubuntu has no default branch.
[16:09] <james_w> give me a moment, I'm on a call
[16:09] <kenvandine> ok
[16:09] <kenvandine> thx
[17:23] <Laney> didrocks: I think I'm just going to request a sync of banshee now
[17:24] <Laney> any objections?
[17:24] <didrocks> Laney: just one sec, was going to ping jcastro about that
[17:24] <jcastro> yo
[17:24] <didrocks> jcastro: do you know about upstream plan for new banshee ? (stable release date, and so on)
[17:24] <didrocks> hey btw :)
[17:24] <Laney> they have a calendar up
[17:24] <jcastro> didrocks: it's following GNOME now
[17:24] <Laney> it follows the gnome schedule
[17:25] <didrocks> sweet, so perfect, no objection Laney for syncing, thanks
[17:25] <jcastro> nice, is this for 1.6.1?
[17:25] <seb128> jcastro, no, 1.7
[17:25] <jcastro> oh
[17:25] <seb128> Laney, I can do the sync for you now
[17:25] <didrocks> jcastro: yeah, with all the new goodness :)
[17:25] <Laney> seb128: ok cool, it's from experimental
[17:25] <Laney> seb128: and will need binary NEWing
[17:25] <seb128> ok
[17:26] <jcastro> if anyone wants to help I think hyperair need some acks for the SRU for 1.6.1 in lucid.
[17:26] <didrocks> seb128: btw, if you can do a binary NEWing row, mutter needs love :)
[17:26] <hyperair> jcastro++
[17:28] <hyperair> bug #585761
[17:28] <ubot2> Launchpad bug 585761 in banshee (Ubuntu Lucid) (and 1 other project) "[SRU] Banshee 1.6.1-1 New upstream bugfix release (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/585761
[17:32] <Laney> hyperair: you subscribed the wrong team, it's ubuntu-sru now
[17:33] <hyperair> Laney: oh whoops.
[17:33] <seb128> you don't need acks before upload
[17:33] <Laney> hyperair: are you sruing podsleuth too?
[17:33] <Laney> (if not, please do)
[17:34] <hyperair> Laney: yes, but i haven't gotten roudn to filing the bug
[17:34] <Laney> no probs
[17:34] <seb128> Laney, synced
[17:35] <Laney> thanks a lot
[17:37] <jcastro> Laney: so it's likely been sitting there the whole time due to a bad tag?
[17:39] <seb128> jcastro, it should be uploaded, it's not a tag issue
[17:39] <seb128> requires somebody to sponsor the upload
[17:39] <Laney> motu-sru always reviewed before upload
[17:39] <Laney> so we're not used to doing it the new way
[17:39] <jcastro> oh ok
[17:39]  * jcastro is still trying to get his head around this
[17:39] <Laney> hyperair can just upload it
[17:40] <seb128> not sure how it works for universe
[17:40] <Laney> it's supposed to be a unified process now AIUI
[17:40] <seb128> ok
[17:40] <seb128> usually for main the sru team review the queue
[17:40] <seb128> then go back to the bug from the changelog
[17:40] <seb128> so if you don't upload they will not notice it
[17:41] <seb128> emails is noisy
[17:41] <seb128> it's easier to use the upload queue for seeing was is waiting for review
[17:41] <hyperair> okay, so i should just upload banshee and podsleuth?
[17:41] <hyperair> using syncpackage?
[17:41] <didrocks> (I don't want to imagine the ubuntu-sru email list)
[17:41] <hyperair> heh
[17:42] <Laney> heh
[17:42] <Laney> you should file a tracking bug for podsleuth first
[17:42] <seb128> don't do sync for sru updates
[17:42] <seb128> you need proper lp bug tracking etc
[17:43] <Laney> I guess you could just add a -1~ubuntu1 entry above it
[17:44] <seb128> you should also make sure debian didn't do any packaging cleaning
[17:44] <seb128> or random changes
[17:44] <seb128> we only want the required changes for sru updates
[17:58] <hyperair> well i didn't do any packaging cleaning, and i was the one who did the podsleuth release
[17:59] <hyperair> either way it's a new upstream release, is that okay?
[17:59] <seb128> depends of the diff it has
[17:59] <hyperair> new upstream bugfix* release.
[17:59] <seb128> but you can always upload and wait for the sru team to review it
[17:59] <hyperair> well you can't really get much worse than lucid's current podsleuth =p
[18:00] <hyperair> it fails completely since hal doesn't start automatically any more
[18:14] <fta> anyone using evolution here? if you are, could you please check the message-id of an email *you* sent to see if its domain is/isn't @localhost.localdomain?
[18:15] <seb128> fta, ubuntu version?
[18:16] <seb128> fta, it isn't on lucid
[18:17] <fta> seb128, yep, i'm working on an upstream bug, and they rejected my patch because on redhat, it's using @localhost.localdomain so my patch leads to rejected emails
[18:18] <fta> i said it's a broken setup but they say it's a popular one
[19:48] <torres09> hey everybody..cannot run gnome on ubuntu 10.04...crashes every 10s or so,...any way i can get ubuntu up ad running? any help is appreciated
[20:00] <stenten> !support
[20:00] <ubot2> The official ubuntu support channel is #ubuntu. Also see http://ubuntu.com/support and http://ubuntuforums.org
[20:07] <didrocks> seb128: thanks for mutter bin NEWing
=== pgraner is now known as pgraner-afk
[20:09] <seb128> didrocks, np, I was pondering doing it or not before weekend ;-)
[20:10] <didrocks> seb128: well, a gir package, not a big deal I think :-)
[20:10]  * didrocks hugs seb128
[20:17] <didrocks> well, time to enjoy the early week-end, see you on Monday!
[20:18] <didrocks> seb128: enjoy your long week-end too :)
[20:19] <Sarvatt> didrocks: mutter needs the same patch as in metacity 1:2.30.1-1ubuntu2 btw
[20:20] <didrocks> Sarvatt: are you sure? from my tests it wasn't needed
[20:20] <didrocks> Sarvatt: did you test and have some issues with it?
[20:20] <Sarvatt> positive, run glxgears
[20:20] <Sarvatt> crashes mutter the the same way as metacity
[20:20] <didrocks> Sarvatt: that's weird, the patch was for a segfault, not performance only (it was crashing there)
[20:21]  * didrocks reinstalled and try mutter --replace again
[20:21] <didrocks> crashing the box before week-end :)
[20:21] <seb128> didrocks, thanks, enjoy your weekend as well!
[20:24] <Sarvatt> http://sarvatt.com/downloads/patches/0001-Use-gdk_screen_get_system_colormap-instead-of-gdk_sc.patch (which is the same as the metacity patch) fixes it and makes mutter usable again on maverick :)
[20:25] <didrocks> Sarvatt: oh, that's fun, it only crash when you use a function which uses GL
[20:26] <didrocks> Sarvatt: for basic usage, no crash
[20:26] <didrocks> I'll upload that now and then week-end time :)
[20:26] <didrocks> thanks for the notice
[20:27] <Sarvatt> no worries, sorry for bringing it up right when you were leaving :)
[20:27] <didrocks> Sarvatt: no pb :) That's weird because you can use mutter without any issue for basic things (moving windows, switching ws, minimizing, closing…) with all the fancy effects
[20:28] <didrocks> it's only when you launch something like glxgears that it crashes
[20:29] <Sarvatt> there were other things that crashed it too, its just glxgears always did it :)
[20:29] <didrocks> Sarvatt: my metacity before the patch was crashing from the beginning
[20:30] <Sarvatt> been my main window manager for a long time and had to switch to compiz about a month ago with the gtk changes :(
[20:30] <didrocks> well, you can switch back now :)
[20:30] <Sarvatt> yeah, i use it from git though and have been adding that patch :D
[20:31] <didrocks> Sarvatt: I'll give it the same name than the metacity one for easier followup
[20:33] <Sarvatt> should be able to just use the metacity one directly? i just didnt have it handy
[20:33] <didrocks> Sarvatt: I have it, I just credit you in the changelog :)
[20:40] <didrocks> Sarvatt: ok, built, tested and it fixes the crash when launching glxgears (at least ;)). Pushed
[20:40] <didrocks> thanks for noticing it
=== bratsche is now known as br-away
=== br-away is now known as bratsche
[22:21] <fta> bratsche, should i file a bug for acroread corrupted display because of rbga? acroread is in partner so i'm not sure. workaround is to set XLIB_SKIP_ARGB_VISUALS=1 in the wrapper
[22:24] <bratsche> ugh
[22:24] <bratsche> Yeah, sure.
[22:25] <bratsche> fta: Thanks.
[22:30] <fta> bug 589409
[22:30] <ubot2> Launchpad bug 589409 in acroread (Ubuntu) "acroread corrupted display when using RGBA in gtk (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/589409
[22:59] <Sarvatt> thanks for the tip fta, that fixes vmware workstation as well
[23:01] <robbiew> kenvandine: ping
=== bjf is now known as bjf[afk]
[23:22] <rickspencer3> kenvandine, I guess gwibber is not starting for some folks, is there a bug report on this?
[23:23] <arand> rickspencer3: Bug #588478
[23:23] <ubot2> Launchpad bug 588478 in desktopcouch (Ubuntu) (and 1 other project) "RuntimeError: Can not find port of couchdb. (affects: 10) (dups: 4) (heat: 66)" [High,Confirmed] https://launchpad.net/bugs/588478
[23:23] <rickspencer3> arand, tx
[23:24] <arand> rickspencer3: Seems to be somewhat figured out what the issue was though..
[23:24] <rickspencer3> *sigh*
[23:24] <rickspencer3> desktopcouch has a tendency to break us :)
[23:25] <kenvandine> rickspencer3, it's the kernel
[23:26] <kenvandine> the way the find the port breaks with the maverick kernel
[23:27] <rickspencer3> oh sweet
[23:27] <rickspencer3> seems "finding ports" has always been a bit hackish
[23:27] <kenvandine> yup :/
[23:27] <rickspencer3> kenvandine, is there a workaround?
[23:27] <kenvandine> boot the old kernel
[23:27] <arand> rickspencer3: run it with sudo >_<
[23:28] <kenvandine> ewwwww
[23:28] <rickspencer3> lol
[23:28] <arand> eww indeed, but for some weird reason it works
[23:28] <kenvandine> humm
[23:28] <rickspencer3> why not just log in as root?
[23:28] <kenvandine> linspire did :)
[23:29] <JanC> only for a short period though  ;)
[23:29] <kenvandine> :)