nm-system-settings crashed with SIGSEGV in PK11_ClearSlotList()

Bug #391173 reported by Lukáš Zapletal
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: network-manager

This is the worst release ever. I am using Ubuntu from its first release. :-( On the same box. Only this version has so many crashes.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/sbin/nm-system-settings
Gconf:

NonfreeKernelModules: nvidia
Package: network-manager 0.7.1~rc4.1.cf199a964-0ubuntu2
ProcAttrCurrent: unconfined
ProcCmdline: /usr/sbin/nm-system-settings --config /etc/NetworkManager/nm-system-settings.conf
ProcEnviron:

Signal: 11
SourcePackage: network-manager
StacktraceTop:
 PK11_ClearSlotList (slot=0x8309438) at pk11slot.c:971
 SECMOD_DestroyModule (module=0x8305688) at pk11util.c:777
 SECMOD_DestroyModuleListElement (element=0x8308818)
 SECMOD_DestroyModuleList (list=0x8309438) at pk11util.c:841
 SECMOD_Shutdown () at pk11util.c:99
Syslog:
 Jun 23 17:12:45 localhost NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
 Jun 23 17:13:15 localhost NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
 Jun 23 17:21:26 localhost NetworkManager: <WARN> nm_signal_handler(): Caught signal 15, shutting down normally.
 Jun 23 17:21:26 localhost NetworkManager: <info> exiting (success)
 Jun 23 17:21:27 localhost kernel: [ 2080.441627] nm-system-setti[3715]: segfault at 8331008 ip b7ea41fe sp bfb3fdb0 error 4 in libnss3.so[b7e52000+127000]
Title: nm-system-settings crashed with SIGSEGV in PK11_ClearSlotList()
Uname: Linux 2.6.28-11-generic i686
UserGroups:

WpaSupplicantLog:

Revision history for this message
Lukáš Zapletal (lzap) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:PK11_ClearSlotList (slot=0x8309438) at pk11slot.c:971
SECMOD_DestroyModule (module=0x8305688) at pk11util.c:777
SECMOD_DestroyModuleListElement (element=0x8308818)
SECMOD_DestroyModuleList (list=0x8309438) at pk11util.c:841
SECMOD_Shutdown () at pk11util.c:99

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in network-manager (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Alexander Sack (asac) wrote :

do you need your configs in /etc/network/interfaces. I suspect that its one of the stanzas in there. can you investigate which one causes this crash and let us know? Thanks!

Changed in network-manager (Ubuntu):
status: New → Incomplete
visibility: private → public
Revision history for this message
Lukáš Zapletal (lzap) wrote :

What you mean if I do need this configuration? Of course I need... Heres the file:

$ cat /etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
dns-nameservers 127.0.0.1
dns-search optinet.cz

It wont crash every time. Sometimes (after boot), restart helps.

Revision history for this message
Victor Vargas (kamus) wrote :

Since this report have a long time without activity, please could you check (if is possible) in latest version included in Karmic if this issue is still happening? Thanks in advance.

Revision history for this message
Lukáš Zapletal (lzap) wrote :

Please close.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in network-manager (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.