Bug 704281 - [abrt] esc-1.1.0-12.fc14: Process /usr/lib64/esc-1.1.0/esc was killed by signal 11 (SIGSEGV)
Summary: [abrt] esc-1.1.0-12.fc14: Process /usr/lib64/esc-1.1.0/esc was killed by sign...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: esc
Version: 6.2
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jack Magne
QA Contact: Chandrasekar Kannan
URL:
Whiteboard: abrt_hash:0baeca0c57f402f0c82f0ae9e96...
Depends On: 704076
Blocks: 748554
TreeView+ depends on / blocked
 
Reported: 2011-05-12 16:48 UTC by Jack Magne
Modified: 2015-01-04 23:48 UTC (History)
7 users (show)

Fixed In Version: esc-1.1.0-23.el6
Doc Type: Bug Fix
Doc Text:
Previously, ESC could have terminated with a segmentation fault after the user had inserted a new smart card into the reader. This was due to a bug in the code which helped to bring a pop-up window to the foreground. The code is no longer needed to assure window focus, therefore it is no longer being executed. As a result, ESC no longer terminates in the scenario described.
Clone Of: 704076
Environment:
Last Closed: 2011-12-06 17:59:59 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1718 0 normal SHIPPED_LIVE esc bug fix update 2011-12-06 01:02:15 UTC

Description Jack Magne 2011-05-12 16:48:06 UTC 
+++ This bug was initially created as a clone of Bug #704076 +++

abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 79611 bytes
cmdline: ./esc
component: esc
Attached file: coredump, 127324160 bytes
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/esc-1.1.0/esc
kernel: 2.6.35.13-91.fc14.x86_64
package: esc-1.1.0-12.fc14
rating: 4
reason: Process /usr/lib64/esc-1.1.0/esc was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1305175224
uid: 500

How to reproduce
-----
1. ESC searched for card reader
2. Card reader was already active with card
3. ESC reports it found reader then crashed

--- Additional comment from flashl on 2011-05-12 00:59:32 EDT ---

Created attachment 498435 [details]
File: backtrace

--- Additional comment from jmagne on 2011-05-12 12:46:48 EDT ---

Thanks for the report. Could you possibly say what kind of reader and card you were using at the time?
Comment 2 Eliska Slobodova 2011-11-07 12:28:07 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Previously, ESC could have terminated with a segmentation fault after the user had inserted a new smart card into the reader. This was due to a bug in the code which helped to bring a pop-up window to the foreground. The code is no longer needed to assure window focus, therefore it is no longer being executed. As a result, ESC no longer terminates in the scenario described.
Comment 3 Asha Akkiangady 2011-11-08 17:43:01 UTC 
Performed following tests on a RHEL-6.2 i386 and x86_64 desktops with esc-1.1.0-23.el6.

1. Start esc and bring up the normal Smart Card Manager UI. 
2. Attempt to insert a legal smart card (enrolled) into the computer in a repeated fashion to verify that the application remains running. 

Tested with Gemalto 64K, Safenet, CAC and PIV smart cards, ESC does not crash.

Marking the bug verified.
Comment 4 errata-xmlrpc 2011-12-06 17:59:59 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1718.html
Note You need to log in before you can comment on or make changes to this bug.