GNOME 2.22 has been released!

Tue Mar 25 22:50:25 PDT 2008

On Tue, 2008-03-25 at 18:59 +0300, Vladimir Grebenschikov wrote:
> On Tue, 2008-03-25 at 11:39 -0400, Joe Marcus Clarke wrote:
> 
> Thank you for answers.
> 
> > > But it still stalls while scanning folders,
> > > like here:
> > > http://212.24.36.217/vova/busy-evolution.png
> > > 
> > > It goes trough long long loop (about minute or even more)
> > > truss shows lots of:
> > > poll({6/POLLIN 11/POLLIN|POLLPRI 12/POLLIN|POLLPRI 14/POLLIN|POLLPRI 15/POLLIN|POLLPRI 16/POLLIN|POLLPRI 18/POLLIN|POLLPRI 17/POLLIN|POLLPRI 23/POL
> ...
> > > poll({6/POLLIN 11/POLLIN|POLLPRI 12/POLLIN|POLLPRI 14/POLLIN|POLLPRI 15/POLLIN|POLLPRI 16/POLLIN|POLLPRI 18/POLLIN|POLLPRI 17/POLLIN|POLLPRI 23/POL
> > > LIN|POLLPRI},9,-1) = 1 (0x1)
> > > etc ...
> > > 
> > > Probably there is such fix for that problem also ? 
> > > (I have large tree of folders)
> > 
> > This is a known bug with imap-uw.  There is a hack for e-d-s (attached)
> > which prevents it at the cost of not being able to subscribe to new
> > folders.
> 
> Hm... I have no imap folders et all, just usual mail folders, this patch
> will still help me ? 
>  
> > > Another strange thing is non-desired auto-mount.
> > > I have 
> > > $ egrep '/m/[CD]' /etc/fstab
> > > /dev/ad0s1              /m/C                    ntfs    rw,noauto,-C=koi8-r     0       0
> > > /dev/ad0s3              /m/D                    msdosfs rw,noauto,-u=operator,-g=operator,-m=775,-l,-L=ru_RU.KOI8-R,-W=koi2dos  0 0
> > > $
> > > 
> > > Both have "noauto" keyword in fstab, but after upgrade they mounted
> > > automatically.
> > > And, what is totally strange, C drive appears on desktop, but D drive
> > > does not.
> > 
> > I don't have any fixed NTFS or FAT volumes so you'll need to analyze
> > this.  The code that handles the auto-mounting can be found in
> > devel/gvfs and devel/glib20 (libgio).  I would think that you shouldn't
> > be able to mount these at all unless you own /m/C and /m/D and you have
> > vfs.usermount set to 1.
> 
> real ownership answers why it shows only C on desktop
> drwxrwxr-x  1 operator  operator  8192 Jan  1  1980 /m/D
> drwxr-xr-x  2 vova      wheel      512 Aug  4  2007 /m/C
> 
> yes, I have vfs.usermount=1
> 
> > If HAL is claiming the volumes, and Nautilus is mounting them using
> > gnome-mount, then you could merge the
> > storage.automount_enabled_hint=false property to turn this off.
> 
> some-thing like: 
> $ hal-device | less
> 0: udi = '/org/freedesktop/Hal/devices/volume_uuid_8CF07973F07963FC'
>   info.parent = '/org/freedesktop/Hal/devices/volume_part1_size_32219840512'  (string)
>   volume.is_partition = false  (bool)
>   volume.mount_point = ''  (string)
>   info.udi = '/org/freedesktop/Hal/devices/volume_uuid_8CF07973F07963FC'  (string)
>   info.subsystem = 'block'  (string)
>   volume.ignore = false  (bool)
>   volume.fsversion = '3.1'  (string)
>   info.capabilities = { 'block', 'volume' } (string list)
>   volume.fsusage = 'filesystem'  (string)
>   info.product = 'Windows'  (string)
>   org.freedesktop.Hal.Device.Volume.method_names = { 'Mount', 'Unmount', 'Eject' } (string list)
>   info.category = 'volume'  (string)
>   volume.fstype = 'ntfs'  (string)
>   org.freedesktop.Hal.Device.Volume.method_signatures = { 'ssas', 'as', 'as' } (string list)
>   volume.label = 'Windows'  (string)
>   info.interfaces = { 'org.freedesktop.Hal.Device.Volume' } (string list)
>   org.freedesktop.Hal.Device.Volume.method_argnames = { 'mount_point fstype extra_options', 'extra_options', 'extra_options' } (string list)
>   volume.uuid = '8CF07973F07963FC'  (string)
>   org.freedesktop.Hal.Device.Volume.method_execpaths = { 'hal-storage-mount', 'hal-storage-unmount', 'hal-storage-eject' } (string list)
>   block.device = '/dev/ntfs/Windows'  (string)
>   volume.block_size = 512  (0x200)  (uint64)
>   volume.mount.valid_options = { 'ro', 'noexec', 'noatime', '-u=', '-g=', '-m=', '-a', '-i', '-C=', '-W=' } (string list)
>   block.major = 0  (0x0)  (int)
>   volume.size = 32219840512  (0x78073c000)  (uint64)
>   block.minor = 95  (0x5f)  (int)
>   volume.num_blocks = 62929376  (0x3c039e0)  (uint64)
>   volume.is_mounted = false  (bool)
>   block.is_volume = true  (bool)
>   volume.is_disc = false  (bool)
>   volume.is_mounted_read_only = false  (bool)
>   block.storage_device = '/org/freedesktop/Hal/devices/storage_serial_5LZ1Q84Z'  (string)
> 
> # hal-set-property --udi /org/freedesktop/Hal/devices/volume_uuid_8CF07973F07963FC --key storage.automount_enabled_hint --bool false
> 
> Executed without error, will check on next boot.

I've confirmed that libgio does not take noauto into account.  If you
want to prevent these volumes from being mounted at boot time, you can
either comment them out of /etc/fstab (then mounting can be done through
hal provided you have fixed volume mounting permission) or change the
ownership of both mount points so user mounting will not work.
Admittedly, this could be considered a bug in libgio.

Joe

-- 
Joe Marcus Clarke
FreeBSD GNOME Team      ::      gnome at FreeBSD.org
FreeNode / #freebsd-gnome
http://www.FreeBSD.org/gnome
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-gnome/attachments/20080326/e669fa0e/attachment.pgp