Bug 688098 - [abrt] pinentry-qt-0.8.1-1.fc14: qt_message_output: Process /usr/bin/pinentry-qt4 was killed by signal 6 (SIGABRT)
Summary: [abrt] pinentry-qt-0.8.1-1.fc14: qt_message_output: Process /usr/bin/pinentry...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: pinentry
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:9f664cc166c1a7c5070d41edff2...
: 782228 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-16 10:24 UTC by john.haxby@oracle.com
Modified: 2012-09-30 09:22 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 15:11:31 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (31.49 KB, text/plain)
2011-03-16 10:24 UTC, john.haxby@oracle.com
no flags Details
File: backtrace (33.59 KB, text/plain)
2012-04-19 23:20 UTC, Simon Farnsworth
no flags Details
fix crash on missing DISPLAY envvar in ibus-qt (2.21 KB, patch)
2012-09-30 09:22 UTC, Peter Wu
no flags Details | Diff

Description john.haxby@oracle.com 2011-03-16 10:24:07 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 32242 bytes
cmdline: /usr/bin/pinentry-qt --display :0.0
component: pinentry
Attached file: coredump, 4374528 bytes
crash_function: qt_message_output
executable: /usr/bin/pinentry-qt4
kernel: 2.6.35.11-83.fc14.x86_64
package: pinentry-qt-0.8.1-1.fc14
rating: 4
reason: Process /usr/bin/pinentry-qt4 was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1300269711
uid: 500

comment
-----
That's all I did.  The pinentry-qt window pops up and almost immediately disappears.   I can't be certain but it seems related to the fact that I have focus-follows-mouse rather than click-to-focus.  I'm also using KDE which is why /usr/bin/pinentry chooses pinentry-qt4.

I can't find the ASSERT message in my ~/.xsession-errors which is where I would've expect it to be.  Sorry.

How to reproduce
-----
1. Attempt to sign a key using enigmail in thunderbird
2.
3.

Comment 1 john.haxby@oracle.com 2011-03-16 10:24:10 UTC
Created attachment 485699 [details]
File: backtrace

Comment 2 Rex Dieter 2011-03-16 12:01:04 UTC
It's probably the focus-follows-mouse thing.  There was a related crasher a release or 2 back related to that, and seems to be a regression.

Comment 3 Stanislav Ochotnicky 2011-03-16 15:31:12 UTC
(In reply to comment #2)
> It's probably the focus-follows-mouse thing.  There was a related crasher a
> release or 2 back related to that, and seems to be a regression.

I believe the crasher was in gtk code. Plus I tested this and couldn't reproduce in KDE 4 with focus follows mouse.

John: Can you reproduce reliably or was it just a one time thing? Do you have any special settings in gpg.conf or gpg-agent.conf? (grab/nograb etc.)

Comment 4 john.haxby@oracle.com 2011-03-16 15:52:33 UTC
I can reproduce this reliably -- I just attempt to sign a key from thunderbird (thunderbird-3.1.9-1.fc14.x86_64, thunderbird-enigmail-1.1.2-1.fc14.x86_64).

I've tried it with click-to-focus and it dies in the same way -- the pinentry-qt4 window pops up and then dies just as it's completely displayed.

I don't have a gpg-agent.conf and my gpg.conf is empty (apart from a comment).

I started thunderbird from the command line in the hope that the ASSERT would appear on stdout.  It doesn't :-(

Comment 5 Ed Greshko 2011-06-09 08:50:21 UTC
It appears the same problem exits in F15 pinentry-qt-0.8.1-3.fc15

Please let me know if additional debug information is needed.

Comment 6 Ed Greshko 2012-03-18 23:41:15 UTC
This problem is not present in F16.

Comment 7 abrt-bot 2012-03-20 18:27:02 UTC
*** Bug 782228 has been marked as a duplicate of this bug. ***

Comment 8 Simon Farnsworth 2012-04-19 23:20:09 UTC
I attempted to send a signed e-mail from within KMail - pinentry dialog popped up, then disappeared without any intervention from me. KMail then gave an invalid passphrase error.

It may (or may not) be relevant that this is the first time I've tried to use pinentry-qt since installing ibus and the English booster, as documented at http://fedoraproject.org/wiki/Features/english-typing-booster


backtrace_rating: 4
Package: pinentry-qt-0.8.1-6.fc17
OS Release: Fedora release 17 (Beefy Miracle)

Comment 9 Simon Farnsworth 2012-04-19 23:20:14 UTC
Created attachment 578805 [details]
File: backtrace

Comment 10 Simon Farnsworth 2012-05-02 08:24:19 UTC
I've now confirmed that uninstalling ibus fixes the error for me.

Comment 11 Fedora End Of Life 2012-08-16 15:11:34 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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 12 Peter Wu 2012-09-30 09:22:10 UTC
Created attachment 619381 [details]
fix crash on missing DISPLAY envvar in ibus-qt

Can somebody mark this bug affecting fc17? (confirmed in comment 8).

Patch is taken from upstream issue:
http://code.google.com/p/ibus/issues/detail?id=1504


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