Error caught by UI! Error: Invalid PDF url data: either string or URL-object is expected in the url property.

[Haoxiyang-bio]

What happened?

First, I recently switch my operation system from WIN11 to ubuntu22.04. I saved my logseq files and try to use it on my linux platform.

I use logseq to record my reading progross just like others. i use zotero to store PDFs and use logseq to import the pdfs, I use logseq's pdf highlight tool and screenshot tool and save the links to the blocks ,so i can redirect the position in the PDFs when i click the links. this perform well on WIN11 before. But when i import the Previous logseq files directory（Generated on WIN11 ） to Logseq on Ubuntu 22.04, Everything looks OK, but when I click the links, it cannot redirect to the corresponding position and the logseq collapse with error information on top right corner (Error caught by UI! Error: Invalid PDF url data: either string or URL-object is expected in the url property.) and note me to REBUILD, RELAUNCH and CLEAR. I try this but when i reopen logseq, the same thing appears.
I also downloaded the previous logseq version on linux and this did not resolve the problems.

can the logseq files(including assets, journals...) saved in windows be used in linux such as ubuntu?

Reproduce the Bug

go to a pdf link and click the reference links generated using the highlight mode or area highlight
Then the logseq collapse.

Expected Behavior

No response

Screenshots

file:///home/mike/%E5%9B%BE%E7%89%87/%E6%88%AA%E5%9B%BE/%E6%88%AA%E5%9B%BE%202022-11-08%2014-48-38.png

Desktop Platform Information

problems occur:
Logseq-linux-x64-0.8.10.AppImage
Ubuntu 20.04

previous platform logseq run normally:
win11
previous logseq version run normally:
Logseq-win-x64-0.7.4.exe

Mobile Platform Information

No response

Additional Context

No response

[Liam-Scott-Russell]

@Haoxiyang-bio Did you ever end up fixing this? If so, would you mind explaining how?

[Haoxiyang-bio]

@Liam-Scott-Russell sorry about my late response. It seems that it is hard to solve the problem. Change the file path of logseq databases did not work. Finally, I turned back to Windows.

[michaelaye]

same problem here using the recommended way of setting the storage path on Linux using the tilde: ~/Zotero.
Making the path absolute removed the issue on Linux, but now I have the problem that this path is synced to my OSX setup where the Zotero storage path is different, so this is still a problem with the current Zotero implementation.

Version: 0.8.18 on popOS (Ubuntu derivate)