Summary: | Trying to save a WPA2 password causes NetworkManager to use 95% CPU and continuously write the same message to system logs. | ||
---|---|---|---|
Product: | [Unmaintained] Network Management | Reporter: | Patrick Boutilier <boutilpj> |
Component: | general | Assignee: | Will Stephenson <wstephenson> |
Status: | RESOLVED UPSTREAM | ||
Severity: | crash | CC: | blueowl, bruno, jreznik, kevin.kofler, lamarque, mhlavink, rdieter |
Priority: | NOR | ||
Version: | 0.9 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Patrick Boutilier
2011-06-18 22:16:03 UTC
We also have a user who got the same symptoms during migration from the old NM 0.8 settings format to the new NM 0.9 one, see: http://lists.fedoraproject.org/pipermail/kde/2011-June/009614.html and followups for details. We are trying to migrate our Fedora 15 users from our custom compat-API-based kludge to your upstream nm09 code, but this looks like a blocker. I hope we can figure out what's going wrong here. It looks like the ifcfg-rh NM plugin used on Fedora is involved somehow. I get this problem sometimes too, but it does not crash my computer nor make the CPU reach 100%. It does not happen with NM-0.8.999, only with 0.8.9997. I do not know why but NM sends too many "update" signals when we open the edit dialog, which by the way does not send update calls to NM when opening. I really do not know why NM is sending those signals. Another thing I have noticed it is that is does not happen when using only keyfile plugin in /etc/NetworkManager/nm-system-settings.conf. If I use ifnet it happens, probably ifcfg-rh is a similar plugin. I use Gentoo and I do not have ifcfg-rh plugin here. According to Rajeesh K Nambiar this is a upstream bug and also affects nm-applet. It has been fixed in NetworkManager-0.8.9997-4.git20110620. This upstream commit for libnm-util fixes the bug: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=864db9f9e80ab547d7dde10fc7a139b22c85c75f *** Bug 278204 has been marked as a duplicate of this bug. *** |