Bugzilla – Bug 130197
konqueror filemanager mode suse 10.0 / kde 3.5beta2
Last modified: 2005-10-26 11:27:42 UTC
Konqueror in filemanager mode takes a lot of cpu in kde 3.5beta2 Ok, i'll know it's beta, so yes, there are some bugs, so i'll report them to fix it ;) 1) clean install, retail suse 10.0, added oss10 as install source 2) download the kde3.5 unstable, did a createrepo 3) add it as source via y2pmsh, newer, upgrade, commit 4) there was a dependency: libqscintilla.so.6, fixed it with supplementary/KDE/update_for_10.0/applications/qscintilla-1.65-3.i586.rpm 5) mv the .kde directory to a backup
Created attachment 55164 [details] strace I'm not sure that this is the right way to debug something like this
after looking again into it: the trace above was with konqueror --profile filemanagement and i was not looking into the cpu load at that moment, but after submitting the log, i'll see that the cpu load was ok. So i go into the properties of the home button, and see there another command: kfmclient openProfile filemanagement and this gives a lot of cpuload...
how can i create a strace of this command: when the process is detached from the terminal, it's not possible to get output... if i try to attach the process (-p) konqueror crashed
one step further: if i do konqueror --profile filemanagement from: - konsole or xterm: no problem - not able to run it from alt + f2, but did it via a little shellscript, no problem - run it from kde panel: lot of cpu usage - run it from desktop: lot of cpu usage
seems to be fixed by kdelibs3-3.4.92-7
Closing as fixed with that kdelibs update. :-)