Bug 463611 - Permanent file deletion doesn't work in Dolphin
Summary: Permanent file deletion doesn't work in Dolphin
Status: RESOLVED DUPLICATE of bug 462845
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 22.12.0
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-12-30 09:16 UTC by nofyb
Modified: 2022-12-30 17:00 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description nofyb 2022-12-30 09:16:13 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Create a file anywhere (or copy/paste one from another place).
2. Try to permanently delete it with the Shift+Del keys, confirm your choice.


OBSERVED RESULT
The file doesn't get deleted.


EXPECTED RESULT
The file should be permanently deleted.


SOFTWARE/OS VERSIONS
Linux: Debian Testing (Bookworm/Sid)
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7


ADDITIONAL INFORMATION

Tried on both NTFS and EXT3 partitions, checked write permissions, it doesn't seem to be about an issue related to these. Shift+Del works fine with the same files in DoubleCommander for example.
Comment 1 Felix Ernst 2022-12-30 13:54:29 UTC
I am 99% sure you got tripped up on the pre-selected button having switched. I'll therefore mark this as a duplicate of that bug, which I recently fixed. If that isn't the case, let me know.

*** This bug has been marked as a duplicate of bug 462845 ***
Comment 2 nofyb 2022-12-30 17:00:30 UTC
(In reply to Felix Ernst from comment #1)
> I am 99% sure you got tripped up on the pre-selected button having switched.
> I'll therefore mark this as a duplicate of that bug, which I recently fixed.
> If that isn't the case, let me know.
> 
> *** This bug has been marked as a duplicate of bug 462845 ***


Oh, indeed, I've just checked, thanks for your help. Glad to see this annoyance is getting reverted...