You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tribler 8.0.7, when Windows OS reports the error (ERROR_INVALID_NAME, 123 (0x7B)) message, "The filename, directory name, or volume label syntax is incorrect.", Tribler simply... stops the download. There is no message or error reported in WebGUI.
System errors like this should be reported so it is easier to interpret why Tribler stopped.
The text was updated successfully, but these errors were encountered:
I can create a similar type of situation in Ubuntu:
Start a download, set the location to some removable medium: I used a USB stick.
Exit Tribler
Remove the USB stick.
Restart Tribler. The download will just sit there on "Downloading 0%" and not do anything.
The logs have this message:
INFO:tribler.core.libtorrent.download_manager.download_manager:Starting download: filename: None, torrent def: <tribler.core.libtorrent.torrentdef.TorrentDef object at 0x73f5a5bd9060>
INFO:tribler.core.libtorrent.download_manager.download_manager:Destination directory does not exist. Creating it: /media/quinten/USB DISK
ERROR:tribler.core.libtorrent.download_manager.download_manager:Unable to create the download destination directory.
Traceback (most recent call last):
File "tribler/core/libtorrent/download_manager/download_manager.py", line 713, in start_download
os.makedirs(destination_directory)
File "/usr/lib/python3.10/os.py", line 225, in makedirs
mkdir(name, mode)
PermissionError: [Errno 13] Permission denied: '/media/quinten/USB DISK'
We need to think of a way to communicate to the user that the download is "broken".
Tribler 8.0.7, when Windows OS reports the error (ERROR_INVALID_NAME, 123 (0x7B)) message, "The filename, directory name, or volume label syntax is incorrect.", Tribler simply... stops the download. There is no message or error reported in WebGUI.
System errors like this should be reported so it is easier to interpret why Tribler stopped.
The text was updated successfully, but these errors were encountered: