Bug 387663 - Dolphin doesn't update view (doesn't show new files) for local filesystem
Summary: Dolphin doesn't update view (doesn't show new files) for local filesystem
Status: CONFIRMED
Alias: None
Product: frameworks-kcoreaddons
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.83.0
Platform: Neon Linux
: HI major
Target Milestone: ---
Assignee: Michael Pyne
URL:
Keywords: usability
: 386838 425098 431927 437445 447894 452434 462737 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-12-07 12:30 UTC by jeremy9856
Modified: 2024-02-12 04:05 UTC (History)
49 users (show)

See Also:
Latest Commit:
Version Fixed In: KF 5.106


Attachments
Screencast showing folder view is not refreshed (687.09 KB, video/mp4)
2018-10-17 03:31 UTC, Mike Robinson
Details
The same folder 1) in Dolphin opened before creating new screenshot and 2) Dolphin opened after screenshot (104.11 KB, image/webp)
2022-01-09 06:50 UTC, soshial
Details
Video recording of the bug (2.58 MB, video/x-matroska)
2023-03-25 14:41 UTC, b2
Details
QT_LOGGING_RULES="kf5.kcoreaddons.kdirwatch.debug=true;kf.kio.core.dirlister.debug=true" dolphin (47.11 KB, text/plain)
2023-03-25 14:44 UTC, b2
Details
Showing Dolphin not updating (1.60 MB, video/mp4)
2023-05-15 08:20 UTC, Evert Vorster
Details
file not updating bug (1.47 MB, video/mp4)
2023-09-12 00:36 UTC, sramey40
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jeremy9856 2017-12-07 12:30:15 UTC
Hello,

I'm on Kubuntu 17.10 and Dolphin (17.04.3) often doesn't update the view and doesn't show new files even if you change directory.

If I open dolphin with this command : 

$ QT_LOGGING_RULES=kf5.kcoreaddons.kdirwatch.debug=true dolphin

there is some messages like that whereas my drive is far from full:

kf5.kcoreaddons.kdirwatch: inotify failed for monitoring 
inotify_add_watch("/media/Data/Downloads") failed: "No space left on device"

The bug is also reported against dolphin

https://bugs.kde.org/show_bug.cgi?id=386838

Thanks !
Comment 1 Martin Oemus 2017-12-21 11:36:55 UTC
I experience the same problem. I'm on Kubuntu 17.10, KDE-Plasma 5.11.4, Frameworks 5.40.0, Kernel 4.13.0, Dolphin 17.04.3.

When I start dolphin with logging like in the comment above, I also get messages like "inotify_add_watch("/etc/fstab") failed: "No space left on device"".

I have enough space left on my partitions:

$ df -h
Dateisystem    Größe Benutzt Verf. Verw% Eingehängt auf
udev            7,8G       0  7,8G    0% /dev
tmpfs           1,6G     26M  1,6G    2% /run
/dev/sdb5       216G     34G  171G   17% /
tmpfs           7,8G    137M  7,7G    2% /dev/shm
tmpfs           5,0M    4,0K  5,0M    1% /run/lock
tmpfs           7,8G       0  7,8G    0% /sys/fs/cgroup
/dev/loop0       84M     84M     0  100% /snap/core/3247
/dev/loop2       84M     84M     0  100% /snap/core/3440
/dev/sdb3        98G     74G   24G   76% /media/Windows
/dev/sdb1        96M     22M   75M   23% /boot/efi
/dev/sda1       466G    277G  190G   60% /media/Daten
tmpfs           1,6G    236M  1,4G   15% /run/user/1000
/dev/loop3       84M     84M     0  100% /snap/core/3604


I also made sure the number of allowed kernel inotify watches is not reached, as described here: https://unix.stackexchange.com/a/13757
Comment 2 Nate Graham 2018-01-30 14:41:35 UTC
*** Bug 386838 has been marked as a duplicate of this bug. ***
Comment 3 jeremy9856 2018-02-24 09:36:35 UTC
I don't use KDE for now because of this. I hope it can be fixed for Kubuntu 18.04. Thanks.
Comment 4 jeremy9856 2018-03-01 12:04:27 UTC
I should mention that of course Dolphin have to be kept open for the problem to occur. I mean the problem doesn't show up on Dolphin start.
Comment 5 jeremy9856 2018-03-10 20:15:11 UTC
I updated the number of allowed kernel inotify watches but that doesn't change anything.
Comment 6 jeremy9856 2018-03-25 08:57:18 UTC
It still happening frequently. Don't know if it's really kcoreaddons since I didn't had the message related to it when I tried again this command and use dolphin for a day and had the problem several times:

QT_LOGGING_RULES=kf5.kcoreaddons.kdirwatch.debug=true dolphin

Trying to convert empty KLocalizedString to QString.
qt.accessibility.core: Cannot create accessible child interface for object:  PlacesView(0x55cbd04d6790)  index:  6
QObject::connect: invalid null parameter
QObject::connect: invalid null parameter
QObject::connect: invalid null parameter
QObject::connect: invalid null parameter
QObject::connect: invalid null parameter
QObject::connect: invalid null parameter
kf5.kcoreaddons.kdirwatch: "KDirWatch-2" stopped scanning "/home/jeremy/Téléchargements/Nouveau Dossier" (now 1 watchers)
kf5.kcoreaddons.kdirwatch: "KDirWatch-2" stopped scanning "/home/jeremy/Téléchargements/Nouveau Dossier" (now 1 watchers)
No text-to-speech plug-ins were found.
No text-to-speech plug-ins were found.
QObject::connect: invalid null parameter
QObject::connect: invalid null parameter
QObject::connect: invalid null parameter
QObject::connect: invalid null parameter
QObject::connect: invalid null parameter
QObject::connect: invalid null parameter
QObject::connect: invalid null parameter
QObject::connect: invalid null parameter
QObject::connect: invalid null parameter
Comment 7 jeremy9856 2018-03-30 13:23:55 UTC
Could it be related to tlp since it apply some powersave settings to hdd/ssd and other part of the system ? I tried to disable it and I didn't had the problem for 2 or 3 days. I re-enabled it and I had the problem once. I'm trying different tlp settings but it's not clear if tlp has anything to do with it.
Comment 8 jeremy9856 2018-03-31 09:12:23 UTC
It's not related to tlp. I disabled it today and it happened... Nautilus was open on the same folder at the same time at it showed the files.
Comment 9 jeremy9856 2018-03-31 09:52:34 UTC
Well I managed to somewhat make it reproducible, at least on my computer :

1. open Dolphin
2. press Ctrl+3 - switch do details view mode (this step isn't needed on my production profile, so probably also other view setting triggering this bug)
3. press F4
4. mkdir abc - create folder "abc"
5. rmdir abc - delete folder "abc" - files view area isn't updated

I saw it here : https://forum.kde.org/viewtopic.php?f=224&t=98940&start=60#p260138

You may need to do mkdir / rmdir several time to trigger the problem. Note that it happen with directories and files. The "inotify failed for monitoring" message doesn't show up.
Comment 10 Christoph Feck 2018-03-31 11:16:26 UTC
Why did you reassign to 'kio'?

I cannot reproduce using the steps from comment #9.

    while true ; do mkdir abc ; sleep 1 ; rmdir abc ; sleep 1 ; done

Ran for several minutes, but view always changed every second.

linux 4.14.9 x86_64
kcoreaddons 5.42
dolphin 17.12.1
Comment 11 jeremy9856 2018-03-31 11:40:03 UTC
I thought it was maybe somewhat related to this one

https://bugs.kde.org/show_bug.cgi?id=316016

I can't reproduce it too. I may be reproducible only when the problem occur first but what trigger it ??
Comment 12 jeremy9856 2018-03-31 11:54:48 UTC
I'm not sure but it seem to happen only (a lot more ?) when there is an accent in the path (eg. /home/jeremy/Téléchargements/Séries). In fact I'm not sure if it even happen outside a directory or parent directory that doesn't have an accent.
Comment 13 Nate Graham 2018-03-31 13:45:50 UTC
FYI, "kio" is obsolete, and the new current product for KIO is "frameworks-kio". Moving back until we can be sure it's KIO.
Comment 14 jeremy9856 2018-03-31 18:17:47 UTC
Forget the accent in the path, it happen without too...
Comment 15 jeremy9856 2018-03-31 19:26:03 UTC
I forgot to say that I have 2 partitions. /root where /home is and /media/Data. I symlink the home folders to /media/Data. It seem that Martin from comment 1 have a /media/Data too.
Comment 16 jeremy9856 2018-04-09 19:14:12 UTC
Well I removed the symlinks of the folders inside /home (Desktop, Downloads, etc...) that pointed to /media/Data and used kde settings (in applications) to change the places of these folders and I didn't had the problem for about a week !

So can it be related to the symlinks ?
Comment 17 Mike Robinson 2018-10-17 03:31:11 UTC
Created attachment 115697 [details]
Screencast showing folder view is not refreshed
Comment 18 Mike Robinson 2018-10-17 03:35:08 UTC
I am also having this problem with Kubuntu 18.04, see the above screencast. This seems to also affects sync programs, (e.g. Seafile), which are supposed to watch certain directories for changes and upload to the server any files that have been changed, however I need to manually tell it to rescan the directories.

I get a "No space left on device" error when running Dolphin:

$ dolphin 
kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "stash"
inotify_add_watch("/etc/fstab") failed: "No space left on device"
inotify_add_watch("/home/mike/.local/share/user-places.xbel") failed: "No space left on device"
inotify_add_watch("/home/mike") failed: "No space left on device"
qt.accessibility.core: Cannot create accessible child interface for object:  PlacesView(0x557fc372cf20)  index:  12
kf5.kio.core: KLocalSocket(0x557fc389e150) Jumbo packet of 132210 bytes
kf5.kio.core: KSambaShare: Could not find smb.conf!

However there is plenty of space left on all drives:

$ df -h
Filesystem                     Size  Used Avail Use% Mounted on
udev                           3.4G     0  3.4G   0% /dev
tmpfs                          691M  1.7M  690M   1% /run
/dev/mapper/mike--debian-root   42G  4.2G   36G  11% /
/dev/mapper/mike--debian-usr    30G  6.8G   22G  24% /usr
tmpfs                          3.4G  101M  3.3G   3% /dev/shm
tmpfs                          5.0M  4.0K  5.0M   1% /run/lock
tmpfs                          3.4G     0  3.4G   0% /sys/fs/cgroup
/dev/sda1                      730M  6.1M  724M   1% /boot/efi
/dev/mapper/mike--debian-tmp    42G   49M   40G   1% /tmp
/dev/mapper/mike--debian-home  504G  152G  327G  32% /home
/dev/mapper/mike--debian-var   133G  3.2G  123G   3% /var
tmpfs                          691M   16K  691M   1% /run/user/129
tmpfs                          691M   20K  691M   1% /run/user/1000
Comment 19 Patrick Silva 2018-11-17 21:35:56 UTC
I have just seen this bug on Arch Linux with Dolphin 18.12 beta.
"Picture" folder was open, I pressed meta+printscreen to take a screenshot of the active window. Dolphin did not show the screenshot until I pressed F5.

I can't reproduce such behavior all the time.
Comment 20 Patrick Silva 2018-11-17 22:19:32 UTC
(In reply to Patrick Silva from comment #19)
> I have just seen this bug on Arch Linux with Dolphin 18.12 beta.
> "Picture" folder was open, I pressed meta+printscreen to take a screenshot
> of the active window. Dolphin did not show the screenshot until I pressed F5.
> 
> I can't reproduce such behavior all the time.

I forgot to post:

Operating System: Arch Linux 
KDE Plasma Version: 5.14.3
Qt Version: 5.12.0 beta4
KDE Frameworks Version: 5.52.0
Kernel Version: 4.19.2-arch1-1-ARCH
Comment 21 Frederik Schwarzer 2018-12-10 22:58:55 UTC
Same her on Kubuntu 18.04.
I see it mostly when downloading email attachments from KMail into a folder already opened in a Dolphin window.
Comment 22 Martin Oemus 2018-12-12 22:16:03 UTC
(In reply to Martin Oemus from comment #1)
> I experience the same problem. I'm on Kubuntu 17.10, KDE-Plasma 5.11.4,
> Frameworks 5.40.0, Kernel 4.13.0, Dolphin 17.04.3.
> 
> When I start dolphin with logging like in the comment above, I also get
> messages like "inotify_add_watch("/etc/fstab") failed: "No space left on
> device"".
> 
> I have enough space left on my partitions:
> 
> $ df -h
> Dateisystem    Größe Benutzt Verf. Verw% Eingehängt auf
> udev            7,8G       0  7,8G    0% /dev
> tmpfs           1,6G     26M  1,6G    2% /run
> /dev/sdb5       216G     34G  171G   17% /
> tmpfs           7,8G    137M  7,7G    2% /dev/shm
> tmpfs           5,0M    4,0K  5,0M    1% /run/lock
> tmpfs           7,8G       0  7,8G    0% /sys/fs/cgroup
> /dev/loop0       84M     84M     0  100% /snap/core/3247
> /dev/loop2       84M     84M     0  100% /snap/core/3440
> /dev/sdb3        98G     74G   24G   76% /media/Windows
> /dev/sdb1        96M     22M   75M   23% /boot/efi
> /dev/sda1       466G    277G  190G   60% /media/Daten
> tmpfs           1,6G    236M  1,4G   15% /run/user/1000
> /dev/loop3       84M     84M     0  100% /snap/core/3604
> 
> 
> I also made sure the number of allowed kernel inotify watches is not
> reached, as described here: https://unix.stackexchange.com/a/13757

As the bug is still active I want to add some feedback: contrary to my first comment the solution presented at stackexchange in fact did solve the issue for me. 
I simply added fs.inotify.max_user_watches=524288 to /etc/sysctl.conf and rebooted.

I'm positive that it already worked a year ago (and I forgot to give timely feedback). Currently I'm running Kubuntu 18.04, KDE-Plasma 5.12.7, Frameworks 5.47.0, Kernel 4.15.0, Dolphin 17.12.3. With the work-around described, the bug does not affect me anymore.
Comment 23 Mike Robinson 2018-12-13 23:36:05 UTC
(In reply to Martin Oemus from comment #22)
> As the bug is still active I want to add some feedback: contrary to my first
> comment the solution presented at stackexchange in fact did solve the issue
> for me. 
> I simply added fs.inotify.max_user_watches=524288 to /etc/sysctl.conf and
> rebooted.
> 
> I'm positive that it already worked a year ago (and I forgot to give timely
> feedback). Currently I'm running Kubuntu 18.04, KDE-Plasma 5.12.7,
> Frameworks 5.47.0, Kernel 4.15.0, Dolphin 17.12.3. With the work-around
> described, the bug does not affect me anymore.

Confirmed this workaround worked for me.
Comment 24 Méven Car 2019-11-22 18:39:19 UTC
Git commit 8f1952ecb156a11289442a0ab02be073c5b98ce4 by Méven Car.
Committed on 22/11/2019 at 18:39.
Pushed by meven into branch 'master'.

Add a descriptive warning when inotify_add_watch returned ENOSPC

Summary: CCBUG: 387663

Reviewers: #frameworks, ngraham, apol

Reviewed By: ngraham, apol

Subscribers: kde-frameworks-devel

Tags: #frameworks

Differential Revision: https://phabricator.kde.org/D25460

M  +11   -2    src/lib/io/kdirwatch.cpp

https://commits.kde.org/kcoreaddons/8f1952ecb156a11289442a0ab02be073c5b98ce4
Comment 25 Alexander Kernozhitsky 2020-02-01 22:15:56 UTC
I also encountered this bug and tried some more advanced ways to get some info.

The best way to reproduce it was

    while true ; do mkdir abc ; sleep 1 ; rmdir abc ; sleep 1 ; done

the extra conditions are:
- Details mode
- Split View
- the directory is on the separate partition (also called /media/data :) )
- when it's reference by symlink

The conditions are not necessary, though; I saw it also on files and on non-symlinked directory.

Also I noted that it's possible to play with KDirWatch's preferred method using the environment variable, KDIRWATCH_METHOD. Of the four methods available (Fam, inotify, QFSWatch, Stat), I could reproduce the bug only on inotify.

Also I was trying to get some more advanced info to detect whether something is wrong with interpreting inotify's data. To do this, I set s_verboseDebug to true in kdirwatch.cpp.

I got the following in the log after creating/deleting directory "abc":
kf5.kcoreaddons.kdirwatch: path= "/media/data/Tasks/ptz2020/day4" sub_entry: 0x0
kf5.kcoreaddons.kdirwatch: path= "/media/data/Tasks/ptz2020/day2" sub_entry: 0x0
kf5.kcoreaddons.kdirwatch: path= "/media/data/Tasks/ptz2020/trial" sub_entry: 0x0
kf5.kcoreaddons.kdirwatch: path= "/media/data/Tasks/ptz2020/day1" sub_entry: 0x0
kf5.kcoreaddons.kdirwatch: path= "/media/data/Tasks/ptz2020/day3" sub_entry: 0x0
kf5.kcoreaddons.kdirwatch: Added Dir "/media/data/Tasks/ptz2020/abc" for "" ["KDirWatch-6"]
kf5.kcoreaddons.kdirwatch: inotify successfully used for monitoring "/media/data/Tasks/ptz2020/abc" wd= 82
kf5.kcoreaddons.kdirwatch: Added already watched Entry "/media/data/Tasks/ptz2020/abc" (now 2 clients) "[KDirWatch-4]"
kf5.kcoreaddons.kdirwatch: Added already watched Entry "/media/data/Tasks/ptz2020/day1" (now 2 clients) "[KDirWatch-4]"
kf5.kcoreaddons.kdirwatch: Added already watched Entry "/media/data/Tasks/ptz2020/day2" (now 2 clients) "[KDirWatch-4]"
kf5.kcoreaddons.kdirwatch: Added already watched Entry "/media/data/Tasks/ptz2020/day3" (now 2 clients) "[KDirWatch-4]"
kf5.kcoreaddons.kdirwatch: Added already watched Entry "/media/data/Tasks/ptz2020/day4" (now 2 clients) "[KDirWatch-4]"
kf5.kcoreaddons.kdirwatch: Added already watched Entry "/media/data/Tasks/ptz2020/trial" (now 2 clients) "[KDirWatch-4]"
kf5.kcoreaddons.kdirwatch: got event 0x400 for "/media/data/Tasks/ptz2020/abc"
kf5.kcoreaddons.kdirwatch: -->got deleteself signal for "/media/data/Tasks/ptz2020/abc"
kf5.kcoreaddons.kdirwatch: 4 "/media/data/Tasks/ptz2020/abc" 2 clients
kf5.kcoreaddons.kdirwatch: Added already watched Entry "/media/data/Tasks/ptz2020" (for "/media/data/Tasks/ptz2020/abc" )
kf5.kcoreaddons.kdirwatch: "KDirWatch-6" emitting deleted "/media/data/Tasks/ptz2020/abc"
kf5.kcoreaddons.kdirwatch: "KDirWatch-4" emitting deleted "/media/data/Tasks/ptz2020/abc"
kf5.kcoreaddons.kdirwatch: 
kf5.kcoreaddons.kdirwatch: scanEntry for "/home/gepardo/.local/share/user-places.xbel" says 0
kf5.kcoreaddons.kdirwatch: "/media/data/Tasks/ptz2020" e->m_ctime= 1580594624 01:03:44 stat_buf.st_ctime= 1580594669 stat_buf.st_mtime= 1580594669 e->m_nlink= 1 stat_buf.st_nlink= 1 e->m_ino= 437305 stat_buf.st_ino= 437305
kf5.kcoreaddons.kdirwatch: scanEntry for "/media/data/Tasks/ptz2020" says 1
kf5.kcoreaddons.kdirwatch: 1 "/media/data/Tasks/ptz2020" 1 clients
kf5.kcoreaddons.kdirwatch: scanEntry for "/media/data/Tasks/ptz2020/abc" says 0
kf5.kcoreaddons.kdirwatch: scanEntry for "/media/data/Tasks/ptz2020/day1" says 0
kf5.kcoreaddons.kdirwatch: scanEntry for "/media/data/Tasks/ptz2020/day2" says 0
kf5.kcoreaddons.kdirwatch: scanEntry for "/media/data/Tasks/ptz2020/day3" says 0
kf5.kcoreaddons.kdirwatch: scanEntry for "/media/data/Tasks/ptz2020/day4" says 0
kf5.kcoreaddons.kdirwatch: scanEntry for "/media/data/Tasks/ptz2020/trial" says 0
kf5.kcoreaddons.kdirwatch: path= "/media/data/Tasks/ptz2020/abc" sub_entry: 0x0
kf5.kcoreaddons.kdirwatch: path= "/media/data/Tasks/ptz2020/abc" sub_entry: 0x0
kf5.kcoreaddons.kdirwatch: path= "/media/data/Tasks/ptz2020" sub_entry: 0x5622d961b920
kf5.kcoreaddons.kdirwatch: Removed Dir "/media/data/Tasks/ptz2020/abc" for "" ["KDirWatch-4"]

During the next creation/deletion rounds, no log entries appeared.

I hope this information can be helpful while finding the bug, and I'll try to dig more of it.
Comment 26 Alexander Kernozhitsky 2020-02-02 18:25:47 UTC
Finally, after some hours of debugging and reading the logs I reached the reason of this bug. It's triggered when:
- KDirWatch uses inotify as a backend
- the watched directory contains a symlink as one of its parent. For example, /d is a symlink to /media/data, and our current directory in Dolphin is something like /d/1/2/3
- the directory is added and then removed:
  $ while true ; do mkdir abc ; sleep 1 ; rmdir abc ; sleep 1 ; done

The problem is that inotify_add_watch reuses the file descriptor if the directory is already watched. When the directory and the another path to it with a symlink (e. g. /d/1/2/3 and /media/data/1/2/3) are watched, inotify API still reuses the file descriptor. But KDirWatch intrinsically considers these path different, so uses different entries for them. The mapping between file descriptors and names is kept in QHash<int, Entry *> m_inotify_wd_to_entry, so the previous entry here is overwritten.

Moreover, when one of these path stops being watched, the file descriptor is freed and the map entry is removed, so the other path doesn't receive events.

I don't know how to fix this in a simple way (maybe use canonical paths inside KDirWatch?)

Also note that it's the only one scenario in which the file system updates are not delivered, there may be other ways to break it and the separate reasons why this happens. Any missing update in KDirWatch can be the reason.

As I stated in the previous message, KDirWatch can use other methods as default (FAM, inotify, QFSWatch and Stat). FAM seems to affect performance. Stat will poll the filesystem each 0.5 seconds, which is not the most efficient way. I don't know anything about QFSWatch and why it's not use as a default. Some comments in the code suggest that it lacks some functionality.

As I workaround, I set the environment variable:

KDIRWATCH_METHOD=QFSWatch
Comment 27 Alexander Kernozhitsky 2020-02-08 21:16:30 UTC
Oops, it seems that switching to QFSWatch doesn't fix this problem fully (I still need to refresh the view manually in my ~/Downloads folder)
Comment 28 Patrick Silva 2020-11-25 11:05:34 UTC
(In reply to Patrick Silva from comment #19)
> I have just seen this bug on Arch Linux with Dolphin 18.12 beta.
> "Picture" folder was open, I pressed meta+printscreen to take a screenshot
> of the active window. Dolphin did not show the screenshot until I pressed F5.

I have just seen this problem again, this time on neon unstable.
My Pictures folder was open, I took some screenshots by pressing printscreen then saving them via "Save as" button of Spectable.
Dolphin only shown the screenshots after I press F5.

Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.20.80
KDE Frameworks Version: 5.77.0
Qt Version: 5.15.1
Comment 29 Attila 2020-12-09 08:23:50 UTC
I see this issue also on Fedora 32 (Dolphin version 20.08.3).

Here my observations:

- It works on local folders. Dolphin updates the view immediately.
- It doesn't work on NFS shares. Dolphin doesn't update the view. I have to press F5 (sometimes more then once).

My questions are:
Are there any options in "fstab" how to mount NFS shares for immediately update?
Should I open a new bug report, because it works on local folders but not on NFS shares?
Comment 30 Michael Pyne 2021-02-25 02:42:20 UTC
NFS might be a different thing. But I have a merge request open for the potential inotify bug, at https://invent.kde.org/frameworks/kcoreaddons/-/merge_requests/81 if anyone who can reproduce the bug is able to take a look at testing.
Comment 31 Patrick Silva 2021-02-26 11:04:08 UTC
On my Arch Linux this problem became worse with recent versions of Dolphin,
it occurs often. For example, when I record my screen with SimpleScreenRecorder, take a screenshot with Spectacle or save a file with Opera internet browser while Dolphin is open, Dolphin does not show the new file until I refresh it manually by pressing F5.

Dolphin 20.12.2
Operating System: Arch Linux
KDE Plasma Version: 5.21.1
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
Comment 32 Attila 2021-02-26 14:39:30 UTC
Perhaps this is a bit different in my case.

1. I open Dolphin 2 times, navgiate to a directory which is served by NFS in both instances of Dolhin. After that I create a Directory in the first instance of Dolphin. The directory appears immidiately in the second instance of Dolphin. So far so good, it works for me.

2. I open Dolphin on computer A and navgiate to a directory which is served by NFS. After that I open Dolphin on computer B and navigate to the same directory. When I create a directory on computer B it doesn't come up on computer A except I press F5.

Just one more issue. When I change the Owner and/or Group of some files on a network folder than I don't see the changes in Dolphin. Even pressing F5 doesn't help in many times. I have to close and open Dolphin again.
Comment 33 Patrick Silva 2021-02-26 15:13:23 UTC
(In reply to Attila from comment #32)
> Just one more issue. When I change the Owner and/or Group of some files on a
> network folder than I don't see the changes in Dolphin. Even pressing F5
> doesn't help in many times. I have to close and open Dolphin again.

related bug reported as bug 416995
Comment 34 Patrick Silva 2021-04-14 13:31:42 UTC
This annoying problem persists on my Arch Linux and neon unstable.
It's not a exclusive Dolphin issue because Nautilus file manager running
on my Arch Linux + Gnome 40 is also affected.
Comment 35 Patrick Silva 2021-04-14 13:32:22 UTC
*** Bug 425098 has been marked as a duplicate of this bug. ***
Comment 36 Michał Zubkowicz 2021-04-16 19:27:04 UTC
Still not refreshing view even on newest KDE Neon.
Comment 37 Attila 2021-04-29 06:30:39 UTC
Can confirm on Fedora 33. It doesn't work.
Comment 38 soshial 2021-05-27 07:00:43 UTC
I can confirm it on my system:

Manjaro Linux
KDE Plasma Version: 5.21.5
KDE Frameworks Version: 5.82.0
Qt Version: 5.15.2
Kernel Version: 5.11.19-1-MANJARO
OS Type: 64-bit

I would bump bug's importance to HIGH, since people expect files to appear while they don't. This bug brings a lot of confusion to a new user, why files don't appear even hours after having been downloaded.
Comment 39 Michał Zubkowicz 2021-05-28 07:58:00 UTC
Worst case is when I'm extracting files, they doesn't show up. I'm experienced user and I've spent 5 minutes searching for files. How anybody can know that he needs to hit refresh button? 

This bug is 3 years old. It's hard to fix or nobody cares? If any help in debug is needed I can provide additional info.
Comment 40 Patrick Silva 2021-05-30 16:05:24 UTC
*** Bug 437445 has been marked as a duplicate of this bug. ***
Comment 41 Patrick Silva 2021-06-03 21:28:14 UTC
*** Bug 431927 has been marked as a duplicate of this bug. ***
Comment 42 klarnorbert 2021-08-13 13:23:56 UTC
Same problem, after fresh install of latest Manjaro. Filed downloaded by Chrome doesn't show up in Dolphin, only after restarting it.
Comment 43 Scott 2021-08-14 12:03:24 UTC
Also have this issue in Kubuntu 20.10 and 21.04.
Comment 44 Attila 2021-09-07 06:30:49 UTC
Hi,

can someone please take care of this bug. It has been reported more than 3 years ago and it is also confirmed.
When I navigate through the folders which are served by NFS, then I have to press F5 on every folder to see new files or directories. This is a really bad user experience, isn't it?
Comment 45 Yman252 2021-09-12 04:45:41 UTC
I've been experiencing this bug for a couple of weeks now as well. 
Mainly in my downloads folder on two different systems. I download a file and it doesn't show up in the downloads folder until i refresh the folder with F5.

Operating System: Manjaro Linux
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Kernel Version: 5.10.61-1-MANJARO (64-bit)
Graphics Platform: X11


Second System:
Operating System: Manjaro Linux
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Kernel Version: 5.10.61-1-MANJARO (64-bit)
Graphics Platform: X11
Comment 46 80p3fy75dc 2021-10-12 19:53:03 UTC
Same issue here on Arch and Gentoo on X11.

- KDE Plasma Version: 5.22.5
- KDE Frameworks Version: 5.87.0
- Qt Version: 5.15.2
Comment 47 Krešimir Čohar 2021-12-08 14:55:34 UTC
I can reproduce this issue on Plasma 5.23.4 on Arch. It takes Dolphin 60 seconds or so (I used a stopwatch) to refresh the contents of any folder I'm putting files into or taking files out of. Nautilus, on the other hand, picks up on things instantly.
Comment 48 Martin Oemus 2021-12-13 07:56:20 UTC
Did you try the workaround of increasing the number of your inotify watches? You can read here how to do that: https://unix.stackexchange.com/questions/13751/kernel-inotify-watch-limit-reached/13757#13757
Comment 49 Patrick Silva 2022-01-04 00:46:48 UTC
*** Bug 447894 has been marked as a duplicate of this bug. ***
Comment 50 soshial 2022-01-09 06:50:21 UTC
Created attachment 145256 [details]
The same folder 1) in Dolphin opened before creating new screenshot and 2) Dolphin opened after screenshot
Comment 51 Brooks Knight 2022-01-24 03:23:36 UTC
Looks like this issue is due to Dolphin not watching a directory, which can happen several ways, already loaded but inactive tabs or second Dolphin window. I did not see any errors in Dolphin.

To reproduce:
1. Open two Dolphin windows of the same folder,
2. Create a file in that folder with the terminal. One window will update and the other won't.
3. In the window that is not working, pressing F5 will have Dolphin correctly watch the folder again.

I already had higher inotify watches due to Insync.

fs.inotify.max_user_watches=1048576

Operating System: KDE neon 5.23
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.3
Kernel Version: 5.13.0-27-generic (64-bit)
Graphics Platform: X11
Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz
Memory: 31.1 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2
Comment 52 Patrick Silva 2022-05-06 14:14:27 UTC
(In reply to Michał Zubkowicz from comment #39)
> Worst case is when I'm extracting files, they doesn't show up. I'm
> experienced user and I've spent 5 minutes searching for files. How anybody
> can know that he needs to hit refresh button? 

It happened with Dolphin 22.04 on my Arch Linux a few days ago. Dolphin did not show files extracted with Ark via context menu until I refreshed the files view manually by pressing F5.

Operating System: Arch Linux 
KDE Plasma Version: 5.24.4
Qt Version: 5.15.3
KDE Frameworks Version: 5.93.0
Comment 53 Méven Car 2022-05-09 08:31:12 UTC
(In reply to Brooks Knight from comment #51)
> Looks like this issue is due to Dolphin not watching a directory, which can
> happen several ways, already loaded but inactive tabs or second Dolphin
> window. I did not see any errors in Dolphin.
> 
> To reproduce:
> 1. Open two Dolphin windows of the same folder,
> 2. Create a file in that folder with the terminal. One window will update
> and the other won't.
> 3. In the window that is not working, pressing F5 will have Dolphin
> correctly watch the folder again.
> 
> I already had higher inotify watches due to Insync.
> 
> fs.inotify.max_user_watches=1048576
> 
> Operating System: KDE neon 5.23
> KDE Plasma Version: 5.23.5
> KDE Frameworks Version: 5.90.0
> Qt Version: 5.15.3
> Kernel Version: 5.13.0-27-generic (64-bit)
> Graphics Platform: X11
> Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz
> Memory: 31.1 GiB of RAM
> Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2

could you reproduce the issue using `QT_LOGGING_RULES=kf5.kcoreaddons.kdirwatch.debug=true dolphin`
Comment 54 Brooks Knight 2022-05-13 02:06:40 UTC
(In reply to Méven Car from comment #53)
> (In reply to Brooks Knight from comment #51)
> > Looks like this issue is due to Dolphin not watching a directory, which can
> > happen several ways, already loaded but inactive tabs or second Dolphin
> > window. I did not see any errors in Dolphin.
> > 
> > To reproduce:
> > 1. Open two Dolphin windows of the same folder,
> > 2. Create a file in that folder with the terminal. One window will update
> > and the other won't.
> > 3. In the window that is not working, pressing F5 will have Dolphin
> > correctly watch the folder again.
> > 
> > I already had higher inotify watches due to Insync.
> > 
> > fs.inotify.max_user_watches=1048576
> > 
> > Operating System: KDE neon 5.23
> > KDE Plasma Version: 5.23.5
> > KDE Frameworks Version: 5.90.0
> > Qt Version: 5.15.3
> > Kernel Version: 5.13.0-27-generic (64-bit)
> > Graphics Platform: X11
> > Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz
> > Memory: 31.1 GiB of RAM
> > Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2
> 
> could you reproduce the issue using
> `QT_LOGGING_RULES=kf5.kcoreaddons.kdirwatch.debug=true dolphin`

user@aurora:~$ QT_LOGGING_RULES=kf5.kcoreaddons.kdirwatch.debug=true dolphin
kf.kio.widgets: The "Insync" plugin still installs the desktop file for plugin loading. Please use JSON metadata instead, see  KAbstractFileItemActionPlugin class docs for instructions.
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: known incorrect sRGB profile
libpng warning: profile matches sRGB but writing iCCP instead

This is all I got :(
Did I miss some part of the command?
Comment 55 Scott 2022-05-13 02:10:18 UTC
(In reply to Méven Car from comment #53)
> (In reply to Brooks Knight from comment #51)
> > Looks like this issue is due to Dolphin not watching a directory, which can
> > happen several ways, already loaded but inactive tabs or second Dolphin
> > window. I did not see any errors in Dolphin.
> > 
> > To reproduce:
> > 1. Open two Dolphin windows of the same folder,
> > 2. Create a file in that folder with the terminal. One window will update
> > and the other won't.
> > 3. In the window that is not working, pressing F5 will have Dolphin
> > correctly watch the folder again.
> > 
> > I already had higher inotify watches due to Insync.
> > 
> > fs.inotify.max_user_watches=1048576
> > 
> > Operating System: KDE neon 5.23
> > KDE Plasma Version: 5.23.5
> > KDE Frameworks Version: 5.90.0
> > Qt Version: 5.15.3
> > Kernel Version: 5.13.0-27-generic (64-bit)
> > Graphics Platform: X11
> > Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz
> > Memory: 31.1 GiB of RAM
> > Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2
> 
> could you reproduce the issue using
> `QT_LOGGING_RULES=kf5.kcoreaddons.kdirwatch.debug=true dolphin`

Two Dolphin windows opened at the same file/folder may show the problem more readily but is not necessary to reproduce the error, they can be showing different files/folders.
Comment 56 Méven Car 2022-05-20 18:51:41 UTC
Git commit a3d37d5c829a98339141ccd6a4e01814f023c1ed by Méven Car.
Committed on 20/05/2022 at 18:45.
Pushed by meven into branch 'master'.

KDirWatch: handle IN_Q_OVERFLOW events

M  +6    -0    src/lib/io/kdirwatch.cpp

https://invent.kde.org/frameworks/kcoreaddons/commit/a3d37d5c829a98339141ccd6a4e01814f023c1ed
Comment 57 Patrick Silva 2022-12-07 12:34:34 UTC
*** Bug 462737 has been marked as a duplicate of this bug. ***
Comment 58 pier andre 2023-01-21 17:15:24 UTC
I confirm today:
on my laptop using leap 15.4 and KDE argon
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7
dolphin Version 22.12.0
if I open a konsole window in the folder rightclick>Action>open terminal here and gives the command

ls > zlist.txt
dolphin doesn’t refres or update the folder contents, to view the new file zlist.txt I have to refresh manually.
it happens also with other commands that creates files given via konsole,
is there a way to automatically refresh or it is a feature/bug or it is a setting wher I can see?
Comment 59 Bug Janitor Service 2023-01-25 12:24:17 UTC
A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kcoreaddons/-/merge_requests/289
Comment 60 Méven Car 2023-01-27 09:37:54 UTC
Git commit 40992e7ef24f8b6ab4502df585b00c2f41c72e75 by Méven Car, on behalf of Méven Car.
Committed on 27/01/2023 at 09:32.
Pushed by meven into branch 'master'.

KDirWatch: output more log when in debug log

M  +12   -20   src/lib/io/kdirwatch.cpp

https://invent.kde.org/frameworks/kcoreaddons/commit/40992e7ef24f8b6ab4502df585b00c2f41c72e75
Comment 61 b2 2023-03-19 23:27:41 UTC
Hi, this is how I can reproduce it a few times, each time I tried.

1. Open Dolphin with only 1 tab.
2. Create a file, Dolphin fill refresh correctly.
3. Open a new tab, has to be on the right from the previous one.
4. Close Dolphin.
5. Open it again.
6. Create a file, Dolphin will not refresh.
7. Refresh the folder manually, new file will show up.
8. The folder will also refresh correctly until Dolphin is closed again.

Fedora 36
Dolphin 22.12.0
Plasma 5.27.1
KDE Framework: 5.103.0
max_user_watches seems to be set to 524288
Comment 62 Rajinder Yadav 2023-03-20 21:20:06 UTC
I am still seeing this problem with Dolpin not showing new files. I have to hit F5 (refresh) multiple times and something this doesn't fails and I need to view another folder and come back to see new files. This bug has been around for a long while and doesn't seem to be getting any attention.

Operating System: openSUSE Tumbleweed 20230318
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.6-1-default (64-bit)
Graphics Platform: X11
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7A38
System Version: 8.0
Comment 64 Nate Graham 2023-03-24 18:49:49 UTC
15-minute bugs are Plasma only at this point and Dolphin isn't a part of Plasma.
Comment 65 Méven Car 2023-03-25 13:47:22 UTC
(In reply to b2 from comment #61)
> Hi, this is how I can reproduce it a few times, each time I tried.
> 
> 1. Open Dolphin with only 1 tab.
> 2. Create a file, Dolphin fill refresh correctly.
> 3. Open a new tab, has to be on the right from the previous one.

I am assuming As Ctrl+T dolphin tab

> 4. Close Dolphin.
Qtrl+Q or ALt+F4, you don't have any more instances opened ?

> 5. Open it again.
> 6. Create a file, Dolphin will not refresh.
> 7. Refresh the folder manually, new file will show up.
> 8. The folder will also refresh correctly until Dolphin is closed again.
> 
> Fedora 36
> Dolphin 22.12.0
> Plasma 5.27.1
> KDE Framework: 5.103.0
> max_user_watches seems to be set to 524288

I could not reproduce using your instructions (with neon + Framework 5.103)

How did you create your file ? How many dolphin instances were running ?

Could report the content of those files:
/proc/sys/fs/inotify/max_queued_events
/proc/sys/fs/inotify/max_user_instances

Can use this command to launch dolphin and report the traces when reproducing the problem:

QT_LOGGING_RULES=kf5.kcoreaddons.kdirwatch.debug=true dolphin
Comment 66 Méven Car 2023-03-25 14:01:10 UTC
(In reply to Méven Car from comment #65)
> (In reply to b2 from comment #61)
> > Hi, this is how I can reproduce it a few times, each time I tried.
> > 
> > 1. Open Dolphin with only 1 tab.
> > 2. Create a file, Dolphin fill refresh correctly.
> > 3. Open a new tab, has to be on the right from the previous one.
> 
> I am assuming As Ctrl+T dolphin tab
> 
> > 4. Close Dolphin.
> Qtrl+Q or ALt+F4, you don't have any more instances opened ?
> 
> > 5. Open it again.
> > 6. Create a file, Dolphin will not refresh.
> > 7. Refresh the folder manually, new file will show up.
> > 8. The folder will also refresh correctly until Dolphin is closed again.
> > 
> > Fedora 36
> > Dolphin 22.12.0
> > Plasma 5.27.1
> > KDE Framework: 5.103.0
> > max_user_watches seems to be set to 524288
> 
> I could not reproduce using your instructions (with neon + Framework 5.103)
> 
> How did you create your file ? How many dolphin instances were running ?
> 
> Could report the content of those files:
> /proc/sys/fs/inotify/max_queued_events
> /proc/sys/fs/inotify/max_user_instances
> 
> Can use this command to launch dolphin and report the traces when
> reproducing the problem:
> 
> QT_LOGGING_RULES=kf5.kcoreaddons.kdirwatch.debug=true dolphin

Even better and more verbose

QT_LOGGING_RULES="kf5.kcoreaddons.kdirwatch.debug=true;kf.kio.core.dirlister.debug=true" dolphin
Comment 67 b2 2023-03-25 14:41:05 UTC
Created attachment 157569 [details]
Video recording of the bug

Hi, I'll attach a log in a moment. In the video I've used mouse for everything unless it's in the terminal, so all should be clear.

As for the instances this is what I got after the video, which I think should list all opened Dolphin instances (if you're looking for something else please let me know)

ps -aux | grep dolphin
d          55031  0.0  0.0 222316  2048 pts/2    S+   15:31   0:00 grep --color=auto dolphin
Comment 68 b2 2023-03-25 14:44:57 UTC
Created attachment 157570 [details]
QT_LOGGING_RULES="kf5.kcoreaddons.kdirwatch.debug=true;kf.kio.core.dirlister.debug=true" dolphin

And here's the log. Hopefully not leaking any of my many secrets.
Comment 69 b2 2023-03-25 14:51:16 UTC
And just for clarity. I've probably did it differently the last time. IIRC I just used to download files through FF, which is how I first noticed it. I've probably also closed Dolphin through alt-F4, but none of this seems to matter--I can reproduce it either way.
Comment 70 Méven Car 2023-03-25 15:18:56 UTC
(In reply to b2 from comment #69)
> And just for clarity. I've probably did it differently the last time. IIRC I
> just used to download files through FF, which is how I first noticed it.
> I've probably also closed Dolphin through alt-F4, but none of this seems to
> matter--I can reproduce it either way.

Thank you very much for your help I can reproduce it locally actually thanks to your video presenting the issue and how the tabs are important.
Comment 71 Méven 2023-03-28 07:29:19 UTC
(In reply to Méven Car from comment #70)
> (In reply to b2 from comment #69)
> > And just for clarity. I've probably did it differently the last time. IIRC I
> > just used to download files through FF, which is how I first noticed it.
> > I've probably also closed Dolphin through alt-F4, but none of this seems to
> > matter--I can reproduce it either way.
> 
> Thank you very much for your help I can reproduce it locally actually thanks
> to your video presenting the issue and how the tabs are important.

I know understand the bug origin, triggered in your scenario.

It is about how dolphin watches directories for changes. When we open directories in dolphin, we add inotify watches and when folders are closed their watch is removed. This is all fine until you add split views and tabs. When a new view  (DolphinView + KFileItemModel + KCoreDirLister) opens, they usually open the previous url before opening the new url, so they remove the watch of the previous opened directory except they don't take into account that another view might still need the watch.
This can happen in a number of ways.

The bad news is that it will need quite some refactoring to fix, but it can be done(tm).
Comment 72 b2 2023-03-28 21:06:16 UTC
Thanks for the explanation, hopefully this will be tackled one day.
Comment 73 Bug Janitor Service 2023-03-31 08:12:46 UTC
A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kio/-/merge_requests/1239
Comment 74 David Faure 2023-04-05 20:05:26 UTC
Git commit a304840cff15e3324010da7877b53c2f6fa7e594 by David Faure, on behalf of Méven Car.
Committed on 05/04/2023 at 11:16.
Pushed by meven into branch 'master'.

KCoreDirLister: AutoUpdate wasn't incremented when a new lister opened an already listed dir

 * Adds a test demonstrating the bug
 * adds a cache eviction test for good measure
 * clean a little tests

M  +92   -32   autotests/kdirlistertest.cpp
M  +2    -0    autotests/kdirlistertest.h
M  +7    -2    src/core/kcoredirlister.cpp

https://invent.kde.org/frameworks/kio/commit/a304840cff15e3324010da7877b53c2f6fa7e594
Comment 75 Bug Janitor Service 2023-04-05 20:12:21 UTC
A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kio/-/merge_requests/1246
Comment 76 Méven Car 2023-04-07 07:15:04 UTC
Git commit 60f14205b6e3119dfc1199964ec1d7d9007ef029 by Méven Car, on behalf of Méven Car.
Committed on 07/04/2023 at 06:43.
Pushed by meven into branch 'kf5'.

KCoreDirLister: AutoUpdate wasn't incremented when a new lister opened an already listed dir

 * Adds a test demonstrating the bug
 * adds a cache eviction test for good measure
 * clean a little tests
(cherry picked from commit a304840cff15e3324010da7877b53c2f6fa7e594)

M  +92   -32   autotests/kdirlistertest.cpp
M  +2    -0    autotests/kdirlistertest.h
M  +7    -2    src/core/kcoredirlister.cpp

https://invent.kde.org/frameworks/kio/commit/60f14205b6e3119dfc1199964ec1d7d9007ef029
Comment 77 Méven Car 2023-04-07 07:41:20 UTC
Thanks to b2 efforts to report a reproductible way to trigger the bug, I was able to fix it.

The commit 60f14205 in KF 5.105 should fix cases where tabs or split views are involved.

Please report if it does not work for after you updated to 5.105.
Comment 78 Méven Car 2023-04-08 14:44:13 UTC
(In reply to Méven Car from comment #77)
> Thanks to b2 efforts to report a reproductible way to trigger the bug, I was
> able to fix it.
> 
> The commit 60f14205 in KF 5.105 should fix cases where tabs or split views
> are involved.
> 
> Please report if it does not work for after you updated to 5.105.

It didn't make for 5.105, will be in 5.106.
Comment 79 Patrick Silva 2023-05-04 13:16:15 UTC
*** Bug 469324 has been marked as a duplicate of this bug. ***
Comment 80 Patrick Silva 2023-05-13 01:58:49 UTC
*** Bug 452434 has been marked as a duplicate of this bug. ***
Comment 81 Evert Vorster 2023-05-14 08:15:41 UTC
Just came here to say I am running into this bug as well, and can't wait for the next release! Good job in getting to it.
Comment 82 Evert Vorster 2023-05-15 08:20:40 UTC
Created attachment 158962 [details]
Showing Dolphin not updating

This is a little video file showing how Dolphin is not updating the directory view when it moves a file itself. 
I thought this bug would have been fixed in 106?

System information:
Operating System: Arch Linux 
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Kernel Version: 6.3.2-AMD-znver2 (64-bit)
Graphics Platform: Wayland
Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics
Memory: 36.9 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: LENOVO
Product Name: 20T8001JUS
System Version: ThinkPad E15 Gen 2
Comment 83 Méven Car 2023-05-15 09:11:13 UTC
(In reply to Evert Vorster from comment #82)
> Created attachment 158962 [details]
> Showing Dolphin not updating
> 
> This is a little video file showing how Dolphin is not updating the
> directory view when it moves a file itself. 
> I thought this bug would have been fixed in 106?

>> The commit 60f14205 in KF 5.105 should fix cases where tabs or split views are involved.
>> Please report if it does not work for after you updated to 5.105.
from https://bugs.kde.org/show_bug.cgi?id=387663#c78

Some cases were fixed, your case was not.
I never was confident all cases where fixed.
Thank you for following it through.

I presume you relaunched dolphin (closing all windows) or reboot after the update, this is needed or the old KF code is still being used. 

Please provide a Detailed step by step of how you get to see the bug, from the moment you opened dolphin (which settings you had), which folders you opened in which split view or tabs and in which order.
A video could do the dead.

Unless I can reproduce it, I won't be able to fix it, as the bug is not evident to reproduce.
Comment 84 mozo 2023-05-15 22:22:10 UTC
I have a similar problem here:
https://bugs.kde.org/show_bug.cgi?id=469324

I think it's not a duplicate but still. If you have any info I'll do my best to provide it.
Comment 85 mozo 2023-05-15 22:23:13 UTC
And one more thing:
If I downgrade to Dolphin 22.12.3 the problem disappears. Every newer version have it.
Comment 86 Ryan E 2023-08-08 04:28:24 UTC
I am getting this bug while using Dolphin to access a networked and password-protected SMB drive. The following steps recreate the bug for me 100% of the time:
1. Auto-mount SMB drive to /media/<share> by adding the following string to /etc/fstab :
//<ip-of-SMB-device>/<network-share> /media/<share> cifs credentials=path/to/.smbcredentials, uid=1000, gid=1000, iocharset=uft8 0 0

2. Reboot.
3. Right click pinned Dolphin icon on the KDE Task Manager. Click "Open New Window".
4. Navigate to /media/<share>
5.  Open a second instance of Dolphin using the pinned icon on the KDE Task Manager.
6. Navigate to smb://<ip-of-SMB-device>/<network-share>
7. Enter credentials.
8. Right-click in the instance pointing to the SMB file path and create hello.txt
9. See that the Dolphin instance pointing to /media/<share> does not reflect changes.
10. Press F5 to refresh and can now see hello.txt

The reverse is not true. If I create a file in the instance pointing to /media/<share>, that file is immediately shown in the file pointing to the SMB address. Everything stated above also applies to directories. It also occurs when using tabs and split views.

System information: 
Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 6.2.0-26-generic (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i7-5600U CPU @ 2.60GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500
Manufacturer: Dell
Product Name: Latitude E7450
Comment 87 Méven Car 2023-08-08 07:53:31 UTC
(In reply to Ryan E from comment #86)
> I am getting this bug while using Dolphin to access a networked and
> password-protected SMB drive.

Report this in a different bug, for network filesystem please.
This is not the same.

Network file systems can't have proper file updates notification nowadays due to lack of implementation on the filesystem level.

 The following steps recreate the bug for me
> 100% of the time:
> 1. Auto-mount SMB drive to /media/<share> by adding the following string to
> /etc/fstab :
> //<ip-of-SMB-device>/<network-share> /media/<share> cifs
> credentials=path/to/.smbcredentials, uid=1000, gid=1000, iocharset=uft8 0 0
> 
> 2. Reboot.
> 3. Right click pinned Dolphin icon on the KDE Task Manager. Click "Open New
> Window".
> 4. Navigate to /media/<share>
> 5.  Open a second instance of Dolphin using the pinned icon on the KDE Task
> Manager.
> 6. Navigate to smb://<ip-of-SMB-device>/<network-share>
> 7. Enter credentials.
> 8. Right-click in the instance pointing to the SMB file path and create
> hello.txt
> 9. See that the Dolphin instance pointing to /media/<share> does not reflect
> changes.
> 10. Press F5 to refresh and can now see hello.txt
> 
> The reverse is not true. If I create a file in the instance pointing to
> /media/<share>, that file is immediately shown in the file pointing to the
> SMB address. Everything stated above also applies to directories. It also
> occurs when using tabs and split views.
> 
> System information: 
> Operating System: Kubuntu 22.04
> KDE Plasma Version: 5.24.7
> KDE Frameworks Version: 5.92.0
> Qt Version: 5.15.3
> Kernel Version: 6.2.0-26-generic (64-bit)
> Graphics Platform: X11
> Processors: 4 × Intel® Core™ i7-5600U CPU @ 2.60GHz
> Memory: 15.5 GiB of RAM
> Graphics Processor: Mesa Intel® HD Graphics 5500
> Manufacturer: Dell
> Product Name: Latitude E7450
Comment 88 alem99393@gmail.com 2023-08-10 13:05:53 UTC
*** Bug 473232 has been marked as a duplicate of this bug. ***
Comment 89 sramey40 2023-09-12 00:36:37 UTC
Created attachment 161568 [details]
file not updating bug
Comment 90 sramey40 2023-09-12 00:37:19 UTC
I have this bug in the 23.08.0 version, but on mine, it just seems like when I send files to a folder, the folder doesn't update unless I refresh it somehow. I am attaching a video demonstrating this.

(In reply to mozo from comment #85)
> And one more thing:
> If I downgrade to Dolphin 22.12.3 the problem disappears. Every newer
> version have it.

Downgrading to this version also solves the problem for me.
Comment 91 sramey40 2023-09-12 00:39:45 UTC
Note: On my video attachment, it is encoded as h265 so it won't play in most browsers. Download it to watch.
Comment 92 Bug Janitor Service 2023-09-12 11:57:29 UTC
A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kio/-/merge_requests/1409
Comment 93 Méven Car 2023-09-12 12:02:29 UTC
(In reply to sramey40 from comment #91)
> Note: On my video attachment, it is encoded as h265 so it won't play in most
> browsers. Download it to watch.

Thanks it shed some light on the case you are talking about: moving/copying files to sub-folders of the current folder, and that folder state doesn't get refreshed.

This bug sort of reported the same issue,  and I fixed it, fixing your case as well:
https://bugs.kde.org/show_bug.cgi?id=440712

https://invent.kde.org/frameworks/kio/-/commit/8b515e3827fa464384ae142cce493e9a97351c5b

I am backporting it, to next KF5 version.
https://invent.kde.org/frameworks/kio/-/merge_requests/1409

It does not solve the case when you move files from the command line though.