Bug 19265 - okular can neither open .djvu or .pdf (plugins not installed?)
Summary: okular can neither open .djvu or .pdf (plugins not installed?)
Status: RESOLVED DUPLICATE of bug 19273
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-30 17:24 CEST by Helge Hielscher
Modified: 2016-08-31 00:01 CEST (History)
0 users

See Also:
Source RPM: okular-16.04.3-1.mga6.src.rpm
CVE:
Status comment:


Attachments

Description Helge Hielscher 2016-08-30 17:24:42 CEST
Description of problem: When I install okular it registers itself in the file-manager that it can open certain file types, like PDF and DJVU. But when I open the file in okular I get "Could not find a plugin to handle the document being passed".


Version-Release number of selected component (if applicable): 16.04.3-1


How reproducible: always


Steps to Reproduce:
1. install okular
2. open a supported file (e.g. .pdf or .djvu)

Results:
okular(23722)/okular (app) Okular::Document::openDocument: No plugin for mimetype '"image/vnd.djvu"
okular(23881)/okular (app) Okular::Document::openDocument: No plugin for mimetype '"application/pdf"'

Expected Result: 
Okular can open all file types it claims to support.
Please install the required plugins alongside okular or provide a package "okular-plugins" (or packages like "okular-plugin-pdf")
Comment 1 Helge Hielscher 2016-08-30 22:05:48 CEST
I found the solution:
I run "kbuildsycoca4 --noincremental" and got
"KConfigIni: In file /usr/share/applications/lximage-qt-screenshot.desktop, line 13: " Invalid entry (missing '=')

Once I fixed it, okular works fine now.
Comment 2 David Walser 2016-08-31 00:01:20 CEST
So it sounds like Bug 19273 is the cause of this issue.

*** This bug has been marked as a duplicate of bug 19273 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE


Note You need to log in before you can comment on or make changes to this bug.