Re: konqueror heavy swapping +kicker and log-in errors
Kevin Krammer wrote:
> What process uses most memory according to top?
>
This is the normal condition, cut from the 'top' command
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ SWAP COMMAND
5997 pol 15 0 91408 31m 11m S 0.0 4.2 0:53.22 57m konqueror
6032 pol 15 0 76712 24m 11m S 4.3 3.3 6:20.76 50m konqueror
6043 pol 15 0 93880 41m 14m S 0.0 5.5 1:11.19 50m konqueror
I will try to get the the snapshop as freezing will occur
I am using a laptop centrino 1.5GHz, with 756MB RAM and 1G swap space
(made of 0.5G swap partition and 0.5G swap file)
The operating system is debian/testing
I am taking this opprtunity to ask help for another kde-related problem:
The kicker freezes sometimes, at the opening of the user session, so
that it has to be restarted by the command
dcop kicker kicker restart
I cannot figure out the reason for the kicker freezing out, since
nothing is tracked in the .xsession-errors log file regarding kicker.
How to force the kicker to run more verbosely?
Anyway, many errors are recorded in the.xsession-errors file:
kcminit: ERROR: Access denied to driver shared memory
libhal.c 911 : Error sending msg: No property info.category on device
with id /org/freedes
ktop/Hal/devices/ide_0_0
kio (KIOConnection): ERROR: Header read failed, errno=104
kio (KIOConnection): ERROR: Header has invalid size (-1)
kio (KLauncher): ERROR: SlavePool: No communication with slave.
kio (KIOConnection): ERROR: Header read failed, errno=104
kio (KIOConnection): ERROR: Header has invalid size (-1)
...
kio (KIOConnection): ERROR: Header read failed, errno=104
kio (KIOConnection): ERROR: Header has invalid size (-1)
kio (KLauncher): ERROR: SlavePool: No communication with slave.
....
QPainter::begin: Painter is already active.
You must end() the painter before a second begin()
QPainter::begin: Painter is already active.
You must end() the painter before a second begin()
Any help?
thank you
--pol
Reply to: