Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.

** Changed in: network-manager (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/934086

Title:
  network-manager crashes every few minutes

Status in “network-manager” package in Ubuntu:
  Incomplete

Bug description:
  The network manager crashes every few minutes causing the lan
  connection to break down everytime. Here is some information from the
  syslog:

  [  945.010234] NetworkManager[5389]: segfault at 1c ip 0808661d sp bfda85c0 
error 4 in NetworkManager[8048000+d5000]
  [  945.016804] init: network-manager main process (5389) killed by SEGV signal
  [  945.016898] init: network-manager main process ended, respawning
  [  978.938262] NetworkManager[5640]: segfault at 1c ip 0808661d sp bfea7d80 
error 4 in NetworkManager[8048000+d5000]
  [  978.952208] init: network-manager main process (5640) killed by SEGV signal
  [  978.952302] init: network-manager main process ended, respawning
  [ 1025.265800] NetworkManager[5742]: segfault at 4 ip 08086f8f sp bfb8de50 
error 4 in NetworkManager[8048000+d5000]
  [ 1025.273044] init: network-manager main process (5742) killed by SEGV signal
  [ 1025.273139] init: network-manager main process ended, respawning
  [ 1059.605983] NetworkManager[5857]: segfault at 1c ip 0808661d sp bfd382a0 
error 4 in NetworkManager[8048000+d5000]
  [ 1059.616561] init: network-manager main process (5857) killed by SEGV signal
  [ 1059.616655] init: network-manager main process ended, respawning
  [ 1104.123048] NetworkManager[5977]: segfault at 4 ip 08086f8f sp bf9ee470 
error 4 in NetworkManager[8048000+d5000]
  [ 1104.133001] init: network-manager main process (5977) killed by SEGV signal
  [ 1104.133098] init: network-manager main process ended, respawning
  [ 1153.007264] NetworkManager[6095]: segfault at 1c ip 0808661d sp bffce590 
error 4 in NetworkManager[8048000+d5000]
  [ 1153.016611] init: network-manager main process (6095) killed by SEGV signal
  [ 1153.016705] init: network-manager main process ended, respawning
  [ 1198.109901] NetworkManager[6253]: segfault at 4 ip 08086f8f sp bfe67c50 
error 4 in NetworkManager[8048000+d5000]
  [ 1198.116845] init: network-manager main process (6253) killed by SEGV signal
  [ 1198.116939] init: network-manager main process ended, respawning
  [ 1244.057906] NetworkManager[6369]: segfault at 4 ip 08086f8f sp bfcb5fc0 
error 4 in NetworkManager[8048000+d5000]
  [ 1244.068609] init: network-manager main process (6369) killed by SEGV signal
  [ 1244.068712] init: network-manager main process ended, respawning
  [ 1289.042801] NetworkManager[6496]: segfault at 4 ip 08086f8f sp bfc78f00 
error 4 in NetworkManager[8048000+d5000]
  [ 1289.048793] init: network-manager main process (6496) killed by SEGV signal
  [ 1289.048885] init: network-manager main process ended, respawning
  [ 1336.078650] NetworkManager[6607]: segfault at 4 ip 08086f8f sp bf9ae470 
error 4 in NetworkManager[8048000+d5000]
  [ 1336.092633] init: network-manager main process (6607) killed by SEGV signal
  [ 1336.092736] init: network-manager main process ended, respawning
  [ 1371.334036] NetworkManager[6724]: segfault at 1c ip 0808661d sp bfe48120 
error 4 in NetworkManager[8048000+d5000]
  [ 1371.340570] init: network-manager main process (6724) killed by SEGV signal
  [ 1371.340665] init: network-manager main process ended, respawning
  [ 1417.517811] NetworkManager[6844]: segfault at 4 ip 08086f8f sp bfc5ea40 
error 4 in NetworkManager[8048000+d5000]
  [ 1417.525380] init: network-manager main process (6844) killed by SEGV signal
  [ 1417.525476] init: network-manager main process ended, respawning
  [ 1439.512146] e1000: eth0 NIC Link is Down
  [ 1471.156417] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: RX/TX

  The bug may probably be related to dual stack connectivity (IPv4 via
  DHCP and IPv6 via SLAAC/DHCPv6. When I changed the IPv6 connection to
  Ignore, the network manager did not restart anymore.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: network-manager 0.9.1.90-0ubuntu5.1
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic i686
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Fri Feb 17 10:46:48 2012
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  IpRoute:
   default via 192.168.0.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.10  metric 1
  Keyfiles: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to oneiric on 2011-10-14 (126 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/934086/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to