Nautilus doesn't respect ACL when creating new files

Bug #88994 reported by Philipp Schlesinger
14
Affects Status Importance Assigned to Milestone
Nautilus
Fix Released
Medium
nautilus (Debian)
Fix Released
Unknown
nautilus (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs
Declined for Edgy by Sebastien Bacher

Bug Description

Binary package hint: nautilus

This bug is due to the removal of a patch shortly before the egdy release:

nautilus (2.16.1-0ubuntu2) edgy; urgency=low
 .
   * debian/patches/02_umask.patch:
     - dropped for now, it creates issues on file creation (Ubuntu: #63934)

An updated and working patch got commited upstream and is part of nautilus 2.16.3.

There even is a bounty regarding this issue: https://launchpad.net/bounties/nautilus-ignores-umask

Revision history for this message
In , Rubén Porras Campo (nahoo) wrote : bug 314796 is forwarded to http://bugzilla.gnome.org/show_bug.cgi?id=327249
Revision history for this message
In , Pierre Habouzit (madcoder) wrote : btspull automated mail
Download full text (115.6 KiB)

user <email address hidden>
forwarded 85437 http://bugs.kde.org/show_bug.cgi?id=20186
tags 85437 + upstream fixed-upstream
usertags 85437 + status-CLOSED resolution-FIXED
tags 223708 + upstream fixed-upstream
usertags 223708 + status-CLOSED resolution-FIXED
forwarded 85443 http://bugs.kde.org/show_bug.cgi?id=20187
tags 85443 + upstream fixed-upstream
usertags 85443 + status-CLOSED resolution-FIXED
forwarded 100894 http://bugs.kde.org/show_bug.cgi?id=6184
tags 100894 + upstream
usertags 100894 + status-NEW
tags 215400 + upstream
usertags 215400 + status-NEW
tags 94567 + upstream wontfix
usertags 94567 + status-RESOLVED resolution-WONTFIX
forwarded 101379 http://bugs.kde.org/show_bug.cgi?id=32192
tags 101379 - wontfix
tags 101379 + upstream
usertags 101379 + status-UNCONFIRMED
usertags 154184 + status-RESOLVED resolution-FIXED
forwarded 102462 http://bugs.kde.org/show_bug.cgi?id=35918
usertags 102462 + status-UNCONFIRMED
forwarded 262988 http://bugzilla.kernel.org/show_bug.cgi?id=4532
tags 262988 + upstream fixed-upstream
usertags 262988 + status-CLOSED resolution-CODE_FIX
tags 132860 + upstream wontfix
usertags 132860 + status-RESOLVED resolution-WONTFIX
usertags 226824 + status-ASSIGNED
tags 221999 + upstream fixed-upstream
usertags 221999 + status-RESOLVED resolution-WORKSFORME
forwarded 103201 http://bugs.kde.org/show_bug.cgi?id=28072
tags 103201 + fixed-upstream
usertags 103201 + status-RESOLVED resolution-FIXED
usertags 169092 + status-NEW
tags 251067 + upstream
usertags 251067 + status-NEW
tags 144907 + upstream
usertags 144907 + status-ASSIGNED
forwarded 111358 http://bugs.kde.org/show_bug.cgi?id=35921
tags 111358 + upstream fixed-upstream
usertags 111358 + status-CLOSED resolution-FIXED
usertags 297529 + status-NEW
tags 223738 + upstream fixed-upstream
usertags 223738 + status-RESOLVED resolution-WORKSFORME
forwarded 116824 http://bugs.kde.org/show_bug.cgi?id=35926
usertags 116824 + status-RESOLVED resolution-WONTFIX
tags 180740 + upstream
usertags 180740 + status-REOPENED
usertags 169146 + status-NEW
tags 223928 + upstream fixed-upstream
usertags 223928 + status-RESOLVED resolution-WORKSFORME
usertags 190690 + status-UNCONFIRMED
tags 266542 + upstream
usertags 266542 + status-NEW
forwarded 116826 http://bugs.kde.org/show_bug.cgi?id=22723
usertags 116826 + status-NEW
tags 311758 + upstream
usertags 311758 + status-RESOLVED resolution-CODE_FIX
tags 303074 + upstream fixed-upstream
usertags 303074 + status-RESOLVED resolution-WORKSFORME
tags 196814 + upstream
usertags 196814 + status-NEW
tags 48602 + upstream wontfix
usertags 48602 + status-RESOLVED resolution-WONTFIX
tags 201323 + upstream
usertags 201323 + status-NEW
tags 238290 + upstream
usertags 238290 + status-NEW
forwarded 231017 https://bugzilla.icculus.org/show_bug.cgi?id=952
usertags 231017 + status-ASSIGNED
usertags 321403 + status-ASSIGNED
forwarded 118834 http://bugs.kde.org/show_bug.cgi?id=35938
usertags 118834 + status-NEW
usertags 200342 + status-NEW
tags 206744 + fixed-upstream
usertags 206744 + status-RESOLVED resolution-FIXED
tags 280412 + fixed-upstream
usertags 280412 + status-RESOLVED resolution-FIXED
tags 310141 + upstream
usertags 310141 + statu...

Revision history for this message
In , Sven Arvidsson (sa) wrote : Evince/Nautilus bugs

tags 366550 + fixed-upstream
tags 365575 + fixed-upstream

severity 314796 normal
severity 322183 normal
merge 322183 314796

quit
stop
thank

Revision history for this message
In , Josselin Mouette (joss) wrote : reassign 314796 to libgnomevfs2-0

# Automatically generated email from bts, devscripts version 2.9.19
reassign 314796 libgnomevfs2-0

Revision history for this message
In , Josselin Mouette (joss) wrote : Bug#314796: fixed in nautilus 2.14.3-1
Download full text (3.3 KiB)

Source: nautilus
Source-Version: 2.14.3-1

We believe that the bug you reported is fixed in the latest version of
nautilus, which is due to be installed in the Debian FTP archive:

libnautilus-extension-dev_2.14.3-1_i386.deb
  to pool/main/n/nautilus/libnautilus-extension-dev_2.14.3-1_i386.deb
libnautilus-extension1_2.14.3-1_i386.deb
  to pool/main/n/nautilus/libnautilus-extension1_2.14.3-1_i386.deb
nautilus-data_2.14.3-1_all.deb
  to pool/main/n/nautilus/nautilus-data_2.14.3-1_all.deb
nautilus-dbg_2.14.3-1_i386.deb
  to pool/main/n/nautilus/nautilus-dbg_2.14.3-1_i386.deb
nautilus_2.14.3-1.diff.gz
  to pool/main/n/nautilus/nautilus_2.14.3-1.diff.gz
nautilus_2.14.3-1.dsc
  to pool/main/n/nautilus/nautilus_2.14.3-1.dsc
nautilus_2.14.3-1_i386.deb
  to pool/main/n/nautilus/nautilus_2.14.3-1_i386.deb
nautilus_2.14.3.orig.tar.gz
  to pool/main/n/nautilus/nautilus_2.14.3.orig.tar.gz

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Josselin Mouette <email address hidden> (supplier of updated nautilus package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

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

Format: 1.7
Date: Thu, 3 Aug 2006 21:41:00 +0200
Source: nautilus
Binary: libnautilus-extension-dev libnautilus-extension1 nautilus-data nautilus-dbg nautilus
Architecture: source i386 all
Version: 2.14.3-1
Distribution: unstable
Urgency: low
Maintainer: Josselin Mouette <email address hidden>
Changed-By: Josselin Mouette <email address hidden>
Description:
 libnautilus-extension-dev - libraries for nautilus components - development version
 libnautilus-extension1 - libraries for nautilus components - runtime version
 nautilus - file manager and graphical shell for GNOME
 nautilus-data - data files for nautilus
 nautilus-dbg - file manager and graphical shell for GNOME - debugging version
Closes: 314796
Changes:
 nautilus (2.14.3-1) unstable; urgency=low
 .
   * New upstream release.
   * 02_umask.patch: honor umask when creating files (closes: #314796).
   * 01_relibtoolise.patch: removed.
   * Bump eel2 build-dependencies.
Files:
 f194e6bfb03dd31107fb077e5f1a96d5 1768 gnome optional nautilus_2.14.3-1.dsc
 a0349c3433b8a261f01f6ec1545e7c42 5990818 gnome optional nautilus_2.14.3.orig.tar.gz
 25b71486533466fa286b776040e27473 14478 gnome optional nautilus_2.14.3-1.diff.gz
 0b3d12bebd52bb0bb1eb886a9062d764 3500240 gnome optional nautilus-data_2.14.3-1_all.deb
 de486f97ea01587ad88a26c5b027e62c 598440 gnome optional nautilus_2.14.3-1_i386.deb
 226b6028e885d17794106d228c568d64 1664880 gnome extra nautilus-dbg_2.14.3-1_i386.deb
 fcb26768675fdafe50f539b983c70d3e 82334 libs optional libnautilus-extension1_2.14.3-1_i386.deb
 e979589f649c15ee08e90d117dd622d7 78228 libdevel optional libnautilus-extension-dev_2.14.3-1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: ...

Read more...

Revision history for this message
In , hobbes (hobbes-poukram) wrote : incomplete solution

Hello,

as described on

http://bugzilla.gnome.org/show_bug.cgi?id=327249

the solution seems incomplete as nautilus still doesn't respect the ACLs
when creating new files. Should I open a new bug ? Or do you reopen this
one ?

Thanks,
--
Rémi

Revision history for this message
In , Josselin Mouette (joss) wrote : Re: Bug#314796: incomplete solution

reopen 314796
found 314796 2.14.3-1
retitle 314796 Nautilus doesn't respect ACL when creating new files
thanks

Le mardi 08 août 2006 à 01:46 +0200, Rémi Letot a écrit :
> Hello,
>
> as described on
>
> http://bugzilla.gnome.org/show_bug.cgi?id=327249
>
> the solution seems incomplete as nautilus still doesn't respect the ACLs
> when creating new files. Should I open a new bug ? Or do you reopen this
> one ?

Reopening with a new title.
--
 .''`. Josselin Mouette /\./\
: :' : <email address hidden>
`. `' <email address hidden>
   `- Debian GNU/Linux -- The power of freedom

Revision history for this message
In , nahoo (nahoo82) wrote : bug upstream fixed

The bug is fixed in upstream.

Greatings.

Revision history for this message
In , Loïc Minier (lool) wrote : tagging 314796

# Automatically generated email from bts, devscripts version 2.9.27
tags 314796 + fixed-upstream

Revision history for this message
In , Josselin Mouette (joss) wrote : Re: Bug#314796: bug upstream fixed

Version: 2.16.3-1

Le jeudi 11 janvier 2007 à 19:53 +0100, Ruben Porras a écrit :
> The bug is fixed in upstream.

It is even fixed in the Debian experimental packages. I'm marking it as
closed with the correct version.

--
 .''`.
: :' : We are debian.org. Lower your prices, surrender your code.
`. `' We will add your hardware and software distinctiveness to
  `- our own. Resistance is futile.

Revision history for this message
Philipp Schlesinger (philipp-sadleder) wrote :

Binary package hint: nautilus

This bug is due to the removal of a patch shortly before the egdy release:

nautilus (2.16.1-0ubuntu2) edgy; urgency=low
 .
   * debian/patches/02_umask.patch:
     - dropped for now, it creates issues on file creation (Ubuntu: #63934)

An updated and working patch got commited upstream and is part of nautilus 2.16.3: http://bugzilla.gnome.org/show_bug.cgi?id=327249

description: updated
Revision history for this message
Sebastien Bacher (seb128) wrote :

That is already fixed to feisty, the problem is minor we will not patch edgy for that

Changed in nautilus:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: Unconfirmed → Fix Released
Changed in nautilus:
status: Unknown → Fix Released
Changed in nautilus:
status: Unknown → Fix Released
Revision history for this message
Randall Thomas (fromagesauce) wrote :

Could you explain the reasons you feel this issue is minor. As I see it, it prevents anything pre-fiesty from being used in a workgroup type environment.

Revision history for this message
Sebastien Bacher (seb128) wrote :

There has been few bugs opened about that and they don't have a lot of subscribers, it doesn't look like high priority for the Ubuntu users at the moment. Edgy is not really a corporate version and feisty will be soon available. That might be something to consider for dapper though

Revision history for this message
Philipp Schlesinger (philipp-sadleder) wrote :

Would be great to have respective related bugs marked as duplicate, if you are aware of them.

Revision history for this message
Sebastien Bacher (seb128) wrote :

There was bug #29282 open about that and it's fixed now

Revision history for this message
compmodder26 (bthelm2-insightbb) wrote :

Is there supposed to be some setting I can use for this in Feisty? I've edited all files I can think of for the umask (/etc/bash.bashrc, etc/profile, /etc/login.defs, ~/.bashrc, ~/.bash_profile), and I'm still not able to get nautilus to obey.

Revision history for this message
PAN007 (systemansvarlig) wrote :

I discovered this bug with Dapper today. We seriously need the ability to share a directory within groups of users. This is NOT a minor issue!

I have 200 ubuntu workstations and several hundred users that are affected.

Revision history for this message
compmodder26 (bthelm2-insightbb) wrote :

I agree for Dapper. Edgy may not be a valid candidate for this patch, but Dapper sure is. I'm willing to bet that anybody that is deploying Ubuntu on a large scale level (e.g. companies/universities who are giving money to the project for support,etc.) is using Dapper because of the LTS. I seriously doubt they want to wait for the next LTS release to have this problem solved.

Revision history for this message
Julien Valroff (julienv) wrote : Re: [Bug 88994] Re: Nautilus doesn't respect ACL when creating new files

Hi,

First, I must say I am not an Ubuntu user.

Le mercredi 14 mars 2007 à 16:10 +0000, Brian Helm a écrit :
> I agree for Dapper. Edgy may not be a valid candidate for this patch,
> but Dapper sure is. I'm willing to bet that anybody that is deploying
> Ubuntu on a large scale level (e.g. companies/universities who are
> giving money to the project for support,etc.) is using Dapper because of
> the LTS. I seriously doubt they want to wait for the next LTS release
> to have this problem solved.

This issue was fixed upstream a quite long time ago, and a patch is
available on GNOME Bugzilla for nautilus 2.14.3[0].

According to the Debian package changelog, it seems another solution was
applied upstream, which could surely be backported for Dapper.

I thus do not understand why this bug would still subsist in Ubuntu,
especially in Dapper!

On Debian, the patch is applied and everything works fine - except a
bug[1] in coreutils which still prevent using folders shared by a group
of users (this also affects nautilus behaviour - just replace cp/mv
commands in the bug report by the copy and cut options in nautilus
contextual menu).

Cheers,
Julien

[0] http://bugzilla.gnome.org/show_bug.cgi?id=327249
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=402332

Revision history for this message
Sebastien Bacher (seb128) wrote :

The shared directory case has been fixed for dapper, you can read bug #36647 about that

Julien, the Debian version had several iterations before being correct, we don't hurry upload to stable LTS version and prefer to make sure everything works as expected

Revision history for this message
Julien Valroff (julienv) wrote :

I fully understand your point of view for Dapper - you should have explained it this way earlier ;-) I wasn't aware the Debian version needed some many changes.

As for the shared directory case, it's not fixed in my (not so isolate) personal example. The nautilus umask bug is now fixed, but when copying a file to a directory with default ACLs, the latter are not applied (the bug is in coreutils as described earlier) - I do not talk about moving file as I clearly understand your explanations on the other bug report (though I don't think it is end-user-friendly).
As far as I know, this is not a bug due to a patch in the Debian/Ubuntu packages.

Cheers,
Julien

Revision history for this message
Sebastien Bacher (seb128) wrote :

Could anybody describe a situation which is not working correctly on dapper, is fixed on feisty now?

Revision history for this message
Roger Miller (zill) wrote :

When creating a file in Nautilus 2.14.3 (Dapper) permissions are not updated as per the umask setting defined in /etc/profile. When umask is changed from default 022 to 002 this should give the group write access with file permissions of 664, but Nautilus maintains file permissions of 600. This causes problems when a group should have write access as a default.
Please fix Dapper and later versions asap. Thanks.

Revision history for this message
compmodder26 (bthelm2-insightbb) wrote :

I don't have Dapper any more to test it, but this was supposedly fixed
to dapper. Try creating a file called .gnomerc in your user's home
directory and placing the umask in it. That has worked in Feisty for
me.

On Sat, 2007-03-24 at 16:53 +0000, Roger Miller wrote:
> When creating a file in Nautilus 2.14.3 (Dapper) permissions are not updated as per the umask setting defined in /etc/profile. When umask is changed from default 022 to 002 this should give the group write access with file permissions of 664, but Nautilus maintains file permissions of 600. This causes problems when a group should have write access as a default.
> Please fix Dapper and later versions asap. Thanks.

Revision history for this message
Roger Miller (zill) wrote :

Thanks for the suggestion Brian but it doesn't work on Dapper. Nautilus still keeps file permissions at 600 :-(

Revision history for this message
philipp sutter (sutter) wrote :

This bug is still present in Gutsy Gibbon. Nautilus still keeps file permissions at 600. this bug is so painful in the process of introducing linux (ubuntu) in our mixed network.

Changed in nautilus:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.