Skip to content
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

Received file location invalid for folders above home directory #52

Closed
Grumium opened this issue Aug 5, 2020 · 6 comments
Closed

Received file location invalid for folders above home directory #52

Grumium opened this issue Aug 5, 2020 · 6 comments

Comments

@Grumium
Copy link

Grumium commented Aug 5, 2020

Platform

Linux Mint 20 Ulyana
Warpinator 1.0.6+ulyana

Issue

Locations for received files above the user's home directory ~ are not recognized upon system startup.
Warpinator set to start automatically shows "invalid save location".

However, locations outside of ~ can be selected manually after startup and are valid throughout the active session.

@mtwebster
Copy link
Member

Can you be a bit more detailed? Do you mean system locations (outside of /home/) are invalid?

Is this location writable at startup?

@Grumium
Copy link
Author

Grumium commented Aug 5, 2020

Sure. If I set the Location for received files to any directory residing at or below /home/*user*/ these locations are valid even after system reboot. In contrary, whenever I choose a directory like /mnt/something or /media/something_else Warpinator throws the error "invalid save location" after reboot, indicating that it is either missing permissions or cannot find the corresponding directory. However, I can manually select the directory again choosing "Other..." -> "+ Other Locations", which works until I reboot.

@Grumium
Copy link
Author

Grumium commented Aug 5, 2020

Okay, chmod a+rwx solved it. Sorry!
I am wondering why Warpinator does not complain about missing permissions when I set the directory manually at first? Warpinator does not run as root.

@mtwebster
Copy link
Member

That is weird - do you remember its permissions before you changed it? It'd be better if it worked with normal permissions - a+rwx scares me :)

@Grumium
Copy link
Author

Grumium commented Aug 5, 2020

Yes, 0755 rwx-rx-rx is not working, 0777 rwx-rwx-rwx works, even without a. I can also take ownership of the directory as the local user to solve the issue.

@mtwebster
Copy link
Member

Oh then all of this makes sense, if you didn't own the folder. I would personally go with owning the folder and back to 755 before opening it for anyone, though in practice this probably won't matter for you.

Regardless I think this can be closed. I may reword the error page to mention permissions/ownership more explicitly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants