Do yourself a favor, remove the Snap install and instead use the appimage. The appimage is the only officially supported distribution format for Linux, and it is the only format against which the developpers want to consider bugs.
I tried to install AppImage. After installing FUSE and change the file permission, I issued the following command (note I have to add --no-sandbox, reference):
./Obsidian-1.6.5.AppImage --no-sandbox
And then I encountered the following issue:
2024-07-10 05:38:20 Loading main app package /tmp/.mount_ObsidiWoJgn5/resources/obsidian.asar
Ignored: Error: ENOENT: no such file or directory, open '/home/eric/.config/obsidian/obsidian.json'
MESA-INTEL: warning: Haswell Vulkan support is incomplete
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
2024-07-10 05:38:20 Checking for update using Github
2024-07-10 05:38:21 Success.
2024-07-10 05:38:21 Latest version is 1.6.5
2024-07-10 05:38:21 App is up to date.
[6739:0710/133825.309262:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
[6739:0710/133848.397741:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
[6739:0710/133848.402084:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!
The installation just freeze there.
I suspect the machine I am installing Obsidian is too old? The CPU is Intel i5-4590.
Anyhow, I then tried to download and install the Debian package
sudo dpkg -i obsidian-1.6.5-amd64.deb
It successfully installed and the problem 2 and 3 originally mentioned in the thread are gone.
The only problem left is Templater plugin still can’t recognize the user scripts.
Very strange though, if I open chrome developer tool from Obsidian, Templater plugin can then recognize the user script and successfully create the new file.
After upgrading to the newest version of Ubuntu, Obsidian stopped opening by clicking on it. If I try to run it through the command line, it gives this error:
[23803:0911/165217.940398:FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /tmp/.mount_ObsidisP2Blh/chrome-sandbox is owned by root and has mode 4755.
Using --no-sandbox does fix the problem for me, but I figured I would add more info anyways, especially since having to go through the command line every time is inconvenient.