Hi,
I just migrated my workstation running CentOS 7 from KDE to MATE.
It looks like I'm having the same problem with the Caja file manager than with Dolphin. Folder contents don't get refreshed automatically, and I have to hit F5.
For example, when I download a file (say, a compressed archive) from the Internet, I have to hit F5 to see the file in Caja. And when I extract the archive, I have to hit F5 again.
Anybody knows where this nagging problem comes from?
Cheers,
Niki
On Mon, Jul 09, 2018 at 02:30:17PM +0200, Nicolas Kovacs wrote:
Hi,
I just migrated my workstation running CentOS 7 from KDE to MATE.
It looks like I'm having the same problem with the Caja file manager than with Dolphin. Folder contents don't get refreshed automatically, and I have to hit F5.
For example, when I download a file (say, a compressed archive) from the Internet, I have to hit F5 to see the file in Caja. And when I extract the archive, I have to hit F5 again.
Anybody knows where this nagging problem comes from?
I've seen it too. sometimes it does get refreshed, and I have never pursued it to see what is going on.
If, for example, I have a folder full of files displayed in caja, then do a bulk rename from a terminal window in the same directory, it does refresh the filenames. Also, when copying a bunch of files from one place into the window, the files do appear in the caja window as they get copied.
Sorry, but I don't know what is different about those two activities versus what you describe
Fred
On 2018-07-09, Nicolas Kovacs info@microlinux.fr wrote:
Hi,
I just migrated my workstation running CentOS 7 from KDE to MATE.
It looks like I'm having the same problem with the Caja file manager than with Dolphin. Folder contents don't get refreshed automatically, and I have to hit F5.
For example, when I download a file (say, a compressed archive) from the Internet, I have to hit F5 to see the file in Caja. And when I extract the archive, I have to hit F5 again.
Anybody knows where this nagging problem comes from?
Cheers,
Niki
What do you see in /proc/sys/fs/inotify/max_user_watches? If you increase the value, does the problem persist?
Le 13/07/2018 à 21:57, Liam O'Toole a écrit :
What do you see in /proc/sys/fs/inotify/max_user_watches? If you increase the value, does the problem persist?
I investigated this, and indeed, it solved my problem.
I wrote a little blog article to summarize my findings and put you in the Thank You notes.
https://blog.microlinux.fr/inotify/
Cheers,
Niki
On 2018-07-20, Nicolas Kovacs info@microlinux.fr wrote:
Le 13/07/2018 à 21:57, Liam O'Toole a écrit :
What do you see in /proc/sys/fs/inotify/max_user_watches? If you increase the value, does the problem persist?
I investigated this, and indeed, it solved my problem.
I wrote a little blog article to summarize my findings and put you in the Thank You notes.
https://blog.microlinux.fr/inotify/
Cheers,
Niki
Je vous en prie. :)
-
Fred Smith -
Liam O'Toole -
Nicolas Kovacs