Yeah, no idea, but commenting out "keysize" makes everything work again.

Thanks a ton @JoshStrobl; I didn't even think of checking the config file for that "keysize" variable!

Sorry, but this solution does nothing for me using TunnelBear; ended up here from this thread.

Apologies & thanks are in order, then, @Jacalz...

I apologize if this isn't the place for this comment...

Changing to the unstable repo upgrades to kernel 5.6.4-152 and I now have no wifi issues.

So i guess it's related to trying to connect to a roku box for me.

Thanks, @JoshStrobl; that upstream bug suggests running the vino-server from cli works, but on my system it does not.

I've also checked this on the 5.6 kernel that ships with Fedora 32 beta and the issue is present there, as well.

This is, apparently, the "upstream" fix: https://lore.kernel.org/linux-wireless/iwlwifi.20200318081237.46db40617cc6.Id5cf852ec8c5dbf20ba86bad7b165a0c828f8b2e@changeid/

{F5743594}Issue persists with com.solus-project.current.5.5.11-151 and I believe more now than ever the issue is either directly a result of or related to iwlwifi.

Although that's a little extreme, it might be my only choice; thanks for the info @feuerstein...

Finding some time during this coronavirus shutdown, it would appear there are "problems" with iwlwifi and dmesg seems to confirm that...

Issue persists with com.solus-project.current.5.5.7-150; I hope this gets resolved soon... it's really a pita...

Just updated to com.solus-project.current.5.5.6-149 and the issue persists...

Thanks, @feuerstein. I wasn't sure what information or logs to include in the report on kernel.org and am willing to add whatever is necessary. Bug 206395 seems spot-on for me, the other two not as much; that bug references a patch already existing to fix the issue. Do you think that will be merged in Solus's tree soon?

Is there a better place for me to report this bug than here?

Thanks for the ideas @feuerstein; those firmware issues are dated—i.e., two years old—but it makes me wonder... Although I'm not having those issues with resuming from sleep, it just *never* works...

{F5627339}It would appear all is good in the boot partition...

Yes... Why would that have anything to do with wifi not working on the latest kernels, but working on an older one? Or, are you referring to the "Unable to parse loader config" message?

Thanks, @DataDrake, those were my thoughts as well, so I've placed display-setup-script in multiple [Seat:*] locations, but none of those config files are read either.

Thanks, @JoshStrobl. I've followed all the slick stuff as per their docs and it doesn't work, so I joined onto a bug thread but it hasn't been touched since last year. Looking through their git, it seems like this is a known issue, but nothing suggested works. Just frustrating.

Just to add my voice; this is still occurring.