You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For at least a month now, control-clicking in evince has not been triggering forward/backward search. This is on several systems that were working properly at some point in the last three months, all running an up-to-date Pop!_OS (Linux, like Ubuntu).
I'm unsure how to debug LaTeXTools itself. journalctl --user only reports that the evince daemon has started... I'm not sure where to look for log messages from the daemon itself.
It might be helpful to note that several other of my synctex evince integrations appear to be broken as well. All of these appear to trace their lineage back to the gedit evince dbus daemon, which I believe is also the case for LaTeX tools. The immediate issue in virtually all of them appears to be that Gtk.main was removed in Gtk4, which Pop!_OS recently moved to.
If provided with some guidance, I'm happy to assist in debugging this issue
The text was updated successfully, but these errors were encountered:
For at least a month now, control-clicking in evince has not been triggering forward/backward search. This is on several systems that were working properly at some point in the last three months, all running an up-to-date Pop!_OS (Linux, like Ubuntu).
I'm unsure how to debug LaTeXTools itself.
journalctl --user
only reports that the evince daemon has started... I'm not sure where to look for log messages from the daemon itself.It might be helpful to note that several other of my synctex evince integrations appear to be broken as well. All of these appear to trace their lineage back to the gedit evince dbus daemon, which I believe is also the case for LaTeX tools. The immediate issue in virtually all of them appears to be that Gtk.main was removed in Gtk4, which Pop!_OS recently moved to.
If provided with some guidance, I'm happy to assist in debugging this issue
The text was updated successfully, but these errors were encountered: