Bug 178476 - info for trash objects should show original location and time of deletion
Summary: info for trash objects should show original location and time of deletion
Status: RESOLVED DUPLICATE of bug 153492
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
: 166861 192672 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-12-22 15:40 UTC by Marc Schiffbauer
Modified: 2012-01-06 12:35 UTC (History)
7 users (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 Marc Schiffbauer 2008-12-22 15:40:56 UTC
Version:           4.1.85 (using Devel)
OS:                Linux
Installed from:    Compiled sources

When viewing the contents of the trash can, you can not see where the objects came from and when they were thrown away. 

But this is a useful or essential information needed in many if not all cases where you want to restore a file. Especially if you deleted some files with the same name from different directories you cannot determine from which place a file cam from right now.

It would be nice to see additional information on the information tab for trash objects like:
  * Date of deletion
  * Original file location
Comment 1 Shaun Reich 2009-02-15 22:53:30 UTC
*** Bug 166861 has been marked as a duplicate of this bug. ***
Comment 2 Dotan Cohen 2009-06-19 23:55:39 UTC
The option to order by deletion date would be great, too. This would make it easy to find the last file deleted, and the oldest files in the Trash as well. Thanks.
Comment 3 Marc Schiffbauer 2009-12-27 22:45:22 UTC
This bug is still valid for KDE SC 4.3.85
Comment 4 Marc Schiffbauer 2010-06-26 11:31:40 UTC
Still valid for 4.4.90
Comment 5 Alexander Potashev 2011-07-17 08:58:20 UTC
*** Bug 192672 has been marked as a duplicate of this bug. ***
Comment 6 Peter Penz 2012-01-06 12:35:38 UTC

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