Bug 419195 - Krename processus does not stop after renaming files
Summary: Krename processus does not stop after renaming files
Status: RESOLVED FIXED
Alias: None
Product: krename
Classification: Applications
Component: general (show other bugs)
Version: 5.0.0
Platform: Debian stable Linux
: NOR normal
Target Milestone: ---
Assignee: Heiko Becker
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-24 20:08 UTC by Freedim
Modified: 2020-10-13 07:55 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Freedim 2020-03-24 20:08:22 UTC
SUMMARY
When the task asked to krename is achieved, the processus named krename does not end and it keeps a handle on the renamed file(s). This prevents the volume hosting the renamed file(s) from being unmounted, for example.

STEPS TO REPRODUCE
1. In Dolphin, right-click on a file in a removable drive and choose Actions > Krename.
2. Rename the file and submit, then click on "close" Krename.

OBSERVED RESULT
- Open KDE's system monitor: the processus krename is still present.
- Try to "release" the removable drive: error message because the drive is "busy"

EXPECTED RESULT
- krename's processus is terminated when the files are successfully renamed
- the removable drive hosting the renamed files can be released.

SOFTWARE/OS VERSIONS
Operating System: Kali GNU/Linux 2020.1 (Very much like Debian stable)
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.62.0
Qt Version: 5.12.5
Kernel Version: 5.4.0-kali4-amd64
OS Type: 64-bit
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 15,5 Gio

ADDITIONAL INFORMATION
Comment 1 Freedim 2020-03-24 20:10:46 UTC
Sorry for my English. The first phrase should be :
"When the task requested from Krename is achieved..."
Comment 2 Heiko Becker 2020-10-08 12:26:59 UTC
Most likely a duplicate of bug 395084

Can you please test with 5.0.1?
Comment 3 Freedim 2020-10-13 07:54:28 UTC
(In reply to Heiko Becker from comment #2)
> Most likely a duplicate of bug 395084
> 
> Can you please test with 5.0.1?

Indeed, the problem seems solved.
Thanks a lot!