Hi,
I wonder if it is possible to see what settings a flatpak installation is using inside the container?

I'm running manjaro and would like to use a program called xmind8.
I can install it from the AUR repository but then it have some issues and work sub-optimal.

When I install the flatpak version of the same program it runs smooth except it is limited when connecting to the environment e.g. for links inside xmind can not be followed to the internet and it will not open files if I click the file but I have to open them from inside the program.

Flatpack installed an environment in the container e.g. the nvidia graphics driver, the same version I'm using in the OS.

I would like to make the AUR version work since I do not know what is wrong but think it might be a settings issue I was wondering what setting is used in the container? E.g. what settings is the nvidia graphics driver using?
Is it possible to see that?

AppImages & flatpacks usually mount the file so it's seen as a subdirectory, and execute the file that way. You should be able to get in and copy the config to your homedir. Check /etc/mtab or /proc/mounts for the mount dir.

I read /proc/mounts and /etc/mtab and have a hard time deciphering where flatpak is hiding.
I run the flatpak program while reading the files.
Here is the printout:

proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
sys /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
dev /dev devtmpfs rw,nosuid,relatime,size=16399112k,nr_inodes=4099778,mode=755,inode64 0 0
run /run tmpfs rw,nosuid,nodev,relatime,mode=755,inode64 0 0
efivarfs /sys/firmware/efi/efivars efivarfs rw,nosuid,nodev,noexec,relatime 0 0
/dev/nvme0n1p2 / btrfs rw,noatime,ssd,space_cache,subvolid=256,subvol=/@ 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev,inode64 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
cgroup2 /sys/fs/cgroup cgroup2 rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot 0 0
pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0
none /sys/fs/bpf bpf rw,nosuid,nodev,noexec,relatime,mode=700 0 0
systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=11794 0 0
mqueue /dev/mqueue mqueue rw,nosuid,nodev,noexec,relatime 0 0
hugetlbfs /dev/hugepages hugetlbfs rw,relatime,pagesize=2M 0 0
debugfs /sys/kernel/debug debugfs rw,nosuid,nodev,noexec,relatime 0 0
tracefs /sys/kernel/tracing tracefs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /tmp tmpfs rw,nosuid,nodev,size=16408856k,nr_inodes=409600,inode64 0 0
configfs /sys/kernel/config configfs rw,nosuid,nodev,noexec,relatime 0 0
fusectl /sys/fs/fuse/connections fusectl rw,nosuid,nodev,noexec,relatime 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,nosuid,nodev,noexec,relatime 0 0
none /run/credentials/systemd-sysusers.service ramfs ro,nosuid,nodev,noexec,relatime,mode=700 0 0
/dev/nvme0n1p2 /home btrfs rw,noatime,ssd,space_cache,subvolid=257,subvol=/@home 0 0
/dev/nvme0n1p2 /var/log btrfs rw,noatime,ssd,space_cache,subvolid=259,subvol=/@log 0 0
/dev/nvme0n1p2 /var/cache btrfs rw,noatime,ssd,space_cache,subvolid=258,subvol=/@cache 0 0
/dev/nvme0n1p1 /boot/efi vfat rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /run/user/1000 tmpfs rw,nosuid,nodev,relatime,size=3281768k,nr_inodes=820442,mode=700,uid=1000,gid=1000,inode64 0 0
gvfsd-fuse /run/user/1000/gvfs fuse.gvfsd-fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0
portal /run/user/1000/doc fuse.portal rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0
/dev/nvme0n1p2 /run/timeshift/backup btrfs rw,relatime,ssd,space_cache,subvolid=5,subvol=/ 0 0

Where do you think the flatpak program resides?

That is with the flatpack loaded and running?

I have found AppImages mounted on /tmp/mnt???? but I have hardly any experience with flatpacks.But it stands to reason they are mounted somewhere, somehow, as configs, libs and programs need to be accessed in a form they recognise.

Yes that is when xmind is running as a flatpak.
I will investigate further, if you can think of anything, do not hasitate to post again.

Really you need to check inside the flatpack environment (some sort of chroot I guess), not your regular filesystem.

Or, maybe the flatpak comes as one big file (IDK, I don't use these things)? Chances are, you can open it with an archive manager and look inside.

Also please tell us why you think you need this. Mayube there's a better way to solve your actual problem.

I want to see what settings they use inside the flatpak container to make xmind8 work so well when I can not make it work good with the install from AUR.
If you have a suggestion on how to make xmind8 work well on majaro, installed from AUR I'm all ears.
What I have found out so far is that the AUR version uses 24 (some units) in load of my nvidia card while stuttering and the flatpak version uses 60 and have a fuent motion. So basically the AUR version does not use my graphics card like it should and as a result becomes very sluggish. Also the flatpak version uses GTK2 instead of GTK3 which the AUR version uses. It might be other stuff wrong with the AUR version as well but that is a start.

The flatpak manpage lists standard locations for flatpaks:

Thanks for the reply!

Perhaps you also know in what files the settings for the nvidia driver is?
Normally I have found out that they are stored in either of these files
I do not have any of them.

what I have with nvidia, xorg and xinit in the name is:

Under /var/lib/flatpak/ and nothing under ~/.local/share/flatpak/