[06:28] <flocculant> knome: ta
[06:29] <flocculant> bluesabre: 3 visual bugs during install now \o/ thankfully only 1 is us :p
[06:29] <flocculant> missing slideshow has been reported elsewhere 
[06:43] <ochosi> also keep in mind that yakkety doesn't contain the latest greybird release...
[06:44] <flocculant> ochosi: that might be the 1 - not sure though
[06:47] <flocculant> bug 1617705
[06:47] <flocculant> the other 2 are slideshow and skip button issue(s) last is probably some gtk3.20/ubiquity thing
[06:51] <ochosi> oh right, yeah, that looks off
[06:51] <ochosi> stupid ubiquity custom widgets...
[06:51] <flocculant> :)
[06:51] <ochosi> i'll have to look into the installer myself for that
[06:51] <flocculant> have fun :p
[06:52] <ochosi> "thank you"
[06:52] <ochosi> :D
[06:52] <flocculant> :D
[06:52] <flocculant> I'll try not to find too much more ;)
[06:55] <flocculant> bluesabre: might be good if you remember that "bluesabre to schedule next meeting" before we're on Final Beta week :p
[06:57]  * flocculant thinks that now we have council with 3 people we should go back to the old way of running meetings
[06:57] <flocculant> I bet Unit193 could agree with me :p
[07:03] <Unit193> Ooooooh veeeery much I agree with flocculant.
[07:04] <flocculant> see - I knew it \o/
[07:05] <Unit193> Predictable, as always.
[07:06] <flocculant> lol
[10:12] <bluesabre> flocculant, indeed, was going to wait until the council results were finalized, and now they are :D
[10:15] <knome> old way being what? :P
[11:02] <flocculant> bluesabre: brave waiting for us to actually get something done ;)
[11:04] <flocculant> knome: not having to wait months for someone to set a meeting :p
[11:07] <knome> i do think that it's a fair way to split the chairing to all team leads
[11:08] <flocculant> of course you do :)
[11:08] <knome> maybe we can do something like a cycling chair, but if a meeting hasn't been held for X weeks, then the council will chair a meeting - after which we go back to the normal cycling chair
[11:08] <flocculant> not that it'll affect me for a long long time now :D
[11:09] <knome> well, i can see how not having meetings held can affect anybody
[11:09] <flocculant> do you mean can't? 
[11:09] <knome> no
[11:10] <knome> i mean if we don't have meetings, it surely affects everybody
[11:10] <flocculant> oic
[11:10] <flocculant> guess so :)
[11:10] <knome> at least theoretically
[11:10] <knome> i very much think regular meetings are good
[11:11] <flocculant> yea - even if it's just a touch base thing - I'd agree with that 
[11:11] <knome> because bringing back people's thoughts to thing X makes them... think about thing X and possible start working on thing X
[11:11] <knome> indeed
[11:11] <knome> and one of my arguments for regular meetings is that when they ARE regular and often enough, they won't be like 3 hour meetings
[11:11] <flocculant> ha ha 
[11:11] <knome> because "finally we are back together, what about this and this and this too?"
[11:14] <flocculant> the meeting cycling needs sorting out too - cos XPL/council/you 3 
[11:16] <flocculant> knome: thought you merged my strat doc changes? 
[11:18] <knome> no... still needs team verification as there are some changes that are not just wording
[11:18] <knome> i'll send a mail about it soonish
[11:19] <flocculant> aah okey doke
[11:20] <flocculant> bbl
[11:24] <knome> same here
[15:18] <akxwi-dave> finally got the f**king Exchange server back up and working after 6 hours
[15:18] <akxwi-dave> sry wrong channel
[15:29] <ochosi> bluesabre: strcmp0 is fine, but you also need tolower stuff somwhow (haven't found the best way yet), otherwise the comparisons are not human-approved
[16:10] <nairwolf> Hi everyone, I hope you're fine
[16:11] <nairwolf> Unit193: I've read your message ;)
[18:11] <knome> could somebody write a short blog article about the intel cursor bug SRU? i can help with formulating, but it would be nice to get somebody who has been following the process closely to get the basic stuff in
[18:12] <pleia2> yeah
[18:12]  * pleia2 drafts
[18:13] <knome> thank you
[18:15] <knome> oh also, we should start pointing to the release pages from the front page, not the release announcement
[18:15] <knome> that way we don't have to worry about update the widget on every update
[18:15] <flocculant> might be worth mentioning that while it is fixed for xenial - same issue appears to have now shown up on trusty
[18:15] <knome> *about updating
[18:16] <flocculant> and isn't covered by the sru
[18:16] <knome> can mention, but i'm not sure how much work we will take to get it SRU'd to trusty; EOL soonish
[18:16] <knome> (eg. if it takes another few months, meh)
[18:17] <flocculant> well yea - I wasn't suggesting sru for trusty
[18:17] <knome> nope
[18:17] <flocculant> iirc bluesabre and I did discuss that a while back - but I couldn't confirm
[18:17] <knome> aaand hmm.
[18:17] <knome> we might need to flush some rewrite rules on xubuntu.org
[18:17] <knome> i wonder how that's possible...
[18:18] <knome> oh
[18:18] <knome> there we go!
[18:18] <knome> so
[18:18] <knome> http://xubuntu.org/release/16-04/
[18:18] <knome> every article with the release "16.04" (or technically, "16-04") will be appearing on that page now
[18:18] <flocculant> nice :)
[18:19] <knome> indeed!
[18:19] <knome> well, they have been doing that previously
[18:19] <knome> but we now have all kinds of other yummy stuff there as well
[18:19] <flocculant> wily is still on http://xubuntu.org/help/ btw
[18:19] <knome> hmm
[18:19] <knome> i thoguht i removed
[18:19] <knome> it
[18:19] <knome> and thought
[18:20] <knome> removed now
[18:20] <flocculant> though it's gone from docs.x - pleia2 did that almost at the same time that I said we should lose it :)
[18:20] <knome> or was it me?
[18:20]  * knome shrugs
[18:20] <knome> yeah, it might have been that.
[18:20] <flocculant> don't think so 
[18:20] <knome> either way, i remember removing it from somewhere
[18:20] <flocculant> :)
[18:21]  * flocculant reboots after gtk update ... 
[18:22] <flocculant> once upon a time I used to reboot after kernel upgrades
[18:22] <pleia2> ok, someone can beautify it http://xubuntu.org/?p=4107&preview=true
[18:22] <pleia2> and publish
[18:23] <knome> also
[18:23] <flocculant> sigh
[18:23] <knome> http://xubuntu.org/release/16-04/ is now updated with download and documentation links that disappear on EOL date
[18:23] <knome> well, the day after...
[18:23] <flocculant> got that stupid login to x.org fail again :(
[18:24] <knome> pleia2, taking over your lock
[18:24] <pleia2> knome: yeah, I'm out of it
[18:24] <pleia2> wp is a bit aggressive :)
[18:24] <flocculant> knome: let me read it before you publish :p
[18:25] <knome> ok
[18:25] <flocculant> ta 
[18:25] <nairwolf> hi, if flocculant is right (intel cursor bug on Trusty), don't you think that could help users to publish a workaround somewhere in the website ? 
[18:25] <flocculant> knome: just in case is all :)
[18:25] <pleia2> nairwolf: the workaround is in all the release announcements...
[18:26] <pleia2> and bug reports
[18:26] <flocculant> nairwolf: perhaps it would help them to report it for trusty instead of adding to a bug report that's marked fix released
[18:26] <pleia2> not sure how much more we can do
[18:26] <flocculant> not that I'm saying we'd do anything - which is unlikely given the time scale
[18:27]  * pleia2 nods
[18:27] <nairwolf> I'm talking about the trusty version. I'm looking for the workaround in trusty pages actually
[18:27] <pleia2> we don't really want to be encouraging people to use trusty
[18:28] <nairwolf> https://xubuntu.org/release/14-04/
[18:28] <nairwolf> I don't see any mention of that, if this bug is actually present on Trusty
[18:28] <flocculant> nairwolf: you won't find it there
[18:28] <nairwolf> Yeah, but some people might have their reason to stay on 14.04
[18:29] <nairwolf> flocculant: where, please ?
[18:29] <flocculant> I didn't say it was anywhere - I said you won't find it there
[18:29]  * flocculant thinks that we should think about only supporting LTS to release of nextLTS.1
[18:30] <nairwolf> pleia2: I know that's somewhere in bug reports. But normal users don't go to launchpad (I may wrong), and they start to search information in the official website. If an annoying bug like that is present, they would like to know if it will be fixed, or if it won't, they would like to have a workaround. That's all
[18:31] <nairwolf> And I agree with flocculant about supporting LTS to release of next LTS.1
[18:31] <flocculant> nairwolf: if we started putting things like that on x.org - we would need a fulltime page writer
[18:31] <pleia2> LTS.1 has been out for over a month
[18:31] <pleia2> but a 2ish release cycle isn't really an option ;)
[18:31] <pleia2> er, support
[18:32] <nairwolf> flocculant: I could help ;)
[18:32] <flocculant> pleia2: then we should support it and sru the intel thing (if it's an issue) in the same way it was for xenial
[18:32] <nairwolf> Now, where users can see bugs known ? On the release announcement ? https://xubuntu.org/news/xubuntu-16-04-1-release/
[18:33] <pleia2> flocculant: probably so, but I'm not the one who has to do the work, easy for me to say :)
[18:33] <flocculant> pleia2: ditto :)
[18:33] <pleia2> nairwolf: yes, under known issues
[18:33] <nairwolf> Do you think that would be great to add more information on this page : https://xubuntu.org/release/16-04/
[18:33] <pleia2> no, it changes too much as we fix things
[18:33] <flocculant> knome: biab
[18:33] <nairwolf> I could help by providing a draft if you want
[18:34] <pleia2> it's not just a once off :) we need to keep it updated for every bug fix that comes out
[18:34] <pleia2> I can't really commit the time to staying on top of that
[18:34] <pleia2> the only reason we're doing a blog post about this fix is that it's pretty major and people complain a lot
[18:35] <nairwolf> okay, okay, I'm a newbie here. 
[18:35] <pleia2> I do appreciate the ideas
[18:35] <nairwolf> my first impression was it doesn't need so much job, but maybe I'm wrong. 
[18:36]  * flocculant washes screen - just imagined bluesabre's face reading pleia2 and flocculant talking about sru's :p
[18:36] <pleia2> lol
[18:36] <nairwolf> I was looking for something to do to help
[18:36] <nairwolf> anyway, I need to go right now, I will be back later
[18:36] <flocculant> nairwolf: one job is never too much - but this one job would be a never ending cycle of words :)
[18:37] <flocculant> nairwolf: you are helping - you just haven't realised it yet ;)
[18:37] <flocculant> really biab now
[18:38] <nairwolf> flocculant: The aim isn't to summarize ALL known bugs, and ALL bug fixes, but the most important. The ones about xubuntu specific package for example. 
[18:38] <nairwolf> see you later
[18:40] <nairwolf> flocculant: if you have time, can you confirm this bug on Yakkety ? #1567556
[18:41] <nairwolf> And I've seen this bug yesterday, but apparently, it will be fixed in the next version of greybird-gtk-theme : #1619059
[18:53] <fg01> Hi, Is some working on this https://bugzilla.xfce.org/show_bug.cgi?id=12763- Incorrect behavior of [Space] keyboard key in Thunar file-list?
[18:58] <knome> sorry, was on phone
[18:59]  * knome releases lock
[18:59] <knome> bbabl
[19:29] <flocculant> knome pleia2 - looking at the intel bug - there are 2 mentions of trusty there - and one of those is me saying I can't confirm it
[19:30] <flocculant> other 'trusty' mentions actually seem to be elementary
[19:30] <flocculant> oh hang on
[19:30] <flocculant> I'll look for 14.04 as well :p
[19:31] <flocculant> add 2 more 
[19:31] <pleia2> I haven't confirmed it either
[19:31] <pleia2> might drop from the post and just let people ask
[19:33] <flocculant> I did drop it - with my hat on :p
[19:34] <pleia2> ty
[19:34] <flocculant> if people want to ask - we can tell them it needs reporting properly from trusty 
[19:34] <flocculant> not piggybacked on a fixed xenial bug
[19:34]  * pleia2 nods
[19:35] <flocculant> I can publish - checked it for stranglish now too
[20:17] <knome> publish is ok, but please make sure it has the 16.04 release term
[20:19] <flocculant> knome: mm that's new on me - tick the 16.04 release box?
[20:19] <knome> yep
[20:19] <knome> same for every article that's related to releases
[20:19] <knome> gets stuff linked on the release page automatically
[20:20] <flocculant> right - just not seen it yet :)
[20:20] <knome> yup, no worries
[20:20] <knome> i've been ticking them here and there
[20:21] <flocculant> :)
[20:21] <flocculant> published
[20:21] <knome> thanks
[20:21] <knome> aaand as you can see: http://xubuntu.org/release/16-04/
[20:21] <flocculant> yup - was just looking :p
[20:22] <knome> i think this is working great now
[20:22] <flocculant> looks to be 
[20:22] <knome> with all the press stuff, links and screenshots too
[20:22] <flocculant> yea - nice one for sure :)
[20:23] <knome> now the next thing is to consider the sidebar in those pages
[20:23] <flocculant> I assume you saw coversation re trusty above 
[20:23] <knome> i don't think this is the one we want to use any more
[20:23] <knome> yes i did
[20:23] <nairwolf> flocculant: do you need I test if the intel bug is present with Trusty ?
[20:23] <nairwolf> I have real hardware for that
[20:23] <knome> which is why i said somebody who has been following should be involved with the article :)
[20:24] <flocculant> :)
[20:24] <pleia2> knome: good to social media it?
[20:24] <flocculant> nairwolf: YOU CAN IF YOU LIKE, NEEDS TO BE REPORTED THOUGH 
[20:24] <flocculant> oops
[20:24] <knome> pleia2, yep - and i can tweet
[20:25] <flocculant> knome: I see what you mean - sidebar looks a bit odd in the context of 'just xenial stuff'
[20:25] <knome> yep
[20:25] <knome> it was much better when we only had the article stuff
[20:25] <knome> then that page was just one of the archive pages
[20:26] <nairwolf> okay, I'm downloading Xubuntu 14.04
[20:26] <nairwolf> I'll tell you later
[20:26] <flocculant> nairwolf: don't expect lots of clamouring on it - we're not sure we'll do anything 
[20:26] <flocculant> that's down to tech 
[20:27] <flocculant> who's going to be so happy that I'll be using xenial for 6 months soon :p
[20:28] <nairwolf> flocculant: Yes, of course, I understand
[20:29] <nairwolf> It's just to verify by someone else
[20:29] <flocculant> knome: just one point re the 16.04 'page' I wonder if we need the blurb between EOL date and Official Links? 
[20:30] <flocculant> similarly for 14.04
[20:31] <knome> i think yeah - it's a nice way to summarize the release
[20:32] <flocculant> not sure I'd pick gnome software ;)
[20:32] <knome> feel free to improve it
[20:32] <flocculant> not that bothered - was just comment :)
[20:32] <knome> a few days ago it said 16.04 is the current development release ;)
[20:32] <flocculant> heh
[20:33] <flocculant> I'll say again that it's nice to see it all in one place though 
[20:33] <knome> indeed
[20:38] <knome> booting up desktop...
[20:40] <pleia2> knome: and should it be on the front page?
[20:41] <nairwolf> flocculant: had you time to check my bug report ?
[20:43] <flocculant> nairwolf: yea sorry - forgot to say, as ochosi said login is greybird everyone will see it in yakkety atm, the fix will land at some point
[20:43] <flocculant> can't confirm the imgur bug - works fine here
[20:45] <flocculant> nairwolf: there are other greybird issues as well 
[20:46] <nairwolf> You can't confirm the imgur bug ? this is weird, because I've tested it twice from my test computer, and from my actual computer. 
[20:46] <nairwolf> and in both case, I couldn't upload to imgur
[20:47] <nairwolf> which other issue ? 
[20:47] <flocculant> ok so perhaps it's something to do with isp's rather than xfce
[20:47] <nairwolf> ochosi said there will be soon a new version. 
[20:48] <flocculant> input box outline(s) some are thick, some are thin, progress indicators during install
[20:48] <nairwolf> I can go on imgur.com with the normal way (browser). I should check how the upload is done
[20:48] <nairwolf> oh,this bug, I've seen your report. Badly, I didn't pay attention to that yesterday
[20:48] <flocculant> nairwolf: well all I can do is try using it - and it works fine for me
[20:49] <flocculant> such is the way of bugs - some people see them some don't - at which point it's got to be something external influencing 
[20:50] <flocculant> could be anything, hardware for example 
[20:50] <flocculant> anyway - time for me to wander 
[20:50] <nairwolf> that's work today, on my actual computer
[20:51] <nairwolf> so I suppose you right, that was something related to isp
[20:51] <flocculant> could be - don't take my word for it there :)
[20:52] <nairwolf> it's funny to say that because I've tested twice at two times differently, and between them, I've uploaded a picture on imgur in the classic way (save picture then upload with browser)
[20:52] <nairwolf> I should retest that on the test computer
[20:57] <nairwolf> someone complain about the intel bug on 14.04
[20:57] <nairwolf> on facebook
[20:58] <flocculant> when it's on launchpad I'll read it
[20:59] <nairwolf> which "it" ? 
[21:00] <flocculant> people complaining about intel in 14.04
[21:00] <flocculant> we certainly can't do anything without that
[21:00] <flocculant> and re what I said (and pleia2) above 
[21:02] <nairwolf> okay, so the best answer is to share them the workaround or to tell them to upgrade, right ? 
[21:02] <flocculant> does the workround work? 
[21:03] <flocculant> don't tell people to upgrade - they'll have to do that eventually - but they might have reason to be using 14.04
[21:03] <flocculant> and finally - anyone who's talking about elementary based on 14.04 I have no interest in at all
[21:04] <nairwolf> I agree with elementary
[21:04] <nairwolf> I'm talking about one guy at facebook, which seemed to talk about xubuntu
[21:05] <nairwolf> but, yeah, maybe we'll see taht on launchpad also
[21:07] <flocculant> nairwolf: if you want to test this issue properly I would install 14.04, test for issue, upgrade to 14.05, test for issue, reinstall 14.04, upgrade to new hwe then test again
[21:07] <flocculant> one sensible report I saw said it was hwe upgrade issue
[21:08] <flocculant> with that - day done - night all :)
[21:09] <nairwolf> you mean, from 14.04.0 to upgrade to 14.04.5 ?
[21:09] <nairwolf> okay, maybe I'll do that this week-end. 
[21:09] <nairwolf> good night flocculant !
[21:35] <bluesabre> ochosi, https://developer.gnome.org/glib/stable/glib-String-Utility-Functions.html#g-strncasecmp gives a bit of detail on sorting without case
[23:21] <knome> pleia2, no, we don't push news items to front page...
[23:22] <pleia2> yeah, just curious :)
[23:23] <knome> basically my idea was/is to replace the link to the release announcement with a link to the release page
[23:23] <knome> that should serve users better too
[23:23] <knome> while allowing a different sidebar for the release pages, i kind of got involved with a huge revamp of the sites css >__<
[23:24] <knome> it's so much sleeker already
[23:24] <knome> ...but there are a few things that aren't working yet