mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
qBittorrent unable to locate files containing 'Left-To-Right-Mark character' in the filename #15233
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#15233
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @vincejv on GitHub (Nov 28, 2023).
qBittorrent & operating system versions
qBittorrent: v4.6.2 (also tested until v4.6.0)
Qt: 6.6.1
Libtorrent: 2.0.9.0
Boost: 1.82.0
OpenSSL: 3.1.4
zlib: 1.3
Operating System:
Linux Pictor 5.15.137 #0 SMP Tue Nov 14 13:38:11 2023 x86_64 GNU/Linux
Ubuntu 22.04.3 LTS x86_64
Docker version 24.0.5, build ced0996
linuxserver image
What is the problem?
Unable to upload torrent, error message "mismatching file size" after several torrent re-creation
File is copyrighted content, I'm not sure if I can upload it in github as "fair use"? It's isolated to this specific file, i've uploaded a bunch of torrents already to a private tracker (1TB+) no issues there
Tried using Transmission 4.0.4, no issue
Steps to reproduce
Full error on fast resume:
When rechecking the torrent file:

Additional context
File is stored on BTRFS FS with the following mount options
autodefrag,noatime,compress=zstd:3,compress-force=zstd:3,space_cache=v2,discard=async,commit=120,device=/dev/sdc1,device=/dev/sdbWhen uploading the torrent and stored in ext4 fs, no issueTried using Transmission 4.0.4, no issue as well
Further Troubleshooting:
ls -alhLog(s) & preferences file(s)
Execution Log
@vincejv commented on GitHub (Nov 28, 2023):
Related: https://github.com/qbittorrent/qBittorrent/issues/19609
@vincejv commented on GitHub (Nov 28, 2023):
Reopening as workaround described on: https://github.com/qbittorrent/qBittorrent/issues/19609 and https://github.com/qbittorrent/qBittorrent/issues/16127 does not work
File name:
Pokémon - S18E137 - The Wisdom Not to Run! WEBDL-1080p.mkvWorks with transmission
@glassez commented on GitHub (Dec 1, 2023):
@vincejv
Having provided quite a lot of information, you still managed to hide what really matters (or just confuse, using incorrect wording).
So maybe it's not about qBittorrent after all? Although, of course, it can also be in qBittorrent+BtrFS...
As I can see there is
éin the file name. There was an Issue somewhere in qBittorrent bug tracker due to the fact that such characters were encoded differently in the torrent metadata and the file system.@glassez commented on GitHub (Dec 1, 2023):
Why do you need to
Run a recheck. Isn't files checked initially?@glassez commented on GitHub (Dec 1, 2023):
Did these entries exactly follow in a row in the log? Theoretically, this should not happen, since the second is possible only when restoring a previously added torrent (i.e., one added before restarting qBittorrent).
P.S. Such questions could have been avoided if you had provided the log as it is, without trying to assume what information might be useful and what might not.
@vincejv commented on GitHub (Dec 1, 2023):
@glassez
No I didn't import the torrent with recheck, but i tried to manually recheck after the import, but the error persists

As part of my troubleshooting I tried to replace the
é, withe, still doesn't work so it's probably something else in the file name, probably the!Yes,
Updated steps to reproduce: (will update the initial post)
Also I think you are correct missed some of the logs
as per initial post, there's no issue importing and rechecking it with Transmission 4.0.4
Is there any work around documented? So i can check if this isn't the case?
@vincejv commented on GitHub (Dec 1, 2023):
@glassez
Please see the attached torrent file here, i've only included the problematic file
Pokémon - S18E137 - The Wisdom Not to Run! WEBDL-1080p.mkv.torrent.zip
@glassez commented on GitHub (Dec 2, 2023):
For some reason file name (written in torrent file) has Left-To-Right-Mark character between
Run!and next space.I wonder what file name qBittorrent gets from the file system?
@vincejv commented on GitHub (Dec 2, 2023):
After confirming with the source metadata TVDB, that seems to be the issue, is it something you will not fix due to BEP-8 specification as mentioned in other issues? I'll update the issue to reflect this.
@vincejv commented on GitHub (Dec 2, 2023):
Hi @glassez
Upon further investigation, seems like not a file system issue, happening in ext4 as well, i think when i copied the file over to ext4, it stripped off the
lrmcharacter somehow.Also it seems like a libtorrent issue since it's happening in Deluge 2.1.1, libtorrent 2.0.9.0 as well. Will file a separate libtorrent issue, what happens is libtorrent completely removes the
lrmcharacter completely while in the file system, thelrmcharacter is still there, that's why it's unable to locate the files.For anyone else reading this, for the meantime, you can use non libtorrent clients such as Transmission as it leaves the filenames alone.
@glassez commented on GitHub (Dec 3, 2023):
Well, then it should definitely be reported to
libtorrent.It seems that the problem only affects the original seeders (that have files with such a names on disk). If someone wants to download such a torrent,
libtorrentwill simply create new files without these characters in the name and use them further.@vincejv commented on GitHub (Dec 3, 2023):
Will also be an issue if someone migrates from Transmission/Non-libtorrent client to QBT/Libtorrent clients and vice versa, nevertheless, it's primarily a libtorrent issue, every tool out there, torrent clients & torrent creators - mktorrent, torrentfile, torf, does not strip off anything in the filenames, including uTorrent/Bittorrent, I don't see why libtorrent will go out of spec.