Concurrently running MakeMKV Installed via Flatpak
Posted: Sat Apr 26, 2025 5:47 pm
Hello Everyone. I'm creating this in the "advanced usage" forum because MakeMKV seems to "work" as expected when I use a single running instance. When I attempt 2 concurrent instances, things seen to fail (in a minor way).
I'm running Debian 12 with KDE. I have installed a "FlatPak" version of MakeMKV (v1.18.1 linux(x64-release)). My only issue with the single instance execution is that the FlatPak configuration doesn't allow the creation of the "MakeMVK_log.txt" within my home directory. Using "FlatSeal", I'm able to give that access and once complete, I get the debug file.
My true issue comes when running 2 or more instances of MakeMKV. I presume that since MKV is running in a "container", the application cannot determine if other MKV processes are running, so they share the same debug file. When running 2 or more instances, the debug file doesn't progress in chronological order (i.e. it appears that both instances write over the top of each other).
Neither here nor there, using a debug file in multiple instances within Flatpak containers appears to cause debug log file corruption.
Yes the solution is: "don't do more than 1 instance" and that will work. But, I thought I read somewhere that the application will increment the log file count (if the app can see multiple instances running). I guess I'm saying that in the flatpak situation, the app can't see its other instances.
I can provide additional information if needed. I can do some testing (if a flatpak install is available).
Thank you!
Larry Schapker
I'm running Debian 12 with KDE. I have installed a "FlatPak" version of MakeMKV (v1.18.1 linux(x64-release)). My only issue with the single instance execution is that the FlatPak configuration doesn't allow the creation of the "MakeMVK_log.txt" within my home directory. Using "FlatSeal", I'm able to give that access and once complete, I get the debug file.
My true issue comes when running 2 or more instances of MakeMKV. I presume that since MKV is running in a "container", the application cannot determine if other MKV processes are running, so they share the same debug file. When running 2 or more instances, the debug file doesn't progress in chronological order (i.e. it appears that both instances write over the top of each other).
Neither here nor there, using a debug file in multiple instances within Flatpak containers appears to cause debug log file corruption.
Yes the solution is: "don't do more than 1 instance" and that will work. But, I thought I read somewhere that the application will increment the log file count (if the app can see multiple instances running). I guess I'm saying that in the flatpak situation, the app can't see its other instances.
I can provide additional information if needed. I can do some testing (if a flatpak install is available).
Thank you!
Larry Schapker