(*** This bug was imported into bugs.kde.org ***) Package: konqueror Version: KDE 3.0.0 Severity: normal Installed from: Compiled From Sources Compiler: g++ 2.95.4 OS: Linux OS/Compiler notes: Debian unstable Browsing my NFS mounted home directory using konqueror in "Select Wallpaper" mode causes kdeinit to use 95% of cpu and famd to use 82% on my dual CPU machine. I get messages like this repeated continuously in /home/acollins/.kde2-errors kio (KDirWatch): Processing FAM event (FAMChanged .kde2-errors Req 2) kio (KDirWatch): KDirWatch-1 emitting dirty /home/acollins/.kde2-errors Running strace on kdeinit gives me over and over again: lstat64("/home/acollins/.kde2-errors" {st_mode=S_IFREG|0600 st_size=43560056 ...}) = 0 write(2 "kio (KDirWatch): " 17) = 17 write(2 "Processing FAM event (FAMChanged"... 55) = 55 write(2 "kio (KDirWatch): " 17) = 17 write(2 "KDirWatch-1 emitting dirty /home"... 55) = 55 I cannot strace famd I get: attach: ptrace(PTRACE_ATTACH ...): Operation not permitted Or as root: --- SIGRTMIN (Real-time signal 0) --- I still have KDE2 installed on my machine but all paths point to KDE3. (Submitted via bugs.kde.org)
On Saturday 18 May 2002 05:37 am ashley.collins@mookie.eclipse.co.uk wrote: > Package: konqueror > Version: KDE 3.0.0 > Severity: normal > Installed from: Compiled From Sources > Compiler: g++ 2.95.4 > OS: Linux > OS/Compiler notes: Debian unstable > > Browsing my NFS mounted home directory using konqueror in "Select > Wallpaper" mode causes kdeinit to use 95% of cpu and famd to use 82% on my > dual CPU machine. > > I get messages like this repeated continuously in > /home/acollins/.kde2-errors That's a nasty loop. Since you log the KDE output to this file you will cha= nge=20 it and the change triggers a fam event which causes KDE output. Try to log to .xsession-errors or .X.err instead they are handled differen= tly=20 to take this problem into account. Cheers Waldo --=20 bastian@kde.org | SuSE Labs KDE Developer | bastian@suse.com
Seems to be a duplicate of #33721 but I think the assignee should decide about that.
*** This bug has been marked as a duplicate of 33721 ***