Bug 392106 - opening (e)PS files from the commandline
Summary: opening (e)PS files from the commandline
Status: RESOLVED FIXED
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources All
: NOR wishlist
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-20 16:35 UTC by RJVB
Modified: 2018-04-06 14:17 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description RJVB 2018-03-20 16:35:24 UTC
Okular can import (E)PS files and show them as PDF, which isn't surprising given that it has a Ghostscript backend. What's more surprising is that it won't open those files from the commandline. At most I get an empty page. Is this an omission or is there a reason why this is less trivial to implement than I think it should be?
Comment 1 Albert Astals Cid 2018-03-20 21:29:06 UTC
okular opens ps and eps files just fine from the command line.

Which error do you get?
Comment 2 RJVB 2018-03-20 22:00:12 UTC
No error, just a white page.

I just see that the file that fails is actually a pdf file that somehow got the eps extension. That's not a problem for ghostscript when left to its own, but probably explains why the backend fails.