Fixes a bug that could cause NM, evolution, and other apps to use 100% CPU in some configurations. Fix IPv6 next hop default setting
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2014-13942
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 danw.
Taskotron: depcheck test PASSED on i386. Result log: https://taskotron.fedoraproject.org/taskmaster//builders/x86_64/builds/6774/steps/runtask/logs/stdio (results are informative only)
Taskotron: depcheck test PASSED on x86_64. Result log: https://taskotron.fedoraproject.org/taskmaster//builders/x86_64/builds/6774/steps/runtask/logs/stdio (results are informative only)
This update is currently being pushed to the Fedora 21 testing updates repository.
This update has been pushed to testing
Wi-Fi works fine.
Critical path update approved
Had to downgrade manually, because dhclient dies. May have to do with other packages, but the log is clear: nov 01 23:14:46 d98142.upc-d.chello.nl NetworkManager[944]: <info> (p21p1): DHCPv4 client pid 1312 exited with status -1 nov 01 23:14:46 d98142.upc-d.chello.nl NetworkManager[944]: <warn> DHCP client died abnormally
Works for me
Critical path update approved
Works OK in normal day to day usage.
Doesn't fix the "100% CPU load in evolution-calendar-factory" issue as claimed.
karma: -1
This update has reached the stable karma threshold and will be pushed to the stable updates repository
Taskotron: upgradepath test PASSED on noarch. Result log: https://taskotron.fedoraproject.org/taskmaster//builders/x86_64/builds/8687/steps/runtask/logs/stdio (results are informative only)
Works after retry updating NetworkManager packages only
Taskotron: depcheck test FAILED on x86_64. Result log: https://taskotron.fedoraproject.org/taskmaster//builders/x86_64/builds/9970/steps/runtask/logs/stdio (results are informative only)
Automatic push to stable based on karma has been disabled for this update due to failure of an AutoQA test. Update submitter, please check the AutoQA test result and see if there is a valid problem to be fixed here, and fix it if so. If the failure is a mistake on AutoQA's part, you can re-enable the automatic push feature for this update if you like, or push it stable manually once it reaches the requirements under the Updates Policy.
This update is currently being pushed to the Fedora 21 stable updates repository.
This update is currently being pushed to the Fedora 21 stable updates repository.
This update has been pushed to stable