NetworkManager crashed with SIGSEGV in strcmp()

[Jose.Torres]

Binary package hint: network-manager

Crash report stated this error. Thought I'd report it as it is different from the others. Please let me know if I can provide any other system information.

bleepbloop:~$ lsb_release -rd
Description: Ubuntu jaunty (development branch)
Release: 9.04

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/sbin/NetworkManager
Gconf:

IfupdownConfig:
 auto lo
 iface lo inet loopback
NonfreeKernelModules: nvidia
Package: network-manager 0.7.1~rc4-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/sbin/NetworkManager --pid-file /var/run/NetworkManager/NetworkManager.pid
ProcEnviron: PATH=(custom, no user)
Signal: 11
SourcePackage: network-manager
StacktraceTop:
 strcmp () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 _nm_marshal_VOID__STRING_STRING_POINTER_POINTER ()
 IA__g_closure_invoke (closure=0x8dedc10, return_value=0x0,
 signal_emit_unlocked_R (node=0x8deeb28, detail=0,
Title: NetworkManager crashed with SIGSEGV in strcmp()
Uname: Linux 2.6.28-11-server i686
UserGroups:

WpaSupplicantLog:

[Apport retracing service (apport)]

StacktraceTop:strcmp () from /lib/tls/i686/cmov/libc.so.6
hal_manager_udi_added_cb (hal_mgr=0x8df0420,
_nm_marshal_VOID__STRING_STRING_POINTER_POINTER (
IA__g_closure_invoke (closure=0x8dedb80, return_value=0x0,
signal_emit_unlocked_R (node=0x8deeb28, detail=0,

[Alexander Sack (asac)]

Can you reproduce this? If so, please attach your syslog taken right after crashing (I am interested in seeing which operation makes NM crash for you)

[Alexander Sack (asac)]

also i guess you use a 3g modem? Can you please run lshal and attach the output while your modem is plugged-in. Thanks!

[papukaija (papukaija)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. If you could test the current Ubuntu development version, this would help us a lot. If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect 357306, and any other logs that are relevant for this particular issue.

[Rolf Leggewie (r0lf)]

looks a lot like bug 282162

[papukaija (papukaija)]

That's a private bug (or for some other reason I can't access that page). Please mark this bug as a duplicate of that bug if you think that this bug is a duplicate of bug 282162. Thanks in advance!

[papukaija (papukaija)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[papukaija (papukaija)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!