** Changed in: nautilus
Status: Unknown = New
--
Nautilus does not respect SFTP home
https://bugs.launchpad.net/bugs/290703
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
Well this is a gvfs issue, upstream was reassigned to the gvfs component
also, rejecting the nautilus task, thanks.
** Changed in: nautilus (Ubuntu)
Status: Incomplete = Invalid
** Changed in: gvfs (Ubuntu)
Status: New = Triaged
--
Nautilus does not respect SFTP home
1. There is unexpected behaviour using (nautilus + gvfsd-sftp).
2. Sebastien says gvfsd-sftp is behaving as it is designed to do.
3. Therefore nautilus is the likely source of the unexpected behaviour.
To me this is very clear. Is there something else that would prove this
is in nautilus as
** Also affects: nautilus (Ubuntu)
Importance: Undecided
Status: New
--
Nautilus does not respect SFTP home
https://bugs.launchpad.net/bugs/290703
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
Sebatien, I agree that SFTP or gvfs is not malfunctioning here, but I
also think Mikko's result should be the actual behavior. Consider:
* After using the Connect to server tool, a non-technical user clicks the
bookmark in the Nautilus sidebar. He is confused to see folders like usr and
etc
why do you think it's a nautilus issue?
** Changed in: nautilus (Ubuntu)
Status: New = Incomplete
--
Nautilus does not respect SFTP home
https://bugs.launchpad.net/bugs/290703
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
thank you for your bug report, that's not really a bug though but how
sftp is working
** Changed in: gvfs (Ubuntu)
Sourcepackagename: nautilus = gvfs
Importance: Undecided = Low
Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs)
--
Nautilus does not respect SFTP home
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
This bug did not have a package associated with it, which is important for
ensuring that it gets looked at by the proper developers. You can learn more
about finding the right package at
