Bug 166256

Summary: Emptying trash blocks plasma totally
Product: [Unmaintained] plasma4 Reporter: Florian Sievert <FlorianSievert>
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: aseigo, bymenda, fablion, jpr, michal.zajac+kde.org
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Florian Sievert 2008-07-10 21:52:32 UTC 
Version:           KDE 4.0.85 (KDE 4.1 >= 20080703) (using Devel)
Installed from:    Compiled sources

Emptying the trash via the applet blocks plasma completly. Try to put lots of big files (>10 GB) into your trash and use "emptry trash". A progress dialog is shown and meanwhile the user is not able to use anything depending on plasma (ex. using the taskbar anymore). After the trash process is finished, plasma reacts fine again. However the user might get confused, why plasma is not reacting anymore.

Using "emptry" trash over the places menu in dolphin seems to have this issue. During emptying the trash everything reacts smooth on user actions. So it doesn't seem to be an issue with a poor pc performance. Maybe the trash applet should be called in a seperate thread in order to avoid blocking plasma.
Comment 1 JP Rosevear 2008-10-31 16:33:33 UTC 
See also https://bugzilla.novell.com/show_bug.cgi?id=440394
Comment 2 Fabien Lion 2008-12-24 10:59:44 UTC 
Even if the files is very small (i have tried with a pdf (4Mo). When I click on empty trash, plasma is blocked.
Comment 3 Rafa Muñoz Cárdenas 2008-12-28 20:28:27 UTC 
Same here with OpenSuse 11.0 beta 2. Plasma hangs totally and after about 10/15 seconds it works again.
Comment 4 Michał Zając 2009-01-03 12:48:43 UTC 
Same here using Kubuntu 8.10. It hangs after every use of the plasmoid, but if you go to trash:/ and empty the content by yourself it doesn't hangs
Comment 5 Aaron J. Seigo 2009-01-03 21:12:23 UTC 

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