Bug 206550

Summary: Multiple processes copying to media devices fail
Product: [Applications] amarok Reporter: Elias Probst <mail>
Component: Collections/Media DevicesAssignee: Amarok Developers <amarok-bugs-dist>
Status: RESOLVED NOT A BUG    
Severity: normal CC: aikawarazuni, hakan, mail, rktspm
Priority: NOR    
Version: 2.3-GIT   
Target Milestone: 2.4.0   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description Elias Probst 2009-09-06 21:41:12 UTC 
Version:           2.1.80 (using 4.3.1 (KDE 4.3.1), Gentoo)
Compiler:          x86_64-pc-linux-gnu-gcc
OS:                Linux (x86_64) release 2.6.30-gentoo-r6

How to reproduce:
→ Copy some tracks to an MTP device
→ While the copy process is still running, copy some more files to the same device

What happens:
→ A message box "Tracks not copied: the device is already being copied to" appears
→ Both copy processes fail

What should happen instead:
→ The other copy processes should be launched serialized (finish the 1st, start the 2nd, finish the 2nd, start the 3rd, ....) to prevent extreme slowdown as it often happens when opening multiple I/O-streams to flash devices.
→ When there are multiple copy processes to different devices, they should run in parallel
Comment 1 Rafael Tesser 2009-10-05 21:50:32 UTC 
I also have this bug, and this is still present in 2.2.0.
Comment 2 Mikko C. 2009-11-22 20:28:45 UTC 
*** Bug 215727 has been marked as a duplicate of this bug. ***
Comment 3 Mikko C. 2009-11-22 20:29:50 UTC 
Changed the title since it's not mtp specific
Comment 4 Myriam Schweingruber 2009-12-10 21:20:57 UTC 
*** Bug 218152 has been marked as a duplicate of this bug. ***
Comment 5 Myriam Schweingruber 2011-09-26 15:15:44 UTC 
Is this still valid with Amarok 2.4.3 or current git?
Comment 6 Elias Probst 2011-09-26 15:26:25 UTC 
(In reply to comment #5)
> Is this still valid with Amarok 2.4.3 or current git?
I don't use Amarok anymore. Could anyone else of the CCs verify this?
Comment 7 Myriam Schweingruber 2011-11-07 11:55:11 UTC 
Closing for lack of feedback. Feel free to reopen if you can reproduce this with the latest git build.