Bug 618024 - [abrt] crash in pinentry-qt-0.8.0-3.fc13: raise: Process /usr/bin/pinentry-qt4 was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in pinentry-qt-0.8.0-3.fc13: raise: Process /usr/bin/pinentry-qt...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: pinentry
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8edb5423fc6aa8ee72ee7a9ff72...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-25 18:17 UTC by Frank Thieme
Modified: 2011-06-29 13:00 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-06-29 13:00:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (33.92 KB, text/plain)
2010-07-25 18:17 UTC, Frank Thieme
no flags Details

Description Frank Thieme 2010-07-25 18:17:56 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/pinentry-qt --display :0.0
comment: pinentry input window will show and before I could type anything it is crashed and KMail says that the passphrase isn't correct.
component: pinentry
crash_function: raise
executable: /usr/bin/pinentry-qt4
global_uuid: 8edb5423fc6aa8ee72ee7a9ff725ce1d81debc84
kernel: 2.6.33.6-147.fc13.x86_64
package: pinentry-qt-0.8.0-3.fc13
rating: 4
reason: Process /usr/bin/pinentry-qt4 was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Write a mail in KMail that will be GPG signed
2. Send the mail
3.

Comment 1 Frank Thieme 2010-07-25 18:17:59 UTC
Created attachment 434269 [details]
File: backtrace

Comment 2 Frank Thieme 2010-08-04 06:26:02 UTC
Same crash even when I receive encrypted mail.

Problem is, that I cannot decrypt those mails then.

I think this is rather medium than low priority...

Comment 3 Frank Thieme 2010-08-04 11:15:55 UTC
Another note: starting "echo GETPIN | pinentry-qt4" from yakuake does not SIGABRT...

Comment 4 Stanislav Ochotnicky 2010-08-04 11:29:17 UTC
(In reply to comment #3)
> Another note: starting "echo GETPIN | pinentry-qt4" from yakuake does not
> SIGABRT...    

That was exactly what I was trying to do. I'll try to reproduce in an other way...

Comment 5 Bug Zapper 2011-06-01 12:52:51 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Bug Zapper 2011-06-29 13:00:00 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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