This bug report is being closed due to your last comment regarding this
being fixed with an update. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more
Today I noticed that the problem was in the bookmark, which specified
the full path to the mount point for shared disk instead of just
sftp://usern...@ip; - I guess that it happened because I chroted the
sftp users inside shared disk, so it was useless to specify the path to
mount point. Anyway I
On one main computer there is SSH server instaled and one of it's
encrypted disks is shared to the other 2 computers on the network using
SFTP. On the main computer I created user accounts for restricting the
access to the shared disk. Users are chroted inside shared disk, so they
are unable to
Here are HOWTOs, which I used for inspiration while setting up the SSH on main
computer:
http://linuxdocument.blogspot.com/2010/01/how-to-restrict-ssh-sftp-user-only.html
http://www.minstrel.org.uk/papers/sftp/builtin (I used mainly step 7.)
--
Nautilus shows error when accessing sftp: Please
apport information
** Tags added: apport-collected
** Description changed:
- When accessing sftp share using bookmark (sftp://usern...@ip/media/DISK)
- in Nautilus after typing the correct password an error dialog shows up
- saying Could not find sftp://usern...@ip/media/DISK; Please check the
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as
detailed as possible.
This will help us to find and resolve the problem.
**
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
Please execute the following command, as it will automatically gather
debugging information, in a terminal:
apport-collect 615589
This will help us to find and resolve the problem. Bear in mind that you
may need to install the python-launchpadlib package from the universe
repository.
