I have been using lucid 64-bit for several months.  I have not seen
the incorrect behavior; the Trash applet seems to work properly.

On Wed, Apr 21, 2010 at 8:17 AM, Sebastien Bacher <email address hidden> wrote:
> could somebody try if that's still an issue on lucid?
>
> --
> Deleted files does not show in Nautilus trash
> https://bugs.launchpad.net/bugs/366379
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “nautilus” package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: nautilus
>
> Greetings.
> When I delete a file by pressing "delete" on the keyboard or by right-clicking a file and then choosing "Move to Trash", the file is removed as intended, but, when you open the trash:/// directory, it does not show any of the deleted files.
>
> I have found similar bug reports on LaunchPad, but most of then are old from the time of Gutsy. Also, those reports shows that it affects NTFS file-system.
>
> https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/193084
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-vfs2/+bug/161018
>
>
>
> Since I am using ext3 and I am using the latest Ubuntu, I have decided to report as a new bug.
>
> My specs are as follows:
>
> OS:  Ubuntu 9.04 64-bit
> DE:  Gnome 2.26.1
> FS:  Ext3
>
> MP: Intel Core 2 Duo
> VC: Intel Corporation Mobile GM965/GL960 Integrated Graphics
>
> ******************
>
> mount:
>
> /dev/sda3 on / type ext3 (rw,relatime,errors=remount-ro)
> tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
> proc on /proc type proc (rw,noexec,nosuid,nodev)
> sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
> varrun on /var/run type tmpfs (rw,nosuid,mode=0755)
> varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
> udev on /dev type tmpfs (rw,mode=0755)
> tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
> devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
> fusectl on /sys/fs/fuse/connections type fusectl (rw)
> lrm on /lib/modules/2.6.28-11-generic/volatile type tmpfs (rw,mode=755)
> securityfs on /sys/kernel/security type securityfs (rw)
> binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
> gvfs-fuse-daemon on /home/rome/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=rome)
>
>
>
>
> cat /etc/fstab:
>
> # /etc/fstab: static file system information.
> #
> # Use 'vol_id --uuid' to print the universally unique identifier for a
> # device; this may be used with UUID= as a more robust way to name devices
> # that works even if disks are added and removed. See fstab(5).
> #
> # <file system> <mount point>   <type>  <options>       <dump>  <pass>
> proc            /proc           proc    defaults        0       0
> # / was on /dev/sda3 during installation
> UUID=3be9374c-9e6e-4c3f-a3a1-a3d05db1c1ac /               ext3    relatime,errors=remount-ro 0       1
> # swap was on /dev/sda4 during installation
> UUID=d564773f-d006-4101-a3ae-31e95a29d189 none            swap    sw              0       0
> /dev/scd0       /media/cdrom0   udf,iso9660 user,noauto,exec,utf8 0       0
>
>
>
> EDIT. Additional info:
>
> This bug is reproducible in a NEWLY installed Ubuntu System.
> The problem goes a away after a couple of restarts.
>
> Please ask me if you need more info. I will be happy to provide it.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/366379/+subscribe
>