@sgibbers17 Sounds like you did the setup for RMTV correctly.

From this I can gather that anything RMTV application related is working (database, reading filename, data retrieval etc).

The issue yo may run into is the file access rights.
I'm not a Linux expert either, but the problem can be found in two places:
- What access rights does the user running RMTV have?
- What access rights are needed to access your media files and directories?

Keep in mind: I'm not a Linux expert and changing access rights of files may be done more refined as what I suggest here.

First you can check the current access rights of you file like so:

ls -l videofile.mp4

Which returns something like this:

-rw-r--r--  1 hans  staff      59443 May 10  2015 videofile.mp4

The first characters (-rw etc) indicating what type of access is set for this file.
"-rw-r--r--" -> In this case the first character indicates if this is a file ("-"), directory ("d") or linked file ("l" an L).
"-rw-r--r--" -> The next set of 3 characters indicate "r" (read), "w" (write), "x" (execute) or "-" (none of the options) for the owner of the file.
"-rw-r--r--" and "-rw-r--r--" -> The 2nd set of 3 does the same or the "group", and the last 3 for "everybody".

Note: You can use my chmod-calculator to determine what the number "777" means. It is also good to read up on how the access rights in general work under Linux. Maybe this article is a good start.

To see if this is a problem, you can try one file first to see what happens, this should provide full access to anyone.

chmod 777 videofile.mp4

which then shows (with "ls -a videofile.mp4") as:

-rwxrwxrwx  1 hans  staff      59443 May 10  2015 videofile.mp4

If this works then you can check the directory that is holding the file and elevate access rights to the directory and all its files with.
Note: full access to the directory may be needed for RMTV to create new files, so maybe this may be needed anyway.

chmod -R 777 video_directory

(assuming "video_directory" is the directory holding your media fies)

Note: "777" means full access for everybody, not sure if this is something you want to limit or not, and in that case you'll need to dig more into the way user access works under Linux.

If this is not working then we'd have to look at who the owner is of the file, but that goes a little beyond what I can recommend is "best".

Hope this helps, feel free to come back to this topic so we can figure this out 😊 

You can avoid playing with the permissions by downloading the version you need, extracting it where you want it backed up to, and then copying it from there to your home directory. see my last post in the below linked thread.

https://www.tweaking4all.com/forum/linux-software/rmtv-not-respecting-dragging/#post-6116

I'm running Ubuntu, not Mint, but a pretty close environment. Mine reports failure every time I try to rename files. But it succeeds in actually moving them!

I dug into the issue with the strace tool and here's what's going on:

rename("/mnt/video/TV/Aqua Teen Hunger Force/Aqua Teen Hunger Force - 02x16 - Broodwich.avi", "/home/me/.local/share/Trash/files/Aqua Teen Hunger Force - 02x16 - Broodwich.avi") = -1 EXDEV (Invalid cross-device link)

and it shows up in the log like this:

FAILED:  /mnt/video/TV/Aqua Teen Hunger Force/Aqua Teen Hunger Force - 01x01 - Rabbot.avi -> /mnt/video/TV/Aqua Teen Hunger Force (2000)/Season 01/Aqua Teen Hunger Force - 01x01 - Rabbot.avi (Failed to move to TrashCan)

My best guess:

- While renaming a file, it tries to add it to the trash for some reason?

- It assumes the trash is in my home folder

- Yet I am using a separate mounted fileserver

- It uses a rename syscall to move it to the trash, which fails because it's a separate filesystem

@aardvarko Hi Aardvarko 😊 

First off: its never a good idea to hijack an existing thread, as it may disappear in the background noise for me (overloaded mailbox) and others may not find your topic if they run into a similar issue. Not to mention the original topic starter getting post related to your questions as well, even if this is undesirable.
It also prevents others from seeing your new question, so they wouldn't even respond (granted: not too many people chime in here). 
So always start your own thread 😉  (no harm done, just letting you know)

Having said that:

- Moving to the Trashcan is an option you can disable - which option are you using right now?

- Linux distros are (IMO) a pain and a mess when it comes to consistency. As a non-Linux user it is really a pain to determine what actually is the Trashcan on "all" distros.
- As a non-Linux user it is difficult to test Linux versions as well

As far as I recall (you're the first one reporting this issue, maybe you're the only one using the move to trashcan option) RMTV first tries to move with a system call, which in your case could fail. If that fails, it will try to copy the file, and then (depending on the options set) either delete the original, or move the original to the Trashcan.

So your first error could because of the initial move attempt (it's not easy to determine if the file is on a local disk or a shared network drive - again: lack of consistency, so this is why I have it try a move first, and if it fails, then use the copy/delete mechanism).

What is the location of your Trashcan? (just so I can try to make this function more compatible with other Linux distros)

@hans Thank you!

I appreciate your image showing me the setting. I looked several times and completely overlooked that dropdown!

So trash cans do indeed vary wildly per distribution and machine. The location identified (~/local/share/Trash) is correct... for the filesystem containing my home folder. But it's per volume/filesystem, so the location I was working from (/mnt/video) does not use that folder.

Honestly, it's a little unusual for software outside of the big families (GNOME, KDE) to support trash on linux--probably for this reason.

Now that I have disabled the trash support (using "MOVE original to the new location") it is working swell. I would encourage other *nix users finding this thread to try the same if they are encountering errors.

I'll try and see if I can come up with something to quick and easy identify if a file (under Linux) resides on the "main" disk or on an external disk or network share.
Any ideas or suggestions are welcome.

(using mount etc to identify this may not really be a proper solution for tasks like copying/moving a file 😉)

Anywho: Glad things work well now for you 😊