Bug 320413

Summary:	Unable to delete files - trash can is full even when empty
Product:	[Unmaintained] kio	Reporter:	spv.nykanen
Component:	trash	Assignee:	David Faure <faure>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	frank78ac
Priority:	NOR
Version First Reported In:	4.10.3
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description spv.nykanen 2013-05-29 08:57:44 UTC

There was A bug report like this, but in that one Dolphin crashed and that doesn't happen.

When I am trying to delete a file, Dolphin says that the trash is full and I should empty it. The trash was empty already, so I was unable to delete the file. 

There should be a opportunity to delete file straight without the trash, if the file is too big for the trash can.
Something like this: The file(s) you are deleting is too big for the trash. Do you want to delete it straight?

Reproducible: Always

Steps to Reproduce:
1. Create a huge file (1gb?)
2. Try to delete it
3. Original setups
Actual Results:  
Dolphin says that the trash is full and I should empty it. The trash was empty already, so I was unable to delete the file. 

Expected Results:  
There should be a opportunity to delete file straight without the trash, if the file is too big for the trash can.
Something like this: The file(s) you are deleting is too big for the trash. Do you want to delete it straight?

Comment 1 spv.nykanen 2013-05-29 09:00:05 UTC

Also I find it sad, that there is no opportunity to format a USB-disk with a right click in Dolphin.

Comment 2 Frank Reininghaus 2013-05-29 11:49:11 UTC

Thanks for the report, but please do not mix different issues in one report - this makes handling the bug database (which is challenging enough already) impossible for a small team of volunteers.

Let's only consider the "Trash is supposed to be full even though it's empty" issue here.

About comment 1: this is covered already by bug 224056.

Comment 3 Jekyll Wu 2013-06-21 08:10:58 UTC


*** This bug has been marked as a duplicate of bug 245482 ***