[00:00] <bluesabre> you bet I was
[00:00] <ochosi> poke what?
[00:01] <bluesabre> ochosi: nvm, you're free to go 
[00:01] <ochosi> :)
[00:01] <ochosi> anyway, i'm quite happy with how productive today's sprint was
[00:01] <ochosi> so kudos to everyone
[00:02] <ochosi> i'll have to set the next meeting soon, then we can see whether there's anything left to discuss
[00:02] <ochosi> bluesabre: have you seen the new MR by andrew for the greeter yet?
[00:06] <ochosi> so many options...
[00:28] <bluesabre> ochosi: haven't seen it yet
[00:31] <bluesabre> ochosi: actually, those look like nice improvements
[00:31] <ochosi> yeah, they are, it's just such a high level of customizability
[00:32] <ochosi> (keeping in mind that it's "just a greeter")
[00:33] <skellat> greeterD
[00:34] <bluesabre> right... eventually we'll run out of things to add though ;)
[00:34] <ochosi> heh
[00:34] <ochosi> as long as things are still stable, i'm fine with it anyway
[00:35] <ochosi> btw, i saw an odd bug about the greeter spawning new indicator processes with each login/logout
[00:35] <ochosi> sounds annoying for machines that run in public places with many users logging in and out each day
[00:36] <bluesabre> yeah, I think there might be a fix in the queue for that one
[00:39] <ochosi> oh cool
[00:39] <ochosi> that'd be relevant also for ll2.0
[00:39] <ochosi> imagine un/locking restarting indicators...
[00:40] <ochosi> i mean spawning indicators each time
[00:40] <ochosi> not really sure how ll2.0 and indicators are going to work anyway
[00:43] <ochosi> anyway, night all!
[00:43] <bluesabre> night ochosi
[00:44] <bluesabre> Unit193: so, any regressions likely by swapping evince to evince-gtk, or should we probably wait for the huge 3.14 drop?
[01:24] <Unit193> bluesabre: I have no idea, Gnome isn't something to predict.  I don't see -gtk picking up any new ones though, Debian still has it.
[01:25] <bluesabre> ok
[03:23] <Unit193> bluesabre: And, you may want to talk to Corsac as well.
[05:11] <Noskcaj> bluesabre, We already have evince 3.14, so it's unlikely anything will break form it
[10:56] <knome> added a mention of the release notes to near the top at http://xubuntu.org/help/
[11:49] <ochosi> folks, have any of you seen this sort of corruption in evince? http://www.zimagez.com/zimage/screenshot-2014-10-27-124835.php
[11:49] <ochosi> (seems related to ubuntu patching out the headerbars and faking a toolbar instead)
[13:28] <elfy> ochosi: yea - can confirm that 3.14.1 in vvampire
[13:30] <elfy> get a bunch of this, which looks familiar in a terminal (evince:12247): Gtk-CRITICAL **: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed
[13:30] <elfy> bbl
[13:47] <ochosi> elfy: hmpf, uncool. we could test whether it's there in evince-gtk too
[14:05] <ochosi> hmpf, yeah, at least in U the corruption happens for both evince and evince-htk
[14:05] <ochosi> gtk
[14:42] <bluesabre> that looks annoying... is that new with an updated theme? it looked fine when I tested earlier
[15:06] <ochosi> bluesabre: yeah, it is. if i open evince without a file, it looks fine. if i open a pdf, i get this sorta corruption
[15:06] <ochosi> installed Ub2 and then upgraded
[15:26] <brainwash> bluesabre: any news re bug 1382977 ?
[15:27] <brainwash> did you or anyone else test the fix from upstream?
[15:39] <elfy> ochosi: ok - so I removed evince, installed -gtk
[15:40] <elfy> when I start it - no corruption as you, then open 1 and no corruption, open another and get corruption
[15:41] <ochosi> elfy: yeah, silly bug :/
[15:41] <elfy> yep
[15:41] <ochosi> the upside seems to be that evince-gtk seems to work just as well/badly as evince
[15:42] <elfy> and re the mimetype issue above - if thunar in vampire includes the upstream fix - then it appears to be ok as I don't get the same thing now here
[15:42] <elfy> ochosi: does this evince issue have a bug report or need one?
[15:43] <ochosi> it doesn't have one yet
[15:43] <ochosi> i've been pinging some folks in u-desktop about it, to see whether it appears in unity too
[15:43] <elfy> ok - I'll do one - start with LP 
[15:43] <ochosi> just to know what to file it against (shimmer-themes or evince)
[15:43] <ochosi> okeydokey, thanks!
[15:43] <elfy> I can confirm or deny in unity first then :)
[15:44] <ochosi> you have unity installedß
[15:44] <ochosi> ?
[15:44] <elfy> no - but I tend to - when *we* get some issues I like to confirm in unity so I can hassle balloons :p
[15:44] <ochosi> ok :)
[15:44]  * ochosi hasn't tried unity in years
[15:44] <elfy> it's only ever a vm 
[15:45] <elfy> it is better than it was seemingly - but I don't use it for long enough to really tell
[15:47] <elfy> oh
[15:47] <elfy> odd
[15:49] <elfy> ochosi: so do you see it with all pdf's?
[15:49] <ochosi> humm, i haven't noticed a pattern
[15:49] <ochosi> it just seemed to pop up randomely
[15:49] <ochosi> have you?
[15:49] <elfy> not seeing a pattern 
[15:50] <ochosi> mka
[15:50] <ochosi> y
[15:50] <elfy> but if I rollup the title bar and then roll down a corrupted one is then uncorrupted
[15:50] <ochosi> yeah, which is why i think it's just a gtk rendering issue
[15:50] <ochosi> and i still suspect it's connected to that headerbar patch
[15:50] <ochosi> the only way to find out for sure would be to try evince 3.14 from upstream
[15:51] <ochosi> maybe there's a gnome3 ppa with evince with headerbar...
[15:52] <elfy> I'll get unity installed for the moment as I'll need it eventually anway
[15:53] <ochosi> elfy: the stuff in "discussion" on the meeting page has actually been discussed, right?
[15:53] <ochosi> so if you don't mind, i'd take it off there to clear space for the next meeting
[15:53] <ochosi> unless there is stuff to be kept around
[15:53] <elfy> yep - fine to clear that
[15:54] <ochosi> ok, ty
[15:58] <ochosi> !team | halloweeny meeting on friday, 11 utc
[15:59] <elfy> might still be awake :)
[15:59] <elfy> or might be unable to type ... 
[16:01] <ochosi> :)
[16:41] <elfy> ochosi: radiance theme in unity http://www.zimagez.com/zimage/screenshot-271014-163954.php
[16:41] <elfy> let me know how you want me to about reporting it 
[17:40] <knome> ochosi, ^ added to calendar
[17:40] <knome> ochosi, and that's 11am, right?
[18:01] <elfy> oh 
[18:01] <elfy> silly me - assumed sensible time at night 
[18:03] <knome> hehe
[18:03] <Unit193> He linked to the clock that said AM.
[18:03] <knome> i'm not paying attention!
[18:03] <knome> :P
[18:04] <elfy> while this whole moving feast time is great - I wonder about the sense in having one person run 3 out of 9 
[18:04] <elfy> and someone else 2 out of 9
[18:05] <slickymasterWork> well, at least it won't crash with dinner time
[18:06] <knome> slickymasterWork, lol, because everything else you can move around except EATING
[18:06] <knome> ;)
[18:07] <slickymasterWork> when my kid is with me is sort of difficult to move meals 
[18:07] <slickymasterWork> one thing that always works great with younger kids is routines knome 
[18:09] <knome> i was just teasing
[18:10] <Unit193> And, http://38.media.tumblr.com/tumblr_m72yoqybvl1qgbyhko1_500.gif
[18:10] <slickymasterWork> yeah, I know :)
[18:11] <slickymasterWork> lol Unit193, quite right, she is
[18:30] <knosys> hello
[18:58] <Unit193> Looks like a short meeting, too bad I can't attend and make it shorter. :D
[18:58] <elfy> lol
[20:12] <knome> http://www.chiark.greenend.org.uk/ucgi/~cjwatson/blosxom/2014/10/26#2014-10-26-moving-on-but-not-too-far
[20:12] <elfy> yea read that 
[20:13] <Unit193> Linked to yesterday ^.  Sum up, LP only, or tiny bugs.
[20:13] <knome> i actually consider that a good thing
[20:14] <Unit193> Stepping down before burning out fully?  Or getting rid of cjwatson? :P
[20:14] <knome> not because he's now away from development, but because him working "full-time" on launchpad is (hopefully) going to be awesome
[20:14] <knome> and stepping down before burnout too
[20:14] <Unit193> Right, but really stinks for Ubuntu.
[20:14] <knome> does it?
[20:14] <knome> and do you mean ubuntu or ubuntu desktop :)
[20:14] <knome> going to eat some, back after that
[20:26] <ochosi> yes, am
[20:26] <ochosi> not pm
[20:27]  * Unit193 PMs ochosi.
[20:27] <ochosi> bbiab
[21:27] <Unit193> http://paste.openstack.org/show/a0y78WkRnO7oeqkiuYF4/
[21:39] <knome> sighj
[21:39] <knome> -j
[21:42] <Unit193> Yeeep, but at least it's the same one as last time I pasted, and not a new one!
[21:45] <Unit193> knome: Did you fix it?
[21:46] <Unit193> knome: We can blame slickymaster if you didn't, because he's docs lead! :D
[21:46] <knome> i didn't, but maybe i should look at it
[21:55] <knome> Unit193, is there a quick way for you to check who has done those translations?
[21:56] <knome> Unit193, especially the ones that bring the translated tags?
[21:56] <knome> would like to tell the contributor to stop doing that because obviously we can't run after them and fix stuff all the time
[22:08] <Unit193> Think so on LP.
[22:20] <knome> https://launchpad.net/~franciscomol
[22:20] <knome> also has done </ application>
[22:20] <knome> i don't know if it's ok to leave spaces like that
[22:21] <knome> and another semi-annoying thing is that he's leaving spaces inside the tags
[22:21] <knome> i mean...
 App name </application>
[22:31] <knome> bluesabre, slickymaster: docs branch for vivid set up
[22:35] <knome> Element placeholder-2 in namespace '' encountered in guimenuitem, but no template matches.
[22:35] <knome> ^ for PT too
[22:35] <knome> tut tut, slickymaster 
[22:40] <knome> Unit193, should running 'make' in the docs root clean up lang directories under desktop-guide ?
[22:47] <Unit193> make clean?
[22:47] <knome> aha
[22:47] <knome> :)
[22:48] <knome> now, why does the makescript need to give me silly line numbers
[22:48] <knome> like 315
[22:48] <knome> i know that's the virtual line number for that spot in the whole documentation, but it's not too useful
[23:14] <knome> Unit193, oh! have you noticed that if you s/--postvalid/--valid/ in scripts/validate.sh, you actually get the context too?
[23:15] <knome> wonder if there's any reason to keep --postvalid as the default argument?
[23:15] <Unit193> Never tried.
[23:15] <knome> /home/knome/Downloads/es.po
[23:15] <knome> eh
[23:15] <knome> --postvalid Validate after parsing is completed. 
[23:15] <Unit193> (Also not always sure what's different/uncommitted here. :P )
[23:16] <knome> oh, yeah
[23:16] <knome> it fails the IDREF attrs
[23:16] <knome> >__<
[23:16] <Unit193> Makefile, debian/control, desktop-guide/Makefile, scripts/translate.sh, scripts/validate.sh, and my own wrapper, I see.
[23:17] <knome> you should do a MP for all the improvements you have stacked there.
[23:17] <Unit193> "improvements", hah. :D
[23:19]  * knome shakes head
[23:20]  * Unit193 be hacking up the buildsystem.
[23:21] <bluesabre> hey all
[23:22] <Unit193> knome: http://paste.openstack.org/show/0nnq42t16hbMea43TRHb/ nothing groundbreaking, and the one is an attempted fix for the current problem, but doesn't fix it.
[23:22] <Unit193> bluesabre: Also, hello.
[23:23] <knome> Unit193, do a MP, i'll merge them today so you can keep hacking
[23:23] <knome> hey bluesabre 
[23:24] <Unit193> knome: Should have bluesabre magically fix it.
[23:24]  * bluesabre is a bit busy through Friday
[23:25] <Unit193> :(
[23:27] <knome> Unit193, all of the validation fails in es.po was from the same user
[23:27] <knome> and all of them was basically that tags were translated
[23:29] <knome> hmm, now pt also magically validates
[23:54] <Unit193> http://paste.openstack.org/show/XYdFzBsMMIinNNlVFqjB/ new one.