Joplin: Links appear to be prefixed with working directory

[edrich49]

Environment

Joplin version: 1.0.187 (prod, linux)
Platform: Linux
OS specifics: Debian

Steps to reproduce

1. View the "Welcome to Joplin!" note in the "Welcome! (Desktop)" notebook.
2. In the viewer pane, click a link such as "Markdown syntax".
3.

Describe what you expected to happen

I expected the link to be navigated to, as exhibited by the tooltip -- "https://joplinapp.org/markdown/", whereas what actually happened was that I received an error dialog box: "/home/richard/Downloads/Joplin/https:/joplinapp.org/markdown: No such file or directory". ["/home/richard/Downloads/Joplin" was my working directory at the time I invoked the program.]

This error also occurs with Joplin version 1.0.179.

Logfile

log.txt

[bedwardly-down]

If you can remove the log text above and just upload the log.txt file, that should be enough. It's under your joplin-desktop directory.

[edrich49]

Apologies. Hope this is now satisfactory.

[rabeehrz]

I couldn't reproduce this issue on Joplin 1.0.187 desktop.

[bedwardly-down]

I can't reproduce this either. @rabeehrz, what Linux distro are you using? I'm on Artix Linux.

What browser are you using, @edrich49? Maybe it's tied to that specific one and that build version for Debian?

[mhimanshu712]

Couldn't reproduce in Ubuntu.

[edrich49]

Apologies. Hope this is now satisfactory.

[edrich49]

@bedwardly-down, I'm using the Firefox browser, version 68.5.0esr (64-bit) running under Debian Linux.

[stale[bot]]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[edrich49]

I still have this problem. Any more ideas, anyone, please?

[edrich49]

The problem is still present in 1.0.199.

[stale[bot]]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[stale[bot]]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.