Description of problem: Trying to open a terminal from an SFTP mounted volume causes nautilus to crash Version-Release number of selected component (if applicable): nautilus-open-terminal-0.9-2.fc9.x86_64 nautilus-extensions-2.22.5.1-1.fc9.x86_64 nautilus-2.22.5.1-1.fc9.x86_64 How reproducible: always Steps to Reproduce: 1. mount sftp volume 2. try to open a terminal from nautilus Actual results: Nautilus crashes Expected results: An SSH session is opened in a terminal Additional info:
Unfortunately, F9 reached its end-of-life on July 10, as announced here: https://www.redhat.com/archives/fedora-announce-list/2009-July/msg00004.html Therefore I have no way to push an update for this problem. However, I will see whether I can provide an unofficial update. You really should be moving to a newer Fedora that is receiving security updates and other bugfixes, though.
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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.
Changing this back to assigned to see if I can provide something unofficial in the next week or so. The closing of this bug was done by our BugZappers team's automated scripts, according to Fedora Project policies. I simply wish to keep this open just a bit longer to see if I can help. If not, I'll close it WONTFIX shortly.
perhaps then the main problem is: Why are nautilus, etc. FC9 when I'm running FC11?? $ uname -r 2.6.29.5-191.fc11.x86_64
nautilus-open-terminal-0.9-12.fc11.x86_64 nautilus-extensions-2.26.3-1.fc11.x86_64 nautilus-2.26.3-1.fc11.x86_64 is whats reported now... sorry for any confusion, I probably inadvertently was in an ssh window. If I need to I can re-file this bug, since there actually is no problem on my fc9 machine
No need to refile, but I think this makes your bug a duplicate of a problem I'm currently investigating. *** This bug has been marked as a duplicate of bug 498175 ***