Can't get dbus working on M1 as guide suggests

[s1gtrap]

Description

Hi, I'm trying to get this working on an M1 machine.

This is my 5th or so attempt but I’m fairly certain it is a clean install (having run brew unlink/brew uninstall for dbus, zathura-pdf-poppler, zathura and girara. This also seems like it might be a dbus problem as the current problem is seemingly only with dbus, but I figured I would try here first as others seem to have resolved their dbus with help from here.

Following the :help vimtex-faq-zathura-macos docs:

1. brew install dbus finishes successfully

2. So does adding export DBUS_SESSION_BUS_ADDRESS="unix:path=$DBUS_LAUNCHD_SESSION_BUS_SOCKET” to .zshrc, naturally.

3. I assume /usr/local/opt/dbus/share/dbus-1/session.conf is substituted by /opt/homebrew/Cellar/dbus/1.14.10/share/dbus-1/session.conf in my case, since I’m on an M1, but if that’s true the entry is changed to the following

   <auth>DBUS_COOKIE_SHA1</auth>
   

4. This is where it starts to go wrong…
Upon reloading the shell and running brew services start dbus, it seemingly starts fine:

   $ brew services start dbus
   ==> Successfully started `dbus` (label: org.freedesktop.dbus-session)
   

   but upon checking

   $ brew services info dbus
   dbus (org.freedesktop.dbus-session)
   Running: ✘
   Loaded: ✔
   Schedulable: ✘
   

   which is where it all starts to go wrong. Running brew services start dbus again

   $ brew services start dbus
   Bootstrap failed: 5: Input/output error
   Try re-running the command as root for richer errors.
   Error: Failure while executing; `/bin/launchctl bootstrap gui/501 /Users/s1g/Library/LaunchAgents/org.freedesktop.dbus-session.plist` exited with 5.
   

   and dbus-launch gets me

   $ dbus-launch
   dbus-daemon[9336]: Failed to start message bus: launchd's environment variable DBUS_LAUNCHD_SESSION_BUS_SOCKET is empty, but should contain a socket path.
   
   EOF in dbus-launch reading address from bus daemon
   

   also running the launchctl command as sudo just gets me:

   $ sudo /bin/launchctl bootstrap gui/501 /Users/s1g/Library/LaunchAgents/org.freedesktop.dbus-session.plist
   Bootstrap failed: 5: Input/output error
   

So yea I’m really at a loss..

Steps to reproduce

No response

Expected behavior

No response

Actual behavior

No response

Do you use a latexmkrc file?

No

VimtexInfo

System info:
  OS: macOS 14.1 (23B74)
  Vim version: NVIM v0.9.4
  Has clientserver: true
  Servername: /var/folders/m6/nyw0tbd5239gngtm06pzykr00000gn/T/nvim.s1g/GvUYPs/nvim.9533.0

VimTeX project: article
  base: article.tex
  root: /Users/s1g/Workspaces/BSc/report
  tex: /Users/s1g/Workspaces/BSc/report/article.tex
  main parser: current file verified
  document class: article
  packages: adjcalc beramono biblatex blx-case-expl3 collectbox courier epstopdf-base etoolbox expl3 fontenc graphics graphicx iftex ifthen infwarerr keyval kvoptions kvsetkeys listings logreq lstlang1 lstlang2 lstlang3 lstmisc ltxcmds pdftexcmds realboxes titlesec trig url xcolor xkeyval xparse xpatch
  compiler: latexmk
    engine: -pdf
    options:
      -verbose
      -file-line-error
      -synctex=1
      -interaction=nonstopmode
    callback: 1
    continuous: 1
    executable: latexmk
  viewer: Zathura
    xwin id: 0
  qf method: LaTeX logfile

[lervag]

I'm sorry; as I don't use Mac myself, I don't really have a good way to help. I'm hoping someone like @clason might be able to help, though?

[clason]

I don't use Zathura, sorry!

[s1gtrap]

@clason Well zathura is far from a must, I just need a PDF viewer to reliably see what I'm working on. But either way this doesn't really appear to be a zathura issue, more of a dbus problem so all depending it might still apply..

[clason]

Yes, but Skim (which I use) doesn't rely on dbus.

[s1gtrap]

Awesome! Skim seems to be working out of the box :)

Not sure what to do about this issue, but other people do appear to be experiencing the same issue with dbus: https://github.com/orgs/Homebrew/discussions/2318

[lervag]

Happy to see you find Skim to work nicely. Regarding the issue, I propose we close it. I don't have any idea how to resolve it, and I don't see the value in keeping things open unless there is someone able and willing to possibly resolve it.

[ravibrock]

Speaking as someone who uses VimTeX on Mac, tt could nip some of these issues in the bud if the docs simply suggest using Sioyek or Skim on MacOS - I remember spending hours trying to get Zathura working on Mac, just to eventually give up and discover that Sioyek is, as far as I can tell at least, roughly a 1-to-1 replacement on Mac that works out of the box.

[lervag]

Thanks for the suggestion, @ravibrock. I've updated the docs.

I'll also take the liberty of closing this issue.

[Zdmai]

Speaking as someone who uses VimTeX on Mac, tt could nip some of these issues in the bud if the docs simply suggest using Sioyek or Skim on MacOS - I remember spending hours trying to get Zathura working on Mac, just to eventually give up and discover that Sioyek is, as far as I can tell at least, roughly a 1-to-1 replacement on Mac that works out of the box.

thanks, that's awsome

[sammmsational]

After trying to make zathura work for a few hours I finally stumbled over this. I suggest adding it to :h vimtex-faq-zathura-macos, unless the recipe [3] in that help page is the fix to this issue, in which case that should be said somewhere in this issue.

[lervag]

After trying to make zathura work for a few hours I finally stumbled over this. I suggest adding it to :h vimtex-faq-zathura-macos, unless the recipe [3] in that help page is the fix to this issue, in which case that should be said somewhere in this issue.

I don't mind updating the docs, but it would be very nice if you could be more specific to what exactly you want me to add to the faq section.

[sammmsational]

I don't mind updating the docs, but it would be very nice if you could be more specific to what exactly you want me to add to the faq section.

Thanks. I'm currently working on a feature request concerning this problem. Once you've taken a look at it and I know more, I can suggest something to add to the docs.