Copying existing tracks to Android device re-copies and eventually crashes
If I upload tracks to an Android device, then try to upload the same tracks over again, given the speed that the second copy goes at I have to assume that RB is re-copying existing tracks. I would expect RB to not waste resources re-copying something that already exists.
When it does this it also pops up a dialog which says Error transferring track: null in it and then eventually completely crashes.
Relevant --debug
log messages:
(19:05:42) <mtp> [queue_task] ../plugins/mtpdevice/rb-mtp-thread.c:142: queueing task: upload track from /tmp/rb-encoder-EEXMQ1
(19:05:42) <mtp> [run_task] ../plugins/mtpdevice/rb-mtp-thread.c:569: running task: upload track from /tmp/rb-encoder-EEXMQ1
(19:05:42) <mtp> [upload_track] ../plugins/mtpdevice/rb-mtp-thread.c:548: unable to send track: PTP Layer error 2002: send_file_object_info(): Could not send object info.
(19:05:42) <mtp> [upload_callback] ../plugins/mtpdevice/rb-mtp-source.c:1132: upload failed: Unable to send file to MTP device: PTP Layer error 2002: send_file_object_info(): Could not send object info.
(19:05:42) <0x55bb6a593b00> [impl_track_upload] ../plugins/mtpdevice/rb-mtp-source.c:1282: track upload finished
(19:05:42) <rhythmbox> [postprocess_transfer_cb] ../shell/rb-track-transfer-batch.c:575: postprocessing failed for transfer file:///tmp/rb-encoder-EEXMQ1: (null)
See the downstream bug report for details such as a stacktrace.
Edited by Brian J. Murrell