unmount problems

James Richard Tyrer tyrerj at acm.org
Thu Apr 21 00:04:37 CEST 2005


Carlos Leonhard Woelz wrote:
> Off the list, as it is off topic for the quality list. The quality list
> is about the quality teams, not about QA. Sorry about the confusing
> name, I know.
> 
> On Wed, 20 Apr 2005 18:24:36 +0200, "Andreas Baer" <andreas_baer at gmx.de>
> said:
> 
>>Hi @all,
>>
>>Sorry for my little disturbance, but I've discovered a bad behavior in
>>KDE (at least for my own usability).
>>I have sometimes problems to unmount disks or directories, which are
>>only mounted for a little time period and I want to umount shortly
>>after using them through KDE. In the most cases I then get back a simple
>>"device is busy" message box, which would be ok if there is a important
>>process that has still access to the mounted source, but after a quick
>>"ps ax | grep ..." I mostly see lines similar to this:
>>
>>"konqueror [kdeinit] konqueror -mimetype inode/directory file:/mnt/sc"
>>or something with "kdeinit and kio_file".
>>
>>After killing all such processes the manual way I can umount my source
>>as usual without problems.
>>
>>My questions are now:
>>
>>- Does anyone know a good solution for that problem?
> 
> 
> Are you using Mandrake? Are you using FAM? There is a FAM bug that has
> these characteristics, AFAIK.
>  
> 
>>- Is there a way to either disable or to minimize the creation of such
>>processes in KDE?
> 
> 
> Try not to have Konqueror preloaded (it is on the bottom option of the
> konqueror config).
> 
> 
>>- Can anyone give me a more detailed explanation what's the reason for
>>their existence?
> 
> 
> A FAM bug (FAM is used by KDirWatch), or an instance of Konqueror loaded
> in the background. But this is based on other reports, I have no special
> knowledge of this code.

I have tried to manage this bug so I will discuss it:

http://bugs.kde.org/show_bug.cgi?id=37780

This has been a very perplexing bug.  If others could help out with it, 
it would be appreciated.

I have KDE 3.4 installed with --enable-dnotify.
I have FAM-2.7.0 with the dnotify patch that I got from Linux From Scratch.
I do not have any automounter installed.

I currently have no problem with the computer refusing to give me my CDs 
and I did in the past.  So, I closed the bug as Works For Me since I was 
unable to reproduce the problem anymore (with the [then] current 
version).  I suspect that the problem may have something to do with 
using an automounter.

Various people made significant changes to KDE 3.4.0 to try to fix the 
problem since they did find issues in the code.

So, the bottom line is, if anyone that is using 3.4.0 is still having 
problems, we can reopen the bug.  I do ask that you provide as much 
information as you can including specific instructions on how to 
reproduce the problem.

-- 
JRT


More information about the kde-quality mailing list