Re: [Bug-AUCTeX] TeX-evince-sync-view

[David Kastrup]

Tassilo Horn <address@hidden> writes:

> Thomas Arildsen <address@hidden> writes:
>
> Hi Thomas,
>
>>> AUCTeX first does
>>>
>>> (dbus-call-method
>>>   :session "org.gnome.evince.Daemon"
>>>   "/org/gnome/evince/Daemon"
>>>   "org.gnome.evince.Daemon"
>>>   "FindDocument"
>>>   "file:///home/horn/some.pdf"   ;; replace with some existing PDF
>>>   t) ;; C-x C-x here
>>>
>>> Does that work, i.e., open an evince window showing some.pdf?
>> This part works, much to my surprise. I pasted the above into the
>> scratch buffer, replaced by an existing PDF and ran M-x
>> eval-buffer. The PDF opened in a new evince window.
>
> Uh, that's strange.  That's exactly what TeX-evince-sync-view does.

Perhaps it is not allowed to do that.

>> When I then run the TeX-evince-sync-view command on a LaTeX document
>> (that has a newly compiled PDF output), nothing happens: no evince
>> windows, no error message, no output from 'dbus-monitor', no output
>> in the *Messages* buffer - nothing...
>
> Hm, so TeX-evince-sync-view is called, doesn't error, and still does
> nothing.  Honestly, I have no clue how that can happen.

I can get diagnostics like the following from Evince (different
application, different context):

    -*- mode: compilation; default-directory: "/tmp/" -*-
    Compilation started at Wed Sep  4 13:16:08

    evince /tmp/rrr.pdf

    ** (evince:26926): WARNING **: Couldn't register with accessibility bus: An 
AppArmor policy prevents this sender from sending this message to this 
recipient, 0 matched rules; type="method_call", sender="(null)" (inactive) 
interface="org.freedesktop.DBus" member="Hello" error name="(unset)" 
requested_reply="0" destination="org.freedesktop.DBus" (bus)

    (evince:26926): EvinceDocument-CRITICAL **: ev_document_get_n_pages: 
assertion 'EV_IS_DOCUMENT (document)' failed

    Compilation finished at Wed Sep  4 13:16:11


AppArmor can really be a beast, and judging from the above (unrelated)
message, it even messes with Dbus.

Evince, as the designated Ubuntu PDF viewer, tends to have its AppArmor
profile nailed shut as fast as possible.

Viewers in AUCTeX are started without connection to a buffer/terminal if
I remember correctly, so you would not get to see any error messages or
bad exist codes.  Perhaps you need to change the "View" entry
appropriately to a function not completely detaching the process in
order to get some more information there.

-- 
David Kastrup