Bug 142278 - amarok does not prevent users from tag editing read-only files
Summary: amarok does not prevent users from tag editing read-only files
Status: RESOLVED UNMAINTAINED
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 1.4.5
Platform: Ubuntu IRIX
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
: 155137 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-02-27 17:41 UTC by Georg Sauthoff
Modified: 2012-08-04 11:55 UTC (History)
1 user (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 Georg Sauthoff 2007-02-27 17:41:23 UTC
Version:            (using KDE KDE 3.5.5)
Installed from:    Ubuntu Packages
OS:                Irix

Hi,

amarok (1.4.3) does not prevent the user that he tag-edit files, that are read-only. Of course it is a bit stupid trying to do it. But imagine this worst case:
You copied 100 mp3 three years ago from a CDR into your home. Of course you forgot, that they are read-only and now you start to tag 100 files with the 'Edit Tag Information ...' Dialog. After 30 minutes hard work everything is tagged and you click 'save & close'. Boom! You get an error message and all your changes are lost!

I found two reports, which describe this problem as a side node, but they unfortunetely got closed without fixing this specific issue:
Bug 110299
Bug 131274

Best regards
Georg Sauthoff
Comment 1 Sebastian Krämer 2007-10-23 02:01:42 UTC
IMO this would really be an improvement. Fortunately this didn't happen to me (yet?).
Comment 2 Kevin Funk 2008-01-05 18:50:55 UTC
*** Bug 155137 has been marked as a duplicate of this bug. ***
Comment 3 Daniel Karlsson 2008-01-06 12:24:45 UTC
Hi, this bug was reported by David Nemeskey in Ubuntu's bug tracker, here's a link: https://bugs.launchpad.net/amarok/+bug/180369

Has any progress been made, anyone actually working on it? 
Comment 4 Lydia Pintscher 2008-06-15 16:00:46 UTC
Amarok 1.4.x is in bugfix-only mode as development is focused on Amarok 2. Unfortunately your bug will very likely not get fixed, as the risk of regressions is too high and the Amarok developers do not have the resources for it. Thank you for your report though.

We should make sure this is not a problem in Amarok 2.
Comment 5 Myriam Schweingruber 2012-08-04 11:55:09 UTC
Closing correctly as Amarok 1.x is unmaintained since quite some time anyway.