Bug 359801 - Dolphin freezes system, if during batch rename filename exists
Summary: Dolphin freezes system, if during batch rename filename exists
Status: RESOLVED WORKSFORME
Alias: None
Product: dolphin
Classification: Applications
Component: general (other bugs)
Version First Reported In: 15.12.1
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-25 18:17 UTC by adimeymuc
Modified: 2016-11-29 10:37 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description adimeymuc 2016-02-25 18:17:53 UTC
Dolphin freezes system completely, if during batch rename filename exists.

eg.: 1)
 in FolderX, containing  files numbered 11.ext to 100.ext, by way of right click "rename" all is selected.
2) In the rename dialogue "new_name#" and # "start with number" is selected. 
2a) the screen gets completely tiled full of "file is being moved messages" -- a bit annoying that but bearable
3) if one of the New numbers already exists, several* error message pop up "file exists already" -- correctly so far -- with the usual choices. Alas the system totally freezes up, no inputs possible.

* apparently a larger number, say 9+ -- works fine with 1 or 2


Reproducible: Always


Actual Results:  
Complete freeze, requires pulling the plug.


No backtrace available.
Comment 1 Spencer Brown 2016-11-28 18:53:08 UTC
Could be an OpenSuse problem, but it seems fixed.  Is it still reproducible for you?
Not reproducible for me on
Archlinux
Frameworks Version 5.28.0-1
Dolphin 16.08.3
The multi-rename works for me with up to 24 files at once.  I also did it a several sucessive times to see if dolphin was mixing up the old and new files, but still no errors.  Also no "file moved messages", so that must be fixed.
Comment 2 Elvis Angelaccio 2016-11-29 10:37:32 UTC
Please try again with newer Dolphin/KIO versions and report back if you still are affected by this issue.