Page 1 of 1

Linux version cant' allow me to save mkv files on a second drive

Posted: Wed Nov 18, 2020 5:54 pm
by gg2tok
Hi,
I am runing Elementary 5.1.7 on one box, and Ubuntu 20.04 on another one.
The 2 boxes are identical, but the os version.
I have the snaped version 1.15.3 installed. I have my / on a 120GB ssd drive and all Data on a second 3TO drive.
So, when I try to create mkv files from a BR, the space is too small on the / ssd drive.
I tried to change the destination path, but it doesnt propose the /mnt directory where is mounted my 3TO drive.
I tried to create on the desktop a simlink to the right destination folder, but then, the saving failed for a permission issue.
I have joint a snapshot of the issue, to help to clarify my issue.
The snapshot is with Elementary, but the issue is the same with Ubuntu.
Thanks for any help.
Cheers.
gg2tok

Re: Linux version cant' allow me to save mkv files on a second drive

Posted: Wed Nov 18, 2020 7:39 pm
by Woodstock
Does the user you are running MakeMKV under have access rights to /mnt? The browse window should show it if you do.

Re: Linux version cant' allow me to save mkv files on a second drive

Posted: Thu Nov 19, 2020 7:20 pm
by gg2tok
Thanks Woodstock for your quick reply.

I understand your point, but as you can see in picture 1, all my folders are root and 755, no difference between /bin or /mnt. It shows /bin or /home, it should show /mnt. One thing that makes me confused, it shows /data-dir or /lib32 or /meta, folders that are NOT on my machine…

Anyway, I finally got a workaround, it seems that the snaped permissions « Read/Write files on removable storage devices » (the one at the bottom of the list) allows me to see the subfolders of the symlink I created on my desktop. Then after that, I could go and save where I wanted.

My saving issue is fixed, remains only the folders difference between what it proposed and what is really on my box.
Thanks again.
Cheers.
gg2tok

Re: Linux version cant' allow me to save mkv files on a second drive

Posted: Fri Nov 20, 2020 12:22 am
by Woodstock
That seems to be a common theme with packages and package managers... Trying to get permissions over and above what we old folks think as normal. You can have some file set to 777 permission, but either selinux or a package manager gets in the way of actually USING the file.