GNOME Bugzilla – Bug 651540
NetworkManager makes freeze all computer and only can take off current
Last modified: 2011-10-13 12:46:53 UTC
Hello, I am using the last version of NetworkManager avaiable in Ubuntu's repos. 0.8.3.998 (as seen in about... by right clicking in the icon) The main problem is that when I plugin a rj45 connector into the hole, and it detects it, the computer freezes. I know it is a NetworkManager problem because if I stop gdm, kill NetworkManager, and stop networking, it doesn't crash. It crashes if I start NetworkManager. No logs that say something about problem (kern.log messages.log), as system just freezes completelly. I have tried to upgrade to the last version, but I don't have Linux Wireless Extensions and I don't know where to download it from. I can add any attachment you need. Using
Using 2.6.38-8 kernel in 64 arch in Ubuntu, 11.04 with gnome-shell
*** Bug 651539 has been marked as a duplicate of this bug. ***
Uops, gave twice to post button...
Did you file a bug in Ubuntu's bugtracker? If so, what is the URL?
No I didn't as Ubuntu is not recognising it as original one (unmodified). I you need logs, tell me what should I post.
I am still waiting for instructions
https://wiki.ubuntu.com/DebuggingNetworkManager https://live.gnome.org/NetworkManager/Debugging
Javier, were you able to collect logs as per instructions in comment#7 ?
Hello Akhil, I currently in a trip to london, and as soon as I get back I will post my results
Hello, I have tried to do that, but there is no log there. I think its a kernel bug, as even when I kill all the networking, with no graphical interface, crashes. I will report if something more happens.
https://bugs.launchpad.net/ubuntu/+bug/826871
NetworkManager itself cannot make the computer freeze, it's likely a kernel driver doing something wrong. Drivers should not ever allow the computer to freeze. First off, what's the output of the commands 'lspci' and 'lsusb' commands when they are run in a Terminal?
From WifiSyslog.txt it appears that that's gnome-settings-daemon that crashes, NM and drivers look okay: Aug 27 01:56:44 javier-PB-ubuntu kernel: [24253.946434] gnome-settings-[1732]: segfault at 7f4a5f954b10 ip 00007f4a5f954b10 sp 00007fffd3d0ad18 error 14 in libdbus-1.so.3.5.4[7f4a5fb96000+42000] Aug 27 01:56:46 javier-PB-ubuntu kernel: Kernel logging (proc) stopped. ... Sep 1 15:50:21 javier-PB-ubuntu kernel: [ 313.188848] gnome-settings-[1707]: segfault at 7f4033379b10 ip 00007f4033379b10 sp 00007ffffa5c6ed8 error 14 in libdbus-1.so.3.5.4[7f40335bb000+42000] Sep 1 15:50:22 javier-PB-ubuntu kernel: Kernel logging (proc) stopped. ... Sep 1 15:50:21 javier-PB-ubuntu kernel: [ 313.188848] gnome-settings-[1707]: segfault at 7f4033379b10 ip 00007f4033379b10 sp 00007ffffa5c6ed8 error 14 in libdbus-1.so.3.5.4[7f40335bb000+42000] Sep 1 15:50:22 javier-PB-ubuntu kernel: Kernel logging (proc) stopped. etc.
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
I am not having that problem any longer. I installed backports packages etc., and now doesn't crash any more. I also want to say that I have prey (http://preyproject.com/) installed, and uses some networking things. Might be the bug from there?
(In reply to comment #15) > I am not having that problem any longer. Closing as INCOMPLETE. :-/