Links like file.pdf #page=pagenumber get a double #page=pagenumber when clicked and fail

OS: Linux 6.17.0-118023-tuxedo #23~24.04.1tux1 SMP PREEMPT_DYNAMIC

Windowmanager: sddm

Desktop: XFCE4

Obsidian Vers. 1.12.7 Installer 1.8.10 no updates are found.

Happens without and with the plugin Better File Link V 1.6.0, no more plugins. I installed BFL because the issue occured and I doubted my ability to create proper file links by hand or drag&drop.

I’m not allowed to use links in here. Not sure how far I do have to truncate/obfuscate the file information that it will pass that gatekeeper.

Steps to reproduce

Create a link to a pdf-file (doesn’t matter which way, except drag&drop). The link works, the pdf-file is opened in the external viewer.
Add a #page=pagenumber behind …pdf like this … /file.pdf #page=381 (without the space)
A click on the link fails with a popup stating that the file … / file.pdf #page=381#page=381 cannot be found.
Somehow somewhere the #page=381 get’s duplicated.

Did you follow the troubleshooting guide? [Y/N]

Yes

Expected result

pdf file should open like I put the “file: … file.pdf #page=381” into the address-line of the browser or
xdg-open “file: … file.pdf #page=381” in the shell.

Actual result

A popup shows up stating the file cannot be found:
Error Message:
Failed to open URI.
Error when getting information for file “/ path/ file.pdf #page=381#page=381”. No such file or directory.
file path/ filename.pdf %23page=381%23page=381

Environment

SYSTEM INFO:
Obsidian version: 1.12.7
Installer version: 1.8.10
Operating system: #23~24.04.1tux1 SMP PREEMPT_DYNAMIC Fri May 8 12:59:30 UTC 2026 6.17.0-118023-tuxedo
Login status: not logged in
Language: de
Insider build toggle: off
Live preview: on
Base theme: adapt to system
Community theme: none
Snippets enabled: 0
Restricted mode: off
Plugins installed: 1
Plugins enabled: 1
1: Better File Link v1.6.0


Additional information

It works with a line like this:

(the line gets deleted with an error message that I cannot use file links here)
created via drag&drop + adding #page=381 manually. Even if the file resides in an nfs-mounted NAS-folder. This way the correct page is show in the embedded picture. It’s possible to copy the link, paste it and add f.e. #page=392.
But I’m not able to create a similar line from scratch manually. Then above error occurs.

The culprit was the link to the troubleshooting guide.Is there a way to edit the post to improve the file:///path/file.pdf information?

I don’t understand you, maybe we close this thread and you try again?