No output html - v1.7.3 on Debian

[mc0e]

Describe the bug

I'm getting no output, in a manner similar to what's described in #204, #218 and #251, but not identical. I'm using LMDE 6 (roughly Debian), Obsidian v1.4.16 installed from the .deb package, and Webpage HTML Export v1.7.3.

• If I try to export "Self-contained Documents", nothing is written.
• If I try to export "Multi-File Website", a lib folder is created with scripts and styles subfolders, and a bunch of files in there, but there is no html.

I get the export options, then when I click the Export button, I get a brief flash of a pop-up window. It might be empty, but it's quick enough to be hard to tell. In my case though the report in the top right of the window says that it's "Finished HTML" with a tick icon.

If I start obsidian from the command line, there's some output there before I export, but nothing from the export itself. It looks normal except for this line, which is output at startup, before I try to export.

libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)

Operating System

LMDE 6 (a Linux Mint edition of Debian bookworm), with everything up to date. Obsidian v1.4.16 Webpage HTML Export v1.7.3

To Reproduce I've tried to export by right clicking on files/folder, using the three-dots menu, and using what I think is called the ribbon, on the far left of the obsidian window. All do the same.

Screenshots The developer console shows just one line:

(2) failed to find render leaf     plugin:webpage-html-export:56581

[KosmosisDire]

Hi thank you, since linux is often the culprit behind weird behaviors is it possible for you to try and reproduce this on windows? Also please try to reproduce with a blank vault with no other plugins or files except a single very simple file. That will help me narrow down what the cause of this might be. Thanks!

[mc0e]

Hi thank you, since linux is often the culprit behind weird behaviors is it possible for you to try and reproduce this on windows? Also please try to reproduce with a blank vault with no other plugins or files except a single very simple file. That will help me narrow down what the cause of this might be. Thanks!

I've reproduced this on my linux system with a fresh vault, with one page added, the export plugin added, the folder set, and nothing else. I'll have a go at this on a windows system soon, though I'm not sure what that could tell you. I assume this isn't impacting every windows user (you could reproduce that yourself, and probably have effectively tested that already?), and if a fresh vault triggers it, then it's presumably not being caused by some aspect of my vaults.

[mc0e]

I've now also replicated this on a Windows 10 system.

• freshly downloaded and installed obsidian
• Created a single page, with just a page name and a single word of text.
• Installed the export plugin
• Attempted export of the page, with no settings changed except for choosing an export path, and enabling the option to open after writing.

Absolutely no other actions taken.

[mc0e]

On the Windows 10 system, I get this in the Obsidian Console log:

[KosmosisDire]

Did you select a file to export from the little sidebar thingy? The fact that it's non-finite makes me think that maybe there was a divide by zero?

[mc0e]

Yes, The above log output is from right clicking on the file, and exporting from that menu.

If I do it with the 'Export Vault to HTML' button on the far left, the log output indicates a slightly different call-stack leading to the error, but the 'non-finite' bit is the same.

This is still on windows. That error wasn't in the console log on Linux.

[KosmosisDire]

This is quite strange, and I am unable to reproduce it. On windows does it still create the lib folder with all the files? I'll look into it more but I am not sure I can do anything without being able to reproduce it. It's possible that the next version will fix thiss since I have done a lot of cleanup of the code which tends to make it more stable. I'll update this when that is released if no other progress is made.

[mc0e]

Yes, the lib folder is still created on windows.

Both operating systems were running on the same hardware. Is there any way that could be relevant? There was that error there before the export on Linux:

libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)

It looks like libva relates to Video Acceleration. Maybe it is related to my video hardware? It's a "NVIDIA GeForce GTX 1050 Ti with Max-Q Design"

[mc0e]

I get the same thing in a VirtualBox machine that I created using vagrant. See attached.

obsidian_export_vagrant_test.tar.gz

It takes a long while for vagrant to build the machine, and sometimes it might look like it's stopped, but eventually you get a LightDM login screen.

Log in as vagrant, pw=vagrant open a terminal, and run obsidian. open the vault at /home/vagrant/vault try to do an export.

[zeukterialpneumaion]

i am getting this on windows 10 ... running obsidian ,1.5.3 and v1.7.3 of the plugin ... same thing produces the "lib" folder, and within it the "scripts" and "styles" folders with js and wasm but no html....

[zeukterialpneumaion]

these are the plugins i am using:

[zeukterialpneumaion]

this is the error log:

[mc0e]

i am getting this on windows 10 ... running obsidian ,1.5.3 and v1.7.3 of the plugin ... same thing produces the "lib" folder, and within it the "scripts" and "styles" folders with js and wasm but no html....

It's a bit of a long shot, but what is your video hardware?

There's very little else in common besides the hardware in the environments I've reporoduced this in (linux, windows, and a VirtualBox virtual machine, but all running on the same laptop) that wouldn't also be shared with most other users. VirtualBox abstracts a lot of the hardware, but I imagine that aspects of the video hardware are exposed in order to make rendering reasonably efficient. Perhaps that somehow affects the function of the rendering system.

FWIW, I'm running a Lenovo X1 Extreme with a "NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] (rev a1)" video card.

[mc0e]

On the Windows 10 system, I get this in the Obsidian Console log:

Is there a way to get a more extended trace of how the error occurred with the values of the arguments passed to the functions at each level of the stack?

[mc0e]

I don't know what I've done differently, or if something has been changed upstream and automatically updated on my system, but I can get an export now. If I start from the little 'export vault' icon on the strip down the left of the window. I get a widget that allows me to select pages (which I haven't seen previously), and after selecting a few and running the export, it now works. Maybe what I had before was the result of an export with nothing selected?

What I'm testing with is very simple, but the only issue I currently see is that I have the plugin option selected to 'Add filename as title', but page headings generated from the file name are invisible. Looks like it comes from this css:

.mod-header {
  display: none !important;
}

[KosmosisDire]

Hi thanks, sounds like you hadn't updated to the latest version or something! The file picker has been there for a while.

The title is a known issue and it's fixed the betas (you can try the beta versions of you'd like)

[zeukterialpneumaion]

hi, sorry late to repond, ok, i am working on a think station p330 ...

• Processor Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz, 3696 Mhz, 6 Core(s), 12 Logical Processor(s) no separate graphics card just the internal:
  • Intel(R) UHD Graphics 630 ... it is now working i believe, have turned off the weighted graph implementation (which you say is experimental) which was i believe the cause in actuality.... that setting had been strangely kept in cache as being turned on previously and so was failing even though it was switched off and appeared to be so...after i deleted the previous files it had generated, the html was generated with a few exceptions... ... so thankyou ... i cleared all the caches and it sprang to life .... it hasd some issues about some pages not being generated... a few levels down in project structure, no exceptional content in them and simple names which is still a mystery ... but yes, thankyou for your work here...

[KosmosisDire]

I hope the experience with this should be better in the latest version 1.8.0. I will close this as both of ou figured it out, and I don't think it will be relevant anymore in 1.8.0. But feel free to open a new issue if that is not the case.