[00:32] <robert_ancell> jasoncwarner_, oh is see what you mean about the password entry size - it seems to be happening everywhere though
[00:32] <smspillaz> robert_ancell: yo
[00:33] <smspillaz> robert_ancell: so those merges for xig -- anything I need to do for them ?
[00:33] <smspillaz> the compiz tests fail without them :)
[00:34] <robert_ancell> smspillaz, looking
[00:35] <robert_ancell> oh, I didn't see your response
[00:37] <robert_ancell> smspillaz, ah, right.  What you really should do is the server should connected to the destroyed signal for the resources and remove them that way
[00:37] <robert_ancell> so you're explicitly destroying the references from both sides, but the server should be implicitly destroying them
[00:38] <robert_ancell> (or the other way around).  The patch has both the server and client responsible which is dangerous if one of them gets out of sync
[00:38] <robert_ancell> make sense?
[00:41] <smspillaz> kind of
[00:41] <smspillaz> hang on
[00:46] <robert_ancell> so there's two ways we can do this - the client destroys itself, and the server detects that and destroys all its resources, or the client destroys all its resources then itself, and the server doesn't care
[00:47] <smspillaz> (from the internal POV I assume)
[00:47] <robert_ancell> yes
[00:47] <smspillaz> robert_ancell: so I think the best way to handle this is to have a XigClientResource which XigSelection and XigDrawable inherit
[00:47] <robert_ancell> yes
[00:48] <smspillaz> and then XigClientResource just has a pointer back to the owner which can be queried by the serer
[00:48] <smspillaz> *server
[00:48] <smspillaz> so when the client goes away the server can listen and clean up
[00:48] <robert_ancell> the server doesn't really even need that
[00:48] <smspillaz> I don't really have time to work on that today
[00:48] <robert_ancell> np
[00:48] <smspillaz> (just needed a status update)
[00:48] <robert_ancell> I'll have a look if I've got time
[00:48] <smspillaz> scarce resource apparantly
[00:49] <robert_ancell> indeed :)
[00:51] <robert_ancell> smspillaz, note you can leave resources behind after quitting, but I'm not 100% how the protocol allows that (e.g. settings a background pixmap then quitting)
[00:52] <smspillaz> robert_ancell: as long as the resource is copied into another client ownership then yes
[03:44] <RAOF> Bah.  The one day I want to do some data manipulation and LibreOffice Calc won't start.
[04:35] <pitti> Good morning
[04:53] <TheMuso> Morning pitti.
[05:37] <pitti> jbicha: did you see the gnome-games FTBFS on arm?
[05:37] <pitti> seems the clutter stuff crept back in, was that due to a bad merge, or due to the new upstream versin?
[05:52] <jbicha> pitti: I saw it but I didn't understand it
[06:35] <didrocks> good morning
[06:37] <pitti> it's a Didier! bonjour
[06:37] <didrocks> pitti: I hope it's the good one! :) How are you pitti?
[06:37] <pitti> no, it's the awesome one!
[06:37] <pitti> I'm quite fine, thanks!
[06:37] <didrocks> :)
[06:37] <pitti> quite funny if your gtimelog says "Total work done: 2 h 6 min" at this hour already
[06:40]  * didrocks hugs pitti. It's half past seven and you are already here for 2 hours?
[06:40] <pitti> yeah, got up with Netti this morning (5:30)
[06:40] <pitti> yesterday I slept until 8:15 (some backlog from the weekend), I guess that sufficiently refreshed me
[06:42]  * pitti gives back a bunch of powerpc/armel build failures due to arch skew
[06:43] <pitti> RAOF: want me to sync colord?
[06:44] <pitti> well, I guess you can sync yourself, too
[06:44] <RAOF> Yeah.  I was going to let it stew in sid for a while.  There's no urgent reason to sync it, is there?
[06:45] <pitti> RAOF: well, you tell me :)
[06:45] <RAOF> I don't _think_ there is :)
[07:22] <pitti> didrocks: hm, was that unity change to keep the launcher visible uploaded?
[07:22] <pitti> didrocks: I just rebooted, and now it doesn't go away any more
[07:22] <pitti> and my windows are under teh launcher
[07:23] <didrocks> pitti: yeah, the strut is not set only at startup
[07:23] <didrocks> that's why the "my windows are under the launcher"
[07:23] <pitti> this is a pretty nasty regression now
[07:23] <didrocks> well, it should be fixed in a few :)
[07:23] <pitti> ok, merci
[07:23] <pitti> didrocks: so, no need for the big "revert" club?
[07:24] <didrocks> pitti: I didn't spot it (as I only did change the default value) as nobody reported it before (it should have been there with "always locked launcher") and I had to run unity-2d in the same session to test my settings change
[07:24] <didrocks> but! unity-2d set the strut and didn't unset it
[07:24] <pitti> ah, I can work around by re-enabling the autohide option
[07:24] <didrocks> so then, when I tested unity, I was thinking eveyrthing is fine : )
[07:24] <didrocks> pitti: yeah, it's only at startup, and no, no need for big revert
[07:25] <didrocks> if we need everytime to reboot a session to recheck everything, I'm afraid of the cost of testing
[07:25] <didrocks> especially with 2d/3d, that's why I tried on the same session
[07:25] <didrocks> didn't thought that the struct can be set by one and kept :/
[07:26] <BigWhale> kenvandine, Gwibber survived overnight test ...
[07:37] <pitti> didrocks: btw, when will you upload the next major unity release?
[07:37] <pitti> didrocks: looking at precise-fixes-report, 41 to go; want to know how much time I have :)
[07:38] <didrocks> pitti: heh, thursday in a week, for feature freeze :)
[07:38] <pitti> that's tough!
[07:40] <didrocks> heh :)
[07:40] <didrocks> oh, I hope we can have a compiz release first
[07:52] <pitti> didrocks: thanks for the unity upload, that was fast
[07:53] <didrocks> pitti: yw ;)
[07:53] <pitti> reproduces nicely in a guest session, so easy to test
[07:54] <didrocks> pitti: well, guest session is taking 4 minutes on my computer to setup
[07:54] <pitti> !
[07:54] <pitti> how's that?
[07:54] <didrocks> and when I'm back the whole screen is black
[07:54] <pitti> didrocks: I meant, I'm happy to test it again once it built
[07:54] <didrocks> 2 Go of RAM
[07:55] <didrocks> (so swapping with thunderbird opened and chromium I guess)
[07:55] <pitti> is that the guest session specifically, or any extra sessino?
[07:55] <didrocks> and when going back, the nvidia blob driver isn't nice
[07:55] <didrocks> pitti: any extra session, I really think it's a memory issue
[07:55] <didrocks> and my disk is slower and slower I guess
[07:55] <didrocks> (almost dying :))
[07:55] <didrocks> so I get regular X crashes on ETOOMANYWRITES
[07:56] <didrocks> pitti: this time I disconnected from my session to test it, but more testing is really appreciated :)
[08:18] <pitti> cyphermox: do you plan to merge modemmanager with Debian? they have 0.5.1, while we still have a git snapshot
[08:25] <rickspencer3> TheMuso, are you still around?
[08:27] <rickspencer3> pitti, TheMuso instead of uploading a half-tested ALSA, why not use the community QA team to confirm that it works well before uploading?
[08:27] <pitti> you could put it into the ubuntu-desktop or sound testing PPA
[08:28] <pitti> but I figure the user space side should be less harmful than the kernel side of .25, and we already have that anyway
[08:29] <rickspencer3> pitti, ok, I replied to TheMuso's email and cc'ed jono asking him to coordinate with the community team
[08:29] <rickspencer3> we may as well have some test cases and do some rigorous testing before uploading it for everbody
[08:30] <rickspencer3> breaking sound has a significant impact on velocity ;)
[08:30]  * rickspencer3 mulls various jokes using the phrase "sound barrier"
[08:31] <TheMuso> rickspencer3: Yeah fair call, but having looked at the changelogs, upstream code is fixes for the most part, userspace wise anyway, as pitti says, the kernel side is not aplicable here. I am more concerned about me ahving broken something with packaging, which would be relatively easy to fix anyways.
[08:31] <TheMuso> And I've been running the 2 core pieces here for a day or so now anyway.
[08:32] <rickspencer3> TheMuso, none the less, I think it wuold be good practice to do some formal testing first
[08:32] <rickspencer3> people get really upset when we break sound
[08:32] <rickspencer3> for instance, I get cranky when I can't watch my Taylor Swift videos
[08:32]  * micahg assumes rickspencer3 isn't maching the process
[08:32] <jasoncwarner_> rickspencer3: uhm...que?
[08:33] <rickspencer3> hi jasoncwarner_
[08:33] <jasoncwarner_> rickspencer3: sorry, my IRC taylor swift alarm went off...
[08:33] <rickspencer3> lol
[08:46] <seb128> hey
[08:47] <rickspencer3> bonjour seb128
[08:47] <seb128> rickspencer3, salut, ca va bien ?
[08:47] <rickspencer3> oui, je vais bien, et tois?
[08:50] <seb128> rickspencer3, j'ai un peu froid mais sinon ca va bien ;-)
[08:50] <seb128> waouh, pitti on an updates rampage \o/
[08:50] <pitti> seb128: bonjour :)
[08:50] <pitti> seb128: wanted to do all the ones you told  me yesterday by the time you woke up :)
[08:50] <seb128> hey pitti, wie gehts? thanks a lot for doing those updates
[08:50] <pitti> (and I managed)
[08:50] <pitti> de rien
[08:51] <seb128> pitti, I was not looking for third day in a row of doing updates full day so it's really appreciated ;-)
[08:52] <pitti> seb128: I also updated g-i and pygobject (unsurprisingly, I guess :) )
[08:53] <seb128> hehe, not a surprise indeed ;-)
[08:54] <BigWhale> Where can I find Ubuntu packaging gurus? I am having trouble with debian/watch file
[08:57] <seb128> not sure about gurus but people here or on #ubuntu-devel should be able to help you
[08:58] <BigWhale> well, I was told that I need watch file and now I am trying to convince uscan to find a file that is available in launchpad
[08:58] <BigWhale> more precisely, this one: http://launchpad.net/kazam/unstable/1.0/+download/kazam_1.0.tar.gz
[09:05] <pitti> BigWhale: ah, launchpad watch files all look teh same
[09:05] <pitti> BigWhale: try this:
[09:05] <pitti> version=3
[09:05] <pitti> http://launchpad.net/kazam/+download .*/kazam_([0-9.]+)\.tar\.gz
[09:05] <pitti> --
[09:05] <pitti> you can test with "uscan --report --verbose"
[09:06] <pitti> seb128: still waiting on ppc to give back the remaining packages; I gave back some this morning, but don't bother about the remaining ones right now, they'll fail again
[09:06] <seb128> pitti, yeah, see the version table, it's full of ppc build issues
[09:07] <seb128> pitti, I've commented on some of the rickspencer3's reassigned bug as well
[09:07] <BigWhale> pitti, thanks.. I'll give it a try
[09:14] <BigWhale> When I'm done with all of this, I'll write this monstrous blog post on how to get software to Ubuntu. :>
[09:18] <seb128> hehe
[09:18] <seb128> pitti, seems like we had a similar reply to jasoncwarner_'s email at the same time ;-)
[09:21] <pitti> seb128: as for gnome-keyring, my gut feeling is that we should backport some fixes; no strong opinion, though
[09:22] <BigWhale> I have one last question about versioning... :> right now I have kazam (1.0.1-0ubuntu1) precise; ... in version file. if I want to make an oneiric release, I have to change the version string, right? so, I change it to what?
[09:23] <seb128> pitti, does it work if I claim you are the maintainer for it and that it's your call? ;-)
[09:23] <pitti> seb128: I had that coming, I guess ;)
[09:23] <seb128> ;-)
[09:24] <pitti> so, I guess I'll have a look at 3.3.5 and check
[09:24] <seb128> pitti, I'm a bit concerned by the work involved by packaging the new sources and by the fact that stef said that the fallback mode was less tested that the new dbus stuff for gnome-shell
[09:24] <pitti> but I think cherry-picking some fixes should be safer
[09:25] <pitti> we don't currently have many problems with the keyring stuff
[09:25] <seb128> though he's usually a good upstream and if we find bugs in the fallback he will probably fix them
[09:25] <pitti> at least that I know of
[09:25] <seb128> right
[09:25] <seb128> we got bitten in the past
[09:25] <seb128> but doing updates when  not needed which created work
[09:25] <pitti> and as long as it doesn't block apps or g-shell from updating, I'd prefer to keep them
[09:25] <didrocks> seiflotfy1: hey, the COPYING shipped in activity-log-manager says GPL2 whereas all the headers are LGPL2+
[09:26] <seb128> pitti, same here
[09:29] <chrisccoulson> good morning everyone
[09:29] <pitti> hey chrisccoulson
[09:29] <chrisccoulson> hi pitti, how are you?
[09:30] <pitti> quite fine, thanks! how about you?
[09:30] <seb128> hey chrisccoulson, how are you?
[09:30] <chrisccoulson> seb128 pitti, tired ;)
[09:30] <chrisccoulson> seb128, you?
[09:30] <didrocks> hey chrisccoulson
[09:30] <pitti> chrisccoulson: burning the midnight oil again?
[09:30] <chrisccoulson> hi didrocks
[09:31] <seb128> chrisccoulson, still stucked into your "going to be at 3am"?
[09:31] <chrisccoulson> yeah ;)
[09:31] <seb128> lu didrocks
[09:32] <didrocks> salut seb128 :)
[10:26] <didrocks> seb128: hey, it seems you forgot to push gnome-menus 3.2.0.1-2ubuntu2 to the vcs
[10:26] <seb128> didrocks, looking
[10:26] <didrocks> so I pushed agateau's branch but got a reject :)
[10:27] <seb128> didrocks, sorry :-(
[10:27] <didrocks> seb128: no worry! do you still have it?
[10:28] <seb128> didrocks, hum, wtf
[10:29] <seb128> didrocks, I pushed but the stored push location was ~ubuntu-desktop/gnome-menus/gnome2/, I probably mixed up my vcses between gnome-menus-2 that we kept by compat and trunk, let me fix that
[10:29] <didrocks> seb128: oh, make sense, yeah, we should remove the ubuntugtk3 and every branhes like that :)
[10:29] <didrocks> branches*
[10:30] <seb128> didrocks, what vcs did you use?
[10:30] <seb128> bzr: ERROR: Not a branch: "bzr+ssh://bazaar.launchpad.net/+branch/lp:~ubuntu-desktop/gnome-menus/ubuntu/".
[10:30] <seb128> I'm getting confused
[10:30] <didrocks> hum
[10:30] <didrocks> lp:~ubuntu-desktop/gnome-menus/ubuntu
[10:30] <didrocks> are you sure about the adress?
[10:31] <didrocks> bzr+ssh://bazaar.launchpad.net/+branch/***lp:***~ubuntu-desktop/gnome-menus/ubuntu/
[10:31] <seb128> lalalal
[10:31] <didrocks> didn't you lp:lp:~ubuntu… ?
[10:31] <seb128> :p
[10:31] <didrocks> :)
[10:31] <didrocks> seb128: I know twice is better than one, but not everytime ;)
[10:33] <seb128> didrocks, hum, so you pushed your revision, should I just merge and push mine?
[10:33] <seb128> didrocks, or should I uncommit it, overwrite with mine and let you rebase?
[10:33] <didrocks> seb128: as you wish, if we want bzr correctness, you can uncommit
[10:34] <didrocks> and I'll rebase
[10:34] <seb128> didrocks, doing that
[10:36] <seb128> didrocks, ok, done, pull --overwrite please and sorry for the work
[10:36] <seb128> didrocks, well, uncommit
[10:36] <seb128> pull --overwrite
[10:36] <seb128> and you should be go to recommit
[10:36] <seb128> with your diff ready to apply or almost
[10:36] <Sweetshark> hi all.
[10:36] <seb128> hey Sweetshark
[10:37] <Sweetshark> http://nabble.documentfoundation.org/next-BoD-call-on-Wednesday-td3719497.html#a3720191 <- nice vote of confidence by an independant
[10:37]  * Sweetshark dances a bit.
[10:39] <didrocks> seb128: no worry :)
[10:49] <rickspencer3> pitti, thanks for your help yesterday: http://theravingrick.blogspot.com/2012/02/girrrr-pygame-gtk-in-goi-world.html
[10:50] <pitti> rickspencer3: btw, a lot of this conversion can be done automatically with pygi-convert.sh
[10:50] <rickspencer3> pitti,  I know
[10:50] <rickspencer3> but I thought it would be useful to have a small test case
[10:51] <pitti> nice that it works now!
[10:51] <rickspencer3> pitti, well, thanks to your work and blog posts, it was pretty easy ;)
[11:30] <ronoc> mvo, hey
[11:30] <ronoc> mvo, how do i tell if updates are installing via that pk interface
[11:31]  * ronoc double checks the pkclient header
[11:39] <manish> didrocks: there?
[11:40] <manish> some imp thing
[11:40] <didrocks> manish: hey hey :)
[11:40] <didrocks> manish: I was looking for you!
[11:40] <didrocks> manish: the COPYRIGHT file is mentionning GPL2
[11:40] <didrocks> where the whole project is licenced LGPL2+
[11:40] <didrocks> can I get a tarball fixing that? :)
[11:41] <manish> will do in a few hours
[11:41] <manish> need to get back home
[11:41] <manish> another thing is
[11:41] <manish> i talked to mhr3 and thansen (a gentoo packager)
[11:41] <manish> that the source package should be named activity-log-manager instead of alm
[11:41] <manish> and no 3 letter binaries
[11:42] <manish> didrocks: activity-log-manager binary and libactivity-log-manager.so? Would it be fine?
[11:42] <didrocks> manish: it's already the case btw :)
[11:42] <didrocks> manish: the source package and binary is activity-log-manager
[11:42] <didrocks> for the lib, sure, you can change :)
[11:43] <manish> didrocks: but the tarball was named alm-0.9.0? remember?
[11:43] <manish> that won't matter. I think so
[11:43] <didrocks> manish: I know and I remember to have renamed it :)
[11:43] <manish> good
[11:43] <manish> I made that mistake
[11:43] <manish> bah.. too many mistakes
[11:43] <didrocks> no worry, it's not the first time our packages don't match the upstream sources :)
[11:43] <didrocks> manish: the COPYING one is an important one
[11:44] <manish> yes
[11:44] <didrocks> manish: I don't push the new version before the new release fixing it is released :)
[11:44] <manish> okay
[11:44] <manish> wait for an  hour
[11:44] <manish> will get back home
[11:44] <didrocks> sure ;)
[11:44] <manish> and do you want me to change the tarball name in this one?
[11:45] <manish> didrocks: I will just tell you the changes I am going to make in this patched tarball
[11:45] <didrocks> manish: it's really as you wish, it doesn't really matter for me
[11:45] <manish> 1) COPYING
[11:45] <manish> 2) tarball name
[11:45] <manish> 3) library name change
[11:45] <didrocks> sounds good! :)
[11:45] <manish> 4) binary name change
[11:46] <manish> now I hope you can make the necessary changes on your side
[11:46] <didrocks> manish: will do!
[11:47] <didrocks> seb128: hum, can you take a screenshot pressing alt?
[11:47] <didrocks> seb128: I have the effect, but nothing is happening here
[11:47] <seb128> didrocks, yes, they go to your Images dir without displaying a dialog
[11:47] <seb128> it's confusing, I need to check upstream if that's wanted
[11:47] <seb128> you only get the dialog if you use gnome-screenshot -i
[11:47] <seb128> i.e the ui
[11:47] <didrocks> seb128: oh waow
[11:47] <seb128> otherwise they are autotaken and stored
[11:48] <seb128> yeah, confusing, I think we will need to fix that ;-)
[11:48] <didrocks> confusing change when you get used to it, indeed
[11:51] <chrisccoulson> c'mon, build faster!!!!
[11:52]  * chrisccoulson cracks whip at armel porter
[11:52] <seb128> poor armel building firefox and then being whiped
[11:53] <chrisccoulson> i'm glad i'm finally getting somewhere with mozilla bug 716036 now
[11:53] <ubot2> Mozilla bug 716036 in Layout "css z-ordering renders invisible text on google search page" [Normal,Unconfirmed: ] http://bugzilla.mozilla.org/show_bug.cgi?id=716036
[11:53] <chrisccoulson> and it looks like a cairo bug ;)
[11:54] <seb128> lol
[11:55] <seb128> why I am not surprised ;-)
[11:55] <chrisccoulson> heh
[11:56] <chrisccoulson> it seems to be drawing transparent glyphs as white on armel for some reason
[11:56] <seb128> I blame xorg :p
[11:57] <chrisccoulson> lol
[12:04] <dpm> hi all, since this morning the unity launcher is not doing autohide and stays on top of all my windows. Is this a known problem, or does anyone have a workaround?
[12:08] <dpm> oh, it was just the default setting that had been changed, I could restore auto-hide from the control center
[12:46] <ronoc> mvo, ping
[12:46] <ronoc> ?
[12:47] <ronoc> mvo, don't know how to figure out when updates are installing
[12:47] <ronoc> will leave it out for now
[12:47] <ronoc> but that was part of the spec
[12:47] <ronoc> it seems much more stable than before using the new pk kit compat layer
[12:48] <ronoc> going to take lunch - let me know what dependencies i should list in my configure.ac
[12:48] <ronoc> I already have the pkglib-lib
[12:49] <ronoc> do i need any others - that python compat pk layer thingie from yesterday
[12:49] <ronoc> ?
[12:49] <ronoc> right lunch
[12:54] <mvo> ronoc: so if aptdaemon creates events on the PK compat layer, than you can watch for those, but I will have to check with glatzor if that is possible/fits into the scheme of things
[12:55] <ronoc> mvo, events as in ?
[12:55] <ronoc> right now i listen for the udpateschanged and reboot_scheduled
[12:55] <didrocks> sil2100: hey, just answered to your email btw
[12:56] <ronoc> signals
[12:56] <mvo> ronoc: creating transactions
[12:56] <mvo> ronoc: aha, I see
[12:56] <ronoc> mvo, yeah but surely transactions can be behind anything
[12:56] <ronoc> i just want to know if there are actual new updates being installed at that moment
[12:57] <sil2100> didrocks: thanks
[12:57] <ronoc> mvo, ill push what i have now
[12:57] <ronoc> we can fix that after FF if we can
[12:57] <ronoc> at least the port has been done :)
[12:58]  * ronoc doesn't want to know anything about transactions ...
[12:58] <ronoc> if i can help it
[13:01] <mvo> ronoc: I'm not sure that is possible  with the current interface, it looks like you need to react to TransactionListChanged and check those if they are updates (unless the C api hides that away)
[13:02] <ronoc> mvo, ok
[13:18] <BigWhale> err I used dput to upload to a ppa, then I canceled the build request, package still got build, then I deleted the package and now I got rejected for a build because apparently my source already exists. How do I get rid of it? :/
[13:19] <seb128> you can't
[13:19] <seb128> upload a new revision
[13:19] <BigWhale> curses
[13:20] <seb128> you can't get the same version published twice
[13:21] <seb128> it would be very confusing for launchpad,users, especially if somebody got the first upload
[13:21] <BigWhale> I agree
[13:36] <BigWhale> I think I secretly hate bzr and launchpad
[13:44] <kenvandine> good morning seb128
[13:44] <kenvandine> did you notice the theme breakages in the latest gtk?
[13:45] <kenvandine> gwibber and evolution seem to be the most broken
[13:45] <seb128> kenvandine, hey, yes, I warned you yesterday before upload: p
[13:45] <seb128> kenvandine, Cimi has a new unico and light-themes
[13:45] <kenvandine> oh... i thought you warned about all the deprecations
[13:45] <seb128> kenvandine, I was about to look at doing those updates
[13:45] <seb128> kenvandine, deprecation and issues ;-)
[13:45] <kenvandine> ok :)
[13:46] <seb128> kenvandine, do you want to do them or do you want to do indicator-session and other stuff? I'm done with GNOME so I've free time
[13:46] <kenvandine> "them"
[13:46] <kenvandine> i will do the indicators
[13:46] <seb128> kenvandine, unico light-themes, I can do them if you want or I can let them to you
[13:46] <kenvandine> oh, are they updated?
[13:46] <kenvandine> i can do those
[13:46] <seb128> kenvandine, Cimi commited fixes an hour ago
[13:47] <kenvandine> woot
[13:47] <seb128> kenvandine, as said I was just going to look at them
[13:47] <kenvandine> seb128, you can do unico
[13:47] <seb128> but I'm happy for you to take them if you are not too busy
[13:47] <kenvandine> i'll do light-themes
[13:47] <kenvandine>  :)
[13:47] <seb128> kenvandine, ok, you do light-themes?
[13:47] <seb128> great!
[13:47] <seb128> on my way ;-)
[13:48] <kenvandine> ronoc, from now on just give me branches and i'll manually update the patch... merging just refuses to work :/
[13:48] <kenvandine> it is easy enough to cherry pick your new revisions and put them in my diff
[13:48] <seb128> kenvandine, get the sound stuff in precise!
[13:48] <seb128> ;-)
[13:48] <seb128> works great here
[13:48] <kenvandine> i plan too :)
[13:49] <kenvandine> ronoc, is that cool with you? if i upload it today?
[13:49] <didrocks> m4n1sh: back home? :)
[13:50] <seb128> kenvandine, btw did you notice that they rolled a new empathy tarball yesterday?
[13:50] <m4n1sh> yes
[13:50] <m4n1sh> working on it
[13:50] <kenvandine> seb128, i did
[13:50] <seb128> kenvandine, just mentioning it in case you didn't notice
[13:50] <seb128> ok, great
[13:50] <kenvandine> on my todo list :)
[13:50] <m4n1sh> didrocks: this is the license? right? http://git.gnome.org/browse/pygobject/tree/COPYING
[13:51] <jdstrand> seb128: hi! is there a bug open on the light-themes issue with the latest gtk? (I couldn't find it). the lack of contrast makes it difficult for me to read email headers in evolution
[13:51] <seb128> jdstrand, we have theme updates to match the new gtk on their way, try back in one hour when the fixes are landed please
[13:51] <kenvandine> seb128, what is the new unico version?  upping the depends in light-themes
[13:51] <jdstrand> seb128: ok, thanks
[13:52] <seb128> kenvandine, 1.0.1-0ubuntu2
[13:53] <seb128> kenvandine, Cimi didn't roll a tarball, I just backport the recent commit
[13:53] <kenvandine> cool
[13:53] <didrocks> m4n1sh: no, it's not, you are using LGPL2
[13:53] <didrocks> +
[13:53] <m4n1sh> yes +
[13:54] <m4n1sh> didrocks: you have the full license text for it?
[13:54] <didrocks> m4n1sh: /usr/share/common-licenses/LGPL-2
[13:54] <didrocks> on your ubuntu system
[13:54] <didrocks> just copy it from here
[13:54] <m4n1sh> thanks
[13:56] <kenvandine> seb128, let me know when you push the unico branch, i'll do a local build to test the theme
[13:57] <kenvandine> seb128, can you also do the notify-osd update?
[13:57] <seb128> kenvandine, ok, 2 minutes
[13:57] <seb128> kenvandine, can do yes
[13:57] <kenvandine> thx
[13:57] <seb128> yw
[13:57] <m4n1sh> didrocks: if bin_PROGRAMS = activity-log-manager
[13:57] <m4n1sh> then alm_CFLAGS changes to activity_log_manager_CFLAGS?
[13:57] <m4n1sh> - changes to _
[13:57] <m4n1sh> right?
[13:58] <didrocks> indeed
[13:58] <m4n1sh> thanks
[14:00] <m4n1sh> didrocks: can you check that the packages you built, in those are AUTHROS going in /usr/doc instead of /usr/share/doc ?
[14:01] <ronoc> kenvandine, lets do it !
[14:01] <tjaalton> is anyone interested in indicator-weather anymore?
[14:01] <kenvandine> ronoc, any changes since yesterday for me to pull in?
[14:02] <tjaalton> it's been crashy since natty
[14:02] <didrocks> m4n1sh: I had to move the doc from /usr/doc to /usr/share/doc, indeed
[14:02] <ronoc> kenvandine, nope just that branch from yesterday, there is however an issue with bluetooth devices
[14:02] <ronoc> that i was going to look at today
[14:02] <ronoc> kenvandine, do you want to wait until i fix that
[14:02] <kenvandine> ronoc, eta?
[14:02] <ronoc> kenvandine, hopefully EOB today
[14:02] <kenvandine> i have plenty to do, so i can just wait a few hours on g-c-c
[14:02] <kenvandine> :)
[14:03] <ronoc> kenvandine, ok cool - will get back to you in a bit
[14:03] <kenvandine> awesome
[14:05] <seb128> kenvandine, unico pushed
[14:05] <kenvandine> thx
[14:06] <seb128> kenvandine, hum, I might switch it back to source v1 though
[14:06] <kenvandine> i just saw, it won't build :)
[14:06] <seb128> kenvandine, I will --overwrite the most recent commit to switch to source v1, v3 doesn't deal well with bzr merge backports
[14:06] <kenvandine> do it
[14:06] <seb128> kenvandine, well edit debian/source/format and change to 1.0
[14:06] <kenvandine> done :)
[14:06] <seb128> it build, just bzr-builddeb is being stupid
[14:07] <m4n1sh> didrocks: if you have time can you look in Makefile.am (folder root)
[14:08] <m4n1sh> cant make out what is wrong over there, even you told that it tries uninstalling wrong files
[14:08] <didrocks> m4n1sh: well, I'm helping on a lot of other stuff, not an issue right now, as I workaround it on the package (and we need the first release ;)) but I'll have a deeper look later
[14:08] <m4n1sh> sure
[14:09] <cyphermox> pitti: I do, that's what I'll be doing today (or cutting a new snapshot, there's some fixes for a bug that might be coming in soon if it didn't already land)
[14:09] <cyphermox> pitti: that was re: modemmanager
[14:09] <pitti> cyphermox: thanks
[14:09] <pitti> cyphermox: might be a good idea to merge with Debian first
[14:09] <cyphermox> yup
[14:10] <cyphermox> pitti: we share packaging branch with debian, so that's going to be real quick :)
[14:13] <kenvandine> seb128, new unico and light-themes fix it for radiance, but not ambiance
[14:13] <seb128> :-(
[14:13]  * kenvandine looks at theme diff
[14:13] <seb128> kenvandine, can you let seem know? well that's the theme I use so it's something :p
[14:13] <kenvandine> hehe
[14:16] <seb128> kenvandine, you can pull --overwrite unico
[14:19] <kenvandine> seb128, oh... it is fixed!
[14:19] <seb128> kenvandine, I still get spammed by px warnings
[14:19] <kenvandine> weird, switching themes back and forth wasn't enough
[14:19] <seb128> gedit background looks wrong
[14:19] <kenvandine> i had to exit and restart them
[14:19] <seb128> oh, maybe I still have the old engine loaded
[14:19] <kenvandine> yeah :)
[14:20] <seb128> kenvandine, gedit is broken for me with the light theme
[14:20] <seb128> the background of the text editor is grey and not white
[14:20]  * kenvandine tries
[14:20] <seb128> still getting the
[14:20] <seb128> Gtk-WARNING **: Theme parsing error: nautilus.css:58:19: Not using units is deprecated. Assuming 'px'.
[14:21] <seb128> the menubar selection color is wrong
[14:21] <seb128> ie if you disable appmenu and try to open a bug
[14:22] <kenvandine> looks fine in ambiance
[14:22] <kenvandine> not radiance
[14:23] <pitti> WTF...
[14:23] <pitti> booting current precise daily in kvm, and I get unity 3D!?
[14:23] <kenvandine> the background looks light, but not quite white in gedit
[14:23] <seb128> kenvandine, it doesn't here
[14:23] <kenvandine> pitti, wow
[14:23] <pitti> it's slow as hell and has some screen corruptions
[14:23] <pitti> but it does kinda work
[14:23] <pitti> LLVM FTW?
[14:23] <kenvandine> i guess!
[14:23] <seb128> pitti, 926859
[14:24] <seb128> is a request to not run under llvm
[14:24] <pitti> seb128: ah :)
[14:24] <pitti> still, quite impressive how well it actually works
[14:24] <pitti> this is -vga std
[14:24] <seb128> kenvandine, gedit is broken with ambiance for me as well
[14:24] <seb128> kenvandine, in a guest session
[14:24] <seb128> kenvandine, the background and selection color seem indentic, i.e I can't see what I select
[14:27] <seb128> kenvandine, is your gedit customized on the profile to use for colors?
[14:27] <seb128> kenvandine, I use "standard" here, it's broken as well in a guest session
[14:28] <kenvandine> seb128, fine for me in a guest session on both of my computers
[14:29] <seb128> kenvandine, hum, k, weird
[14:29] <kenvandine> the document background color is more gray though
[14:29] <seb128> kenvandine, do you get the nautilus.css warnings?
[14:29] <seb128> kenvandine, what is the selection color?
[14:30]  * bcurtiswx waves hi
[14:30] <seb128> hey bcurtiswx
[14:30] <Sarvatt> pitti: yeah it's not *quite* there yet, mesa 8.1 hopefully!
[14:30] <kenvandine> no i don't
[14:30] <kenvandine> seb128, do you have the updated theme?
[14:31] <Sarvatt> pitti: vmware 3D passthrough works out of the box now though and unity works perfect under it via vmware player
[14:32] <m4n1sh> didrocks: go https://launchpad.net/activity-log-manager/0.9/0.9.0
[14:32] <m4n1sh> done
[14:32] <seb128> kenvandine, I've r189
[14:32] <didrocks> m4n1sh: sweet, taking :)
[14:33] <pitti> Sarvatt: I tried again with the default -vga, still all stripes
[14:33] <kenvandine> seb128, there are more
[14:33] <kenvandine> r190 was the latest when i grabbed it
[14:33] <pitti> Sarvatt: nice to hear! I always wanted to test some 3D stuff under kvm
[14:33] <pitti> Sarvatt: that might make automatic tests easier, too
[14:33] <kenvandine> seb128, which includes menubar changes :)
[14:33] <seb128> lol
[14:33] <seb128> kenvandine, I pulled like 10 minutes ago
[14:34] <kenvandine> :)
[14:37] <seb128> kenvandine, still having the px warning with radiance
[14:37] <seb128> and the menubar label issue
[14:37] <seb128> and the background one
[14:37] <seb128> I don't get the warning about nautilus.css in ambiance though
[14:38] <kenvandine> ok... i really need to move to having a separate packaging branch for light-themes
[14:38] <seb128> I guess the ambiance change to nautilus.css in r189 need to be applied to the other theme
[14:38] <kenvandine> sharing trunk with cimi is hard
[14:38] <seb128> $ bzr diff -c 189 | diffstat | grep nautilus
[14:38] <seb128>  Ambiance/gtk-3.0/apps/nautilus.css      |   10 -
[14:38] <seb128> $
[14:38] <seb128> he updated only one of the themes
[14:40] <kenvandine> yeah
[14:40] <seb128> kenvandine, I'm really puzzled why you don't get the issues...
[14:40] <kenvandine> so the menu label problem, you me when you select a menu item you can't see it right?
[14:40] <seb128> I mean I unset UBUNTU_MENUPROXY
[14:40] <kenvandine> my package was based on r189
[14:40] <seb128> run gedit
[14:40] <seb128> and click on file
[14:41] <seb128> the label text is white
[14:41] <kenvandine> but he committed to trunk while i was in the middle
[14:41] <slomo_> tjaalton: i've uploaded gst-plugins-bad with your changes and a small fix now btw
[14:41] <slomo_> tjaalton: might want to look on git.debian.org for the small change in debian/rules that was also necessary
[14:41] <kenvandine> ok, yeah i see that
[14:41] <kenvandine> but the menu items are fine
[14:41] <seb128> great ;-)
[14:41] <seb128> yeah, just the menu bar
[14:41] <kenvandine> and the background/selection issue
[14:41] <seb128> well anyway that's minor
[14:42] <seb128> kenvandine, I would welcome you applying the nautilus.css px fixes to the second theme before uploading
[14:42] <seb128> kenvandine, and I think we should fix the gedit selection color stuff
[14:42] <seb128> it makes gedit almost impossible to use
[14:42] <seb128> like I've been dnding text arround trying to select stuff to copy and trying again
[14:43] <pgraner> seb128, have you heard about todays update breaking flash's audio
[14:43] <seb128> kenvandine, ok, anyway Cimi seems on it
[14:43] <seb128> pgraner, no
[14:43] <tjaalton> slomo_: yeah I noticed that, thanks. it complained about not finding the libs on build but didn't bother fixing it :)
[14:43] <seb128> pgraner, but I'm not the right guy to ask about audio, try diwic or TheMuso
[14:44] <pgraner> seb128, its happend to quite a few of the kernel team
[14:44] <pgraner> seb128, cool
[14:44] <seb128> pgraner, TheMuso sent an email to the ubuntu-devel list about a new alsa being uploaded earlier today
[14:44] <seb128> so it might have to do with that
[14:44] <pgraner> seb128, hmmm haven't got to that list yet
[14:44] <slomo_> tjaalton: without that fix automatic codec installation will be broken :)
[14:44] <slomo_> tjaalton: but other than that everything was fine
[14:45] <tjaalton> slomo_: ahah, ok. well, it was getting late too and needed to push it out :)
[14:58] <didrocks> m4n1sh: /usr/share/applications/alm.desktop
[14:59] <didrocks> it still executes alm
[14:59] <didrocks> I'll still push that version for now
[14:59] <didrocks> this can go with other fixes :)
[15:31] <seb128> kenvandine, Laney: btw what happened to the libproxy update? is that still on track for this cycle?
[15:31] <Laney> oh, yeah, it's still a thing
[15:32] <Laney> let me push some stuff
[15:40] <didrocks> m4n1sh: still around? :p
[15:41] <kenvandine> Laney, last i looked it was fine with me besides a few tweaks to make it build
[15:41] <kenvandine> Laney, it would be great to get that uploaded
[15:41] <Laney> you had a patch, can you send that over?
[15:41] <kenvandine> let me find that
[15:41] <Laney> mozjs185 is in debian now thanks to chrisccoulson
[15:44] <kenvandine> http://paste.ubuntu.com/834023/
[15:44] <kenvandine> Laney, ^^
[15:53] <kenvandine> oh... indicator-applet source was removed?
[15:53]  * kenvandine was confused by the source going to NEW
[15:56] <seb128> kenvandine, yes
[15:56] <seb128> kenvandine, it was not building in oneiric...
[15:56] <pitti> seb128: do you happen to know which spell checker dictionaries gedit uses these days?
[15:56] <kenvandine> seb128, builds now :)
[15:56] <seb128> pitti, enchant
[15:56] <pitti> seb128: language-selector still installs aspell-XX for it
[15:56] <kenvandine> ported to the gnome3 panel
[15:56] <m4n1sh> didrocks: saw the upload. Great
[15:57] <seb128> pitti, which can use whatever is available, ispell, aspell, myspell
[15:57] <pitti> Depends: aspell-en | myspell-dictionary | aspell-dictionary | ispell-dictionary | hunspell-dictionary
[15:57] <didrocks> m4n1sh: yeah, however, there are quite some stuff to fix for your next upload :)
[15:57] <pitti> seb128: we already install hunspell for LibO, so it would be nice to be consistent and use that for gedit, too
[15:57] <pitti> seb128: for custom dictionaries, etc.
[15:57] <seb128> pitti, I think that works, gedit uses enchant which can use hunspell
[15:57] <pitti> seb128: ok, I'll move gedit to hunspell-*, thanks
[15:57] <didrocks> m4n1sh: so, the stuff still install in doc/alm and not activity-log…
[15:57] <m4n1sh> yes
[15:57] <didrocks> m4n1sh: also the desktop files are refering alm
[15:57] <seb128> pitti, is getting pulling in dictionnaries?!
[15:57] <m4n1sh> didrocks: so doc is still not fixed
[15:58] <m4n1sh> need to look at it
[15:58] <pitti> seb128: language-selector does
[15:58] <seb128> oh ok
[15:58] <didrocks> m4n1sh: the desktop files are renamed and pointing the correct namespace?
[15:58] <pitti> seb128: i. e. "wa::gedit:aspell-"
[15:58] <seb128> pitti, yeah, please use hunspell ;-)
[15:58] <pitti> seb128: if you have "gedit" installed (the trigger package), then it installs aspell-$LANG
[15:58] <m4n1sh> didrocks: OH NOES
[15:58] <seb128> pitti, I though we consolidated that cycles ago
[15:58] <seb128> to only use hunspell
[15:59] <pitti> seb128: we do that for gedit, abiword, and sylpheed
[15:59] <m4n1sh> didrocks: again I missed that. Looks like I need some rest. Too much stress at daywork too
[15:59] <m4n1sh> didrocks: you might need to add a small patch then
[15:59] <seb128> pitti, I think it's a leftover
[15:59] <didrocks> m4n1sh: quite easy to fix, and that can wait on next upload :)
[16:00] <pitti> seb128: ah, sylpheed uses gtkspell which uses enchant
[16:00] <pitti> moving that, too
[16:00] <m4n1sh> didrocks: yes
[16:00] <pitti> abiword I'm not sure of
[16:00] <didrocks> m4n1sh: I guess you are looking for another release before eow?
[16:00] <m4n1sh> didrocks: 2 line patch on each .desktop.in file
[16:00] <m4n1sh> yes
[16:00] <didrocks> with some of seif fixes
[16:00] <didrocks> m4n1sh: and renaming them
[16:00] <m4n1sh> yes
[16:00] <seb128> pitti, I just checking, gedit uses hunspell-fr just fine here
[16:00] <didrocks> m4n1sh: that can wait on next release, no worry
[16:00] <pitti> seb128: merci
[16:00] <seb128> pitti, I don't have any other *spell-fr*
[16:00] <seb128> and correction work, it underlines words etc
[16:01] <seb128> pitti, de rien ;-)
[16:04] <m4n1sh> didrocks: won't that error in the .desktop.in file break ccpanel integration?
[16:04] <didrocks> m4n1sh: surprinsingly not
[16:05] <didrocks> m4n1sh: not sure how it get the right name, but it works
[16:05] <m4n1sh> updating
[16:10] <kenvandine> aquarius is here, everyone hide!
[16:10] <apw> so am i reading correctly that we'll only have 'launcher visible' and 'launcher not visible' from now on
[16:11] <apw> if we do go that way, i think we will need to consider that i may wish to have different defaults per launcher in a multi-window setup
[16:11]  * aquarius grins
[16:11] <didrocks> apw: indeed, that's the new default
[16:12] <aquarius> pitti, ping about power stuff: my machine has "Hibernate" disabled in the "When the lid is closed" dropdown in Power Settings. Would you be the person to ask why that is?
[16:12] <didrocks> apw: there are still the other options in myunity or ccsm, but design want to remove the code path
[16:12] <pitti> aquarius: yes, we disabled it by default
[16:13] <pitti> aquarius: see bug 812394
[16:13] <ubot2> Launchpad bug 812394 in ayatana-design "Disable hibernate option by default" [Critical,Fix committed] https://launchpad.net/bugs/812394
[16:14] <aquarius> ah, thanks; will read that bug once launchpad starts talking to me
[16:15] <dobey> pitti: i don't think the detection is working right though
[16:15] <pitti> dobey: detection of what?
[16:15] <apw> didrocks, so did you say we can have different defaults per screen
[16:15] <dobey> pitti: whether a system supports hibernate or not; it should be choosable if the system supports it, no?
[16:15] <pitti> dobey: there's no UI for turning it back on
[16:15] <didrocks> apw: no, I saw you can still have intellihide for now, but it may be removed soon
[16:16] <pitti> dobey: it's not a matter of detection, that's what we had before (essentially, "do I have enough unencrypted swap space")
[16:16] <didrocks> as multiple configuration per screen, you should ask on unity-design ML first
[16:16] <pitti> dobey: it's just disabled, as it's painfully slow and allegedly rather unreliable
[16:16] <dobey> pitti: i thought it queried powerd or something for it?
[16:16] <apw> didrocks, right but one good feature of auto hide, is i can use window placement to show which launchers i can see by default, and i've become used to seeing the left one all the time, and not the rest
[16:16] <apw> didrocks, hmmm talking to designers, not something i have the language for
[16:17] <dobey> pitti: what good is a UI that is always disabled? "disabled by default" isn't a description. it's a lie. :)
[16:17] <aquarius> pitti, is it permanently disabled? That is: is there a list somewhere with "laptops that support hibernate" in it to which I should request that my laptop is added? (Mine supports hibernate fine with sudo pm-hibernate)
[16:17] <aquarius> pitti, if it's honestly not turn-on-able in any way then fine, I'm just curious why it was disabled rather than removed entirely in that case :)
[16:17] <aquarius> sorry if this is covered in the bug. LP is not talking to me.
[16:17] <pitti> aquarius: there is is not really such a thing like a "laptop which supports hibernate"
[16:18] <dobey> pitti: it's actually reasonably fast on my machines, and in fact does work reliably, unlike suspend which in fact, never works.
[16:18] <pitti>  it's a matter of partitioning
[16:18] <apw> aquarius, because when we removed support in the kernle for that very reason, there was a riot
[16:18] <pitti> aquarius: it was deemed too confusing to have two options, users accidentally clicking the wrong one, and then having to wait several minutes, etc.
[16:18] <apw> aquarius, and the decision was to leave the infrastructure in so ubuntu derivatives could use it
[16:19] <pitti> but as I said, there's no UI to turn it back on
[16:19] <aquarius> apw, pitti, right, that makes sense. So I should think of this as: Ubuntu does not do hibernation at all, yes?
[16:19] <seb128> there should be one over time
[16:19] <aquarius> (as I say, no problem if that's the decision)
[16:19] <pitti> aquarius: from an user's POV, essentially yes
[16:19] <seb128> the ui is speced in https://docs.google.com/a/canonical.com/document/d/1ILTJDiDCd25Npt2AmgzF8aOnZZECxTfM0hvsbWT2BxA/edit?ndplr=1
[16:19] <seb128> but we dropped that workitem
[16:19] <seb128> ETOOMUCHTODO
[16:19]  * aquarius grins
[16:20] <seb128> so not this cycle
[16:20] <dobey> i love UI that makes me think there is just something wrong with my computer :(
[16:20] <aquarius> being me, I can live with sudo pm-hibernate. I just wanted to check whether it was specific to my laptop or not :)
[16:20] <didrocks> apw: heh, I can only say "good luck" :-)
[16:20] <aquarius> is it safe to tweak the dconf setting directly? or is that likely to punish me in the future because I've set a setting that the UI specifically prevents me from setting?
[16:20] <dobey> aquarius: no. the UI equally hates everyone :)
[16:21] <pitti> aquarius: it's in /var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla
[16:21] <apw> didrocks, indeed, not worth the pain i suspect, just live with randomly chaning semantic every day
[16:21] <pitti> aquarius: arguably it should be in dconf instead of polkit, yes
[16:22] <aquarius> ah, so the bloke on askubuntu who said I should set org.gnome.settings-daemon.plugins.power.lid-close-ac-action to hibernate is full of lies, then :)
[16:23] <aquarius> or is the dconf thing actually the setting that says what to do, and the polkit thing is what disables choosing it in the UI?
[16:25] <pitti> mvo: hm, I'm having a hard time using aptdaemon from language-selector; when you cancel the polkit dialog for installation, the transaction crashes with aptdaemon.errors.NotAuthorizedError, but it doesn't seem to send out any signal
[16:26] <pitti> mvo: I already tried to print self.apt_dialog._transaction.status in the polling loop, but it doesn't change
[16:26] <pitti> mvo: is there a method to catch exceptions in the client?
[16:28] <pitti> mvo: at least it doesn't call the "finished" signal
[16:28] <m4n1sh> didrocks: not showing up
[16:29] <didrocks> m4n1sh: it does here and it did for seb128 as well
[16:29] <m4n1sh> totally confused.. how can it work
[16:29] <didrocks> m4n1sh: anyway, better to focus on next release :)
[16:29] <m4n1sh> yes
[16:29] <m4n1sh> first some rest
[16:29] <m4n1sh> and whisky..
[16:30] <didrocks> heh, enjoy :)
[16:32] <pitti> mvo: also tried to set error_handler, but that's not being called either
[16:32] <pitti> glatzor: ^ maybe you have an idea how to handle this? (see my ping to mvo 10 lines up)
[16:33] <pitti> mvo, glatzor: this uses defer=True
[16:35] <glatzor> pitti, could you please repost
[16:35] <glatzor> I was disconnected
[16:37] <pitti> glatzor: http://paste.ubuntu.com/834099/
[16:38] <glatzor> pitti, you are already using the pk interface or the normal aptdaemon client?
[16:40] <pitti> glatzor: normal aptdaemon
[16:42] <pitti> glatzor: that's bug 863875, BTW
[16:42] <ubot2> Launchpad bug 863875 in language-selector "Freezes when cancelling authenticate dialog" [High,In progress] https://launchpad.net/bugs/863875
[16:42] <pitti> reproducible with opening language-selector, trying to install packages (initial warning that support is incomplete, or adding a new language), and cancelling the auth dialog
[16:43] <pitti> AFAICS the transaction just seems to crash in the background, and the exception is never propagated anywhere
[16:46] <pitti> anyway, need to run for today, will look into this more tomorrow
[16:46] <pitti> good night everyone!
[16:47] <glatzor> pitti, night
[16:47] <didrocks> have a good night pitti :)
[17:15] <seb128> kenvandine, newed indicator-applet btw
[17:16] <kenvandine> seb128, thx
[17:46] <ronoc> mvo, ping
[17:47] <ronoc> i'm going to send a tarball towards kenvandine soon with that port to pk api, just so you know - (remember the libpackagekit pulls in package kit by default)
[17:47] <kenvandine> ronoc, that is ok, i'll build it in a chroot :)
[17:48] <ronoc> ah cool, thx kenvandine
[17:59] <didrocks> have a good night everyone!
[18:55] <jbicha> is there a tracking bug yet for the gtk text entry padding issue?
[19:03] <jasoncwarner_> hey kenvandine , pgraner just pinged me about this bug..is this part of some of the themeing issues we had recently?  https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/926269
[19:03] <ubot2> Launchpad bug 926269 in indicator-sound "sound indicator has white background on the volume and mic sliders" [Undecided,New]
[19:03] <kenvandine> yes
[19:03] <kenvandine> that is an ido bug
[19:03]  * kenvandine finds the right bug to dupe that
[19:04] <jasoncwarner_> kenvandine: when you say ido bug, is that a code bug, a theme bug or something else?
[19:04] <kenvandine> well, theme/gtk changes caused the breakage
[19:04] <kenvandine> but it needs to be fixed in libido
[19:04] <jasoncwarner_> kenvandine: and, asking another way *cough*cough*, is there a way to auto test stuff like this?
[19:04] <jasoncwarner_> kenvandine: ah, ok
[19:04] <kenvandine> we knew about this
[19:04] <kenvandine> it doesn't break usability
[19:04] <kenvandine> just ugly :)
[19:05] <kenvandine> https://bugs.launchpad.net/ubuntu/+source/ido/+bug/925700
[19:05] <ubot2> Launchpad bug 925700 in ido "light-themes draws the background of volume slider as white" [High,Confirmed]
[19:05] <jbicha> gtk's been doing a lot of theme changes (breakage) this cycle, hopefully they're almost done...
[19:05] <jasoncwarner_> kenvandine: dark themes too ;)
[19:05] <kenvandine> hey... seb128 assigned that one to me!
[19:06] <kenvandine> the problem is DX doesn't really have anyone maintaining ido
[19:06] <kenvandine> cimi was looking for somone to fix it but no takers
[19:07] <kenvandine> we'll get it fixed
[19:07] <kenvandine> but that certainly shouldn't be a high, it doesn't break usability
[19:11] <jbicha> ok I guess we can use bug 928814 to track it then
[19:11] <ubot2> Launchpad bug 928814 in gtk+3.0 "Text input padding too small with GTK 3.3.14" [Undecided,Confirmed] https://launchpad.net/bugs/928814
[19:14] <kenvandine> jasoncwarner_, theme related stuff has been kind of a disaster for the past couple weeks
[19:14] <kenvandine> each gtk release has made cimi have to race to play catch up
[19:19] <jbicha> and they've done a lot of releases
[19:20] <nessita> hello everyone! I'm getting some "new" warnings in my terminal, a few examples are:
[19:20] <nessita> Gtk-WARNING **: Theme parsing error: gnome-panel.css:67:25: Not using units is deprecated. Assuming 'px'.
[19:20] <nessita> Gtk-WARNING **: Theme parsing error: nautilus.css:10:20: Not using units is deprecated. Assuming 'px'.
[19:20] <nessita> Gtk-WARNING **: Theme parsing error: unity.css:19:25: Not using units is deprecated. Assuming 'px'.
[19:20] <nessita> shall I report that?
[19:21] <kenvandine> nessita, have you updated in the past few hours?
[19:21] <dobey> gtk on api stability: we won't break api (unless it's api we think people don't really care about)
[19:22] <nessita> kenvandine: this morning
[19:22] <kenvandine> the latest gtk3-engines-unico and light-themes should fix those
[19:22] <nessita> kenvandine: ack!
[19:22] <kenvandine> update again :)
[19:22]  * nessita re updates
[19:22] <kenvandine> gtk 3.3.14 deprecated stuff
[19:22] <nessita> kenvandine: thanks!
[19:23] <kenvandine> nessita, np
[19:23] <kenvandine> nessita, you should actually have quite a bit of brokeness theme wise if you are seeing that still
[19:23] <kenvandine> an upgrade will do you lots of good :)
[19:26] <nessita> kenvandine: :-)
[19:27] <cancer> hey there
[19:27] <cancer> I am a student of B.Tech CSE . My skill sets are C, C++, Java . and I wanna contribute to Ubuntu
[19:28] <cancer> where should I start from ?
[19:59] <dobey> kenvandine: hrmm, so maybe the crashes i'm seeing aren't gnomekeyring
[19:59] <dobey> but not sure what they'd be
[19:59] <kenvandine> oh?
[19:59] <dobey> seems to happen mostly when clicking add and then the [-] button under the list
[20:00] <dobey> since i can't actually add any accounts, it's very hard to isolate what exactly the problem is though
[20:00] <kenvandine> oh... so maybe it is the loading
[20:00] <dobey> because apparently keyring won't actually load or add any of the accounts
[20:00] <kenvandine> that is when it would load the gtk module for the service
[20:01] <dobey> yeah, it seems that some list is getting corrupted
[20:01] <dobey> probably the linked list of children in one of the widgets
[20:01] <kenvandine> but displaying that list of accounts really comes from all GetAccounts in the service
[20:02] <dobey> it also seems that the list of available services, and the path to the UI modules, also comes from the service
[20:02] <kenvandine> dobey, your branch also changes the service to use gnomekeyring via GI right?
[20:02] <dobey> i changed all instances of gnomekeyring, yeah
[20:02] <kenvandine> the path is assumed, based on the name
[20:02] <kenvandine> ok.. maybe try your UI changes against gwibber-service that is installed
[20:03] <kenvandine> and
[20:03] <kenvandine> you can use d-feet to verify GetAccounts returns a list of accounts, against your modified version
[20:03] <kenvandine> s/and/or/
[20:03] <dobey> hmm
[20:04] <kenvandine> since the accounts UI never loads any of the code the service uses
[20:04] <kenvandine> they can be independent
[20:04] <dobey> ** Message: console message:  @0: event.layerX and event.layerY are broken and deprecated in WebKit. They will be removed from the engine in the near future.
[20:04] <dobey> lovely
[20:05] <s9iper1> kenvandine: 3.3.5  uploaded ?
[20:05] <kenvandine> s9iper1, not yet
[20:05] <kenvandine> doing the indicators first
[20:05] <kenvandine> it might be tomorrow before i get to it
[20:05] <s9iper1> hmmm
[20:05] <kenvandine> sorry
[20:05] <kenvandine> i've got a pile of updates to do
[20:06] <s9iper1> hmmm i understand
[20:06] <s9iper1> np
[20:06] <dobey> kenvandine: so looks like it's still not showing the accounts, even when getting them from the installed service
[20:06] <kenvandine> interesting
[20:06] <kenvandine> stick a print statement after it gets the accounts
[20:06] <kenvandine> make sure you are getting data
[20:06] <dobey> so i guess i broke something
[20:06] <kenvandine> yup :)
[20:07] <dobey> where exactly does it get the accounts in the code for the accounts app?
[20:07] <kenvandine> accounts.py
[20:08] <kenvandine>     accounts = json.loads(self.gwibber.GetAccounts())
[20:08] <kenvandine> add a print accounts
[20:08] <dobey> hmm
[20:08] <dobey> so yeah, it got data
[20:08] <kenvandine> ok
[20:08] <kenvandine> oh
[20:09] <dobey> even with the gwibber-service from my branch, it shows it getting data
[20:09] <kenvandine> comment out the keyring call in populate_account_tree
[20:09] <dobey> although, gwibber-service itself doesn't seem to be polling the account for new posts
[20:09] <kenvandine> i forgot that was there, it highlights the entry if it can't find the secret
[20:10] <dobey> yep, keyring call is blocking it
[20:10] <kenvandine> woot
[20:10] <kenvandine> narrowing it down :)
[20:10] <kenvandine> so that must be it
[20:10] <dobey> well one problem at least :)
[20:11] <kenvandine> indeed
[20:13] <dobey> i wish i could figure out the stupid box expansion issues though. the ~32px tall embedded webkit is not very useful :(
[20:14] <kenvandine> i would focus on making it function first :)
[20:15] <dobey> well it's easier to test functionality, when the buttons aren't twice as large as the available display area :P
[20:19] <desrt> seb128: hey.  want to do a new gmake upload now? :)
[20:20] <seb128> desrt, I was just checking the debian version, I somewhat saw that coming :p
[20:20]  * desrt is so predictable
[20:20] <seb128> ;-)
[20:21] <seb128> desrt, I wonder why debian put it in experimental for 8 months and didn't move it out of there
[20:21] <desrt> seb128: -> #gtk+
[20:21] <seb128> desrt, since you make you look at make I will make you look at another nessita's bug :p
[20:22] <nessita> seb128: I can certainly find some :-D
[20:22] <seb128> desrt, https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/925676
[20:22] <ubot2> Launchpad bug 925676 in gtk+3.0 "GtkBuilder will not connect properly the activate-link signal to a GtkLinkButton" [Undecided,New]
[20:22] <seb128> nessita, oh, I've one on my list ;-)
[20:22] <desrt> seb128: i don't like bugs :p
[20:22] <nessita> seb128: right! you always are a step ahead of me
[20:22] <desrt> you're making my day bad!
[20:23] <seb128> desrt, I'm just make things even for your pings! ;-)
[20:24] <desrt> oh no.  more python bugs
[20:24] <desrt> nessita: are you working on a gtk version of the ubuntu one preferences?
[20:25] <nessita> desrt: hem... short answer: no. But I ported the ubuntu gtk SSO dialog to gi
[20:25] <nessita> desrt: that's where all those bugs came from
[20:25] <desrt> i'd be a lot happier to fix your bugs if i knew it was for a gtk preferences panel for ubuntu one ;)
[20:26] <nessita> desrt: well, ... if the plans turn out like we expect, we're dropping the Gtk controlpanel in favor of the Qt one. Yes, I know. No, I can't change that :-)
[20:26] <desrt> nessita: didn't platform team say that they don't want to ship the Qt panel?
[20:27] <nessita> desrt: last info I have, but info flows faster that I can tell, is that we can have the qt control panel. We're now sorting the issue about having the room in the CD for pyqt4
[20:27] <kenvandine> nessita, i think we have been convinced otherwise
[20:28] <kenvandine> assuming the planets align properly
[20:28] <nessita> kenvandine: what do you mean exactly?
[20:28] <kenvandine> making room for pyqt4, etc
[20:29] <nessita> kenvandine: perhaps the english is confusing me... are you telling me that you have been convinced to *not* make room in the CD?
[20:29] <nessita> or to do make room?
[20:29] <seb128> there is no such thing as room on the CD
[20:29] <kenvandine> hehe
[20:29] <seb128> whoever told you that: that's a lie! ;-)
[20:29] <kenvandine> i think we have been convinced that we can ship the qt4 control panel
[20:30] <kenvandine> but that assumes things like that happen
[20:30] <dobey> it assumes gwibber stops f'n crashing for me ;)
[20:30] <kenvandine> i suspect this is part of the driver for dobey hacking on gwibber to drop the webkit-gtk2 dep
[20:30] <kenvandine> which i appreciate a ton :)
[20:30] <seb128> did I say today how much I hate webkit?
[20:30] <seb128> hate webkit hate hate hate
[20:31] <desrt> seb128: more than i hate our mess of a build system?
[20:31] <kenvandine> seb128, add it to your quit message in xchat
[20:31] <seb128> desrt, I think at least as much
[20:31] <desrt> seb128: that's a lot of hate
[20:31] <kenvandine> :-D
[20:31] <nessita> kenvandine: yes, we plan on taking ownership of the room that dropping the gtk2 webkit will make
[20:31] <desrt> because i HATE libtool
[20:31] <seb128> you would think "it's ok, it's 8mb source"
[20:31] <desrt> and i'm not so crazy about automake either
[20:31] <desrt> and now i hate gmake :p
[20:32] <kenvandine> such a common conversation :)
[20:32] <seb128> until you realize the stuff takes 5hours to build on your i5 laptop, take 10G disk space you don't have on your 80G ssd and then run out of memory because ld goes over 3G
[20:32] <desrt> kenvandine: arguing about who gets to claim the free space or arguing about which software is more worthy of hate?
[20:32]  * ejat just do and update in precise .. now my launcher does not apper if u turn ON in behaviour
[20:32] <desrt> seb128: get a thinkpad :p
[20:32] <kenvandine> haha
[20:32] <kenvandine> both :)
[20:32]  * desrt just built webkit in ~20 minutes
[20:32] <seb128> desrt, I opted for "close firefox"
[20:32] <seb128> desrt, no way
[20:33] <ejat> normal or bugs?
[20:33] <desrt> seb128: it's in jhbuild
[20:33] <desrt> i just had to build gnome-shell to do a demo
[20:33] <desrt> and it has a webkit depend
[20:33] <desrt> it sucks, but it's not *that* bad
[20:33] <seb128> ejat, try asking on #ubuntu-unity
[20:33] <ejat> seb128: ok
[20:33] <seb128> desrt, I think you didn't build webkit but only some part of it
[20:33] <dobey> desrt: you are just a long-haired ball of hate wrapped up in a kilt, aren't you?
[20:34] <seb128> desrt, it takes over 3hours on my i5, no way it takes less than an hour whatever cpu you got
[20:34] <jbicha> desrt: what kind of computer do you have, mine takes hours until it runs out of disk space :(
[20:34] <desrt> seb128: i7 here with 8GB of ram and fast new intel SSD
[20:34] <jbicha> I need to get a bigger partition
[20:34] <jbicha> Core 2 Duo here!
[20:34] <desrt> maybe i don't build the whole thing
[20:34] <dobey> seb128: it's really fast if you build it all on a ramdisk
[20:35] <seb128> desrt, https://launchpad.net/ubuntu/+source/webkit/1.7.4-0ubuntu1/+build/3120654
[20:35] <desrt> ./configure --prefix /home/desrt/jhbuild/install --libdir /home/desrt/jhbuild/install/lib --enable-introspection --disable-static
[20:35] <seb128> Finished on 2012-01-26 (took 10 hours, 10 minutes, 58.7 seconds)
[20:35] <seb128> on amd64 builders
[20:35] <desrt> maybe --disable-static helps?
[20:35] <desrt> are you doing parallel make?
[20:35] <dobey> --disable-static definitely helps
[20:35] <seb128> no, it's broken in 1.7.4
[20:35] <desrt> works for me?
[20:35] <seb128> not in 1.7.4
[20:35] <desrt> make -j4 here, so using all 4 virtual cores
[20:35] <seb128> they might have fixed it in 1.7.5
[20:36]  * micahg wonders who seb128 knows with 24GB RAM to build webkit in a ramdisk
[20:36] <desrt> ya.  i have 1.7.5
[20:36] <seb128> which breaks on documentation build
[20:36] <seb128> when you break out of srcdir
[20:36] <seb128> hate webkit ;-)
[20:36] <seb128> micahg, yeah, weren't you supposed to maintain webkit? why do I have to deal with those updates? ;-)
[20:37] <dobey> webkit is a pretty good thing to hate though. building it is only one of many reasons :)
[20:37] <micahg> well, I'm supposed to do the stable releases :)
[20:37] <seb128> micahg, good, because I'm not going to do those for sure :p I just stepped up for the new serie because nobody was
[20:37] <micahg> but I realized earlier this week, I'm going to need to port glib/gstreamer/cairo code back to make it work
[20:38] <seb128> urg, have fun!
[20:38] <seb128> desrt, joke aside want to have a quick look to nessita's bug? ;-)
[20:38] <micahg> I tried building webkit with -j17 and it overheated my laptop
[20:38] <seb128> desrt, if you notice anything stupid in her example
[20:39] <nessita> seb128: thanks?
[20:39] <seb128> nessita, yw ;-)
[20:39]  * nessita is not stupid, though she makes some stupid things occasionally
[20:40] <seb128> nessita, you can join mvo in the pygobject hater club ;-)
[20:40] <nessita> seb128: I HATE pygobject. I use python because i hate segfaults, and now I'm getting plenty
[20:40] <seb128> yeah, same for mvo
[20:41] <seb128> no nice error trapping with pygobject
[20:41] <seb128> you just get plain C segfaults
[20:41] <dobey> yay introspection!
[20:41] <nessita> *not*
[20:42] <desrt> nessita: please bounce that bug upstream
[20:43] <nessita> desrt: care to help me giving me details how to do that? not sure what that means (can guess opening a new bug report in the pygobject bug tracker)
[20:43] <desrt> nessita: this looks like a gtk bug
[20:43] <nessita> desrt: hum, shall we try the same snippet in C before reporting upstream?
[20:43] <seb128> nessita, https://bugzilla.gnome.org/enter_bug.cgi?product=gtk%2B
[20:43] <desrt> nessita: that would be very helpful, actually
[20:44] <desrt> would prove that the bug is with C
[20:44] <desrt> actually, you know, after reading a bit more i am not convinced gtk is to blame anymore
[20:44] <seb128> nessita, let me try with C
[20:44] <desrt> i thought i saw something obviously wrong, but i misunderstood it
[20:45] <nessita> seb128: you read my mind, I may get a stroke if I write C again
[20:45] <nessita> :-P
[20:47] <m4n1sh> seb128: can you ask didrocks to upload the patch to privacy tomorrow whenever you find him online?
[20:47] <m4n1sh> someone hit on the issue with the .desktop file
[20:47] <m4n1sh> https://bugs.launchpad.net/activity-log-manager/+bug/928946
[20:47] <ubot2> Launchpad bug 928946 in activity-log-manager "The .desktop.in files don't match with executable file name" [High,Confirmed]
[20:47] <seb128> m4n1sh, what patch?
[20:47] <seb128> m4n1sh, ok
[20:47] <m4n1sh> the first comment on that bug
[20:47] <m4n1sh> I need to sleep
[20:47] <seb128> m4n1sh, ok
[20:47] <m4n1sh> good night
[20:48] <seb128> 'night
[20:55] <dobey> kenvandine: hrmm, got a bit further, now seeing this: http://pastebin.ubuntu.com/834453/
[20:55] <dobey> kenvandine: any ideas?
[20:56] <kenvandine> ok, that is what i got
[20:56] <kenvandine> looks like broken gir
[20:56] <kenvandine> the GnomeKeyringResult type isn't know or something
[20:57] <desrt> nessita: found the issue.  pretty sure it's a pygobject thing
[20:57] <nessita> desrt: nice! what was it?
[20:58] <dobey> kenvandine: i don't think that's it exactly. Result is an enum in the gir.
[20:58] <desrt> the signal connection function for python's override to GtkBuilder 'connect_signals' function sets the 'after' flag on the signal connection by default
[20:58] <desrt> at which point it's too late to cause the default action not to occur
[20:58] <nessita> desrt: I see. Makes sense since the dummy callback was indeed being called, but was not cancelling the call to the default handler
[20:58] <dobey> kenvandine: maybe it's something that deals with the return value, and out values, for python? the bit that adjusts it to return a tuple instead of just the one value?
[21:00] <kenvandine> dobey, i bet you are right
[21:00] <desrt> found the commit that introduced the issue
[21:01] <desrt> http://git.gnome.org/browse/pygobject/commit/?id=9f34d120845d936b04546a5cea599ec67e9181a7
[21:01] <dobey> kenvandine: ah. looks like perhaps GnomeKeyringfound type isn't bound
[21:01] <kenvandine> dobey, the gir says it takes an out
[21:01] <kenvandine> ok
[21:02] <desrt> nessita: did you file a bug?
[21:02] <nessita> desrt: upstream? not yet. Want me to?
[21:02] <desrt> no.  i can
[21:02] <nessita> desrt: ack, thanks!
[21:03] <dobey> kenvandine: hrmm, maybe not
[21:03] <dobey> kenvandine: yeah, but the <type> for that out is missing the c:type=
[21:03] <dobey> kenvandine: but it doesn't seem to be as simple as adding that
[21:04] <desrt> https://bugzilla.gnome.org/show_bug.cgi?id=669705
[21:04] <ubot2> Gnome bug 669705 in general "GtkBuilder signal connect override is buggy" [Normal,Unconfirmed]
[21:08] <dobey> locale: /lib/i386-linux-gnu/libc.so.6: version `GLIBC_2.15' not found (required by locale)
[21:08] <dobey> locale: /lib/i386-linux-gnu/libc.so.6: version `GLIBC_2.15' not found (required by locale)
[21:08] <dobey> fun
[21:08] <dobey> also bad X for screwing up the paste
[21:10] <dobey> kenvandine: hrmm, i guess the typelib is a bit busted though
[21:17] <rye> light themes are too light for my taste now - http://ubuntuone.com/0MLW9MY01Qqo80QnWloeY1 :)
[21:18] <rye> white labels on lightgrey, white text in white textboxes
[21:18] <rye> deja-dup
[21:18] <dobey> heh
[21:20] <desrt> seb128: may be worth a vendorpatch on this one
[21:20] <desrt> nessita: you are on precise?
[21:20] <dobey> kenvandine: ah, i see!
[21:20] <jbicha> hmm, yelp is broken with Ambiance & Radiance now, white text on white background
[21:21] <seb128> jbicha, open a bug on light-themes and give us the number
[21:21] <seb128> rye, same for you
[21:21] <rye> ah, it is not known?
[21:22] <seb128> jbicha, rye: in fact I can't confirm any of those, did you install the gtk3-engine-unico and light-themes updates from today?
[21:22] <rye> sorry for spamming the channel, i thought I was posting in #u1 one, got tricked because d0bey and ness1ta are here
[21:22] <kenvandine> there has been lots of fallout from recent gtk changes, and we need to make sure the theme keeps up
[21:22] <kenvandine> seb128, i confirmed in yelp
[21:22] <dobey> kenvandine: i think the find_items_sync needs an (array) annotation for the found parameter maybe?
[21:22] <kenvandine> main page is fine
[21:22] <kenvandine> but if you follow links you'll see it
[21:22] <seb128> yeah, and I can confirm in deja-dup there
[21:23] <kenvandine> dobey, according to the gir, yes
[21:23] <seb128> desrt, thanks for debugging it
[21:23] <jbicha> seb128: yes, I have gtk3-engines-unico 1.0.1-0ubuntu2 which is the latest
[21:23] <seb128> desrt, nessita: I just wrote a C version and can confirm it works in C, while desrt went directory to find the buggy commit :p
[21:24] <nessita> desrt: yes, update a couple of mins ago
[21:24] <seb128> jbicha, open a bug then, I will assign it to Cimi
[21:24] <nessita> seb128: :-)
[21:24] <desrt> seb128: i try to convince pbor to do a release
[21:24] <seb128> nessita, it remembered me why you hate C :p
[21:25] <nessita> hahahaha
[21:25] <desrt> *reminded
[21:25] <seb128> desrt, correct
[21:25] <seb128> I forgot -Wl,--export-dynamic when building
[21:25] <seb128> which is needed for the signal stuff to work
[21:25] <desrt> :)
[21:25] <seb128> it took me some minutes to figure that out
[21:25] <seb128> some days I hate C ;-)
[21:25] <desrt> you're supposed to use pkg-config with gmodule-export
[21:25] <desrt> desrt@moonpix:~$ pkg-config  --cflags --libs gmodule-export-2.0
[21:25] <desrt> -pthread -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include  -Wl,--export-dynamic -pthread -lgmodule-2.0 -lrt -lglib-2.0
[21:26] <seb128> desrt, well I just used pkg-config --cflags --libs gtk+-3.0 because I was doing a quick testing :p
[21:26] <desrt> just for future reference
[21:26] <seb128> desrt, thanks
[21:26] <desrt> it sets whatever is the appropriate flags for the platform you are on
[21:27] <seb128> desrt, pbor to release what?
[21:27] <desrt> seb128: pygobject
[21:27] <desrt> with nessita's two fixes
[21:27] <seb128> oh, I didn't know he was a maintainer for it
[21:27] <desrt> he's been reviewing my patches...
[21:28] <seb128> well we got a tarball on monday
[21:28] <desrt> he just pinged me about this latest one too
[21:28] <desrt> oh?
[21:28] <desrt> damn :p
[21:28] <seb128> pitti packaged it today
[21:28] <desrt> maybe vendor-patches then :)
[21:28] <dobey> kenvandine: making a patched package to test with :)
[21:28] <seb128> yeah
[21:28] <kenvandine> dobey, woot :)
[21:29] <seb128> desrt, if it lands in git we can convince pitti to backport it I'm sure ;-)
[21:29] <seb128> desrt, just get it landed in git and that should be enough
[21:32] <jbicha> seb128: bug 929126
[21:32] <ubot2> Launchpad bug 929126 in light-themes "Help viewer shows white text on white background in precise" [Undecided,New] https://launchpad.net/bugs/929126
[21:33] <seb128> jbicha, thanks
[21:33] <seb128> jbicha, knowing Cimi bonus point if you add a screenshot ;-)
[21:34] <jbicha> seb128: thanks, I'll add that in a second
[21:34] <desrt> seb128: at pbor's typical rate i imagine that will happen some time between 10 and 60 minutes from now
[21:34] <seb128> jbicha, thank you, I will ping him tomorrow
[21:34] <seb128> desrt, no hurry, pitti is off for the night
[21:34] <desrt> oh look.  it's landing right now.
[21:35] <rye> bug #929128
[21:35] <ubot2> Launchpad bug 929128 in light-themes "deja-dup backup window is white on lightgrey, white text on white background in details" [Undecided,New] https://launchpad.net/bugs/929128
[21:36] <seb128> rye, thanks
[21:36] <seb128> nessita, you can thanks desrt again ;-) I will ping pitti tomorrow to get the fix backported so we unblock you
[21:37] <nessita> seb128, desrt: thanks a lot! though I'm not blocked, we have a workaround in place for that
[21:38] <desrt> nessita: keep the reports coming :)
[21:38]  * nessita will try
[21:38] <desrt> gives me work to do while i wait for DBO to fix bamf :)
[21:40] <seb128> desrt, want to debug a gedit,gtk issue in exchange for pbor's review :p https://bugzilla.gnome.org/show_bug.cgi?id=669687
[21:40] <ubot2> Gnome bug 669687 in gtk "spell checking menu has lot of empty space" [Normal,Unconfirmed]
[21:40] <seb128> desrt, I guess geometry stuff are not your stuff though ;-)
[21:41] <seb128> I should rather ping cosimoc or Company about this one
[21:41] <desrt> seb128: more likely someone like company for that :)
[21:41] <desrt> ya.  i'm not touching this :)
[21:44] <dobey> kenvandine: hrmm, that didn't seem to fix it :(
[21:44] <kenvandine> :(
[22:01] <dobey> kenvandine: ah, no. the gir is fine
[22:03] <kenvandine> dobey, oh?
[22:04] <dobey> well, it's not converting a python dict to a GArray
[22:04] <dobey> but i am not sure that's a problem with the gir
[22:09] <dobey> kenvandine: it appears AttributeList is bound as an alias to GArray, and the utility functions like _append_string() for it, are not bound
[22:10] <kenvandine> but we don't need to use those...
[22:11] <dobey> kenvandine: except we do, because how else do you create the list of attributes?
[22:11] <kenvandine> oh
[22:11] <kenvandine> for the out parameter
[22:12] <dobey> no, for the attribute list
[22:12] <dobey> not the out parameter
[22:12] <dobey> the out is actually fine
[22:12] <kenvandine> oh... i see
[22:12]  * kenvandine got confused
[22:12] <dobey> hrmm
[22:12] <dobey> the gir is a bit broken though
[22:13] <dobey> because it thinks gnome_keyring_attribute_list_* are functions of the GnomeKeyringAttribute type
[22:13] <dobey> whee
[22:15] <dobey> so yeah, the gir is broken :(
[22:15] <dobey> but not in the way we thought
[22:17] <dobey> and i'm not quite sure how to fix it exactly
[22:20] <dobey> oh ken quit. what a quitter