Update to 1.10.6 release
sudo dnf upgrade --refresh --advisory=FEDORA-2018-6b7a05a4bf
Please login to add feedback.
|0||0||Test Case QA/TestCases/NM Mobile Broadband|
|0||0||Test Case QA/TestCases/NM VPN OpenVPN|
|0||0||Test Case QA/TestCases/NM VPN vpnc|
|0||0||Test Case QA/TestCases/NM WEP|
|0||0||Test Case QA/TestCases/NM WPA|
|0||0||Test Case QA/TestCases/NM Wifi|
|0||0||Test Case DNS-over-SSL|
|0||0||Test Case DNSSEC-trigger|
|0||0||Test Case NM Bonding|
|0||0||Test Case NM Ethernet|
|0||0||Test Case NM Gnome Hotspot|
|0||0||Test Case NM KDE Hotspot|
|0||0||Test Case NM Wireless|
|0||0||Test Case NM nmcli|
|0||0||Test Case NetworkManager assume|
|0||0||Test Case NetworkManager bt pan|
|0||0||Test Case NetworkManager celldata|
|0||0||Test Case NetworkManager ipv6|
This update has been submitted for testing by thaller.
This update has been pushed to testing.
Works as expected
This update has been submitted for batched by bodhi.
NetworkManager fails to start on recent kernels (4.15, 4.16) e.g. 'killed by SIGSEGV' and this cannot be reported through
@bluepencil, there is not enough information to figure out why it crashes for you. Consider opening a bug and providing a backtrace. Also, install NetworkManager-debuginfo package.
O.K. But I have to own up that problem with starting NM disappeared by itself yesterday after recent system upgrades :)
@bluepencil, odd, but thanks!! :)
Not at all, in relation to networking I still have to find way around with DNS caching:
bindhave the same problem with making interface unresponsible after reaching a certain amount of queries. It appeared since 4.15 kernel version and never shows when booting with 4.14 on the same machine :)
Wi-Fi works fine.
This update has been submitted for stable by bodhi.
This update has been pushed to stable.