lua error - Invalid Argument
Closed this issue · 7 comments
On Windows 10, I get the following error in the VLC log file...
lua error: Error loading script C:\Program Files\VideoLAN\VLC\lua\intf\trakt.luac: trakt.lua:313: /T:/Media/Video/TV/Band.of.Brothers/Season.01/Band.of.Brothers.s01e01.Currahee.1080p.mp4: Invalid argument
Installation and activation work fine. The Windows Service is running. I tried v2.0.0a1 and v2.0.0a1.dev. And tried re-installing VLC. Also tried both x64 and x86 versions of VLC (with corresponding TraktForVLC version).
Same error every time. Any ideas?
Changing line 313 of trakt.lua with this:
local fil = assert(io.open(string.sub(fileName, 2), 'rb'))fixed the problem for me. But that's NOT the right way to fix the bug, obviously.. I think that's something related with the filename under Windows and having DRIVE_LETTER:/PATH/FILENAME rather than /DRIVE_LETTER:/PATH/FILENAME should solve the bug.
In my case I had to remove the first two characters to achieve the correct pattern, probably I had some white-space or whatever at the start of the filename and removing the first char was not enough. That's probably something to consider for a real fix.
After the edit I'm getting another error message:
[000000000264bb90] [trakt] main interface error: connection failed: Connection refused by peer
[000000000264bb90] [trakt] lua interface error: (call_helper) Command: "date" "--format" "%s.%f"
[000000000264bb90] [trakt] lua interface error: (call_helper) Command exited with code -1
I don't think it's related to my edit but I want to be sure before opening a new issue..
Where is your trakt.lua file?
I only have a trakt.luac file under .../VideoLAN/VLC/lua/intf
You should open an issue for that other error - I get that too.
Hm, it seems the URI provided by VLC on WIndows 10 is not in the right format. That's kinda weird... I'm wondering why there's a / at the beginning... Could you please run VLC in debug mode (-vv) and paste the full log ? It would help me see what VLC gives.
Also, @Ale46 - Please open an issue for the second problem. I'll need more details on it and I don't want to pollute this thread.
Found the problem for this issue. Will push a fix soon.
Perfect!
Seems to be working fine now on the newest dev version
Thanks for the confirmation!