[dolphin] [Bug 430585] Dolphin fails to change the capitalization of the name of a file located in a Samba share

[Harald Sitter]

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

--- Comment #2 from Harald Sitter <sitter at kde.org> ---
Case sensitivity is indeed the trouble there. Before the rename there's a stat
call on the destination and if it exists the rename dialog is triggered. That
is however falling into the case insensitivity trap as renaming a->A will have
A existing because A=a.

This particular problem needs addressing in kio-extras and I threw together a
hack that does some in depth comparison between src and dst to figure out if
they might be the same file, alas, that revealed a problem with change
notifications because windows servers send FilesRemoved before the FileRenamed
which makes the file disappear from dolphin's model :@

That does kind of need fixing in dolphin first though (does that code even live
in dolphin?)

signal time=1611157682.777775 sender=:1.3315 -> destination=(null destination)
serial=19 path=/; interface=org.kde.KDirNotify; member=FilesRemoved
   array [
      string "smb://user@windev2004eval.local/Users/User/Desktop/New folder
(6)/a"
   ]
signal time=1611157682.778322 sender=:1.3315 -> destination=(null destination)
serial=20 path=/; interface=org.kde.KDirNotify; member=FileRenamed
   string "smb://user@windev2004eval.local/Users/User/Desktop/New folder (6)/a"
   string "smb://user@windev2004eval.local/Users/User/Desktop/New folder (6)/A"
signal time=1611157682.778640 sender=:1.3315 -> destination=(null destination)
serial=22 path=/; interface=org.kde.KDirNotify; member=FilesChanged
   array [
      string "smb://user@windev2004eval.local/Users/User/Desktop/New folder
(6)/A"
   ]

After that FilesChanged notification dolphin should have gone "what A?" and
done a stat but it didn't so the file disappeared entirely.  In fact, perhaps
already after FileRenamed since dolphin at that point doesn't know about
neither a nor A.
If that can't be fixed in dolphin or where ever I can take a look at handling
it lower in the kio-extras side but from what I recall of the notification code
it's actually fairly horrible to put context on these events since one file
operation translations into a multitude of events, twice as many for
renaming/moving.

-- 
You are receiving this mail because:
You are on the CC list for the bug.