Error: spawn /usr/bin/dot ENOENT

[nixternal]

"/usr/bin/dot -Tpng,/run/user/1000/snap.obsidian/tmp-22262-UjL2HCdRHDQr" failed, Error: spawn /usr/bin/dot ENOENT

Also get this if just using dot. Running latest Obsidian snap on Ubuntu 18.04. If I run dot on that file from the command line, without the comma in between png & /run/user/1000/..... it works just fine. Any pointers will be greatly appreciated. Thanks!

[dko1905]

Same issue, although using Flatpak instead of Snap.

"/usr/bin/dot -Tpng,/run/user/1000/app/md.obsidian.Obsidian/tmp-57-m1d5DRyBJSFX" failed, Error: spawn /usr/bin/dot ENOENT

[ishfb]

Same issue on Ubuntu 18.04 having installed the plugin with Obsidian community plugins menu.

Looks like somewhere in the source code comma is used to concatenate dot parameters.

[dko1905]

It's probably a quick fix

[xokomola]

Got the same error on Mac OS. Args on the commandline should not be separated by comma. When you copy the command-line and change "-Tpng,/run/..." to "-Tpng /run/..." then it will generate a PNG correctly.

[everwitt7]

I ran into this issue too (on a Mac) and the error stems from a path issue to the executable. All you need to do is replace Dot Path in the community plugins tab with the output from this command.

> which dot
/opt/homebrew/bin/dot

dot was in my $PATH variable, but it seems like passing in the full path to the executable works, and you do not have to change any code...

[d0ssant0s]

Hi, I got the same issue (on a Linux Mint) and I'd rather avoid depending on a graphviz installation, so I've decided to play with d3-graphviz. This seems to work, but there's certainly a better or a proper way to use d3 in an obsidian plugin:

import { Plugin } from 'obsidian';
import { MarkdownPostProcessorContext } from 'obsidian';
import { createHash } from 'crypto';
// import {graphviz} from 'd3-graphviz'; => does not work :-/

export default class GraphvizPlugin extends Plugin {
  async onload() {
    console.debug('Load graphviz plugin');
    const processors = new Processors(this);
    
    this.app.workspace.onLayoutReady( () => {
      const d3Sources = ['https://d3js.org/d3.v5.min.js',
        'https://unpkg.com/@hpcc-js/wasm@0.3.11/dist/index.min.js',
        'https://unpkg.com/d3-graphviz@3.0.5/build/d3-graphviz.js'];

      for (const src of d3Sources) {
        const script = document.createElement('script');
        script.src = src;
        (document.head || document.documentElement).appendChild(script);
      }
      this.registerMarkdownCodeBlockProcessor('dot', processors.d3graphvizProcessor.bind(processors));
    });
  }
  onunload() {
    console.debug('Unload graphviz plugin called');
  }
}

export class Processors {
  plugin: GraphvizPlugin;
  constructor(plugin: GraphvizPlugin) {
    this.plugin = plugin;
  }
  public async d3graphvizProcessor(source: string, el: HTMLElement, _: MarkdownPostProcessorContext): Promise<void> {
      console.debug('Call d3graphvizProcessor');
      const div = document.createElement('div');
      const graphId = 'd3graph_' + createHash('md5').update(source).digest('hex').substring(0, 6);
      div.setAttr('id', graphId);
      div.setAttr('style', 'text-align: center');
      el.appendChild(div);
      const script = document.createElement('script');
      // graphviz(graphId).renderDot(source); => does not work

      // sometimes d3 is undefined, so there must be a proper way to integrate d3
      script.text =
        `if(d3!= undefined) { 
          d3.select("#${graphId}").graphviz()
          .onerror(d3error)
         .renderDot(\`${source}\`);
      function d3error (err) {
        d3.select("#${graphId}").html(\`<div class="d3graphvizError"> d3.graphviz(): \`+err.toString()+\`</div>\`);
        console.error('Caught error on ${graphId}: ', err);
      }
    }`;
      el.appendChild(script);
  }
}

HTH

[QAMichaelPeng]

@d0ssant0s , thanks for sharing the idea of using d3-graphviz, do you mind to send a PR of your change? I just don't want to make the change without creditting you as committer. Thanks.

[d0ssant0s]

@QAMichaelPeng I'm glad it was useful.

[QAMichaelPeng]

@d0ssant0s , commented. This is the first time I use github's pr review and not sure if I did it correctly. Please let me know if you didn't see the comments. Thanks.

[andreasio]

The experimental D3 feature doesn't work for me. But I'd prefer the traditional dot anyways.

I get the same ENOENT error.

I provide the path /usr/bin/dot but I can see that the Obsidian flatpak install only ask's for permission to home, media , mnt and run/media.

I dont know if this is related? That Obsidian flatpak (on fedora) at least, doesn't have access to the usr/bin folder?

OS: Fedora 37
Obsidian: 1.1.9
Method of install flatpak: flatpak install md.obsidian.Obsidian.flatpakref
Method of install graphviz: sudo dnf install graphviz

[lambainsaan]

I ran into this issue too (on a Mac) and the error stems from a path issue to the executable. All you need to do is replace Dot Path in the community plugins tab with the output from this command.

> which dot
/opt/homebrew/bin/dot

dot was in my $PATH variable, but it seems like passing in the full path to the executable works, and you do not have to change any code...

This worked for me.

[dane]

Setting the dot path to the value of which dot (/opt/homebrew/bin/dot) addressed this problem for me.

I'm running:

• MacOS Ventura 13.4.1
• dot from graphviz version 8.1.0 (20230707.0739)
• Obsidian 1.3.5 (Installer 1.3.5)