ports/136435: gnome-keyring+hald prevents umount of usb drive without '-f'

bob frazier bobf at mrp3.com
Tue Jul 7 18:00:14 UTC 2009


>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 at 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:



More information about the freebsd-ports-bugs mailing list