Bitwarden not launching when Security Center is enabled

I currently have to disable security center in order for it to work

Before disabling:

> journalctl -f | grep -i bitwarden
Jan 19 18:53:02 Y4M1-II systemd[9053]: Started snap.bitwarden.bitwarden-34dc335c-8809-4e0a-93bd-ff50745fb275.scope.
Jan 19 18:53:02 Y4M1-II kernel: audit: type=1400 audit(1737330782.273:433): apparmor="DENIED" operation="open" class="file" profile="snap.bitwarden.bitwarden" name="/mnt/home/870E4TB/yamiyuki/Documents/" pid=20039 comm="head" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Jan 19 18:53:02 Y4M1-II kernel: audit: type=1400 audit(1737330782.319:434): apparmor="DENIED" operation="rmdir" class="file" profile="snap.bitwarden.bitwarden" name="/mnt/home/870E4TB/yamiyuki/Documents/" pid=20042 comm="rmdir" requested_mask="d" denied_mask="d" fsuid=1000 ouid=1000

After launching Security Center:

Jan 19 18:54:17 Y4M1-II systemd[9053]: Started snap.bitwarden.bitwarden-ba517534-eea8-44b8-918b-122caf02f13c.scope.

Nothing pops up at all.

After disabling, it starts to work

> sudo snap get system homedirs            
/mnt/home

By disabling the security center, do you mean toggling off the “Require apps to ask for system permissions” setting, or disabling the snap as a whole?

Additionally, can you please share the result of:

getent passwd "$(whoami)"

and

echo 'echo $SNAP_REAL_HOME' | snap run --shell desktop-security-center

That way, we can get a better idea of what directory the home interface ought to be granting access to.

I won’t be home for a while, but my office desktop has similar setup:

jgamao@FTO-Y4M1:~$ echo 'echo $SNAP_REAL_HOME' | snap run --shell desktop-security-center
/home/jgamao
jgamao@FTO-Y4M1:~$ sudo snap get system homedirs
/mnt/home

I need both /home & /mnt/home because all the ones in /mnt/home are drives that are not the primary drive.