Bug 188337 - Add an option to remove stale tracks from MTP devices' database
Summary: Add an option to remove stale tracks from MTP devices' database
Status: RESOLVED WORKSFORME
Alias: None
Product: amarok
Classification: Applications
Component: Collections/MTP player (show other bugs)
Version: 2.1-SVN
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-28 14:09 UTC by Mikko C.
Modified: 2022-11-17 05:12 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mikko C. 2009-03-28 14:09:28 UTC
Version:           2.1-SVN (using 4.2.68 (KDE 4.2.68 (KDE 4.3 >= 20090327)), Gentoo)
Compiler:          x86_64-pc-linux-gnu-gcc
OS:                Linux (x86_64) release 2.6.29

As the title says.
It can happen that a track fails to copy but the meta-info is copied in the database.
If that happens, it won't be possible to copy that track anymore, because Amarok will complain:

amarok:      The following tracks failed to copy
amarok:      "AC/DC"  -  "Moneytalks"  with error:  "Already on device"
Comment 1 Simeon 2011-12-20 15:33:46 UTC
This wish has been granted.This report should be removed.
Comment 2 Myriam Schweingruber 2011-12-21 00:03:24 UTC
(In reply to comment #1)
> This wish has been granted.This report should be removed.

So sorry, please disregard this message, there was a misunderstanding with the
Google Code-In student.
Comment 3 postix 2022-10-18 17:46:13 UTC
Is this still an issue?
Comment 4 Bug Janitor Service 2022-11-02 05:05:35 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2022-11-17 05:12:55 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!