Summary: | knetworkmanager spontaneous crash | ||
---|---|---|---|
Product: | Network Management | Reporter: | Steffen Möller <steffen_moeller> |
Component: | general | Assignee: | Will Stephenson <wstephenson> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | andresbajotierra, frank78ac |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian unstable | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Steffen Möller
2010-12-06 10:36:44 UTC
[Comment from a bug triager] This looks related to bug 210878, which describes a crash when the NetworkManager daemon is restarted. Do you remember if there were some system update in progress on background that may have caused the NetworkManager restart ? Regards Whatever it is, it is inconsistent in its behaviour. The network manager did not crash this time that I booted. What I had done a few boots earlier was to add eth0 with DHCP to the network manager. But what I had used before and still use is /etc/network/interfaces and a call to ifup eth0. That for some reasons does not come up automatically for me. $ ls /etc/udev/ .dev/ hdparm.rules links.conf pcmcia.rules rules.d/ udev.conf usbmount.rules $ ls /etc/udev/rules.d/ 70-persistent-cd.rules 70-persistent-net.rules 85-pcmcia.rules z60_hdparm.rules z60_usbmount.rules z60_xserver-xorg-input-wacom.rules moeller@Toshiba:~ $ cat /etc/udev/rules.d/70-persistent-net.rules # This file was automatically generated by the /lib/udev/write_net_rules # program run by the persistent-net-generator.rules rules file. # # You can modify it, as long as you keep each rule on a single line. # PCI device 0x8086:0x109a (e1000e) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:15:b7:0f:0f:5d", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" # PCI device 0x8086:0x4222 (iwl3945) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:18:de:4e:bf:b5", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0" The network manager is still up while I am typing this, it crashed long ago last time. *** This bug has been marked as a duplicate of bug 258469 *** |