After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 789062 - Evince 'silently quits' without any backend
Evince 'silently quits' without any backend
Status: RESOLVED OBSOLETE
Product: evince
Classification: Core
Component: general
3.26.x
Other Linux
: Normal normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-10-16 15:00 UTC by Dominique Leuenberger
Modified: 2018-05-22 17:24 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Dominique Leuenberger 2017-10-16 15:00:58 UTC
disclaimer: yes, this can be 'put off' as a packaging peccularity, but nevertheless I consider it a wrong behavior of evince

in openSUSE, we package 'evince' - the application as 'evince' and all backends as evince-plugin-XXXdocument (e.g. pdfdocument, psdocument, xpsdocument)

All of them come with AppStream meta information which makes GNOME Software show all the extensions as options - PDFDocuments is 'recommended' by our evince package (but not hard required)

If a user decides (for whatever reason) to remove all document handlers, then evince simply fails to start and exits with error 1.

Neither when starting it on a terminal nor from a launcher there is any indication to what is going on.

At a bare minimum, when evince reaches this state, it should create a messagebox claiming there are no available document handlers installed
Comment 1 GNOME Infrastructure Team 2018-05-22 17:24:19 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/evince/issues/843.