GNOME Bugzilla – Bug 691516
network-manager becomes unresponsive, requiring a service restart
Last modified: 2020-11-12 14:25:20 UTC
Originally reported at: https://bugs.launchpad.net/bugs/825897 After network-manager has been running for a while (overnight) it becomes unresponsive: - unable to uncheck "Enable Wireless" - doesn't list the numerous additional networks under "More Networks" - doesn't find new networks This behavior persists until the network-manager service is restarted via: sudo service network-manager restart ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: network-manager 0.8.4~git.20110319t175609.d14809b-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sat Aug 13 09:25:50 2011 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to natty on 2011-07-25 (19 days ago)
For clarity this bug is still present the let latest versions of nm-applet available in Ubuntu 12.10. And since the original filing of this report with Ubuntu (over a year ago) I've since found that simply killing and restarting nm-applet is sufficient to temporarily rectify the issue.
I got a new stack trace on Ubuntu 12.10 and this time it shows something interesting. There seems to be stack corruption on thread 3, because gdb shows an impossible stack trace. The parameters to the g_dbus_proxy_call_sync frame are invalid and would have crashed the program if such a call had actually been made, and the calling address is not in any loaded module. I checked it against /proc/<pid>/maps and it seems to be in stack space. Also, gdb says that the g_dbus_proxy_call_sync frame called g_main_loop_run at gdbusproxy.c:3102, but there is no code to call g_main_loop_run anywhere near there. (gdb) thread apply all bt full
+ Trace 231377
Hmm, the stack corruption wasn't present the next time the bug happened though. Maybe that was a coincidence. I tried putting a breakpoint on applet_device_disconnect_db and clicking Disconnect. The breakpoint isn't hit. So it seems that the Gtk widgets are getting into an inconsistent state. (gdb) thread apply all bt full
+ Trace 231403
bugzilla.gnome.org is being shut down in favor of a GitLab instance. We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time. If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/ Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).