Bug 130197

Summary:	konqueror filemanager mode suse 10.0 / kde 3.5beta2
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Frederik Vos <frederik.vos>
Component:	KDE	Assignee:	E-mail List <kde-maintainers>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	i686
OS:	SuSE Linux 10.0
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	strace

Description Frederik Vos 2005-10-23 13:52:24 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

Comment 1 Frederik Vos 2005-10-23 13:55:29 UTC

Created attachment 55164 [details]
strace 

I'm not sure that this is the right way to debug something like this

Comment 2 Frederik Vos 2005-10-23 14:01:03 UTC

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...

Comment 3 Frederik Vos 2005-10-23 14:11:55 UTC

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

Comment 4 Frederik Vos 2005-10-23 14:21:28 UTC

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

Comment 5 Frederik Vos 2005-10-26 08:51:00 UTC

seems to be fixed by kdelibs3-3.4.92-7

Comment 6 Stephan Binner 2005-10-26 11:27:42 UTC

Closing as fixed with that kdelibs update. :-)