[kdepim-users] kde slow to start after a crash

[Walter Cazzola]

Hi,
thanks for having addressed me to akonadi and nepomuk, top was just
stating that X and init was the most cpu consuming processes but turning
off akonadi and nepomuk addressed me to the real problem, i.e., their
configuration files.

Walter

On Wed, 22 Feb 2012, Anders Lund wrote:

> Hi Walter,
>
> I wonder why you post to this exact list - do you a suspect kdepim application
> is responsible for your problems?
>
> In any case, I personally think my netbook is slow at starting a kde session,
> which includes starting the desktop and usually kmail, akregator, 1-4
> konqueror windows, konsole (yaquake), choqok and maybe some libreoffice
> instances and okular - that would take about 3 minutes maybe.
>
> I suggest that you log into a text console and runs top prior to starting kde,
> and then switch to the text console to monitor what is happening.
>
> I have experienced that nepomuk and/or akonadi sometimes have problems
> behaving during startup, especially if they were jammed at shutdown. Try
> restarting both from within your kde session once it runs. for akonadi, run
> "akonadictl restart" from the command prompt or a konsole window, for nepomuk,
> stop/start it using systemsettings.
>
> Possibly turn off file and/or email indexing if those are running (the latter is
> only relevant if you have mail resources defined for kmail), that is in the
> desktop search module in systemsettings as well.
>
> Anders
>
> Onsdag den 22. februar 2012 21:54:42 Walter Cazzola skrev:
>> Dear KDE Experts,
>> I've a quite frustrating problem, yesterday trying to send a file via
>> Skype this crashed and my linux-box became unresponsive.  After
>> rebooting KDE started really very slowly (it is taking more or less 20
>> minutes to be fully loaded and responsive) and this happens at every
>> reboot (and since this is a laptop it is quite frequent). And also once
>> started many applications (e.g., korganizer, klipper) are still
>> unresponsive and theirs menu take long time to appear.
>>
>> I got the same problem with the same causes one year ago and at that
>> time I have solved reinstalling all the whole system but at the time was
>> a quite new installation and it was inexpensive to do that but now I'd
>> prefer to avoid. I have already tried to remove the cache and lock files
>> but it didn't work.
>>
>> Any idea about how to solve the issue? If you address me I can provide
>> log files as well.
>>
>> My system is FC13 up to date with KDE 4.5.3, nvidia card and kernel
>> 2.6.34.7-63. I can provide any piece of log if you address me to what to
>> look for. I know it is quite old but it works for my needs and it took
>> so long to be fine tuned that I don't like the idea to start again.
>>
>> Thanks for the help
>>
>> Walter
> _______________________________________________
> KDE PIM users mailing list
> Subscription management: https://mail.kde.org/mailman/listinfo/kdepim-users
>

-- 
_______________________________________________
KDE PIM users mailing list
Subscription management: https://mail.kde.org/mailman/listinfo/kdepim-users