[03:20] <sadneophyte> Hey I was wondering if there was a problem with wpasupplicant and if anyone had a fix for it!
[03:28] <sadneophyte> I was wondering if anyone wanted to help me troubleshoot a really odd wireless problem
[07:29] <sadneophyte> hey are there any people with launchpad accounts here I have a bugfix/solution which should be
[07:30] <alkisg> which should be what?
[07:30] <sadneophyte> ahh
[07:30] <alkisg> Are you asking someone to file a bug report for you?
[07:30] <sadneophyte> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839
[07:31] <sadneophyte> is solved by regression to earlier codebase: https://launchpad.net/ubuntu/+source/wpa/2:2.4-1.1ubuntu1
[07:31] <alkisg> The bug is about gnome-shell, but this channel is about mate
[07:31] <sadneophyte> alkisg, this effects the mate wpa supplicant implementation
[07:32] <sadneophyte> and the ubuntu 18.04 wpa supplicant
[07:32] <alkisg> sadneophyte: ok, and what are you asking people here? Why aren't you just commenting on the bug report?
[07:33] <sadneophyte> someone with a launchpad account could post that fix to the buglist and help cannonical regress 18.04 codebase
[07:33] <sadneophyte> 18.04 pulled to far upstream for the wpa supplicant
[07:33] <alkisg> "post that fix to the buglist"? I don't understand
[07:34] <alkisg> That bug report is the correct place to do things
[07:34] <alkisg> There's no other "buglist"...
[07:34] <sadneophyte> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839
[07:34] <sadneophyte> that is a buglist
[07:34] <sadneophyte> for launchpad bionic
[07:34] <alkisg> It is a bug report, yes, and people did mention their experience there
[07:35] <alkisg> What do you want us to do with that bug report? Be more specific
[07:37] <alkisg> sadneophyte: maybe you didn't understand how bug reports are processed? Users mention things in bug reports, and developers may or may not work on them. If the problem is solved upstream, e.g. in the wpa-supplicant package, then it's easier to backport the fix to Ubuntu
[07:37] <alkisg> So if you're trying to help in solving that bug, you first need to contact the upstream maintainers
[07:37] <sn> alkisg, there is no upstream for this package.
[07:38] <alkisg> sn, it's not developed anywhere? :)
[07:38] <sn> wpa supplicant is sort of mature software
[07:38] <sn> they chose the unstable playground for an sbin program
[07:39] <alkisg> sn, latest commit, two days ago: http://w1.fi/cgit
[07:40] <sn> anyways it takes a microwave electrical engineer to design these protocols, I don't think there will be a bugfix in the next couple of years.
[07:40] <sn> hah!
[07:40] <sn> 2 days or 8 years?
[07:40] <alkisg> http://w1.fi/cgit/hostap/
[07:40] <alkisg> I see daily commits there
[07:40] <sn> hostap isn't wpa supplicant
[07:41] <sn> although the converse might be true
[07:42] <sn> anyways, I won't be making an ubuntu one account to post the solution, so whatever.
[07:44] <alkisg> Are you sadneophyte?
[07:44] <alkisg> I didn't even understand if you have a solution, or you're looking for one
[07:44] <alkisg> If you mean "downgrading is the solution", then this is already mentioned in the bug report
[07:45] <alkisg> I see patches sent for wpa_supplicant by canonical even in June 2018: http://lists.infradead.org/pipermail/hostap/2018-June/038643.html
[07:58] <sn> alkisg, its all cool man. 18.04 shipped with broken system critical software.  Mate picked it up.  I found somewhere to post where I didn't have to join cannonicals terms of service.  Its solved. no problem.
[07:59] <alkisg> sn, mate uses the same archive as all ubuntu flavors, sure
[08:00] <sn> thanks, sorry if I wasted your time.
[08:00] <alkisg> So if I understood you correctly, you wanted someone from IRC to say "yes affects sn too" because you didn't want to do it yourself
[08:00] <alkisg> ...but we couldn't provide information as it doesn't affect e.g. me
[08:00] <alkisg> So it wouldn't be useful to any developers trying to actually solve the bug
[08:00] <alkisg> np, cheers
[08:00] <sn> no, the maintainers don't know where the bug is.  A regression solves the problem
[08:01] <alkisg> Regression isn't what you think
[08:01] <alkisg> You mean 'downgrade'
[08:01] <sn> the december version of bionic alpha shipped with this wpa supplicant
[08:01] <alkisg> Regression is when a bug "fix" introduces a new bug
[08:01] <sn> ohhh sorry
[08:02] <alkisg> So you're saying that downgrading the package works around the issue
[08:02] <alkisg> This is already mentioned in the bug report there
[08:02] <alkisg> And the Ubuntu maintainers haven't yet acted upon it. Possibly because not enough people are affected.
[08:02] <sn> maybe, I though it said a regression did not solve the problem
[08:02] <alkisg> Me, I can't click "affects me too" because it doesn't. If you want to click it, sure, go ahead; I can't click it for you
[08:02] <alkisg> Don't say "regression", say "downgrade"
[08:03] <sn> down!*!grade
[08:03] <alkisg> Some said it helped, some said it didn't
[08:03] <sn> with a double d
[08:03] <alkisg> Usually developers only post solutions when they know why something happened and why it gets fixed
[08:04] <alkisg> Canonical doesn't fix all the bugs. More than 90% of the bugs are solved by upstream or by the users. Don't expect a distro to solve all the bugs it sees, noone has that kind of manpower.
[08:05] <alkisg> So you could mention the issue in the upstream mailing list, find a fix from there, and _then_ notify the distribution to cherry pick the fix
[08:06] <sn> no, but 18.04 needs to be super stable awesome sauce.  not duct tape testing.
[08:07] <alkisg> Eh, I don't think you understood how distributions work :)
[08:07] <alkisg> There's no distribution that can do that without the users themselves doing most of the work
[08:08] <sn> meh, I almost gave up on figuring how to downgrade wpa supplicant, which would have meant using debian instead of this awesome new shine mate
[08:08] <sn> shiny*
[08:08] <sn> and is it shiny
[08:09] <sn> I haven't seen something so nice since KDE 3.44 came out or gnome 2.3
[08:09] <sn> It is really nice.  I am really glad it made it to the LTS realease
[08:10] <sn> anyways thanks.
[11:51] <mate|34393> ayuda
[19:56] <timb67> any chance Ubuntu Mate will be made available to work on the ASUS Tinkerboard?
[19:59] <alkisg> timb67: does any ubuntu run on that?
[20:07] <diogenes_> it's compatible with the second-generation and later Raspberry Pi
[20:07] <diogenes_> so it should work
[20:08] <timb67> I tried once and it did not work...I suppose I could try again.
[20:09] <diogenes_> timb67, you tried what mate version?
[20:13] <timb67> so when the Ubuntu-Mate 18.04 is released for the Raspberry Pi (hopefully in July), that same version should work on the ASUS Tinkerboard, correct?
[20:27] <alkisg> One is ARM Cortex-A53, the other Rockchip RK3288, one uses proprietary blob, the other uses uboot...
[20:28] <alkisg> They don't sound too similar
[20:29] <alkisg> But once you get the boot manager and the kernel running, the rest (desktop environment etc) should be easy
[20:30] <timb67> Thanks...I am going to give it another try with 16.04 for the Raspberry Pi...we'll see what happens.
[20:31] <alkisg> I'd start with armbian to get the boot manager and kernel, and then copy the rest from mate
[20:34] <timb67> good idea. I am using armbian now so I'll see if I can make that work
[20:34] <alkisg> https://www.armbian.com/tinkerboard/
[20:34] <alkisg> It says it's already xenial
[20:35] <alkisg> So just apt install ubuntu-mate-desktop on top of that
[20:55]  * deskwizard is putting that on his todo list
[20:55] <deskwizard> that'd be sweet, wonder why I never thought of that