pyNeighborhood changes folder permissions

[John Russell]

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.

[Linus Hoppe (linus-hoppe-deactivatedaccount)]

Couldn't reproduce the error. Can you please try the latest version from PPA. This version fixes some permission-errors and shows several debug-messages in the mainwindow. Please report any messages.

Besides, we need more information to fix a possible bug. please mount the backup-share and post the output of 'mount'. Please describe how you would mount the share manually.

[John Russell (jrussell-88)]

Hi Linus, thanks.

Do you mean to mount backup-share in pyNeighborhood?

Actually this is a pretty simple problem / bug. PyNeighborhood seems to
adopt the privileges of the parent folder for the mounted sub-folder,
overwriting the privileges of the folder itself. Where there aren't any
differences between the privileges for the parent and the folder, it doesn't
affect it. Where the parent is owned by root rather than the user account it
changes the privileges and causes a problem. The user can't write to the
share.

Allowing pyNeighborhood to use its own folder works ok as it's owned by the
user, but changing the location of the mount point to say /mnt/backups
causes a problem because - with user privileges for /mnt/backups,
pyneighborhood overwrites those with those of /mnt i.e. root. Possibly
because it is recreating the /mnt/backups folder? The user cannot then write
to the share.

Try those locations, with the rights I have mentioned and see if the problem
reproduces.

On 6 December 2010 23:21, Linus Hoppe <email address hidden> wrote:

> Couldn't reproduce the error. Can you please try the latest version from
> PPA. This version fixes some permission-errors and shows several debug-
> messages in the mainwindow. Please report any messages.
>
> Besides, we need more information to fix a possible bug. please mount
> the backup-share and post the output of 'mount'. Please describe how you
> would mount the share manually.
>
>
> ** Changed in: pyneighborhood
> Status: New => Incomplete
>
> ** Changed in: pyneighborhood
> Importance: Undecided => Medium
>
> ** Changed in: pyneighborhood
> Assignee: (unassigned) => Linus Hoppe (linus-hoppe)
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> 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.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/pyneighborhood/+bug/685989/+subscribe
>

[Patrick Geltinger (patlkli)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi John.

Thank you for your explanations.
I will take a look at it asap.

 affects pyneighborhood
 assignee patlkli
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk0CnqIACgkQpNtrFn8mkgfIXgCgpxnSb51wDu0QISy/chCpRdns
gL0AoNaNQuE1vc2AM/WjJjnGHc61swpv
=7Ws0
-----END PGP SIGNATURE-----

[Patrick Geltinger (patlkli)]

Sorry for the signature stuff.

Message signing currently seems to bug a bit here. ;)

[Patrick Geltinger (patlkli)]

Well, pyNeighborhood *itself* does neither remove nor chmod any mount directories.

If something changes the permissions, I tend to assert that 'mount' itself does change the permissions.

However, I'll continue looking for the reason for your issue and check back in once I've found something.

[John Russell (jrussell-88)]

OK - very strange; I'll try mount directly and see if I can shed any further
light on it.

On 11 December 2010 05:05, Patrick Geltinger <email address hidden> wrote:

> Well, pyNeighborhood *itself* does neither remove nor chmod any mount
> directories.
>
> If something changes the permissions, I tend to assert that 'mount'
> itself does change the permissions.
>
> However, I'll continue looking for the reason for your issue and check
> back in once I've found something.
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> 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.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/pyneighborhood/+bug/685989/+subscribe
>

[John Russell (jrussell-88)]

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!

[Patrick Geltinger (patlkli)]

I gonna check this later today.

There obvisously are some changes in Maverick's GTK version, so we may have to fix something.

[Linus Hoppe (linus-hoppe-deactivatedaccount)]

Can you please add a screenshot of your problem and of the filechooser appearing?
Please try to use the "mount"-command and mount it manually. Maybe there is a problem with mount or smb.

[Linus Hoppe (linus-hoppe-deactivatedaccount)]

We can reproduce the bug now, trying to fix it.

[Betz Stefan (encbladexp)]

Fixed with rev 565 in upstream repository.