Hide Forgot
Description of problem: nautilus won't set up gvfs-sftp mount point for another user on another host. It will set up a gvfs-sftp mount point for me on that other host. ssh works, sftp works; these are not the issues. I get a dialog (included) Error: DBus error org.freedesktop.DBus.Error.ServiceUnknown: The name :1.65784 was not provided by any .service files Version-Release number of selected component (if applicable): $ rpm -q -f /usr/libexec/gvfsd-sftp gvfs-1.6.2-1.fc13.i686 How reproducible: I don't know how to get it *into* this state. Now that it is in this state, the effect is reproducible. Steps to Reproduce: 1. ALT-F2 sftp://USERNAME.com/home/USERNAME/Adminstration ... excites the dialog 2. ALT-F2 sftp://wbaker.com/home/wbaker/Desktop ... works Actual results: See the dialog, included Expected results: The sftp mount point is set up for USERNAME@robot-hand The sftp mount point is set up for wbaker@robot-hand Additional info: Actualities: a screenshot of the dialog that pops up dbus-monitor spew for the duration of the incident (a repeatable behavior) Oddly, this "used to work" in the sense that during my login session across the months here, I have a work flow that requires that I use this sftp mount point to drop a file into another user's account. I've done this several times. Thus, I must have done something to rejigger the names/numbers of handlers in dbus which "breaks" the sftp://USERNAME.com/home/USERNAME case but does not break the sftp://wbaker.com/home/wbaker case. That it is broken now is the issue of this report. That there is not enough information to remediate is another issue. Perhaps a full logout/login cycle would clear it. Or not. ssh and sftp from my account to USERNAME.baker.org works flawlessly.
Created attachment 477346 [details] dbus-monitor during the attempt to gvfs-sftp mount sftp://USERNAME.com/home/USERNAME/Administration
Created attachment 477347 [details] Actuality of the dialog presented back up to the desktop
Do you see any crashes in dmesg? Could you please test this on F14 or rawhide?
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.