No output

The place to discuss linux version of MakeMKV
Post Reply
flatpak_user
Posts: 1
Joined: Mon Oct 27, 2025 10:36 am

No output

Post by flatpak_user »

Hi,

I am using MakeMKV version 1.18.2 from flatpak.
When I create the mkv the process looks just fine, but the folder that is supposed to be created is just not there at the end.
When I try to create the folder beforehand I still get the message that the folder is not present and will be created.

I suppose it is some problem with flatpak and the mapping of the file system or some persmission issue.
Any one seen this and can help?
bluewestshadow
Posts: 1
Joined: Mon Aug 24, 2026 10:23 am

Re: No output

Post by bluewestshadow »

Hi, I assume you already solved your flatpak problem. Just in case and if any other struggle:

Yes it's annoying, that MakeMkv does not tell that output folders are not accessible. I guess this is not or not easy possible to detect since flatpak is only an opbtion. For devs: maybe write a 0kb file to destination directory and check if it can be accessed after write?

To solve the problem on user side. The Prroblem is that flatpak and all other of those technologies (snap - iikks, appamor) are sandboxes. Thats for security reasons. Every sandbox has its configuration with permissions, file access a.s.o.

You can check this by:

---

bluewestshadow@valhalla:~$ flatpak info --show-permissions com.makemkv.MakeMKV

#Output:

[Context]
shared=network;ipc;
sockets=wayland;fallback-x11;
devices=all;
filesystems=xdg-videos;xdg-config/kdeglobals:ro;~/.MakeMKV:create;

[Session Bus Policy]
com.canonical.AppMenu.Registrar=talk
org.kde.kconfig.notify=talk
org.kde.KGlobalSettings=talk

[Environment]
JAVA_HOME=/app/jre
PATH=/app/jre/bin:/app/bin:/usr/bin
--

as you see the filesystem access is relativ restrictive. I do my secure copies on an other HDD than my homedir with 2TB - mounted as '/media/store' and my ripping dir is under './Store/Convert/Video/Rip/'. So path I have to access within the sandbox is: '/media/Store/Store/Convert/Video/Rip/' Now I had the same Issue as you. To tell the sandbox, that you want to access other parts of your filesystem just extend it by:

--
bluesestshadow@valhalla:~$ sudo flatpak override com.makemkv.MakeMKV --filesystem="/media/Store/Store/Convert/Video/Rip/"
--

you always can check changes you made to sandbox config with:

--
bluesestshadow@valhalla:~$ flatpak override --show com.makemkv.MakeMKV

#Output:

[Context]
filesystems=/media/Store/Store/Convert/Video/Rip;
--

Now lets have a look how our sandbox config looks like now:
---
bluewestshadow@valhalla:~$ flatpak info --show-permissions com.makemkv.MakeMKV
[Context]
shared=network;ipc;
sockets=wayland;fallback-x11;
devices=all;
filesystems=/media/Store/Store/Convert/Video/Rip;xdg-videos;xdg-config/kdeglobals:ro;~/.MakeMKV:create;

[Session Bus Policy]
com.canonical.AppMenu.Registrar=talk
org.kde.kconfig.notify=talk
org.kde.KGlobalSettings=talk

[Environment]
JAVA_HOME=/app/jre
PATH=/app/jre/bin:/app/bin:/usr/bin
---

As we see now the sandbox knows that we want to access this path. Restart all running MKV instances and try it out. It should work now ;)
Post Reply