pyneighborhood team mailing list archive

[John Russell <685989@xxxxxxxxxxxxxxxxxx>]

I upgraded to version 0.5.3maverick1 as you suggested and repeated the
problem.

To mount the share manually - Using Nautilus 2.32.0, I select the
'Network' folder and navigate to an instance of the server, 'Backups'
shared folder, click on that and Nautilus mounts it from which point it
is browsable in Nautilus and mounted as 'smb://servername/backups' if I
have selected 'Server' which appears to be the Windows instance or
'smb://servername.local/backups' if I selected 'Server (Samba)'.

Coming back to it today, something rather odd is happening. 
 
After I click on the connect icon in pyNeighborhood, and the connection settings dialog pops up, I check "Individual mountpoint" which has a blank mountpoint field and a folder icon to select the mountpoint. 

Now when I click on the folder icon to select a mountpoint, the Nautilus window appears; I navigate to /mnt and then I can hit either the 'Cancel' button or the 'Open' button:
- Open puts me in a sub-directory, or does nothing if there is no sub-folder 
- Cancel closes Nautilus and drops me back to the connection settings dialog with a blank mountpoint field (None) unless I have selected a file in which case it 'keeps' the name of the file in the mountpoint field.  

I have tried selecting a variety of folders without changing this
behaviour. So I can't repeat the process that led to the problem I
described.

Previously, the mountpoint field 'remembered' the folder I had navigated
to - at least that's what I remember. And I repeated the behaviour I
described with both versions of pyNeighborhood many times.

Have I missed something obvious? Thanks!

-- 
You received this bug notification because you are a member of
pyNeighborhood, which is subscribed to pyneighborhood.
https://bugs.launchpad.net/bugs/685989

Title:
  pyNeighborhood changes folder permissions

Status in pyNeighborhood:
  Incomplete

Bug description:
  I am running Ubuntu 10.10 and using pyNeighborhood to map a network folder Backups to a folder in my Home folder. With my network password set, I can write to the Backups folder.

When pyNeighborhood maps Backups to eg /mnt/Backups then Backups is owned by Root, and I cannot write to it. 

If I change the ownership of /mnt/Backups, and give read/write access to my account, then pyNeighborhood changes ownership to root when it maps the network folder, and I cannot write to /mnt/Backups. 

How can I configure pyNeighborhood to allow me to write to Backups, as I can if I set the share up without pyNeighborhood?

This is a common problem as I have seen it described in many places, however the fix of using a folder in the Home directory doesn't work for me as I wish to backup my Home directory to the network folder.