[06:31] <flocculant> bluesabre: so now we've got people complaining that numlockx is on (laptops) in the original report there was some laptop-detect=0 comment - there's some comment about laptop-detect in this https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734701
[06:31] <flocculant> anyway - got the user on the forum to report it to x-d-s
[06:43] <flocculant> flexiondotorg: did you know you're affected by bug 1754836
[06:43] <flexiondotorg> flocculant: Looking now...
[06:45] <flocculant> flexiondotorg: I didn't do an actual usb install of Mate, but I expect it'd be the same there as for us
[06:46] <flexiondotorg> I'll have to test. But I've not knowingly encountered this issue.
[06:46] <flexiondotorg> We did have boot delays due to seeding snaps, but those issues are resolved.
[06:47] <flocculant> flexiondotorg: I just tried it in qemu - to check .xsession-errors and there it is 3 25s timeouts
[08:38] <ochosi> bluesabre: please pull in the latest elementary-xfce commit to xubuntu-artwork too, need that for the CSD icons to be fixed
[10:13] -SwissBot:#xubuntu-devel- ::xubuntu-artwork:: [bionic] r337 Update elementary-xfce window manager icons from d823986... (by Sean Davis)
[11:07] <tomreyn> hi! is https://xubuntu.org/news/testing-for-xubuntu/ still as much of a problem?
[11:07] <tomreyn> (i'd be happy to spend some time testing if needed.)
[11:26] <flocculant> tomreyn: it's been a problem since April 2014 ;)
[11:26] <flocculant> for some reason community involvement just after 14.04 released went belly up 
[11:26] <flocculant> s/with testing
[11:27] <flocculant> tomreyn: what we (Dev and QA) are mostly after is testing of Xubuntu Dev during the 6 month cycle prior to release
[11:27] <flocculant> though of course testing iso's at milestones has it's role too
[12:30] <bluesabre> Unit193: what's the standard versioning scheme for packages with a git snapshot?
[12:31] <bluesabre> Looking to do a greybird 3.22.7 + 031f985
[12:33] <bluesabre> I'd just do it as a patch, but pngs
[12:34] <flocculant> hi bluesabre 
[12:34] <bluesabre> hi flocculant 
[12:34] <bluesabre> how's it going?
[12:34] <flocculant> pretty good thanks :)
[12:35] <flocculant> got people complaining about numlockx :d
[12:35] <bluesabre> Saw that
[12:35] <flocculant> and I found the blueman thing in mate ;)
[12:35] <bluesabre> Guess I'll need to tweak our script
[12:35] <bluesabre> and that's good news
[12:35] <bluesabre> (means it will probably get looked at)
[12:36] <flocculant> yea - wasn't sure about that laptop-detect thing in the original numlock report - but I guess
[12:36] <bluesabre> flocculant: you have a desktop?
[12:36] <flocculant> and yea re the timeout jibel is looking at some 'timeout/long boot things'
[12:37] <flocculant> I do have desktop
[12:37] <bluesabre> what does...
[12:37] <bluesabre> laptop-detect
[12:37] <bluesabre> echo $?
[12:37] <bluesabre> get you?
[12:37] <bluesabre> I have a laptop and it returns 0
[12:38] <bluesabre> looking at the manpage, that seems right
[12:38] <tomreyn> thanks for your feedback, flocculant. maybe it would be a good idea to have a tiny utility integrated into xubuntu by default which allows users to opt-in to receiving your calls for testing / reminders
[12:38] <bluesabre> so flocculant, you should get 1 from that echo
[12:38] <flocculant> bluesabre: how do I run that ?
[12:39] <flocculant> laptop-detect gives nothing
[12:39] <bluesabre> flocculant: right, it sets a return code, that "echo $?" gives you that return code
[12:40] <flocculant> laptop-detect echo $ gives me unknown option 
[12:40] <tomreyn> flocculant: i suspect that a relevant fraction of users are usually happy to help testing but may need (and expect to be provided with) a reminder when to do so. the same probably goes for donations, if needed.
[12:40] <bluesabre> two lines :)
[12:40] <bluesabre> here
[12:40] <bluesabre> laptop-detect; echo $?;
[12:41] <flocculant> 1 
[12:41] <flocculant> :D
[12:41] <flocculant> tomreyn: I agree - but I'd not want to have some thing installed which let us ping people ...
[12:42] <tomreyn> flocculant: just those who opted in to it. why not?
[12:42] <bluesabre> flocculant: cool, so since that works like I'd expect, I'll add that to our script
[12:42] <flocculant> I'd say that given we use mailing lists/social media and launchpad we've pretty much covered people who want to be part of the community
[12:42] <flocculant> tomreyn: ^^
[12:42] <flocculant> bluesabre: ack
[12:43] <flocculant> bluesabre: I'll get rid of the lightdm script I added locally ages ago so I'm using 'ours' then wait to see update - then make sure it works
[12:44] <flocculant> I'll also ping the user in the forum about it too
[12:44] <flocculant> tomreyn: we can lead people to water ... ;) seemingly it takes whinges to make people take notice - sadly
[12:45] <tomreyn> flocculant: personally, i'd not want to "be part of the community", i'd be happy to provide occasional (say twice a year) test feedback on specific tasks. that's because i like using xubuntu, and want to support it going forward, but also my spare time is too valuable to make me want to engage with the project in a general sense (i.e. joining a community)
[12:45] <flocculant> tomreyn: you read the blog post - responded - part of the community ;)
[12:45] <tomreyn> (and i suspect i'm not alone in this take on things)
[12:46] <tomreyn> well, that was merely accidential, i guess.
[12:47] <tomreyn> i was wondering which new features will be available in 18.04. but obviously it's too late now to make any impact.
[12:48] <tomreyn> i do understand that maintaining multiple communication channels in parallell is a taxing task for a volunteer run project (i assume that's what xubuntu is).
[12:54] <flocculant> tomreyn: https://wiki.xubuntu.org/releases/18.04/release-notes
[12:54] <flocculant> and yea - definitely a volunteer project :)
[14:05] <ochosi> bluesabre: thanks, i can do stable releases before final freeze
[14:19] <knome> privacy is a sensitive are
[14:19] <knome> area too.
[14:44] <flocculant> well yea
[15:27] <flocculant> ninetls: odd issue with sn plugin and dropbox icon xfce 14297
[16:48] <ali1234> hmm that reminds me of something
[16:52] <ali1234> indicator spec defines three events: menu, primary, secondary
[16:53] <ali1234> there is no consistency of what those events mean though
[16:53] <ali1234> and some desktops don't send all of them
[17:43] <slickymaster> knome, checked your slideshow branch
[17:43] <slickymaster> I like it, and my position is to go ahead with it
[18:22] <ninetls> flocculant: yes, I noticed that too when investigated dropbox this week
[18:23] <ninetls> it provides 2 menus: middle click activates its internal menu, left click activates native menu. they even look different.
[20:32] <ochosi> gah, missed willem by a few secs
[21:09] <Unit193> bluesabre: Usually what you see in configure.ac, and either bump up for the git snapshot (if it has the current version there), or drop back (if it has the next version, as Xfce usually does.)  So in your case 3.22.7+git20180324.031f985-0ubuntu1
[21:10] <Unit193> With numlockx, what if it's a laptop but docked? :3
[21:13] <Unit193> (And for dropbox, if you left click, click away, then right click it works. :P)
[21:24] <flocculant> Unit193: so what we're saying is that eventually any click you like :p
[21:25] <flocculant> ninetls: ack - thanks