Rclone large files have issues opening from Proton Drive

Suspected Bug
1

What is the problem you are having with rclone?

When opening large files from a mounted Proton Drive account some apps have issues receiving the data (tested with WINE, Gnome Videos, and VLC)

Run the command 'rclone version' and share the full output of the command.

- os/version: ubuntu 24.04 (64 bit)
- os/kernel: 6.11.0-21-generic (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.24.0
- go/linking: static
- go/tags: none

yes

Which cloud storage system are you using? (eg Google Drive)

Proton Drive

The command you were trying to run (eg rclone copy /tmp remote:tmp)

Paths modified to simplify output

$ vlc ~/rclone/protondrive/29.8MB.mp4
VLC media player 3.0.20 Vetinari (revision 3.0.20-0-g6f0d0ab126b)
[000063544a27a550] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.
[0000768764001170] mp4 demux error: MP4 plugin discarded (no moov,foov,moof box)
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x768764c19880] moov atom not found
[0000768764001170] avformat demux error: Could not open /home/danholli/rClone/ProtonDrive/Backups/Secure/Who is it Really.mp4: Unknown error 1094995529

7zip also gives error popup stating:

Cannot open file
'Z:\home\danholli\rclone\protondrive\10.4.7z' as archive
Z:\home\danholli\rclone\protondrive\10.4.7z
Cannot open the file as [7z] archive
Errors:Headers Error

after attempting to load displaying the full file size but no increase from 0 bytes processed

The rclone config contents with secrets removed.

[ProtonDrive]
type = protondrive
username = redacted
password = redacted
2fa = redacted
client_uid = redacted
client_access_token = redacted
client_refresh_token = redacted
client_salted_key_pass = redacted

A log from the command with the -vv flag

https://gist.github.com/DanHolli/32fd0486664fbcbd3dea292c4036456a

This is the output of the mount command

2

welcome to the forum,

that output does not seem to show any issues?
in addition, the two files mentioned in your post, did not see them in the output??

3

The gist.github link is the output, sorry I was tired when I posted and failed to format it nicely, unfortunately it doesn't seem to want me to be able to edit it

the paths were simplified for the commands to save on retyping as again tired and likely poor decisions. I've reviewed all paths in the output are correct and correlated to the issue

as for exactly what it's doing while trying to read, you can see in the mount command output

2025/04/14 03:33:59 DEBUG : Backups/Secure/Backups.7z: ChunkedReader.openRange at 10358784 length 134217728
2025/04/14 03:34:00 DEBUG : Backups/Secure/Backups.7z: ChunkedReader.RangeSeek from -1 to 10358784 length -1
2025/04/14 03:34:00 DEBUG : Backups/Secure/Backups.7z: ChunkedReader.Read at -1 length 4096 chunkOffset 10358784 chunkSize 134217728
2025/04/14 03:34:00 DEBUG : Backups/Secure/Backups.7z: ChunkedReader.openRange at 10358784 length 134217728
2025/04/14 03:34:01 DEBUG : Backups/Secure/Backups.7z: ChunkedReader.RangeSeek from -1 to 10358784 length -1
2025/04/14 03:34:01 DEBUG : Backups/Secure/Backups.7z: ChunkedReader.Read at -1 length 4096 chunkOffset 10358784 chunkSize 134217728
2025/04/14 03:34:01 DEBUG : Backups/Secure/Backups.7z: ChunkedReader.openRange at 10358784 length 134217728
2025/04/14 03:34:03 DEBUG : Backups/Secure/Backups.7z: ChunkedReader.RangeSeek from -1 to 10358784 length -1
2025/04/14 03:34:03 DEBUG : Backups/Secure/Backups.7z: ChunkedReader.Read at -1 length 4096 chunkOffset 10358784 chunkSize 134217728
2025/04/14 03:34:03 DEBUG : Backups/Secure/Backups.7z: ChunkedReader.openRange at 10358784 length 134217728
2025/04/14 03:34:04 DEBUG : Backups/Secure/Backups.7z: ChunkedReader.RangeSeek from -1 to 10358784 length -1
2025/04/14 03:34:04 DEBUG : Backups/Secure/Backups.7z: ChunkedReader.Read at -1 length 4096 chunkOffset 10358784 chunkSize 134217728
2025/04/14 03:34:04 DEBUG : Backups/Secure/Backups.7z: ChunkedReader.openRange at 10358784 length 134217728
2025/04/14 03:34:05 DEBUG : Backups/Secure/Backups.7z: ChunkedReader.RangeSeek from -1 to 10358784 length -1
2025/04/14 03:34:05 DEBUG : Backups/Secure/Backups.7z: ChunkedReader.Read at -1 length 4096 chunkOffset 10358784 chunkSize 134217728
2025/04/14 03:34:05 DEBUG : Backups/Secure/Backups.7z: ChunkedReader.openRange at 10358784 length 134217728
2025/04/14 03:34:07 DEBUG : Backups/Secure/Backups.7z: ChunkedReader.RangeSeek from -1 to 10358784 length -1

and

025/04/14 03:34:09 DEBUG : &{Backups/Secure/Backups.7z (rw)}: Flush: 
2025/04/14 03:34:09 DEBUG : Backups/Secure/Backups.7z(0xc000cb0040): RWFileHandle.Flush
2025/04/14 03:34:09 DEBUG : &{Backups/Secure/Backups.7z (rw)}: >Flush: err=<nil>
2025/04/14 03:34:10 DEBUG : &{Backups/Secure/Backups.7z (rw)}: Flush: 
2025/04/14 03:34:10 DEBUG : Backups/Secure/Backups.7z(0xc000cb0040): RWFileHandle.Flush
2025/04/14 03:34:10 DEBUG : &{Backups/Secure/Backups.7z (rw)}: >Flush: err=<nil>
4

imho, the protondrive backend has been abandoned for a long time now, many issues in the forum, bugs not getting fixed.
the company protondrive is openly hostile to rclone, will not provide tech support.
so have zero expectation it will work.

might test --vfs-cache-mode=full

5

I tested that as well last night without -vv and it provided the same ultimate result of the file not being loaded for use, here in an hour or two I can run it with the verbosity and see if the logs look the same or give another error