That is correct. I was a bit quick in my explanation and didn't fully explain
myself. Nautilus assumes that the directory has been created and then attempts
to access it. If it wasn't possible to create the directory because the mounted
directory is read-only, Nautilus shouldn't assume that it exists as it is doing
in this instance.
If the .Trash-$USER directory couldn't be created, it shouldn't attempt to
mount it. I still feel that this is a bug. Maybe it's as simple as changing the
log message to indicate the actual problem rather than just saying that it
couldn't be mounted, etc.
** Summary changed:
- Nautilus attempts to create a .Trash-$USER directory under the autofs mount
"/net"
+ Nautilus attempts to access a .Trash-$USER directory under the autofs mount
"/net"
** Description changed:
Binary package hint: nautilus
[EMAIL PROTECTED]:~# /etc/init.d/autofs start
Starting automounter: done.
==> syslog <==
Apr 1 14:50:15 guapuraT61 kernel: [18916.265351] SELinux: initialized (dev
autofs, type autofs), uses genfs_contexts
Apr 1 14:50:16 guapuraT61 automount[10582]: >> /sbin/showmount: can't get
address for .Trash
Apr 1 14:50:16 guapuraT61 automount[10582]: lookup(program): lookup for
.Trash failed
Apr 1 14:50:16 guapuraT61 automount[10582]: failed to mount /net/.Trash
Apr 1 14:50:16 guapuraT61 automount[10589]: >> /sbin/showmount: can't get
address for .Trash-500
Apr 1 14:50:16 guapuraT61 automount[10589]: lookup(program): lookup for
.Trash-500 failed
Apr 1 14:50:16 guapuraT61 automount[10589]: failed to mount /net/.Trash-500
Apr 1 14:50:16 guapuraT61 automount[10597]: >> /sbin/showmount: can't get
address for .Trash
Apr 1 14:50:16 guapuraT61 automount[10597]: lookup(program): lookup for
.Trash failed
Apr 1 14:50:16 guapuraT61 automount[10597]: failed to mount /net/.Trash
Apr 1 14:50:16 guapuraT61 automount[10603]: >> /sbin/showmount: can't get
address for .Trash-500
Apr 1 14:50:16 guapuraT61 automount[10603]: lookup(program): lookup for
.Trash-500 failed
Apr 1 14:50:16 guapuraT61 automount[10603]: failed to mount /net/.Trash-500
- Nautilus attempts to create a .Trash-$USER directory under the autofs mount
"/net" and consequently fails and reports a bunch of errors to /var/log/syslog.
- There should be an ignore statement somewhere so that nautilus will
ignore/not create the .Trash-$USER directory on read-only directories such as
nfs shares that have been exported read-only.
+ Nautilus attempts to mount and access a .Trash-$USER directory under the
autofs mount "/net" and consequently fails and reports a bunch of errors to
/var/log/syslog.
+ There should be an ignore statement somewhere so that nautilus will
ignore/not create the .Trash-$USER directory on read-only directories such as
nfs shares that have been exported read-only and consequently *not* attempt to
use the directory.
Additional information:
[EMAIL PROTECTED]:~# lsb_release -rd
Description: Ubuntu hardy (development branch)
Release: 8.04
[EMAIL PROTECTED]:~# apt-cache policy nautilus
nautilus:
Installed: 1:2.22.1-0ubuntu1
Candidate: 1:2.22.1-0ubuntu1
Version table:
*** 1:2.22.1-0ubuntu1 0
500 http://us.archive.ubuntu.com hardy/main Packages
100 /var/lib/dpkg/status
--
Nautilus attempts to access a .Trash-$USER directory under the autofs mount
"/net"
https://bugs.launchpad.net/bugs/210468
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
