[17:56] <flocculant> supposedly 16.04.1 releases next week 
[17:58] <flocculant> bluesabre: ^^, so even though we know we've got the 2 main issues (thunar and the intel/lock thing) I guess we've got no choice but to say yes there
[18:23] <knome> flocculant, i guess we can say no, but i'm not sure if that'd block the upgrade route for xubuntu... most likely not
[18:23] <flocculant> hardly worth bothering then in that case ;)
[18:23] <knome> yeah
[18:24] <flocculant> just checking where we stand with the intel thingy
[18:54] <flocculant> bluesabre: so this isn't right ... flocculant dons his positivity hat
[18:54] <flocculant> I happened to see a fleeting glimpse short while ago to an update for xorg-server-intel (or close)
[18:54] <flocculant> yakkety - suspend or lock > no cursor loss here
[18:55] <flocculant> updated xenial - still have an issue
[18:56] <Unit193> It's not been SRU'd.
[18:56] <flocculant> I know that Unit193 
[18:56] <Unit193> So, that's a good sign.  The changelog really doesn't show it though. :P
[18:56] <flocculant> just checking something else out
[18:57] <flocculant> Unit193: yea I know that too - I did check when I saw the update :)
[18:57] <flocculant> just haven't had time to physically do anything here
[19:08] <flocculant> bluesabre: so installing xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 from yakkety on the xenial and suspend and work as expected, no cursor loss (at least here)
[19:08] <Unit193> \o/
[19:09] <flocculant> what do we want to do about that - I can put an urgent call out for testing that - but don't want to do so if we're not actually going to be able to do more than say 'well it works'
[19:10] <flocculant> Unit193: indeed :)
[19:13] <flocculant> if I don't here anything overnight I'll go ahead with a tentative shout out I guess :)
[19:15] <flocculant> ochosi might want to read that ^^ 
[19:31] <flocculant> Unit193: and how long would an SRU take - I'm really wanting to read no more than a week :p
[19:32] <Unit193> Would be best to file it now and state that we want it in for the point release.
[19:35] <flocculant> well I don't think I'd want to file it - bound to get something wrong there
[19:35] <flocculant> perhaps it's best if I at least get a call out to test it now 
[19:35] <Unit193> bluesabre, bluesabre, bluesabre!  We need a SRU filed! :3
[19:36] <flocculant> ha ha 
[19:36] <Unit193> Done.
[19:36] <Unit193> flocculant: I'd test it if I hit it, but...
[19:36] <flocculant> yea - I only just manage to - laptop is in an advanced state of disrepair ... 
[19:43] <flocculant> Unit193: does this make sense? http://paste.ubuntu.com/19106931/
[19:44] <Unit193> flocculant: FWIW, you can have them just  apt-get install xserver-xorg-video-intel/xenial  to restore.
[19:45] <flocculant> actually that syntax? 
[19:45] <flocculant> if so - I'll do that rather than get them download from packages twice
[19:47] <flocculant> could they apt-get install package/yakkety?
[19:47] <flocculant> that's all new to me - learned todays thing now :)
[19:49] <Unit193> No, because people won't have that repo.  And yes that exact syntax.
[20:00] <ochosi> flocculant: sounds like a plan to me
[20:00] <ochosi> and also good to hear there's a tentative fix
[20:00] <ochosi> i think i read about some git version of the intel driver having fixed the issue for someone before
[20:14] <flocculant> Unit193: ack
[20:15] <flocculant> ochosi: yep - all we can do is test it I guess
[20:18] <ochosi> yeah, that plus filing the SRU as early as possible (agreed with Unit193 that bluesabre shall do that :p)
[20:21] <flocculant> well mail's off now
[20:38] <flocculant> night all
[20:45] <ochosi> night!
[20:45] <ochosi> and thanks
[20:47] <mozmck> Are live-build and the other live-* scripts used to build the xubuntu iso images?
[22:06] <bluesabre> evening all
[22:06] <bluesabre> I see highlights!
[22:07] <knome> :)
[22:13] <ochosi> evening bluesabre 
[22:13] <bluesabre> hey ochosi 
[22:13] <bluesabre> hi knome 
[22:13] <knome> o/
[22:13] <bluesabre> cooking dinner :)