firefox-bin crashed with SIGSEGV in SECMOD_GetReadLock()

Bug #144849 reported by Jack Wasey
6
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: firefox

hopefully with firefox-dbg installed this time.

ProblemType: Crash
Architecture: i386
Date: Mon Sep 24 20:06:21 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/firefox/firefox-bin
NonfreeKernelModules: cdrom
Package: firefox 2.0.0.6+2-0ubuntu4
PackageArchitecture: i386
ProcCmdline: /usr/lib/firefox/firefox-bin
ProcCwd: /home/jack
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: firefox
StacktraceTop:
 SECMOD_GetReadLock (modLock=0x0) at pk11list.c:71
 PK11_GetAllTokens (type=528, needRW=0, loadCerts=1,
 PK11_GetBestSlotMultiple (type=0xbfe992ec, mech_count=1,
 PK11_GetBestSlot (type=528, wincx=0x0) at pk11slot.c:2100
 PK11_CreateDigestContext (hashAlg=SEC_OID_MD5)
Title: firefox-bin crashed with SIGSEGV in SECMOD_GetReadLock()
Uname: Linux antibes 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev root scanner sudo video

Tags: apport-crash
Revision history for this message
Jack Wasey (jackwasey) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:SECMOD_GetReadLock (modLock=0x0) at pk11list.c:71
PK11_GetAllTokens (type=528, needRW=0, loadCerts=1, wincx=0x0) at pk11slot.c:1949
PK11_GetBestSlotMultiple (type=0xbfe992ec, mech_count=1, wincx=0x0) at pk11slot.c:2039
PK11_GetBestSlot (type=528, wincx=0x0) at pk11slot.c:2100
PK11_CreateDigestContext (hashAlg=SEC_OID_MD5) at pk11cxt.c:410

Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in firefox:
importance: Undecided → Medium
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.