-
Notifications
You must be signed in to change notification settings - Fork 10
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
Filebot not found #32
Comments
No problem, this usually boils down to one of a few things on windows:
|
It's best to just assume that the |
@rednoah, Yeah my module starts with checking the path, but it dosen't always work, particularly when permissions and strange path modifications for deluge users come in. I'm on the lookout for more places to check. |
Hi. Filebot is installed at C:\Program Files\FileBot\Filebot.exe C:\Users\Fexigo>filebot -version Same permission for both programs. |
okay, just to make sure it's not the permissions, when you start deluge, can you right click it and hit run as administrator? If filebot still doesn't show up it'll have to be something else. |
@Laharah It's kinda tricky on Windows. I'd call commands with Actually, many users somehow end up with fucked up If FileBot is managed by the Windows Store, then the executable will be here:
|
I'm having the same issue but on Mac OS. "Filebot version not found". I have Filebot installed and Deluge, and Filebot Tool works too. Any ideas? |
Sure, can you open up Terminal and tell me the output of these commands?
And can you also tell me a little about how your deluge is setup (eg. is it running on a server or locally)? |
On |
Hi. Also tried to reinstall deluge, filebot multiple times. |
@fexigo can you tell me a bit more about your setup? Is deluge in client-server mode or in "classic" mode (you can check by going to preferences -> interface)? What version of windows are you on? |
Hi. Im using classic mode and its a windows 7 pro computer. The strange thing about this is when i right click the torrent and choose Filebot Tool i can see in task manager that two processes of Filebot *32 is started. And if i try to reboot my computer i got a system error that telling me that the application was unable to start correctly (0xc0000000XX). |
Hmm, okay, it seems like something else is going on. I've posted a release with some extra debug logging here: https://github.com/Laharah/deluge-FileBotTool/releases/tag/1.1.9 Can you run it with logging on (see instructions here) and send me the logs? |
Wow! That is strange. Now its working. hmmmmmmm |
That is really weird, I only added some logging. Well, if you run into problems, feel free to post back here! I'm going to keep this open incase @Inglend needs more help. |
I was a little bit fast. When i launch deluge-debug.exe everythings works. But if i lanuch deluge.exe i still got Filebot not found. |
are deluge-debug.exe and deluge.exe both in the same folder? Are you launching them both the same way from the command line? |
You can correctly install
|
Yes now it works! thank you! |
Sorry, i have been away for some time. If i start deluge with just using the icon its not working. If i start deluge debug from cmd line it working. I have also tried to start deluge from cmd line without any success |
okay this a weird one. Since you can't get debug logs, you'll have to download and install this special debug version I made: https://github.com/Laharah/deluge-FileBotTool/releases/tag/1.1.9-debug It will log the filebot error to the filebot version string (where it normally says "Filebot not found" in the rename dialog). Could you copy what it says to me? |
Following all the suggestions posted in this issue, I still run into the "File not Found" problem. Using your debug release, it shows "[Error 5] Access is denied." What I've found is that upon restarting my computer, there are no issues. Everything launches and doesn't indicate any problems. However, if Deluge is closed and reopened, the problem returns. Additionally, when Deluge is first opened, a Filebot.exe process is started (which I assume is normal). However, when Deluge is closed, the Filebot.exe process is not ended. I anticipate this could be part of the issue, though ending the process doesn't seem to help. If Deluge is reopened multiple times, multiple Filebot.exe processes stack up. |
The filebot launch when starting deluge is just a version check and making sure that filebot.exe can be accessed, it should close almost immediately. With the Frankly, I don't really know what could be causing these problems. The fact that the debug version of deluge works and the normal one doesn't is mystifying enough. The fact that it only runs once after a reboot is also really weird. What happens if you reboot, run deluge, quit, kill the filebot task that's still running, and then relaunch deluge? Does it still give you access denied? Can you double check the permissions? Check and reset the permissions for the entire |
Hi
I got an windows 7 computer with the latest version of Deluge, Java, Filebot and FilebotTool plugin for Deluge. But I still get the message "Filebot not found". Filebot -version is working, and I can start Filebot.
What am I doing wrong??
The text was updated successfully, but these errors were encountered: