Symtom: After mounting a CD-rom (or any device) in KDE-3.1-RC2 it can not be unmounted if "any" window of konqueror is open (webbrowser or filemanager.) It may be necessary to enter a directory on the CD (and then leaving it again) after mounting the CD to invoke the problem. On;y after closing every window of konq, a cdrom can be unmounted. Resolution: For KDE3.1-RC2 in the kdelibs ebuild change the entry --enable-dnotify to --disable-notify Ofcourse you will lose the (whatever) benefit of dnotify ?!? I emerged kdelibs 3.1 rc3 as well, but with --disable-dnotify in the ebuild straight away, so I don't know wether the problem would occur there too. I suspect though. I also noticed these entries in the kde3.1 final ebuild in portage and they might cause trouble there too... A discussion on the is here: http://forums.gentoo.org/viewtopic.php?p=130569#130569
We let kde use FAM anyway, and our fam comes aptched to support dnotify (in addition to imon). So we can disable kdelibs' direct dnotify suport (which might even be conflicting with fam?) - but we'd have to count on users starting the fam daemon (/etc/init.d/fam). I'll make a test build to see if that fixes this, and so on...
Actually, kde uses FAM if the server is running, falls back to dnotify if it isn't, and falls back to polling if dnotify isn't supportd by the kernel (fex. on linux 2.2). So if you have fam running, disabling dnotify should have no effect. If you don't have fam running, disabling dnotify will make kde use polling - cpu-intensive, but always works. Do you have fam running? If not, try enabling it, I suppose. If you do, try disabling it (and using dnotify). I've reproduced this bug (the unmounting part) and it's present here _only_ when fam is used, not when dnotify is used! Wierd... AFAICS, using fam is only better than direct dnotify if you have IMon in your kernel. Can't remember if we do or not, I don't seem to...
I can't use fam, because after a random period is will go for 100% CPU usage. A problem that I always had as long as I use gentoo on different hardware too. Fam also locks the unmounting of CD-roms like dnotify does. Is there no way to tell those two systems (fam and dnotify) to leave the cdroms alone? It is simply not usable like this.
With both fam and dnotify turned off, kde will fallback to polling, which is slow, cpu-intensive, and on network ioslaves generates extra traffic too. Not nice. Of course, in the case of linux 2.4, fam uses dnotify internally anyway (unless we have IMon kernel patch, which we probably don't). So this sounds like some dnotify i.e. kernel bug?...
Correction: fam prefers dnotify over imon. So we get dnotify no matter what.
Well these really are fam problems not kde ones... According to Azarah, the 99% cpu usage problem is due to a bg in glibc. It is fixed in the current glibc cvs and so glibc 2.3.2 will be ok; he's looking (?) at adding the fix to our glibc 2.3.1. See bug #14420 for further info. The locking problem is possibly fam one too; can someone please check if it's still present in kde 3.1 final?
This seems to be fixed in kde cvs head. Haven't checked 3.1-final yet. Anyone else?
Fixed at least in 3.1.1a, just checked.
Just emerged entire rc4 system incl. kde 3.1.1a and the problem persists! I have not modified the kdelibs ebuild, so dnotify an libfam support are both enabled. When a cd is mounted and I browse some dirs, I can not unmount it wihout closing every single konqueror window. Fam is NOT used in this scenario.... I will try with fam also...
UPDATE: I now enabled fam and yes it works ok then!! I am using gentoo 2.4.20-r2 kernel and I have imon enabled as a module I also made a symlink from /usr/src/linux/include/linux/imon.h to /usr/include/linux/imon.h to enable imon support for fam. (otherwise it well tell you "imon.h" is not available during configure. and it will not be used.) So this means that it still does not work properly without making some manual modifications.
UPDATE2: I now confirm that also without imon support for FAM as I descibed before, I am able to unmount my CD-roms when fam is enabled. SO as long as fam is enabled, (that is still a manual modification) everything seems fine. When I disable FAM it breaks again.
Well, I have 2 freshly compiled kde systems here, one with dnotify enabled and one with dnotify disabled for kdelibs. Only when both dnotify AND /etc/init.d/fam are disabled, I can unmount my cdroms whenever I want.... Otherwise they are locked. This is in KDE 3.1.2, but also KDE CVS.. I checked bugs.kde.org and this seems to be something that is bugging a LOT of people. It is not specifically gentoo related. Nevertheless, the last mandrake and redhat I installed did both NOT have this problem. Funny thing is that in some rare cases this problem does not occur. An old gentoo 1.2 w kde 3.0.2, works fine with fam enabled. I'm really puzzled, not a programmer, and therefore not someone likely to be able to fix this myself :(
Could you post the kde bug # here so we can track it?
http://bugs.kde.org/show_bug.cgi?id=37780
according to http://bugs.kde.org/show_bug.cgi?id=37780, it's fixed
fixed upstream.
