After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 165727 - fully reproducible unmount lock with USB key (famd)
fully reproducible unmount lock with USB key (famd)
Status: RESOLVED DUPLICATE of bug 102760
Product: nautilus
Classification: Core
Component: Metadata
2.8.x
Other All
: Normal major
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-01-30 17:41 UTC by Christophe Combelles
Modified: 2005-01-30 20:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8



Description Christophe Combelles 2005-01-30 17:41:33 UTC
Please describe the problem:
The long standing problems with umount and famd are almost completely solved,

excepted just this small one :
(small but very irritating from a user point-of-view)


The following is fully reproducible :
with latest famd installed and running
- insert and mount an USB key
- open it with nautilus
- right-click on any file -> 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 media
famd      4195      ccomb   38r      DIR        8,1   16384          1
/media/I-Stick


This time the bug does not come from famd, but from the "NOTES" component of the
properties window. If you just delete the file libnautilus-notes-view.so, the
problem cannot be reproduced again.
Some object is not unreferenced, and there is probably just one line to add to
fix the bug. This would be nice to help because some distro use (or will use)
Gnome 2.6/2.8.

More info in 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=280311
http://qa.mandrakesoft.com/show_bug.cgi?id=12617


regards
Ch C.

Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Sebastien Bacher 2005-01-30 17:54:30 UTC
you have already added the same description in #102760, why opening a duplicate
now ? I'm closing this bug as a duplicate of #102760.

*** This bug has been marked as a duplicate of 102760 ***
Comment 2 Christophe Combelles 2005-01-30 18:24:08 UTC
sorry, but I sometimes feel that old bugs are sometimes sinking into oblivion.
#102760 is reported against nautilus 2.0, and it it is not a duplicate.
#102760 is a melting pot of many bugs found in fam and nautilus. This is not
good to have a multibug report. Every bug should be isolated and reported
separately, and since I could isolate this one a bit, I created a new report.
Why not creating a bug report saying "nautilus has problems", and then set all
other bugs as duplicate of this one ?
Comment 3 Sebastien Bacher 2005-01-30 20:41:18 UTC
there is around 900-1000 bugs on nautilus, open an extra bugs for an issue
already in bugzilla will no fix it faster. #102760 has been opened against
nautilus 2.0 but the version can be updated if the bug is still here, I've
updated it to 2.8. I agree than different issues should have different bug, but
you have send exactly the same comment in #102760. So either that's an another
issue and the comment in #102760 is not at the right place, either this bug is a
duplicate. If you are sure than #102760 as nothing to do with this issue feel
free to reopen this bug.