| Summary: | [abrt] seahorse-3.2.0-1.fc16: calculate_keyserver_uri: Process /usr/bin/seahorse was killed by signal 11 (SIGSEGV) | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jared Smith <jsmith.fedora> | ||||||||||||
| Component: | gtk3 | Assignee: | Matthias Clasen <mclasen> | ||||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 16 | CC: | aschmidt, bugzilla, guillaumepoiriermorency, Healf1972, mclasen, ncorrare, redhat-bugzilla, sumstultussedesquoque, tbzatek, XGaryG | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | x86_64 | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| Whiteboard: | abrt_hash:8090008f83d392d1fb0255c14b201793c0afc965 | ||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2013-02-13 17:55: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
Jared Smith
2011-10-12 21:31:14 UTC
Created attachment 527790 [details]
File: maps
Created attachment 527791 [details]
File: backtrace
Package: seahorse-3.2.0-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Creating a custom key server I tried to add a keyserver. If I choose custom, it crashes every time. rating: 4 Package: seahorse-3.2.1-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Opened seahorse, opened preferences then selected custom instead of ldap. Then instant crash. Was trying to add an hkp key server, why is this not compiled in anymore? backtrace_rating: 4 Package: seahorse-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne) Created attachment 555549 [details]
File: backtrace
I have selected "Custom" Key Server Type instead of "LDAP Key Server" in preferences, and it crashed. It's reproducible and happens every time I select "Custom". backtrace_rating: 4 Package: seahorse-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne) Created attachment 563934 [details]
File: backtrace
1. Open seahorse 2. Go to Edit → Preferences 3. Click 'Add' 3. Change 'Key Server Type' to "Custom" 4. Segfault. backtrace_rating: 4 Package: seahorse-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne) Created attachment 564428 [details]
File: backtrace
Backtrace analysis of bugs across components suggests the actual bug is in component gtk3 instead of component seahorse, reassigning to gtk3. Bugs which were found to be similar to this bug: empathy: bug #711855 seahorse: bug #757574 This comment is automatically generated. *** Bug 711855 has been marked as a duplicate of this bug. *** *** Bug 757574 has been marked as a duplicate of this bug. *** Surprise for me is that this isn't a showstopper in F17, as well as listed as unassigned Severity and Priority nearly six months after the first report. Unless Seahorse is deprecated in Gnome3? Or maybe it's working again in F17, anyone else tested? This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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, you are encouraged to click on "Clone This Bug" 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 Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. |