Comment 2 for bug 150877

Just to clarify, I'm _not_ referring to an SMB share that has been mounted to a local mount point (e.g. via an entry in fstab, or via the "mount" command) - I'm only referring to remote directories accessed via a path in Nautilus that starts with smb:// (or ssh://, or ftp://). The following steps might be a better way to reproduce the problem - provided you can ssh to your local machine:

* Open a Nautilus window and press ctrl-L to focus the path
* Enter a path of "ssh://username@localhost" - replacing "username" as appropriate
* Enter your password when prompted, and tell it to remember the password until you log out
* You should now be looking at the filesystem of your local machine, but accessed via ssh
* Navigate to a directory in which you have full access rights (e.g. /home/username)
* Right click, select an option from the "Create Document" menu, then edit the document and save it - in other words, verify that you do have rights to create and edit files via that window

* Now open a second Nautilus window and navigate to a directory containing an archive of some sort
* Double-click on the archive to open Fileroller
* Drag a file from Fileroller into the first Nautilus window (the ssh window). You will be prompted to allow access for Fileroller, which you should then accept ("Allow once" or "Always allow")
* The file is _not_ created at the destination

If you were already doing something along these lines, then please leave this until someone else confirms the problem - but if you were extracting to a SMB share that has a real local mount point, it might be worth trying these steps instead to see if you can more easily reproduce the problem.