Bug 414886 - most recent updates crippled onboard networking on my Ryzen 7 PC (gigabyte board)
Summary: most recent updates crippled onboard networking on my Ryzen 7 PC (gigabyte b...
Status: RESOLVED NOT A BUG
Alias: None
Product: plasma-nm
Classification: Plasma
Component: general (show other bugs)
Version: 5.17.4
Platform: Neon Linux
: NOR critical
Target Milestone: ---
Assignee: Jan Grulich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-06 08:33 UTC by Neon_user
Modified: 2019-12-11 05:24 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Neon_user 2019-12-06 08:33:03 UTC
SUMMARY
Most recent KDE NEon updates (installed on Dec 5, 2019) disabled network. If I boot to the most recent kernel version for my machine (4.15.0-72-generic #81-Ubuntu), the network does not work at all. But if I instead use recovery boot for the same kernel version, my network activity is functional and normal.

STEPS TO REPRODUCE
1. Boot to 4.15.0-72-generic #81-Ubuntu
2. 
3. 

OBSERVED RESULT
Network does not function at all, and all command line network tools I've used fail, even ping, which reports "ping: sndmsg: operation not permitted".

EXPECTED RESULT
Normal network activity, which is achieved by using the "recovery" boot of the same kernel version.


SOFTWARE/OS VERSIONS
Windows: Windows 7 Professional
macOS: 
Linux/KDE Plasma: 4.15.0-72-generic #81-Ubuntu
(available in About System)
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.2

ADDITIONAL INFORMATION
I was able to verify that it was indeed the recent KDE Neon configuration that was causing the issue, by also dual booting to Windows 7, opening Firefox to verify connectivity, then running speedtest.net to verify speed. All functions and settings were as expected including full duplex and 1000mbps, as they were in the linux recovery boot.
Comment 1 Neon_user 2019-12-11 05:23:11 UTC
Scratch this bug.

I tried experimenting with my VPN, and found that removing it, then reinstalling, solved the connection problem.

I apologize for the false alert.