/srv/irclogs.ubuntu.com/2018/06/25/#ubuntu-mate.txt

sadneophyteHey I was wondering if there was a problem with wpasupplicant and if anyone had a fix for it!03:20
sadneophyteI was wondering if anyone wanted to help me troubleshoot a really odd wireless problem03:28
sadneophytehey are there any people with launchpad accounts here I have a bugfix/solution which should be07:29
alkisgwhich should be what?07:30
sadneophyteahh07:30
alkisgAre you asking someone to file a bug report for you?07:30
sadneophytehttps://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/174883907:30
ubottuLaunchpad bug 1748839 in network-manager (Ubuntu) "Problem to connect to WPA2/PEAP WIFI - gnome-shell" [Undecided,Confirmed]07:30
sadneophyteis solved by regression to earlier codebase: https://launchpad.net/ubuntu/+source/wpa/2:2.4-1.1ubuntu107:31
alkisgThe bug is about gnome-shell, but this channel is about mate07:31
sadneophytealkisg, this effects the mate wpa supplicant implementation07:31
sadneophyteand the ubuntu 18.04 wpa supplicant07:32
alkisgsadneophyte: ok, and what are you asking people here? Why aren't you just commenting on the bug report?07:32
sadneophytesomeone with a launchpad account could post that fix to the buglist and help cannonical regress 18.04 codebase07:33
sadneophyte18.04 pulled to far upstream for the wpa supplicant07:33
alkisg"post that fix to the buglist"? I don't understand07:33
alkisgThat bug report is the correct place to do things07:34
alkisgThere's no other "buglist"...07:34
sadneophytehttps://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/174883907:34
ubottuLaunchpad bug 1748839 in network-manager (Ubuntu) "Problem to connect to WPA2/PEAP WIFI - gnome-shell" [Undecided,Confirmed]07:34
sadneophytethat is a buglist07:34
sadneophytefor launchpad bionic07:34
alkisgIt is a bug report, yes, and people did mention their experience there07:34
alkisgWhat do you want us to do with that bug report? Be more specific07:35
alkisgsadneophyte: 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 Ubuntu07:37
alkisgSo if you're trying to help in solving that bug, you first need to contact the upstream maintainers07:37
snalkisg, there is no upstream for this package.07:37
alkisgsn, it's not developed anywhere? :)07:38
snwpa supplicant is sort of mature software07:38
snthey chose the unstable playground for an sbin program07:38
alkisgsn, latest commit, two days ago: http://w1.fi/cgit07:39
snanyways 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
snhah!07:40
sn2 days or 8 years?07:40
alkisghttp://w1.fi/cgit/hostap/07:40
alkisgI see daily commits there07:40
snhostap isn't wpa supplicant07:40
snalthough the converse might be true07:41
snanyways, I won't be making an ubuntu one account to post the solution, so whatever.07:42
alkisgAre you sadneophyte?07:44
alkisgI didn't even understand if you have a solution, or you're looking for one07:44
alkisgIf you mean "downgrading is the solution", then this is already mentioned in the bug report07:44
alkisgI see patches sent for wpa_supplicant by canonical even in June 2018: http://lists.infradead.org/pipermail/hostap/2018-June/038643.html07:45
snalkisg, 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:58
alkisgsn, mate uses the same archive as all ubuntu flavors, sure07:59
snthanks, sorry if I wasted your time.08:00
alkisgSo if I understood you correctly, you wanted someone from IRC to say "yes affects sn too" because you didn't want to do it yourself08:00
alkisg...but we couldn't provide information as it doesn't affect e.g. me08:00
alkisgSo it wouldn't be useful to any developers trying to actually solve the bug08:00
alkisgnp, cheers08:00
snno, the maintainers don't know where the bug is.  A regression solves the problem08:00
alkisgRegression isn't what you think08:01
alkisgYou mean 'downgrade'08:01
snthe december version of bionic alpha shipped with this wpa supplicant08:01
alkisgRegression is when a bug "fix" introduces a new bug08:01
snohhh sorry08:01
alkisgSo you're saying that downgrading the package works around the issue08:02
alkisgThis is already mentioned in the bug report there08:02
alkisgAnd the Ubuntu maintainers haven't yet acted upon it. Possibly because not enough people are affected.08:02
snmaybe, I though it said a regression did not solve the problem08:02
alkisgMe, 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 you08:02
alkisgDon't say "regression", say "downgrade"08:02
sndown!*!grade08:03
alkisgSome said it helped, some said it didn't08:03
snwith a double d08:03
alkisgUsually developers only post solutions when they know why something happened and why it gets fixed08:03
alkisgCanonical 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:04
alkisgSo you could mention the issue in the upstream mailing list, find a fix from there, and _then_ notify the distribution to cherry pick the fix08:05
snno, but 18.04 needs to be super stable awesome sauce.  not duct tape testing.08:06
alkisgEh, I don't think you understood how distributions work :)08:07
alkisgThere's no distribution that can do that without the users themselves doing most of the work08:07
snmeh, I almost gave up on figuring how to downgrade wpa supplicant, which would have meant using debian instead of this awesome new shine mate08:08
snshiny*08:08
snand is it shiny08:08
snI haven't seen something so nice since KDE 3.44 came out or gnome 2.308:09
snIt is really nice.  I am really glad it made it to the LTS realease08:09
snanyways thanks.08:10
mate|34393ayuda11:51
timb67any chance Ubuntu Mate will be made available to work on the ASUS Tinkerboard?19:56
alkisgtimb67: does any ubuntu run on that?19:59
diogenes_it's compatible with the second-generation and later Raspberry Pi20:07
diogenes_so it should work20:07
timb67I tried once and it did not work...I suppose I could try again.20:08
diogenes_timb67, you tried what mate version?20:09
timb67so 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:13
alkisgOne is ARM Cortex-A53, the other Rockchip RK3288, one uses proprietary blob, the other uses uboot...20:27
alkisgThey don't sound too similar20:28
alkisgBut once you get the boot manager and the kernel running, the rest (desktop environment etc) should be easy20:29
timb67Thanks...I am going to give it another try with 16.04 for the Raspberry Pi...we'll see what happens.20:30
alkisgI'd start with armbian to get the boot manager and kernel, and then copy the rest from mate20:31
timb67good idea. I am using armbian now so I'll see if I can make that work20:34
alkisghttps://www.armbian.com/tinkerboard/20:34
alkisgIt says it's already xenial20:34
alkisgSo just apt install ubuntu-mate-desktop on top of that20:35
* deskwizard is putting that on his todo list20:55
deskwizardthat'd be sweet, wonder why I never thought of that20:55

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!