20:00 #startmeeting Xubuntu community meeting 20:00 Meeting started Tue Mar 27 20:00:23 2018 UTC. The chair is knome. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 20:00 20:00 Available commands: action commands idea info link nick 20:00 who's here for the meeting? 20:00 (we encourage you to make some noise now even if you are just lurking) 20:01 lurking 20:01 hello willem :) 20:01 yup 20:01 (and while we do that...) 20:01 #topic Open action items 20:01 none carried on 20:02 #topic Updates and Announcements 20:02 #subtopic Wallpaper contest results (knome) 20:02 this is still work on progress, i've pinged people who need to do some more voting; results will be published as soon as we're ready 20:02 #subtopic Dbus timeout bug (flocculant) 20:03 https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1754836 20:03 Launchpad bug 1754836 in pulseaudio (Ubuntu) "Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)" [Undecided,Confirmed] 20:03 right 20:03 this sounds like a nasty one 20:03 so this is mostly about the fact we've 4 weeks left - and what we do if there's not change here 20:04 not as bad as it sounds 20:04 effectively (afaik) rubbish boot time to live session 20:04 yes 20:04 rubbish first boot time after install 20:05 assuming no bluetooth available 20:05 obviously it's not good - but it could be worse 20:05 have we heard any more from daniel from the bug than that single comment? 20:06 oh right - well he's wrong anyway :p 20:06 and did ali1234 end up with something that can lead to a fix? 20:06 will cooke is aware of the issue (ubuntu have a 25s delay - amongst other issues) 20:06 right... that sounds good (and i don't mean to sound snarky) 20:06 jibel is aware and looking at it amongst other things 20:06 i never found anything beyond what i wrote on the bug 20:07 ali1234, ok 20:07 oh yea 20:07 checked over the weekend - mate are affected - flexiondotorg was notified 20:07 yep 20:08 maybe this can get more leverage from there as well 20:08 mmh 20:08 anything else on this or shall we just keep an eye on it for now? 20:08 well 20:09 we need to at least have some idea of what we're going to do - I'd guess bluesabre will check logs later 20:09 the only workaround for this i can come up with is drop the bluez stuff (if even that helps) and that's a bit meh too for those who *do* have bluetooth 20:09 but nothing we can actively do now 20:09 especially if they are bt-only 20:09 i mean for input 20:10 I think I'd rather release note the problem for non-bt than leave bt floundering 20:10 yes 20:10 well 20:10 #info in case a fix or a good workaround isn't found, add a mention about this in the release notes 20:10 actually I'd pretty much refuse to release without bt even if it's a bit meh 20:11 yes, i don't think that's a very realistic option, just a fix for the bug... :P 20:11 yup 20:11 :) 20:11 shall we move on? 20:12 yea 20:12 #subtopic Numlockx on laptops (flocculant) 20:12 https://bugs.launchpad.net/ubuntu/+source/xubuntu-default-settings/+bug/1759112 20:12 Launchpad bug 1759112 in xubuntu-default-settings (Ubuntu) "Disable numlockx on laptops" [Undecided,New] 20:12 heh 20:12 i know... :P 20:13 so... what's the issue numlock being on with laptops? 20:13 so - at the weekend Sean and I discussed this a bit - some input from krytarik too - needs script to include laptop-detect 20:14 again - was just a put it on the table thing given just you and I atm :) 20:14 sure, but i'd like to know why it's a problem 20:15 and also, this sounds like a relatively easy one... 20:15 to fix, that is 20:15 if it is indeed an issue 20:15 currently - numlockx is on - which is fine on desktop - perhaps not so fine on a laptop - turn it off - reboot - turn it off 20:16 i understand, but why isn't it fine on laptop? 20:16 we 'could' do this with information on wiki or something too 20:16 knome: I just brought compaints to Sean's attention 20:16 or complaint 20:16 our blog is a bit more accessible than the wiki i think, so an article there would be good 20:18 anyway - up to dev's I suppose which they do 20:18 yep 20:18 i just dug through the links pasted here 20:18 good job krytarik, i'm sure that's a great solution (: 20:18 :D 20:18 moving on then 20:19 #subtopic Freezes 20:19 #info Documentation String Freeze: March 29 (two days!) 20:19 #info Final Beta Freeze: April 2 (for final beta on April 5) 20:20 #info (non-language-pack) Translation Freeze: April 12 20:20 likely to be April 3rd 20:20 ahha 20:20 well anyway, there that is 20:20 yup 20:20 so for the docstringfreeze, we need to get the slideshow in order 20:20 2nd is official date 20:20 i'll try to fix up that tomorrow 20:20 oh yea - that's sparse ... 20:21 anything else for the announcements? 20:21 but I see the damn thing too many times during a cycle to do more than shudder at it regardless 20:21 not for announcements 20:21 ok, moving on then :) 20:21 #topic Discussion 20:22 since there are no agenda items on the wiki, any other discussions? 20:22 * flocculant has something 20:22 floor is yours 20:22 (obviously...) 20:22 #subtopic - Result of Dev/QA recent blogpost 20:22 you aren't a chair 20:22 #subtopic - Result of Dev/QA recent blogpost 20:22 there we go 20:23 so iirc we did this just before the first Beta 20:23 march 4 20:23 we got increased coverage from NEW people on the tracker then 20:23 so hopefully - we'll see similar next week 20:24 maybe we could repost on social media to remind people of this 20:24 and also we got someone come by to start running 18.04 as daily and check things and report stuff 20:24 good good :) 20:25 so Willem - thanks for that - logged forever in the Xubuntu meeting archive 20:25 :) 20:25 yes, thank you willem :) 20:25 it's very much appreciated 20:25 good to see new people - always adds new perspectives 20:25 ok - nothing else from me 20:25 you're welcome :-) 20:25 not from me either 20:26 knome: yea - we can certainly be loud over the weekend I think 20:26 I'll start on m/l - then ping for twitter/g+ 20:26 #action knome, pleia2 and flocculant to coordiate some social media publicity for final beta testing 20:26 * meetingology knome, pleia2 and flocculant to coordiate some social media publicity for final beta testing 20:26 coordinate too, but who cares 20:26 :) 20:26 i guess i do... 20:26 #undo 20:26 Removing item from minutes: ACTION 20:26 ha ha 20:26 #action knome, pleia2 and flocculant to coordinate some social media publicity for final beta testing 20:26 * meetingology knome, pleia2 and flocculant to coordinate some social media publicity for final beta testing 20:27 #nick pleia2 20:27 #topic Schedule next meeting 20:27 next up is our fantastic artwork lead and council member ochosi 20:27 #action ochosi to schedule next meeting 20:27 * meetingology ochosi to schedule next meeting 20:27 #nick ochosi 20:27 any final words for the archive? 20:27 that'll be the Cantankerous Cicada first meeting then ... 20:27 :D 20:28 unless we get up in speed and have it within a week or 1,5 20:28 :) 20:28 might be useful that 20:28 I think needed 20:28 yep 20:28 always useful before a release 20:28 if ochosi forgets I'll call one 20:28 I'll likely be the one getting itchy for it :p 20:28 yes, let's try to do this probably very early next week 20:29 anyway... 20:29 #endmeeting