Bug 276536 - MTP: Unable to send more than one file to device
Summary: MTP: Unable to send more than one file to device
Status: RESOLVED DUPLICATE of bug 238912
Alias: None
Product: amarok
Classification: Applications
Component: Collections/MTP player (show other bugs)
Version: 2.4.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: 2.4.2
Assignee: Amarok Developers
Depends on:
Reported: 2011-06-26 15:19 UTC by Dainius Masiliūnas
Modified: 2011-12-20 11:45 UTC (History)
1 user (show)

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


Note You need to log in before you can comment on or make changes to this bug.
Description Dainius Masiliūnas 2011-06-26 15:19:30 UTC
Version:           2.4.0 (using KDE 4.6.0) 
OS:                Linux

Trying to send more than one music file to an MTP device results in an error that one is being sent already. However, the first file is transferred correctly, even though Amarok shows it as still being sent. Forcing it to abort results in the same error.

Reproducible: Always

Steps to Reproduce:
1. Open Amarok.
2. Connect an MTP device.
3. In Media Sources, open Local Music and wait for the device to be detected.
4. Go to Files, right-click on a music file, choose Copy To Collection.
5. Choose to copy.
6. Repeat steps 4 and 5.

Actual Results:  
Amarok shows a progress bar at the lower right indicating 0%. After completing step 6, an error "Tracks not copied: the device is already being copied to" appears.

Expected Results:  
The progress bar should go up to 100% and Amarok should allow copying more files to the device.

Using iRiver T10a. When sending the first file, the device indicates "Tranferring..." and after a while shows "USB Connect", indicating that the transfer was successful, yet Amarok is stuck at 0%. Transferred file is confirmed to be received successfully.

Using openSUSE 11.4 x86-64, libmtp 1.0.6-4.1.
Comment 1 Sven Krohlas 2011-06-26 16:00:52 UTC
Sounds very much like a dupe of bug 238912 to me, could you please test with current git master or the soon to be released 2.4.2 beta?

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