https://bugs.kde.org/show_bug.cgi?id=334533
Henrik Fehlauer <rk...@lab12.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rk...@lab12.net Resolution|DUPLICATE |--- Status|RESOLVED |REOPENED Ever confirmed|0 |1 --- Comment #7 from Henrik Fehlauer <rk...@lab12.net> --- Reopening because the former duplicate has been solved, while this one is still a problem in current git master. In detail: - In Bug 378786, scrolling triggers the problem. The fix in https://phabricator.kde.org/D8822 hides the issue by accepting the rename as soon as scrolling starts, so the bug can never occur. - In Bug 331236, the problem is triggered by moving around with the keyboard before sorting happens. This is fixed (probably by accident) in https://phabricator.kde.org/D6312, after which starting a rename is blocked until the renamed file has been sorted and given focus again. - However, for changes to files not coming from Dolphin (i.e. as described above, which translates to all sorts of valid scenarios in reality) the problem persists. >From a high-level view, it seems that inline renaming operates on the list position pointing to a (randomly changing) file, instead of a stable handle to the actual file (not necessarily an inode, as KIO is network transparent). Note that when disabling inline renaming, the bug does not occur. It would be worth checking where this difference in behaviour comes from. See also this comment: https://phabricator.kde.org/D8822#168476 -- You are receiving this mail because: You are watching all bug changes.