[06:25] <flocculant> Unit193: I did - you were right :p
[06:27] <Unit193> A couple are translation only, whisker has small changes, weather uses a new version of the same API.
[06:28] <flocculant> k
[17:41] <flocculant> evening lurkers
[17:42] <pavlushka> evening flocculant !
[17:42] <flocculant> hi pavlushka 
[17:42] <flocculant> and hi cm2 
[17:44] <pavlushka> flocculant: had your evening tea?
[17:44] <flocculant> cm2: the 16.04.1 release will get whatever fixes for not-xubuntu and anything we can get in from xfce if there is anything
[17:45] <flocculant> but as far as intel wireless things landing - we're not able to really do anything there, personally I'd like to see that back of the disappearing cursor on lock/suspend with intel more :)
[17:46] <flocculant> but to be honest I'm not *completely* sure what .1 will have
[17:46] <flocculant> the first point release is more (afaik) about making sure there is a sane and working upgrade from previous LTS
[17:48] <flocculant> knome: re "ACTION: knome to initialize voting on the council proposal on devel ML (week from now)" I assume that refers in truth to getting nominations? 
[17:48] <cm2> flocculant: do you know what the wireless issue is about? bug in iwlwifi?
[17:49] <flocculant> cm2: not really - not actually seen it or heard of it 
[17:49] <flocculant> and people in *here* use intel and wireless and not heard them shouting either
[17:49] <flocculant> like ochosi for instance 
[17:49] <cm2> flocculant: ok; but it's always after a suspend.
[17:49] <flocculant> yup
[17:50] <cm2> flocculant: not in general. and restarting NM fixes it.
[17:50] <cm2> so not the end of the world.
[17:50] <flocculant> I did point skjones at something 
[17:50] <flocculant> right - that's what I found
[17:50] <cm2> i was looking through the power manager code, and there is a wait for a network manager dbus call.
[17:51] <cm2> because it doesn't happen when issuing a "systemctl suspend"
[17:51] <flocculant> given it's *buntu not just us - then that's definitely not something we'd be looking at specifically
[17:51] <cm2> xfce4-power-manager
[17:51] <cm2> flocculant: or do you mean you heard of the wireless thing from other *buntus?
[17:52] <flocculant> www.debugpoint.com/2016/05/quick-fix-no-wireless-connection-after-sleep-suspend-in-ubuntu-16-04-xenial-xerus/ and the bugs appear to be *buntu
[17:53] <flocculant> also not sure I saw that when checking out the cursor issue on my dead and dying lappy
[17:53] <cm2> flocculant: speaking of which, the xna vs sna doesn't help me
[17:53] <cm2> odd because it seems to work for everyone else
[17:54] <flocculant> cm2: ok - it was just something I saw while looking through 6 million reports (it felt like) 
[17:54] <flocculant> I think that the vt change is the best one generally
[17:54] <cm2> flocculant: :) so i won't tell you about my flickering lightdm
[17:55] <flocculant> and the sna issue seems to cause other problems too
[17:55] <flocculant> cm2: you can - I'll ask for the bug number :p
[17:55] <flocculant> and I'd love to see it tested with yak too 
[17:55] <flocculant> just to check that
[17:55] <cm2> flocculant: will do.
[17:56] <flocculant> awesome
[17:56] <cm2> flocculant: long weekend here, so maybe i'll have some time
[17:56] <flocculant> :)
[17:56] <flocculant> same here 
[18:01] <flocculant> cm2: you appear to be about a bit at the moment - I assume you know that our testing/qa team is always looking for people who're not just drive-by testers? 
[18:02] <flocculant> (and I think I recognise from ubuntuforum - or might be coincidence of course)
[18:06] <cm2> flocculant: yes i know. 
[18:06] <cm2> i'm a dev. thinking that maybe i should help with code?
[18:07] <flocculant> I'm sure that bluesabre and Unit193 would love to know that and have some help :)
[18:07] <flocculant> maybe send a mail to the dev list offering - they're not about till later in the *day*
[18:07] <flocculant> not sure what tz you are
[18:07] <cm2> flocculant: ok; i've been putting this off for like 5 years it seems like ;)
[18:08] <cm2> all the while enjoying my xubuntu experience
[18:08] <flocculant> and frankly more dev help trumps testing - unless you're not testing your code and/or fixes :p
[18:09] <flocculant> cm2: funnily enough I've been about more or less as long as you (gnome2/unity change)
[18:09] <cm2> flocculant: :)
[18:09] <cm2> although dont remind me. that was painful at first.
[18:09] <flocculant> yup
[18:09] <cm2> xubuntu has come a long way!!
[18:09] <flocculant> it certainly has :)
[18:10] <cm2> flocculant: btw, the thunar crashing thing, was it whilst renaming files?
[18:10] <flocculant> cm2: seems so - I can do that if I keep at it for a while
[18:11] <flocculant> but general re-naming I don't see it
[18:11] <cm2> flocculant: i already saw a patch for it.
[18:11] <flocculant> knome was seeing it often
[18:11] <flocculant> cm2: we applied a couple/few patches - which is what we have in yak ppa afaik
[18:12] <cm2> flocculant: ah ok. i'm looking at it now, g_file_monitor and friends.
[18:12] <flocculant> if that's the case ( bluesabre Unit193 ) ^^ then if we SRU it needs to be in yak? 
[18:13] <cm2> flocculant: it might be in it already
[18:13] <flocculant> cm2: seems that thunar activity in xfce is 'low'
[18:13] <cm2> flocculant: yes, but mostly it's because it is stable.
[18:13] <flocculant> cm2: I think we do have those patches - but I got lost between what we found pre-release and now
[18:14] <flocculant> and it's harder still because I have to manically rename things to crash it
[18:14] <cm2> flocculant: yeah, i've been trying to crash it but to no avail :)
[18:15] <flocculant> well that's good :)
[18:15] <cm2> flocculant: he he he yes.
[18:15] <flocculant> ok - evening time - disappearing for a while - be back later
[18:16] <cm2> flocculant: have fun
[18:16] <flocculant> well ... mostly food needed :p
[18:16] <cm2> :)
[22:18] <bluesabre> evening all
[22:18] <knome> hello
[22:19] <flocculant> hi bluesabre 
[22:20] <bluesabre> hey knome flocculant
[22:20] <bluesabre> how's it going?
[22:20] <knome> not too shabby
[22:20] <flocculant> as good as expected :)
[22:20] <bluesabre> better than I hoped :D
[22:21] <flocculant> ha ha 
[22:23] <Unit193> bluesabre!
[22:23] <bluesabre> hey Unit193
[22:24] <bluesabre> I'll start catching up from all the pings this week soon
[22:27] <Unit193> \o/
[22:27] <Unit193> I dumped off a packaging thing for you. :P
[22:29] <knome> Unit193 and the big dumb
[22:29] <knome> ...i mean dump
[22:29] <knome> (;
[22:29] <Unit193> knome haates me again. :'(
[22:29] <knome> noooo
[22:29] <knome> me loves you
[22:29] <knome> :D
[22:29] <Unit193> >_>
[22:29] <Unit193> KEEP BACK!
[22:30] <knome> ahahah
[22:30] <flocculant> hah
[22:30] <bluesabre> yeah, saw that, decided to keep it on the backburner til I made it to the weekend :D
[22:30] <Unit193> Ahaha. :D
[22:30] <Unit193> bluesabre: I got the others up!  Well, kind of ignored panel plugins because meh.  Xfconf might be fixed though.
[22:30] <bluesabre> saw that too, good news from aliov
[22:31] <flocculant> that's all great - personally I'd love to know what's going to happen about intel lock cursor fail :p
[22:32] <Unit193> Nothing I can do, and you certainly don't want me to try patching core things like that...
[22:33] <flocculant> Unit193: wfm
[22:33] <flocculant> or rather I've not got the problem so go for it :p
[22:33] <bluesabre> flocculant: I don't really know what to do with that, not touching the kernel, probably shouldn't change intel defaults for everybody
[22:33] <flocculant> Unit193: or are you talking about interesting stuff :D
[22:33] <flocculant> bluesabre: I agree with that :)
[22:34] <Unit193> that == intel drivers.
[22:36] <Unit193> bluesabre: I'm presuming http://paste.openstack.org/show/505960/ is of no importance.
[22:39] <Unit193> flocculant: Want to test xfconf before I copy it into xubuntu-dev/xfce4-gtk3? :P
[22:39] <Unit193> (I hit http://paste.openstack.org/show/505957/ too, but that's actually of no interest to us anyway.)
[22:42] <flocculant> Unit193: not right now ;)
[22:58] <bluesabre> Unit193: looks important
[22:59] <Unit193> :3
[23:00] <Unit193> Well, gtk/gnome stuff/etc always output warnings all over, so wasn't a surprise and the desktop worked. :P
[23:06] <bluesabre> fair enough :)