[lucid] modem-manager crashed with SIGSEGV in dbus_g_method_return_error()

[Per Ångström]

Binary package hint: modemmanager

I was just plugging in my 3G USB modem. As always on Lucid, Networkmanager tried to connect, failed and tried again until it succeeded. This was the first time I had Apport running, so I could get a crash report.

As this happens on Lucid, I thought it ought to have a new bug report. I am aware of bug #453093, but I see that it has not received any official attention.

ProblemType: Crash
Architecture: amd64
Date: Sun Jan 17 17:41:23 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/sbin/modem-manager
Package: modemmanager 0.2.git.20091014t233208.16f3e00-0ubuntu1
ProcAttrCurrent: unconfined (enforce)
ProcCmdline: /usr/sbin/modem-manager
ProcEnviron:

ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
SegvAnalysis:
 Segfault happened at: 0x7f2caaa17357: mov %rdx,(%rax)
 PC (0x7f2caaa17357) ok
 source "%rdx" ok
 destination "(%rax)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: modemmanager
StacktraceTop:
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 dbus_g_method_return_error ()
Tags: lucid
Title: modem-manager crashed with SIGSEGV in dbus_g_method_return_error()
Uname: Linux 2.6.32-10-generic x86_64
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 _dbus_list_unlink (list=0x1e8e1f0, link=0x1e73c60)
 _dbus_list_pop_first_link (list=0x1e8e1f0)
 _dbus_connection_preallocate_send_unlocked (
 _dbus_connection_send_and_unlock (
 dbus_g_method_return_error (context=0x1e96b80,

[Per Ångström (autark)]

It happened again! I had been having trouble getting NetworkManager recognize my modem when it was plugged in from boot, so I removed and reinserted it a couple of times.

[Per Ångström (autark)]

And it happened again, now on my second laptop.

[Per Ångström (autark)]

Confirming, since it has happened on two different machines, both running Lucid.

[Per Ångström (autark)]

Near the end of the attached syslog, you can find where modem-manager segfaulted. This is from my second machine.

[Per Ångström (autark)]

It happened again, now on resuming from suspend to RAM.

[Per Ångström (autark)]

I haven't seen this in a long time. Maybe it has been fixed.

[Mörgæs (moergaes)]

Closing due to age.
If a similar bug appears in 15.10 please open a new report.