| Summary: | [abrt] pinentry-qt-0.8.1-1.fc14: qt_message_output: Process /usr/bin/pinentry-qt4 was killed by signal 6 (SIGABRT) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | john.haxby <john.haxby> | ||||||||
| Component: | pinentry | Assignee: | Rex Dieter <rdieter> | ||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 14 | CC: | axel.thimm, ed.greshko, rdieter, simon, sochotni, yehielb | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | abrt_hash:9f664cc166c1a7c5070d41edff219b347ae2e393 | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2012-08-16 15:11:31 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Attachments: |
|
||||||||||
|
Description
john.haxby@oracle.com
2011-03-16 10:24:07 UTC
Created attachment 485699 [details]
File: backtrace
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. (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.) 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 :-( 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. This problem is not present in F16. *** Bug 782228 has been marked as a duplicate of this bug. *** 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) Created attachment 578805 [details]
File: backtrace
I've now confirmed that uninstalling ibus fixes the error for me. 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 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 |