Bug 436035
Summary: | seahorse-agent reports error during login | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Espen Stefansen <libbe> |
Component: | seahorse | Assignee: | Seth Vidal <skvidal> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 8 | CC: | steve |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-01-09 06:06:17 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Espen Stefansen
2008-03-04 22:21:05 UTC
Same issue under Fedora 9. Expected Result; Attempting to ssh to a host returns the seahorse passphrase window Actual result; Attempting to ssh to a host produces; Jul 14 19:51:48 nx6320 seahorse-agent[2748]: Failed to send buffer Jul 14 19:51:48 nx6320 seahorse-agent[2748]: Failed to send buffer in /var/log/messages. I don't get any prompt for a passphrase from seahorse-agent. Restarting avahi-daemon also returns; Jul 14 20:00:27 nx6320 seahorse-agent[2882]: failure communicating with to avahi: Daemon connection failed Jul 14 20:00:27 nx6320 seahorse-agent[2748]: failure communicating with to avahi: Daemon connection failed Version-Release number of selected component (if applicable): seahorse-2.22.2-1.fc9.i386 Ok, further testing has found the following; I had a key in my ~/.ssh called id_rsa.1 (as a result of creating a second key). This key had been picked up by seahorse, but was not being used. Once I moved the key to id_rsa, I was prompted for a passphrase and this has been cached since I provided a passphrase. I do not know if the solution of importing this key into seahorse would have mitigated the problem. This worked fine in seahorse under Fedora 8. So, a suitable test case from my point of view is; move a rsa private key file from id_rsa to id_rsa.1, then try to ssh to a host with the public part of the key in authorized hosts. This message is a reminder that Fedora 8 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 8. 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 '8'. 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 8'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 8 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 Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 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. |