From owner-freebsd-ports-bugs@FreeBSD.ORG Tue Jul 7 18:00:13 2009 Return-Path: Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CABB61065691 for ; Tue, 7 Jul 2009 18:00:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A08828FC25 for ; Tue, 7 Jul 2009 18:00:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n67I0DGx024173 for ; Tue, 7 Jul 2009 18:00:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n67I0DF0024172; Tue, 7 Jul 2009 18:00:13 GMT (envelope-from gnats) Resent-Date: Tue, 7 Jul 2009 18:00:13 GMT Resent-Message-Id: <200907071800.n67I0DF0024172@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-ports-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, bob frazier Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD4211065673 for ; Tue, 7 Jul 2009 17:56:38 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id BB6548FC18 for ; Tue, 7 Jul 2009 17:56:38 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id n67Huc9w074670 for ; Tue, 7 Jul 2009 17:56:38 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id n67Huc4w074669; Tue, 7 Jul 2009 17:56:38 GMT (envelope-from nobody) Message-Id: <200907071756.n67Huc4w074669@www.freebsd.org> Date: Tue, 7 Jul 2009 17:56:38 GMT From: bob frazier To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: ports/136435: gnome-keyring+hald prevents umount of usb drive without '-f' X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jul 2009 18:00:14 -0000 >Number: 136435 >Category: ports >Synopsis: gnome-keyring+hald prevents umount of usb drive without '-f' >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jul 07 18:00:13 UTC 2009 >Closed-Date: >Last-Modified: >Originator: bob frazier >Release: 7.2 'STABLE', ports RELEASE_7_2_0 >Organization: SFT Inc. >Environment: FreeBSD BSDSilver.SFT.local 7.2-STABLE FreeBSD 7.2-STABLE #1: Tue Jun 30 21:02:37 PDT 2009 root@BSDSilver.SFT.local:/usr/obj/usr/src/sys/GENERIC amd64 >Description: after performing a 'mount' on an external USB drive, gnome-keyring apparently uses hald to obtain key information for a drive. Unfortunately this process then causes "device busy" messages when you attempt to unmount it. gnome-keyring was compiled with 'HALD' support enabled (I am rectifying this 'problem' at this time). The workaround is to use the '-f' flag when unmounting the drive, taking care that nothing "truly important" is actually trying to access the drive before unmounting. OS version: 7-STABLE ports tree: RELEASE_7_2_0 >How-To-Repeat: a) install gnome-keyring (as part of gnome) with the HALD feature compiled in b) mount an external USB drive from a command line while the gnome desktop is running [in this case, using a FAT32 file system] c) subsequently unmount the same device. Note the error message, similar to "umount: unmount of /ramstick failed: Device busy". d) re-attempt the unmount, this time with the '-f' flag to force unmount e) note entries in /var/log/messages implicating gnome-keyring as the culprit >Fix: at this time I'm removing the HALD support from gnome-keyring and will add a supplement to this bug report if this does NOT rectify the problem. It appears that the default setting is to have HALD support enabled. >Release-Note: >Audit-Trail: >Unformatted: