Created attachment 855072 [details] output of: journalctl -b | grep "NetworkManager\|firewalld" Description of problem: I use KDE and have configured network (WLAN) over "kde-plasma-nm". Although system is able to establish connection when I log in as user, I get many, many network-related error-lines in my logs. Most of them are being repeated many times. Repeated error-lines: --------------------- 1) file devices/nm-device.c: line 6928 (nm_device_add_pending_action): should not be reached 2] file devices/nm-device.c: line 6979 (nm_device_remove_pending_action): should not be reached 3) firewalld[474]: yyy-mm-dd hh:mm:ss ERROR: UNKNOWN_INTERFACE: wlp9s0 Single error-line: ------------------ nm-dispatcher.action[1276]: Script '/etc/NetworkManager/dispatcher.d/20-chrony' took too long; killing it. I will attach whole output of the following command here: # journalctl -b | grep "NetworkManager\|firewalld" Version-Release number of selected component (if applicable): NetworkManager-0.9.9.0-26.git20131003.fc20.x86_64 How reproducible: Every boot Any idea what goes wrong here?
Sorry, forgot to mention that I use the following WLAN-PCI-card: # lspci | grep Network 09:00.0 Network controller: Qualcomm Atheros AR9227 Wireless Network Adapter (rev 01)
I can confirm this occurs with the Fedora 20 rawhide package: NetworkManager-0.9.9.0-26.git20131003.fc20.x86_64 NetworkManager is failing to get authentication info and floods log. It works correctly if gnome-keyring is launched with gnome-session/gdm but sometime cannot get to this stage due to massive IO usage, This issue is fixed in the most recent git version (07edeabbc34d3c98089ec4299e457325dc78856b) of NetowrkManager from master. When compling configure with --with-session-tracking=systemd This ensures proepr support with Fedora 20 as the default session tracking is ConsoleKit, which is no longer supported,
Hi there, on each system-start there are ~9.000 new lines related to this bug. As it's flooding the logs, size of /var/log/journal/ is growing ~400MB each month. Would it be possible to push a new version of NetworkManager to testing, as comment #2 sounds promising it might solve the problem? Thanks!
It's been almost seven months since this issue was last reported; three months since @Reyad\ Attiyat correctly concluded the problem is in the NetworkManager.x86_64 1:0.9.9.0-41.git20131003.fc20 @updates-testing version of the NetworkManager package. Are there any plans to replace the version available from @updates-testing repo with a "fixed" version so that the problems with the package aren't further disseminated? and adapted?
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.