[18:51] <ethana2> hello, I just installed and fully updated Kubuntu 17.10 alpha 2 and it's not connecting to my wifi using my TP-Link TL-WN821N even though I turned off random MAC in NetworkManager.conf, any idea what could be going wrong?
[18:52] <ethana2> It sees all the networks just fine but when I try to connect to mine it says "Configuring Interface" for a bit and then just stops
[18:55] <tsimonq2> ethana2: Support for Kubuntu is available in #kubuntu :)
[18:57] <ethana2> tsimonq2:  acheronuk from #kubuntu sent me here
[18:58] <ethana2> I'll lurk both channels for a while
[18:59] <acheronuk> yes, I was covering both bases a sounds like an underlying network-manager issue
[19:00] <tsimonq2> acheronuk: ack
[19:53] <ethana2> I reconfigured WPA supplicant to log, and then reproduced the issue, and it didn't log anything... and I moved /var/log/syslog to /var/log/syslog.old and restarted rsyslogd and it's not making a new /var/log/syslog file...
[19:54] <ethana2> tested 'logger' command directly from the CLI... nothing in /var/log... guess it's time to review my complete rsyslogd config
[20:39] <ethana2> ok, /etc/rsyslog.d/50-default.conf has *.* going to /var/log/syslog and I restarted rsyslog and reloading it isn't a valid action for the service... maybe it's just queuing up large amounts of log entries before writing to disk as a power saving measure? But I have my / on an SSD so I'd prefer it write them whenever it's got a block worth
[20:40] <ethana2> Did I confuse rsyslog? I do this on RHEL all the time
[23:53] <ethana2> I found that the way I broke my syslog was touching a file with the wrong permissions for syslog to write to.. I got out of wpa supplicant that authentication was timing out, and people on stackexchange say the n/ac functionality may just need disabled so I've modified my /etc/modprobe.d/iwlwifi.conf file accordingly and if that doesn't work I'll revert the change
[23:58] <ethana2_> Well, that didn't work, resuming investigation