NetworkManager crashed with SIGSEGV in dbus_message_iter_append_basic()

[Vesa Laitinen]

Binary package hint: network-manager

Booted Ubuntu while mobile phone was connected to USB port. After login Network manager died. Took phones USB cable out and back in Network manager started working and connected to internet. Phone was Nokia E90.

Maverick 10.10
network-manager:
  Asennettu: 0.8.1+git.20100810t184654.ab580f4-0ubuntu2

Asennettu means installed.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: network-manager 0.8.1+git.20100810t184654.ab580f4-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-22.32-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
CRDA: Error: [Errno 2] Tiedostoa tai hakemistoa ei ole
Date: Mon Sep 20 10:44:01 2010
ExecutablePath: /usr/sbin/NetworkManager
Gconf:

IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
IpRoute:
 10.6.6.6 dev ppp0 proto kernel scope link src 109.240.212.52
 169.254.0.0/16 dev ppp0 scope link metric 1000
 default via 10.6.6.6 dev ppp0 proto static
Keyfiles: Error: [Errno 2] Tiedostoa tai hakemistoa ei ole
ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x6e8770: pcmpeqb (%esi),%xmm0
 PC (0x006e8770) ok
 source "(%esi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm0" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: network-manager
StacktraceTop:
 ?? () from /lib/libc.so.6
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 dbus_message_iter_append_basic () from /lib/libdbus-1.so.3
 ?? () from /usr/lib/libdbus-glib-1.so.2
Title: NetworkManager crashed with SIGSEGV in dbus_message_iter_append_basic()
UserGroups:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #625776, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.