Bug#280311: [Fwd: [Bug 12617] [nautilus] UNCONFIRMED: fully reproducible umount lock with USB key (famd)]

Christophe Combelles ccomb@free.fr, 280311@bugs.debian.org
Thu, 09 Dec 2004 16:08:47 +0100


This is a multi-part message in MIME format.
--------------010006020902020105030902
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


--------------010006020902020105030902
Content-Type: message/rfc822;
 name="[Bug 12617] [nautilus] UNCONFIRMED: fully reproducible umount lock with USBkey (famd)"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="[Bug 12617] [nautilus] UNCONFIRMED: fully reproducible umount lock with USBkey (famd)"

Return-Path: <apache@qa.mandrakesoft.com>
Received: from qa.mandrakesoft.com (ezoffice.mandrakesoft.com [212.11.15.34])
	by pm-mx3.mx.noos.fr (Postfix) with ESMTP id 52BA1269AB
	for <ccomb@noos.fr>; Thu,  9 Dec 2004 15:02:33 +0100 (MET)
Received: by qa.mandrakesoft.com (Postfix, from userid 48)
	id CAC4967CC4; Thu,  9 Dec 2004 15:02:23 +0100 (CET)
From: [fcrozat] <bugzilla@qa.linux-mandrake.com>
To: ccomb@noos.fr
X-loop: qa@qa.linux-mandrake.com
Bug-id: 12617
Reply-To: 12617@qa.linux-mandrake.com
Subject: [Bug 12617] [nautilus] UNCONFIRMED: fully reproducible umount lock with USB key (famd)
X-Bugzilla-Reason: Reporter 
Message-ID: <bug12617.20041209140223.733041@qa.linux-mandrake.com>
References: <bug12617.20041208114043.142690@qa.linux-mandrake.com>
Date: Thu,  9 Dec 2004 15:02:23 +0100 (CET)
X-Mmail: \Recent                                 
X-M-Uid: 171.1102600955

User ID: 76, 13 bugs reported (10 fixed, 0 duplicate, 0 invalid), 1493 comments.

http://qa.mandrakesoft.com/show_bug.cgi?id=12617





------- Additional Comments From fcrozat@mandrakesoft.com  2004-12-09 15:02 -------
Bug in no longer visible when using gamin.

Bug is still present with nautilus 2.8.x when using fam.

It is caused by note property page which isn't unref correctly (it is a bonobo
object) when property dialog is closed. 

Problem is no longer present with nautilus >= 2.9.1 because bonobo is no longer
used inside nautilus.

I haven't find a way to fix this, and I'm afraid we'll have to wait until GNOME
2.10 is out to get this fixed properly.

-- 
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.


------- Reminder: -------
assigned_to: fcrozat@mandrakesoft.com
status: UNCONFIRMED
distribution: 10.1-official
creation_date: 
description: 
On a fresh 10.1 official installation, with Gnome as default desktop.
The following is fully reproducible :

- insert and mount an USB key
- open it with nautilus
- right-click on any file or directory -> click on "properties"
- close the properties windows
- close the nautilus window
- try to unmount -> impossible

famd still has an open file on the file whose properties have been shown
#  lsof|grep removable
famd      4635      ccomb   162r      DIR        8,1   10240          1228
/mnt/removable/some_dir

The procedure is very simple and since everyone owns an USB key nowadays,
everyone will encounter this problem. So this is critical for a Desktop oriented
distribution.

Here is the equivalent in Gnome DB:
http://bugzilla.gnome.org/show_bug.cgi?id=102760

Here is the Debian's equivalent :
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=280311
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=234787

Here is similar reports in Redhat's:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=131770
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=123677
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=122764

A similar report in FAM's:
http://oss.sgi.com/archives/fam/2004-02/msg00000.html

All this reports mention the same kind of bugs, but this is a multiple bug.
Maybe some of them are resolved, but this one's not, and it is probably in
nautilus or libgnomevfs.
The simple procedure I told is the only one I found to be 100% reproducible on
both mdk10.1 and Sarge/Sid.

Upgrading to gnome 2.8 does not resolve the bug. It still appears in Sid's gnome
2.8.



--------------010006020902020105030902--