It should be more clear that Shotwell maintains its own Trash

Bug #655278 reported by Matthew Woerly
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
One Hundred Papercuts
Fix Released
Undecided
Unassigned
Shotwell
New
Unknown
shotwell (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: shotwell

One would expect that "Move to Trash" would move a file to Gnome's Trash. However, this is not the case. It's not obvious that it's moved to Trash within Shotwell, especially when a lot of tags are present and the Trash section is all the way at the bottom of the list.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: shotwell 0.7.2-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: wl
Architecture: amd64
Date: Tue Oct 5 12:43:24 2010
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: shotwell

Revision history for this message
Matthew Woerly (nattgew) wrote :
Revision history for this message
Adam Dingle (adam-yorba) wrote :

Yes, this is potentially confusing.

One possible solution would be to unify the Shotwell and GNOME trashes; see http://trac.yorba.org/ticket/2645 .

Omer Akram (om26er)
Changed in shotwell (Ubuntu):
importance: Undecided → Low
status: New → Triaged
Changed in shotwell:
status: Unknown → New
Revision history for this message
Maui Muc (stefan-mauerberger) wrote :

Yes, this is really misleading and I almost wrote a additional bug report! I would highly favor to unify both, the Shotwell and GNOME trashes. However, this will take some time so I would recommend to simply rename 'Move to Trash' to e.g. 'Move to Shootwell's Trash'. This makes clear that Shotwell has its own Trash, which is not related to the file system.

Changed in hundredpapercuts:
milestone: none → precise-6-photos
importance: Undecided → Low
no longer affects: hundredpapercuts
Changed in hundredpapercuts:
milestone: none → papercuts-s-shotwell
Revision history for this message
Anthony Harrington (linuxchemist) wrote :

I too would like to see them unified. In the meantime, however, i'm currently correcting these strings for en_GB, en_CA and en_AU.
We call the bin on the desktop the "Rubbish Bin" (this is true for en_gb, i'm not sure how much it spread from our team's work), and i've tweaked shotwell to have its bin be called "Shotwell's Bin" (which is reasonably short and to the point).

These updates will be in Saucy by default and the other series releases when their lang packs are updated. Should you wish to have your lang pack updated before this, there is a ppa updated regularly which can be added with:

sudo add-apt-repository ppa:ubuntu-langpack/ppa

and updating and upgrading.

This bug may be considered....half done. This will no longer be an issue for (most? all?) english locale users once the lang packs update, but the route cause of the problem means that shotwell must get rid of it's bin and send deleted images to the default bin.

Revision history for this message
Anthony Harrington (linuxchemist) wrote :

its* yikes, my spelling tonight.

That should do it on my end. The majority of english locale users are on en_GB, en_CA or en_AU (i'm not even sure if there are translation teams on launchpad to handle the rest?) so now australian and british users can look forward to "Shotwell's Bin" and Canadian users "Shotwell's Trash" (i'm sure 'garbage' might have been more appropriate but this is a stop gap measure for the time being). Canadian english translations really don't get a lot of TLC, but en_CA locale users are welcome to take a more direct role if they want more ideal phrasing.

Revision history for this message
Paul White (paulw2u) wrote :

Checking shotwell 0.28.4 in Ubuntu 18.04 I would say that this is fixed as I'm seeing "Shotwell's Bin" as per comment #5.

Changed in hundredpapercuts:
status: New → Fix Released
Changed in shotwell (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.