Bug 711149 - [abrt] seamonkey-2.0.14-1.fc14: sc_unlock: Process /usr/lib64/seamonkey-2.0.14/seamonkey-bin was killed by signal 6 (SIGABRT)
Summary: [abrt] seamonkey-2.0.14-1.fc14: sc_unlock: Process /usr/lib64/seamonkey-2.0.1...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: seamonkey
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:f84c1b649f27b0706e7543a00f0...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-06 16:38 UTC by Richard Troxel
Modified: 2011-12-07 13:05 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-07 13:05:37 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (57.01 KB, text/plain)
2011-06-06 16:38 UTC, Richard Troxel 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Richard Troxel 2011-06-06 16:38:47 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 58378 bytes
cmdline: /usr/lib64/seamonkey-2.0.14/seamonkey-bin http://start.fedoraproject.org/
component: seamonkey
Attached file: coredump, 187232256 bytes
crash_function: sc_unlock
executable: /usr/lib64/seamonkey-2.0.14/seamonkey-bin
kernel: 2.6.35.13-91.fc14.x86_64
package: seamonkey-2.0.14-1.fc14
rating: 4
reason: Process /usr/lib64/seamonkey-2.0.14/seamonkey-bin was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1307377686
uid: 500

How to reproduce
-----
1. logged into GDM with PIV card
2. locked screen for half hour
3. re-connected; was asked for PIV PIN twice
Comment 1 Richard Troxel 2011-06-06 16:38:49 UTC 
Created attachment 503283 [details]
File: backtrace
Comment 2 Martin Stransky 2011-12-07 13:05:37 UTC 
We're using mozilla crash reporter now, ABRT is no more used for Firefox/Thunderbird. If you can reliably reproduce the crash (you have a testcase, reproduction steps, etc.) please reopen the bug and attach the reproduction info and assign it directly to me (stransky).

Thanks!
Note You need to log in before you can comment on or make changes to this bug.