From owner-freebsd-gnome@FreeBSD.ORG Tue Apr 17 00:10:55 2007 Return-Path: X-Original-To: freebsd-gnome@freebsd.org Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 605AF16A402; Tue, 17 Apr 2007 00:10:55 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from frontmail.ipactive.de (frontmail.maindns.de [85.214.95.103]) by mx1.freebsd.org (Postfix) with ESMTP id EB5EC13C483; Tue, 17 Apr 2007 00:10:54 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from mail.vtec.ipme.de (Q7c07.q.ppp-pool.de [89.53.124.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by frontmail.ipactive.de (Postfix) with ESMTP id B3D42128829; Tue, 17 Apr 2007 02:10:46 +0200 (CEST) Received: from [192.168.18.3] (unknown [192.168.18.3]) by mail.vtec.ipme.de (Postfix) with ESMTP id 410D73F4E8; Tue, 17 Apr 2007 02:10:23 +0200 (CEST) Message-ID: <46241076.8070107@vwsoft.com> Date: Tue, 17 Apr 2007 02:10:30 +0200 From: Volker User-Agent: Thunderbird 1.5.0.10 (X11/20070306) MIME-Version: 1.0 To: Joe Marcus Clarke References: <462356A9.2070604@vwsoft.com> <462371C9.7040903@freebsd.org> <46238457.8010202@vwsoft.com> <4623A6E1.2090504@freebsd.org> In-Reply-To: <4623A6E1.2090504@freebsd.org> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-VWSoft-MailScanner: Found to be clean X-MailScanner-From: volker@vwsoft.com X-ipactive-MailScanner-Information: Please contact the ISP for more information X-ipactive-MailScanner: Found to be clean X-ipactive-MailScanner-From: volker@vwsoft.com Cc: freebsd-gnome@freebsd.org Subject: Re: gnome-mount unmount problem X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Apr 2007 00:10:55 -0000 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 = 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=gid:operator but AFAIR this has been the only change. As there >>>> 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 restart >>> 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". > > gnome-volume-manager is responsible for mounting file systems. How many > instances or g-v-m are you running? Do you have any other scripts or > session instances that start gnome-mount? > > Joe > Joe, thank you for your time on this. %ps ax | grep vol 1265 ?? Ss 0:04.87 gnome-volume-manager --sm-disable There's just one instance running and it's started from gnome-session. How does g-v-m decide on which volumes to mount (automount) at gdm login? 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=' by default. On my troubled notebook system, I've had 'Allow=uid:__all__' in it. Setting this to 'Allow=' and rebooting the system, Gnome came up with no automounted volumes. 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. Thanks, Volker