[06:55] <flocculant> bluesabre: following robert ancell's comment on bug 1627304 - tested that - works to lock session, get to guest, logout, get back to session
[06:56] <flocculant> obviously without light-locker involvement
[07:14] <flocculant> bluesabre: I've narrowed this locking issue down to close to a date ... http://changelogs.ubuntu.com/changelogs/pool/universe/x/xubuntu-default-settings/xubuntu-default-settings_16.10.1/changelog
[07:15] <flocculant> somewhere roundabout 31st July
[07:15] <flocculant> reinstalled light-locker, purged x-d-s, installed the 16.04 version - all works ok 
[07:16] <flocculant> not had time to check if previous apparmor thing works with that old version 
[07:19] <flocculant> yes I did 
[07:19] <flocculant> so with old apparmor service, old x-d-s then everything works as expected
[09:34] <bluesabre> flocculant, so, its probably related to systemd...
[09:34] <bluesabre> https://launchpad.net/ubuntu/yakkety/+source/xubuntu-default-settings/+changelog
[09:36] <Unit193> He's in -release now with pitti.
[09:37] <bluesabre> aha
[10:10] <bluesabre> Unit193, actually, the xfce session was never migrated fully, still using startxfce4
[10:11] <Unit193> Well no, it wouldn't.
[10:12] <bluesabre> so...
 bluesabre: Look at -session too.
[10:13] <bluesabre> was more informational than anything?
[10:13] <Unit193> No, there was something I thought did an override, but couldn't remember.  Looking now.
[10:13] <bluesabre> ok, thank you
[10:16] <Unit193> https://launchpadlibrarian.net/275014126/xfce4-session_4.12.1-3ubuntu1_4.12.1-3ubuntu2.diff.gz I see.  Well I guess we'll see if user sessions work. :D
[10:20] <bluesabre> :)
[10:21] <bluesabre> flocculant, in case you miss it, we uploaded a new xubuntu-default-settings (16.10.2) that should resolve the locking issues
[10:44] -SwissBot:#xubuntu-devel- ::xubuntu-default-settings:: [trunk] r627 Revert systemd user unit changes (LP: #1622303), release 16.... (by Sean Davis)
[10:56] <flocculant> bluesabre: thanks :)
[11:05] <flocculant> bluesabre: \o/
[11:06] <flocculant> so that works - and so does guest, without fiddling with that apparmor profile
[11:06] <bluesabre> flocculant, neat!
[11:07] <flocculant> so - panic over till it's akxwi-dave's turn :p
[11:07] <flocculant> of course I'll keep the panic ticking over until that new x-d-s lands in the image ...
[11:08] <bluesabre> :D
[11:08] <flocculant> not really even sure why I started looking there this morning - but I did :)
[11:08] <bluesabre> much appreciated
[11:08] <flocculant> :)
[11:09] <flocculant> welcome - glad we don't need to worry about changing the locker
[11:10] <knome> woot
[11:10] <flocculant> yup
[11:11] <knome> nice
[11:12] <knome> btw, while relatively unlikely, i *might* be a bit late for the meeting today - if that happens, just boot the meeting and i'll pick the chair when i pop in
[11:13] <flocculant> ack - I'm relaxed about that meeting now :p
[11:13] <knome> yup
[11:16] <bluesabre> I'll probably be at least a few minutes late for the meeting
[11:16] <bluesabre> traffic some days is lovely, some days !@#$@!$
[11:17] <flocculant> tell me
[11:19] <flocculant> I will double check before meeting that reverted x-d-s plus what's going to change in the app.profile doesn't explode
[11:20] <flocculant> cos I can't remember quite what state which vm is in anymore :p
[12:12] <akxwi-dave> flocculant:  I have your telephone number, so only panic if you see its me ringing :-)
[12:18] <knome> isn't it fair for anyone to panic if akxwi-dave rings?)
[12:19] <akxwi-dave> oh yes...  :-)
[14:36] <flocculant> ha h a
[15:18] <flocculant> do we have to wait 7 days for x-d-s out of proposed?
[16:55] <flocculant> no we don't
[16:56] <flocculant> rebuilt iso, tested from scratch with a clean install \o/
[19:54] <knome> ok, not going to be late
[20:08] <flocculant> not going to be about for ages when it gets to it now :)
[20:09] <knome> ;)
[20:09] <knome> the reason i might have been late was a potentially very long board game - or one that started late
[20:10] <knome> but we're done now ;)
[20:10] <flocculant> :)
[20:22] <nairwolf> I completly forgotten there is a meeting tonight
[20:23] <nairwolf> badly, I'm completely unable to assist and participate
[20:23] <nairwolf> I will just read your discussion
[20:23] <nairwolf> I've seen some progress with the lock bug in the ml. Sorry for not being able to help you in this particular time...
[20:24] <flocculant> nairwolf: no problem - that's sorted now - I rebuilt iso with new package to confirm that
[20:26] <nairwolf> ok, the iso version 20160928 doesn't contain the new package? 
[20:30] <flocculant> yes it does - that's the one I rebuilt
[20:31] <nairwolf> ok ;)
[20:31] <nairwolf> if I find time this night, I would be able to test it
[21:20] <knome> !team | Meeting in 10 minutes!
[21:29] <fliberty> awesome - bnc died at the wrong time :p
[21:30] <knome> is there a right time?
[21:30] <fliberty> 4am :D
[21:32] <knome> #startmeeting Xubuntu community meeting
[21:32] <meetingology> Meeting started Wed Sep 28 21:32:14 2016 UTC.  The chair is knome. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[21:32] <meetingology> Available commands: action commands idea info link nick
[21:32] <knome> so.. who's here for the meeting?
[21:32] <fliberty> yup
[21:34] <knome>  anybody else? :P
[21:34] <knome> maybe we'll just wait for bluesabre 
[21:34] <fliberty> yep
[21:36] <fliberty> I'd guess he's not so omgomgomg now he knows that we're ok :)
[21:36] <fliberty> I know I am ...
[21:37] <knome> or maybe he is, remember he is likely in the middle of some traffic...
[21:37] <knome>  :P
[21:37] <bluesabre> o/
[21:37] <fliberty> oh yea :)
[21:37] <knome> o hai
[21:37] <fliberty> oh there he is :p
[21:37] <fliberty> hi bluesabre :)
[21:37] <knome> #topic Open action items
[21:37] <bluesabre> hi fliberty knome 
[21:38] <knome> #ACTION knome to look at installer slideshow and make sure everyting is up-to-date 
[21:38] <meetingology> ACTION: knome to look at installer slideshow and make sure everyting is up-to-date
[21:38] <knome> bluesabre, did you prepare file manager testing for Z?
[21:38] <bluesabre> knome, only started researching and dumping notes
[21:38] <knome> if not, maybe that would be better in a blueprint anyway?
[21:38] <bluesabre> I'll like the pad though
[21:38] <bluesabre> and yeah
[21:38] <fliberty> http://pad.ubuntu.com/xubuntu-z-filemanager
[21:38] <knome> oki, good
[21:39] <knome> bluesabre, Unit193: did you write a report of the state of Thunar?
[21:39] <fliberty> I started making a few notes on that pad ^^
[21:39] <Unit193> Yeah, sort of.
[21:39] <knome> do you still need to do some work on it?
[21:40] <bluesabre> Yes, I'd say so.
[21:40] <knome> #ACTION bluesabre and Unit193 to write a report of the state of Thunar (eg. which patches we carry and what they should do) and make sure all of them are in a PPA 
[21:40] <meetingology> ACTION: bluesabre and Unit193 to write a report of the state of Thunar (eg. which patches we carry and what they should do) and make sure all of them are in a PPA
[21:40] <bluesabre> works for me
[21:40] <knome> (that's just the old item, passing it forward)
[21:40] <knome> #topic Updates and Announcements
[21:41] <fliberty> #info We didn't release Final Beta due to bug 1622303
[21:41] <fliberty> phew memory for number worked ... 
[21:41] <knome> #info Final Freeze October 6 – thursday next week
[21:41] <knome> got to get the stuff in...
[21:42] <fliberty> #info little testing done for beta, I called a halt to it
[21:42] <bluesabre> looking forward to the new wallpaper :)
[21:42] <knome> that, and need to make sure the installer slideshow is "ok"
[21:42] <fliberty> #info qa/dev lots of backwards and forwards on sorting out the lock bug
[21:42] <bluesabre> that too
[21:42] <knome> so what caused the bug?
[21:43] <fliberty> knome: looks ok as long as no changes other than rat instead of cow on there 
[21:43] <fliberty> I've looked at it rather a lot lately ...
[21:43] <knome> fliberty, and no release numbers need changing?
[21:43] <bluesabre> knome, changes to xubuntu-default-settings regarding systemd user sessions, we rolled back and resolved the issue
[21:43] <fliberty> change to xubuntu-default-settings in late July/early August
[21:43] <fliberty> that :p
[21:44] <fliberty> knome: release numbers ?
[21:44] <knome> what was that change supposed to fix/bring?
[21:44] <knome> fliberty, eg. it doesn't boldly say "Welcome to Xubuntu 16.04!" ?
[21:44] <fliberty> oh it might 
[21:45] <fliberty> was more thinking of content of the top of my head
[21:45] <bluesabre> knome, "the entire session runs in one unit, it's not split up" per pitti
[21:46] <knome> ok... :P
[21:46] <bluesabre> I'm not very knowledgeable about init systems, systemd, and users and all that :D
[21:46] <Unit193> Well, systemd user sessions rather than upstart.
[21:46] <bluesabre> apparently I need to get there
[21:46] <bluesabre> Unit193 knows more about this stuff :D
[21:46] <fliberty> knome: nope - it says 16.10
[21:46] <knome> \o/
[21:46] <fliberty> but rat :p
[21:47] <knome> mmh...
[21:47] <knome> any other updates?
[21:47] <fliberty> but you knew that because it's not the last minute yet :D
[21:47] <bluesabre> maybe use the ubuntu yak logo as a mask on top of our mouse :D
[21:47] <fliberty> lol
[21:47] <knome> fliberty, yep, that's the spirit, fix the animal on the last possible night
[21:48] <fliberty> :)
[21:48] <bluesabre> (I think it would work, http://www.omgubuntu.co.uk/wp-content/uploads/2016/09/yak.jpg)
[21:48] <bluesabre> but yeah, nothing more from me
[21:48] <fliberty> nor me
[21:48] <knome> (how are yaks and tahrs even different?)
[21:48] <fliberty> well
[21:49] <fliberty> one starts with a y for a start 
[21:49] <bluesabre> the former is clearer to pronounce
[21:49] <knome> ;)
[21:49] <knome> #topic Discussion
[21:49] <knome> #subtopic Light-locker (bluesabre/flippylant)
[21:49] <knome> anything specific more?
[21:49] <fliberty> \o/
[21:49] <fliberty> not that I'm aware of
[21:50] <bluesabre> Not much to say here, light-locker is here to stay for now, but other lockers *can* work for us in the future if we need them
[21:50] <knome> mhm
[21:50] <bluesabre> Thanks to everyone who hopped aboard the locker testing on short notice
[21:51] <knome> indeed, thanks people
[21:51] <fliberty> I'd add if we get problems with it again we should be a bit more pro-active at thinking about changing and/or involving elsewhere
[21:51] <fliberty> this would have been really close to the wire :D
[21:51] <bluesabre> indeed
[21:51] <knome> or make sure our systemd expert Unit193 is at hand
[21:51] <fliberty> :)
[21:51]  * bluesabre gives the badge of init-honor to Unit193 
[21:52]  * fliberty gives the badge of running around shouting to akxwi-dave 
[21:52] <bluesabre> :D
[21:53]  * fliberty keeps the poke akxwi-dave with the stick to run around shouting :p
[21:53] <knome> #subtopic Other discussion (and badge handings)
[21:53] <knome> anything else?
[21:53] <fliberty> oh bah
[21:53] <knome> (:
[21:53] <fliberty> could have announcemented Release Candidate 
[21:53] <fliberty> quick sub-topic so I can do the obligatory on that please :p
[21:53] <bluesabre> Looking forward to next cycle, light-locker might come up again... if there were no actual issues with the systemd migration, it could be an incompatibility with light-locker or xfce and we might have to reevaluate
[21:54] <knome> #topic Yet another announcement section
[21:54] <fliberty> #info Release Candidate next week
[21:54] <fliberty> #action Xubuntu-team to test and report on tracker
[21:54] <meetingology> ACTION: Xubuntu-team to test and report on tracker
[21:54]  * bluesabre hopes we participate in that one
[21:54] <fliberty> hah
[21:54] <knome> yeah
[21:54] <bluesabre> :D
[21:54] <fliberty> it was close :p
[21:55] <bluesabre> #nick Xubuntu-team
[21:55] <bluesabre> if that wasn't already done and is still required
[21:55] <knome> actually, the final freeze is likely not thursday :P
[21:55] <knome> anyway
[21:55] <fliberty> #action bluesabre to please double check mugshot and webcams after enabling it
[21:55] <meetingology> ACTION: bluesabre to please double check mugshot and webcams after enabling it
[21:55] <bluesabre> oh yeah
[21:56] <bluesabre> #action bluesabre to update development blueprints for end of cycle
[21:56] <meetingology> ACTION: bluesabre to update development blueprints for end of cycle
[21:56] <fliberty> if for no other reason than to keep the bug chugging along on notes etc
[21:56] <knome> anybody else wants to pop up and throw work items at bluesabre?
[21:56] <fliberty> oooh I'm back \o/
[21:56] <knome> flocculant, you should either say something or we should #nick you
[21:57] <bluesabre> knome, have we started the -z- blueprints already?
[21:57] <flocculant> I'm back - bye fliberty 
[21:57] <bluesabre> bye fliberty, you were a welcome presence
[21:57] <bluesabre> awww
[21:57] <bluesabre> :(
[21:57] <flocculant> I saaw it :D
[21:57] <knome> bluesabre, nope, but there's nothing stopping us from creating stuff when we have content for them
[21:57] <bluesabre> knome, I'll probably get started with that soon
[21:58] <knome> great! if you need help... 
[21:58] <bluesabre> maybe add a bit to the release announcement that we like contributors :D
[21:58] <knome> so let's close this meeting
[21:58] <knome> #topic Schedule next meeting
[21:58] <knome> #action ochosi to schedule next meeting
[21:58] <meetingology> ACTION: ochosi to schedule next meeting
[21:58] <knome> #endmeeting
[21:58] <meetingology> Meeting ended Wed Sep 28 21:58:43 2016 UTC.  
[21:58] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/xubuntu-devel/2016/xubuntu-devel.2016-09-28-21.32.moin.txt
[21:58] <bluesabre> yay
[21:58] <bluesabre> thanks knome!
[21:58] <flocculant> lets not have ochosi doing that - might want one before he returns :p
[21:59] <flocculant> thanks knome 
[21:59] <knome> flocculant, he should be back tomorrow
[21:59] <knome> and minutes are up
[21:59] <knome> the wiki was blazing fast tonight
[21:59] <flocculant> knome: re website announcement for release - I'd perhaps like it more people orientated given wiki will be tech
[21:59] <knome> (no irony added)
[22:00] <knome> flocculant, yes, all improvement suggestions are welcome
[22:00] <flocculant> knome: re wiki - did you look at # on x.wiki yet? 
[22:00] <Unit193> Blazing == loaded within 3 minutes?
[22:00] <flocculant> ha ha 
[22:00] <knome> (though we still probably want to list bugs etc)
[22:00] <knome> Unit193, no, loaded instantly
[22:00] <knome> Unit193, editing too
[22:00] <knome> Unit193, and saving
[22:00] <knome> Unit193, and creating a new page
[22:00] <flocculant> knome: bluesabre's contributors loved type thing 
[22:00] <knome> flocculant, yep, that's good
[22:01] <flocculant> I'll probably do this cycles release note on u.w - don't have to think so much about formatting, unless I get around to editing the one I dropped on x.wiki
[22:01] <flocculant> of course
[22:01] <Unit193> bluesabre: You got the pad or do I need to search for it?
[22:02] <flocculant> Unit193: which ?
[22:02] <Unit193> Thunar.
[22:02] <flocculant> https://piratenpad.de/p/thunar-patches
[22:02] <flocculant> http://pad.ubuntu.com/xubuntu-z-filemanager
[22:03] <flocculant> thjose ones? 
[22:04] <Unit193> Yep, first.
[22:04] <flocculant> k 
[22:08] <flocculant> well - thanks for running meeting and for people turning up even though it wasn't strictly required as it turns out
[22:08] <flocculant> night all :)
[22:08] <knome> nighty flocculant 
[22:09] <Unit193> Slightly updated it.  Something else you wanted in it, knome/
[22:09] <bluesabre> night flocculant 
[22:09] <bluesabre> thanks Unit193 
[22:09] <knome> i'll look a bit later
[22:10] <Unit193> Sure.  I have no idea what's going on. :D
[22:10] <knome> ;)
[22:10] <bluesabre> :D
[22:33] -SwissBot:#xubuntu-devel- ATTN: Xubuntu Core 16.10 - i386 - i386 built.
[22:34] <Unit193> Oooh, I figured out what I was doing.
[23:20] -SwissBot:#xubuntu-devel- ATTN: Xubuntu Core 16.10 - amd64 - amd64 built.