[00:06] <bluesabre> flocculant, we're not likely to get it fixed before beta, and I haven't seen cavalier about recently (light-locker's dev), so if we can't figure something out, we should keep the option of moving to xscreensaver or gnome-screensaver open
[00:07] <bluesabre> which will mean some fast and heavy testing
[00:08] <bluesabre> flocculant, I personally use gnome-screensaver, the VT switch is pretty annoying with some of my hardware (functional, but oh so slow)
[05:42] <flocculant> bluesabre: ack for that, given you didn't say anything about this issue and us not releasing tomorrow - I'll say we're not releasing tomorrow :)
[05:44] <flocculant> I'll tell infinity in -release now, if you want to change our minds - in -release as well please :)
[05:52] <flocculant> bluesabre: quick check of g-screensaver on this machine - wasn't slower than light-locker
[06:56] -SwissBot:#xubuntu-devel- ::xubuntu-docs:: [yakkety] r621 Launchpad automatic translations update. (by Launchpad Translations on behalf of ubuntu-core-doc)
[06:58] <flocculant> that's locking and suspend btw
[09:15] <bluesabre> flocculant, alrighty
[11:08] <flocculant> bluesabre: well - sent a testing call to the m/l, specifically pointing at the lock issue - perhaps we'll get some sensible comments on the bug
[11:23] <flocculant> bluesabre: given a choice between xscreen and the gnome one - I'd pick gnome 
[11:23] <flocculant> which I'm surprised by :p
[11:24] <flocculant> knome: if we're going to release note on wiki.x.o then where? subsection of dev,docs or qa? or section of it's own? 
[11:25] <knome> probably own section
[11:25] <flocculant> I'd imagine it having testing/release(s)/archived which ever
[11:25] <knome> maybe
[11:25] <knome> releases/xx.xx/release-notes
[11:26] <flocculant> wfm - and creating the section is easy? 
[11:26] <knome> yep
[11:26] <flocculant> not sure what you mean by that
[11:26] <knome> by what?
[11:26] <flocculant> eleases/xx.xx/release-notes
[11:26] <knome> oh, so
[11:26] <knome> http://wiki.xubuntu.org/releases/16.10/notes-beta
[11:26] <knome> for example
[11:27] <flocculant> aah right
[11:27] <flocculant> no
[11:27] <knome> then we could dump all release-specific stuff under that section
[11:27] <flocculant> we decided cycle or so back we would have a rolling note during dev cycle - which once released stops being changed
[11:27] <knome> mhm
[11:27] <knome> so it would be just one set of notes?
[11:28] <flocculant> knome: works like this
[11:28] <knome> then just notes-beta --> release-notes
[11:28] <flocculant> start z notes - edit, edit, edit, so when milestone happens note is current
[11:28] <knome> yep
[11:28] <flocculant> on release, note is forzen
[11:29] <knome> i'd still keep them under /releases
[11:29] <flocculant> oh yea
[11:29] <flocculant> running short of time now - I know what's in my head, I'll note it down later on a pad or something for you to see 
[11:30] <flocculant> back later
[11:30] <knome> http://wiki.xubuntu.org/releases/16.10/release-notes
[11:30] <knome> and see http://wiki.xubuntu.org/releases/16.10/release-notes?do=index for how it looks in the sitemap
[14:09] <krytarik> knome, flocculant: How about just "/releases/16.10/notes" instead?
[14:13] <knome> what if we want to do other kinds of notes?
[14:13] <knome> :P
[14:39] <Unit193> https://bugs.debian.org/838462
[15:05] <flocculant> knome: could do it like that - and given I'm not bothered enough to start wanting to delete pages on that wiki - I guess akxwi-dave will ;)
[15:47] <akxwi-dave> here he goes again, volunteering me..   Oh well.. :-)
[16:29] <flocculant> akxwi-dave: luckily for you I was volunteering you to get someone to delete something if you didn't want it :p
[16:29] <flocculant> no actual work involved - just some good old qa qwining :p
[17:29] <Unit193> flocculant: FWIW, if we change xscreensaver.desktop as shipped in xfce4-session (or add an override in x-d-s), "Switch Users" in xscreensaver will go to lightdm's login (xscreensaver ships a wrapper, /usr/share/xscreensaver/xscreensaver-wrapper.sh
[17:31] <flocculant> riiiiight
[17:31] <flocculant> alternatively installing gnome-screensaver just works :p
[17:31] <Unit193> (I'm informing, based on deps I surprisingly have nothing against gnome-screensaver.)
[17:31] <flocculant> and looks relatively modern against the xscreensaver from the 90s :p
[17:32] <Unit193> Hah, well it works, so hard to change for me.  Biggest thing against the gnome one, if it tries to install when I upgrade. :P
[17:33] <flocculant> I guess that post-b2 we'll have to make some sort of decision quite rapidly there
[17:34] <flocculant> Unit193: well yes it works - as long as I didn't try to do what sean asked me to do
[17:34] <flocculant> we keep having light locker issues *shrug*
[17:34] <Unit193> "Switch user"?  WFM!  (And only have one user.)  Again, not against gnome-screensaver (and really should try it out myself.)
[17:36] <flocculant> anyway - bit away ish now
[18:02] <flocculant> knome: quick question - on u.wiki you can # and it doesn't 'show' - no love for that with dokuwiki?
[18:03] <knome> it *should* work
[18:04] <flocculant> http://wiki.xubuntu.org/releases/16.10/release-notes
[18:04] <knome> i'll look into it, if not this week, then next
[18:04] <flocculant> okey doke
[18:04] <knome> will be away pretty much all weekend and lot of friday
[18:05] <flocculant> I did have a quick shufty about on the interwebs - what I saw talked about plugins
[18:05] <knome> yep
[18:05] <flocculant> ack - no rush obviously for this :)
[18:05] <knome> but basic commeting should work without the plugins
[18:05] <knome> and i did install a plugin once...
[18:05] <flocculant> right - appears not to atm
[18:06] <flocculant> anyway - enough of that, quick important thing then :p
[18:06] <flocculant> did you start announcement for b2? 
[18:06] <knome> nope
[18:06] <flocculant> k
[18:07] <davmor2> flocculant: they'll be a respin I found an issue it only affect everything :(
[18:07] <flocculant> though it's not going to announce a release - so I guess not too much problem - I can knock one out quickly if need be
[18:07] <flocculant> davmor2: we're very very very unlikely to be releasing anyway for a bug 
[18:08] <Unit193> I believe you'll have to add a plugin.
[18:08] <knome> apparently - i wrote a plugin
[18:08] <knome> apparently - it's not working (any more)
[18:08] <knome> weirdo.
[18:08] <flocculant> davmor2: the 3rd party thing? 
[18:09] <davmor2> flocculant: Yeap
[18:09] <flocculant> okey doke
[18:10] <davmor2> flocculant: kinda a hard to use a laptop with no wifi, gfx, sound, etc if you system required drivers or firmware installing :)
[18:10] <flocculant> davmor2: unless there's some miraculous fix for a light-locker issue then I'll be nixing it anyway for us
[18:10] <flocculant> davmor2: indeed :)
[18:10] <flocculant> on the positive side - at least this isn't Final :D
[18:11] <davmor2> no that in 3 weeks right so no pressure :(
[18:12] <flocculant> yup
[18:13] <flocculant> davmor2: tbh we keep getting light-locker things for the last couple of years - could be time to look elsewhere or even backwards
[18:26] <flocculant> I assume we don't need a 'slideshow shows some rat instead of some cow' bug?
[18:34] <davmor2> flocculant: just have a string of cowsays and nobody will notice the lack of slides ;)
[18:34] <flocculant> :)
[18:40] <akxwi-dave> flocculant: lol i know.. no worries.. after a long day at work..my attempt at humour.. :-)
[18:43] <flocculant> :)
[19:00] <flocculant> \o/ new tester got in touch 
[19:07] <akxwi-dave> nice.. who?
[19:09] <flocculant> dave has mail :p
[19:13] <akxwi-dave> nice...
[19:29] <Unit193> Ubuntu's ll has these extra configure flags: --enable-late-locking=yes --enable-lock-on-lid=yes --enable-lock-on-suspend=yes --enable-settings-backend=yes
[20:27] <flocculant> bluesabre: re locker, not sure what we'll need to do if we decide to change, nor how much time we'd get, nor how much testing we'll need, maybe we need to try and actually be about at the same time to properly discuss it - I'm not going to be able to be around late tomorrow - but can be on Friday if that helps
[20:35] <knome> Unit193, do we know if ll works better for them?
[20:35] <knome> i guess one option is to disable suspend for 16.10
[20:35] <knome> if that's the feature causing the problems
[20:36] <knome> that might be the "least intrusive way"
[20:40] <knome> one discussion we probably want to have before release anyway is if we are going to recommend avoiding the non-LTS path now more than often
[20:40] <knome> eg. we know many new xfce development'ish packages are going to be in before the next LTS,
[20:41] <knome> thunar might be broken and we're looking for a potential replacement,
[20:41] <knome> light-locker might be broken and we're looking for a potential replacement,
[20:41] <knome> what else?
[20:41] <knome> so at least as i've understood it, we've been pretty stable with non-LTS releases before - will this be the case even this time?
[20:45] <Unit193> knome: Corsac wants nothing to do with xscreensaver, so pretty sure he uses it.  I'd say we shouldn't "recommend avoiding it", but just be clear that file manager changes, etc might happen.
[21:16] <flocculant> knome: it's not suspend - it's locking, just that suspend uses locking 
[21:17] <flocculant> really don't think we should be thinking about disabling lock
[21:18] <flocculant> I did manage to try ll with the first 3 of the flags u uses - I assume - changed them with dconf editor - made no difference here
[21:20] <flocculant> this was from infinity to me earlier today "Maybe we can get it fixed in time, maybe not, but the more testing you can do, even if you don't release with the milestone, the better shape we'll be in to figure out how to move forward for release."
[21:20] <flocculant> so I assume from that we'll likely get some help here 
[21:20] <flocculant> that said - we've got 4 weeks to make a decision one way or the other
[21:21] <flocculant> back tomorrow
[22:11] <bluesabre> flocculant, I'll do some testing and write up some documentation for the lockers and whatnot
[22:11] <bluesabre> hopefully tonight