-
Notifications
You must be signed in to change notification settings - Fork 274
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: LS-005 when adding torrents or magnet links. #1085
Comments
Same here. Transmission daemon work on Asus RT-AC56U, client on Mac OSX Sierra. |
Exactly the same here. Remote (on local lan):
Local:
Remote GUI 5.14 build bb79014 |
as usual unhappy and sad maс os. I don't yet understand what is happening with the program in this operating system. A code of 5 lines causes a crash only in this sad OS. :)) Perhaps there is a reason in the open source compiler for this system. |
To be fair, it doesn't crash the application and after clicking 'OK' the transfer starts anyways, so it's more an annoyance than a major bug. |
This is a serious mistake, because I enclosed the code in try-cath. Without this protection, the program would immediately crash. Protection allows you to continue execution. |
I saw that, but is that in order to work around the problem in the first place? Any idea what the exception is (if it was raised)? Maybe there's a way to fix it fully. I could try and do so if I find a way to compile the program. |
I entered protection from the failure for other reasons. Possible problems in maсos are:
There is nothing to cause a mistake. |
I got rid of this error. Basically, I had to manually type in the destination folder path, but here are my steps: |
Hi @g000phy! You nailed it! That exception raised (error LS-005) is all about the destination directory:
When you first open a torrent or magnet link, you'll notice that the 'destination directory' is empty, and you're still able to click 'OK', add the torrent (with the LS-005 error message) and get it to start. As you pointed out, if you fill the 'Destination directory' once, that parameter gets saved in transgui.ini: [AddTorrent.] ...and any future torrent download will pick it up from there, preventing the error LS-005 from being raised. So in short, as you mentioned, in 'Download dir' you paste the download dir path on the server and the issue goes away. Thanks a lot for finding this out! This now makes transmission remote GUI much nicer to use :) |
Note that the bug still exists, but the workaround is so simple and effective I think there's no point leaving this issue open. I'm very happy with the resolution anyways. |
I'll see when the time comes. :) |
Where can I find the transgui.ini on macOS? |
On Mac it's in /Users//.config/Transmission Remote GUI/transgui.ini |
Something didn't work well, so in your home directory: .config/Transmission Remote GUI/transgui.ini Note that this is an invisible directory |
The workaround does not seem to work for me. |
Odd, did you make sure that LastDownloadDir= was set correctly in your ini file? |
Yes, this is in the .ini file, it is a valid path on my NAS: |
Sorry to hear that, not sure why it is happening for you :/ |
The error has been fixed. I dont know your version of the TRGUI. The error was in the function cbDestFolder.Items.Insert (0, s); Whoever has a problem with LS-005 is no longer receiving this message. |
You are absolutely right, the update did not go through because macOS did not let it, it needed one more confirmation and I was still running the old version. |
Hi,
I've been successfully using transmission-remote-gui v5.14 on Mac OS 10.12.6 connecting to transmission-daemon 2.93 (3c5870d4f5) on Arch Linux on a local LAN. I can add torrents and magnet links, but whenever I do so, I always get an popup error message "Error: LS-005. Please contact the developer". The error does not seem to prevent me from actually starting the transfer, and looking through Please see attached screenshots. Looking in main.pas:2548 it seems to be related to the destination directory. Not sure why, both my "download-dir" and "incomplete-dir" settings on the daemon are set to the same writeable local directory /raid5_volume/Downloads_BT.
Any idea what is going on?
The text was updated successfully, but these errors were encountered: