Bad design

[Clarence Weaver]

Binary package hint: rhythmbox

This is not really a bug but rather a very bad design which is contrary to the whole philosophy of Linux; do one thing and do it well. Rhythmbox is *not* a file browser, but rather a music player/ripper/burner and it in no way should ever allow a user to delete a file from the file system. Removing a song from the playlist is ok, remove a file from the file system is not ok. Those two functions are placed adjacent to each other when right clicking on the playlist files. (Remove and Move to Trash) A slip of a mouse with a hair trigger left button erases every highlighted file in the playlist from the filesystem instantly without even the benefit of confirmation, and without a "trash" container, irrevocably removes forever all the files represented by those playlist items. This is inexcusable. Better that the Devs spend time fixing real bugs than including functions that are outside the realm of a music application.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: rhythmbox 0.13.1-0ubuntu6
ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
Uname: Linux 2.6.35-24-generic i686
Architecture: i386
Date: Sun Jan 30 14:04:19 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.utf8
SourcePackage: rhythmbox

[Leo Arias (elopio)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

There is a similar report with an interesting discussion at https://bugzilla.gnome.org/show_bug.cgi?id=326776

[Omer Akram (om26er)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Clarence Weaver (kenb)]

Bug 326776 is certainly similiar. In fact it is identical to what I am reporting here so I desire to mark this one as over and done with because 326776 is where this report belongs. Sorry I missed it initially.