I’ did change from opensuse13.1 to leap 42.3 and so i migrated the very useful krusader from version 2.4 to 2.6.
All my settings were gone because of the configuration files have been migrated from ~/.kde/share/local and config to ~/.local and ~/.config
After six month of problems (with plasma and other software), i’m still unable to find how to disable the very annoying auto-refresh of the panel(s).
It’s refreshing the icon’s and the status bar about every second (depending how much cache settings and data is on the active panel)
The CTRL-R (reload, refresh panel) is still working (but not useful with this time interval of autorefresh)
I tried a lot of custom settings in krusader and krusaderrc but nothing is working…
I didn’t find something in the systemsetting nor kde.org or on the web …
So i need some help from you because i think it’s maybe a suse parameter.
Yes, the autoreload is always on, no matter watt i did to get rid off, but only with version 2.6 … i have to say that maybe most user do not have a problem with this autoreload of the panel.
~/.config/krusaderrc newly created (fresh start) has “AutoResizeColumns=true” but that’s unfortunately not the problem
I spend a lot of time (night’s) to do some comparison with another OS under gnome and krusader 2.5
The auto reload, seems to me is executed each time an access to the directory from the active panel is done, not necessarily a writing.
So i have to add that i use leap 42.3 with plasma5 on an SSD and that my home directory was not formatted at the new installation of Leap 42.3 !
i tested with: Krusader has “Show the icones for the filenames and folders” on
I wiped every entrance in the fstab for the ssd.
I reactivated “.xsession-errors-:0”. (before all logs were send to /dev/null)
I find out that baloo does a lot of the file accessing.
I stopped baloo with “balooctl disable”
After that, i had a lot of “KConfigIni” writing in “.xsession-errors-:0”, this file was now grooving very fast
I deleted all the files that made this errors (mainly “desktop files” from previous kde).
Then i had “libkomparediff” errors every seconds …
After killing some process, i found out that my SIP application is creating a lot of entries in the “.xsession-errors-:0”
Woaw now the auto reload in the krusader panel is activated after every access in the directory but not every seconds any-more…
Is this not really crazy especially that baloo has blocked some logs ?
My preferred sip application is not plasma5 clean/compatible, very sad !
I think it’s a Plasma5 problem in relation with kde4/3 and or gnome applications that make a lot of file-system accessing (gnome desktop hasn’t this behaviour) anyway, the access are only in the cache (RAM) not on the SSD.
So my question is still not answered but has nothing to do with Suse.
Is the auto reload in 2.6 dbus triggered or systemd5 related ? is there anyway to change this behaviour for example in a plasma5 parameter’s ? maybe I shall take some time to look at the source code…
In the interval i may live with auto refresh enabled !
Hello, well it could bee but no, if a change my fstab it doesn’t change de behaviour if a file is writen.
if a file is accessed, the refresh is not done with noatime.
So i found out that my SIP programme is updating every second the config file (very stupid).
Thanks anyway, i will change the SIP program and live with auto refresh on.