Date: Mon, 16 Apr 2007 20:37:02 -0400 From: Joe Marcus Clarke <marcus@FreeBSD.org> To: Volker <volker@vwsoft.com> Cc: freebsd-gnome@FreeBSD.org Subject: Re: gnome-mount unmount problem Message-ID: <1176770222.1579.32.camel@shumai.marcuscom.com> In-Reply-To: <46241076.8070107@vwsoft.com> References: <462356A9.2070604@vwsoft.com> <462371C9.7040903@freebsd.org> <46238457.8010202@vwsoft.com> <4623A6E1.2090504@freebsd.org> <46241076.8070107@vwsoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-bt32ftgbG8CENW1TEsPJ Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2007-04-17 at 02:10 +0200, Volker wrote: > On 04/16/07 18:40, Joe Marcus Clarke wrote: > > Volker wrote: > >> On 04/16/07 14:53, Joe Marcus Clarke wrote: > >>> Volker wrote: > >>>> Hi again... > >>>> > >>>> While I've experienced trouble with gnome-mount, I probably shot > >>>> myself into the foot (or have found another gnome-mount bug?). > >>>> > >>>> When logging into gdm, gnome-mount is mounting all volumes it can > >>>> find (can this be configured in any way?). When trying to unmount > >>>> such an automounted volume, I'm getting: > >>>> > >>>> gnome-mount --no-ui --block --unmount --verbose --device > >>>> /dev/label/xchange > >>>> gnome-mount 0.6 > >>>> libhal-storage.c 1330 : INFO: called LIBHAL_FREE_DBUS_ERROR but > >>>> dbusError was not set. > >>>> ** (gnome-mount:1402): DEBUG: Unmounting > >>>> /org/freedesktop/Hal/devices/volume_uuid_DB29_8A68 > >>>> ** (gnome-mount:1402): DEBUG: Setting up 750ms timer for Flushing > >>>> Cache dialog > >>>> ** (gnome-mount:1402): DEBUG: in unmount_done : user_data =3D 0x0 > >>>> > >>>> ** (gnome-mount:1402): WARNING **: Unmount failed for > >>>> /org/freedesktop/Hal/devices/volume_uuid_DB29_8A68: > >>>> org.freedesktop.Hal.Device.Volume.PermissionDenied : Volume mounted > >>>> by uid UNKNOWN cannot be unmounted by uid 1001. > >>>> > >>>> This is the same with any automounted volume (either FAT, NTFS). I'm > >>>> always getting "...mounted by uid UNKNOWN...". > >>>> > >>>> Unmounting these gnome automounted volumes as root, gives me the > >>>> chances to manually mount and unmount them properly from the panel. > >>>> These mounts are really done by gnome, as I've checked the mount > >>>> status before logging into gdm. > >>>> > >>>> Last week while trying to find a solution for the gnome-mount NTFS > >>>> problem, I've changed polkitd and hal permissions to > >>>> Allow=3Dgid:operator but AFAIR this has been the only change. As the= re > >>>> are not many settings for HAL, polkit and gnome-mount, I'm not quite > >>>> sure if this is my mistake or if it's a bug. > >>>> > >>>> Any hints on how to hunt this? > >>> What version of hal do you have installed, and when did you last rest= art > >>> it? > >>> > >>> Joe > >>> > >> > >> Joe, > >> > >> sorry for not posting this info. I'm using latest hal from ports: > >> hal-0.5.8.20070403 > >> > >> As this is my notebook, it's restarted on a daily basis. My desktop > >> machine (also using Gnome2, latest) does not automount everything it > >> can find so I'm unable to recreate the problem on that desktop. > >> > >> The main question is: Why or when does gnome-mount automount volumes > >> and how does one disable automounting? If gnome-mount would not > >> automount on startup, volumes can be mounted and unmounted without > >> error. If it does automount, I'm receiving the error message > >> "mounted by uid UNKNOWN". > >=20 > > gnome-volume-manager is responsible for mounting file systems. How man= y > > instances or g-v-m are you running? Do you have any other scripts or > > session instances that start gnome-mount? > >=20 > > Joe > >=20 >=20 > Joe, >=20 > thank you for your time on this. >=20 > %ps ax | grep vol > 1265 ?? Ss 0:04.87 gnome-volume-manager --sm-disable >=20 > There's just one instance running and it's started from gnome-session. >=20 > How does g-v-m decide on which volumes to mount (automount) at gdm > login? It depends on the settings in the Removable Drives and Media capplet. It may not mount anything. If "Mount removable media when inserted" is not checked, then g-v-m will not mount anything when it starts. >=20 > I _think_ I've solved that problem. I've compared the hald and > polkitd settings with my desktop system (which is less manipulated > than my notebook) I've figured out the hal-storage-fixed* settings > are set to 'Allow=3D' by default. On my troubled notebook system, I've > had 'Allow=3Duid:__all__' in it. >=20 > Setting this to 'Allow=3D' and rebooting the system, Gnome came up > with no automounted volumes. What volumes exactly were being mounted that were not mounted before? This setting should only control the mounting of fixed disks (i.e. those with storage.removable=3Dfalse in hal). >=20 > Could you please give me some pointers on how hald, polkitd, g-v-m > and gnome-mount interact and which knobs and settings are where to > find? I would try to start some man pages for them as this issue > seems to be a typical "user (me) did stupid things and screwed up a > running system by the lack of docs". But I need more knowledge about > these to write anything about them. Admittedly, there is what I consider to be a bug in g-v-m where it will try to mount all unmounted volumes with info.ignore=3Dfalse as long as that "Mount removable media when inserted" box is checked. I think there needs to be a separate property that explicitly lets one disable the auto-mounting of fixed media. Joe >=20 > Thanks, >=20 > Volker >=20 >=20 --=20 Joe Marcus Clarke FreeBSD GNOME Team :: gnome@FreeBSD.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome --=-bt32ftgbG8CENW1TEsPJ Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQBGJBasb2iPiv4Uz4cRAmTpAJ9TbSa900BFEDSC6zgFwMnNkyNPDwCeO1xq rCY3+m19UaLMK8gt4h9VpIs= =5vIi -----END PGP SIGNATURE----- --=-bt32ftgbG8CENW1TEsPJ--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1176770222.1579.32.camel>