Hi,

I'm having a strange problem. A couple of days ago, Okular failed to open a PDF. I thought the file was damaged, but it turned out other readers could open and display it correctly. Since I am using Okular for KF5 from git, I simply compiled again the latest git and it turned out even more files weren't working, files that used to work before.
There is no error message on the console
It seems independent of the file type. I couldn't open a djvu file either.
It doesn't seem to be having anything to do with the file name either
The error simply says "could not open". I can't seem to be getting any further information.

as Evince and qpdfview also use Poppler for rendering if you test with one of them it will indicate whether a Poppler or Okular issue. Might also try Gimp.

That was also one of my first guesses, but Gimp, Inkscape, evince, gv, mupdf and qpdfview all work perfectly fine.

have you tried a pre-compiled package

are there any warnings/errors in the compilation log sound like a compilation error

I'm on Gentoo, there are no pre-compiled packages As for stable versions, I am running KF5 only, with no kde4libs installed. That means I can't install any stable version of Okular without installing a whole bunch of libraries, which I'm trying to avoid.
I can find quite a few warnings in the build log, most of them being unused parameter warnings. I can't associate any of them with the problem I'm having.
Here's a copy of the build log:
https://owncloud.tu-berlin.de/index.php ... mX68ItM19X

found the following in the log, guessing you should try resolving it

-- The following RECOMMENDED packages have not been found:

* Poppler-Qt5 (required version >= 0.12.1) , A PDF rendering library , <http://poppler.freedesktop.org>
Support for PDF files in okular.

Same here on arch linux. while using this package from aur: https://aur.archlinux.org/packages/okul ... works-git/

It seems that there is a problem with spaces. If the filename contains spaces, the file can only be opened via file → open but not via console or desktop file.

naraesk wrote:Same here on arch linux. while using this package from aur: https://aur.archlinux.org/packages/okul ... works-git/

It seems that there is a problem with spaces. If the filename contains spaces, the file can only be opened via file → open but not via console or desktop file.

if you're running the fish shell could be https://bugs.kde.org/show_bug.cgi?id=311373

Nope, normal bash and all other applications don't have this problem.
That's the latest commit of okular-frameworks: https://github.com/KDE/okular/commit/a7 ... cb86638966
Since it's about dermining the path of a file I'd guess this is causing the problems.

https://bugs.kde.org/show_bug.cgi?id=359319

yes, that appears to be the problem. I thought I had tried removing spaces from file names, but it seems to be working now when I do.