I failed to mention, that all other programs were running normally and
there was hardly any CPU load in the system, while DT's UI was unresponsive.
The most useless is: "it's quite fast for me" But it is. No problem here.
I already assumed that it was no general problem of DT ;-)
1. Reboot
2. Do nothing for at least 20 minutes (huge time but you most likely
have something running in the background that hogs the computer)
I did this, only started DT to trigger any processes it might start and
instead of 20 minutes I let it run over night.
Now it works just fine.
3. run: systemd-analyze blame
Didn't know that command, but it does look really interesting - thanks
for showing it to me :-)
I wouldn't be surprised if you had the updatedb and the
updatedb.timer process running.
I don't see any updatedb processes in the list, but the top time
consumer is man-db.service now with over 17 seconds - maybe this was the
culprit.
The only thing I don't understand is, why this number should be relevant
for my problem.
From "systemd-analyze --help":
blame Print list of running units ordered by time to init
Why is time to init relevant here?
But this is only to understand what's happening.
The most important fact is that you pointed me in the right direction
and my DT is running smoothly now!
Thank you very much!
Rico
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to [email protected]
