I use OpenSuSE 12.3 64 bits and all the latest updates made on the machine.
Every single time I boot my install shows that after some minutes in the desktop kio_file shows on the system monitor with a very high CPU usage.
I sadly can not reproduce the bug/feature because I have no idea When the problem starts … and the hugely filed workspace has about 10 app’s running … multiple browsers and windows on at the same time also .
I wonder if anyone has the same problem?
Also I have seen this Thread in KDe but the version OS12.3 uses should have the problem fixed …
IMO you might closely inspect your bootup sequence to see where/when disk activity is initiated, to read the system log immediately after boot, you can use tail, eg
tail -n 1200 /var/log/messages
But,
Before looking further I’d recommend observing how your system boots without a cluttered workspace. Maybe you just have limited resources (particularly RAM which would cause swapping which would show up both as high disk and CPU usage). Rather than creating a new workspace for your current User, probably simpler is to just create a new User and boot to it.
You can also use the “free” tool and top to inspect resource availability and running processes. I wrote a “how to” for free you might want to look at User:Tsu2/free tool - openSUSE
It’s not on boot … it depends on a application running on the system … actually it could not be on boot otherwise it would not be kio_file that is KDE dependent.
And since yesterday I suspect that the application is Konqueror … I was maybe lucky and had crash on konqueror and decide to remake the files opened again and checked! bang kio_file boosted cpu usage!
Then went to the command prompt and:
Konqueror some how does not handle some system API correctly … I also have an Old /home because I migrated the PC to the latest 12.3 leaving the same old /home partition … hence this could be a problem of the setup and init params left behind.
Konqueror version 4.10.5 (same as KDE) does give the following error:
"/org/freedesktop/UDisks2/drives/PIONEER_DVD_RW__DVR_105_CBDL112252WL" : property "Drive" does not exist
"/org/freedesktop/UDisks2/drives/WDC_WD10EACS_00D6B0_WD_WCAU42527953" : property "Drive" does not exist
"/org/freedesktop/UDisks2/drives/HDS725050KLA360_KRVN65ZAGYDM9F" : property "Drive" does not exist
"/org/freedesktop/UDisks2/drives/Floppy_Drive" : property "Drive" does not exist
"/org/freedesktop/UDisks2/drives/WDC_WD10EACS_00D6B0_WD_WCAU42634527" : property "Drive" does not exist
"/org/freedesktop/UDisks2/block_devices/dm_2d1" : property "MountPoints" does not exist
"/org/freedesktop/UDisks2/block_devices/dm_2d0" : property "Name" does not exist
"/" : property "DeviceNumber" does not exist
"/" : property "Device" does not exist
"/" : property "MediaCompatibility" does not exist
"/" : property "MediaRemovable" does not exist
"/" : property "Removable" does not exist
"/" : property "ConnectionBus" does not exist
"/org/freedesktop/UDisks2/drives/WDC_WD10EACS_00D6B0_WD_WCAU42634527" : property "DeviceNumber" does not exist
"/org/freedesktop/UDisks2/drives/WDC_WD10EACS_00D6B0_WD_WCAU42634527" : property "Device" does not exist
"/org/freedesktop/UDisks2/drives/HDS725050KLA360_KRVN65ZAGYDM9F" : property "DeviceNumber" does not exist
"/org/freedesktop/UDisks2/drives/HDS725050KLA360_KRVN65ZAGYDM9F" : property "Device" does not exist
"/org/freedesktop/UDisks2/block_devices/dm_2d2" : property "Name" does not exist
"/org/freedesktop/UDisks2/drives/WDC_WD10EACS_00D6B0_WD_WCAU42527953" : property "DeviceNumber" does not exist
"/org/freedesktop/UDisks2/drives/WDC_WD10EACS_00D6B0_WD_WCAU42527953" : property "Device" does not exist
"/org/freedesktop/UDisks2/block_devices/fd0" : property "Name" does not exist
"/org/freedesktop/UDisks2/drives/Floppy_Drive" : property "DeviceNumber" does not exist
"/org/freedesktop/UDisks2/drives/Floppy_Drive" : property "Device" does not exist
konqueror(4606) KSambaSharePrivate::testparmParamValue: We got some errors while running testparm "Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
ERROR: pid directory /var/run/samba does not exist
"
Maybe you just have limited resources (particularly RAM which would cause swapping which would show up both as high disk and CPU usage). Rather than creating a new workspace for your current User, probably simpler is to just create a new User and boot to it.
(Also the PC it’s a bit old no doubt but it’s a quad core, actually it’s a fake Quad core , I would call it a Dual Dual Core … intel 9550 it’s not lack of resources … 2TB hdd and 12GB Ram …)