Bug 359223 - [framework] okular cannot open files with spaces in path or name (both from terminal and from dolphin)
Summary: [framework] okular cannot open files with spaces in path or name (both from t...
Status: RESOLVED FIXED
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
: 359319 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-02-10 09:53 UTC by Stas
Modified: 2016-02-26 16:15 UTC (History)
7 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 Stas 2016-02-10 09:53:37 UTC
Hello, I have updated my oukular-frameworks-git AUR package and now I have a problem, that I cannot ope pdf files which contain spaces in the path or name. It does not work from terminal aud from Dolphin. However, I can open those file from within okular with the open dialog.

The Error I get is the following:
QCommandLineParser: option not defined: "raise"

So I think something is going wrong with the QT5 libraries and okular combination?!

Would be nice, when you could have a look at that bug, okular is a program I use all the time ;)
And thanks for the great job by the way.

Reproducible: Always

Steps to Reproduce:
1. Try to open pdf with spaces in name or path
2. "Could not open" - error
Comment 1 Stas 2016-02-10 09:55:29 UTC
Ok, just checked: the error occurs even when a pdf file is opened (contains no spaces) so it is not the relevant information.
Comment 2 Michael Rydén 2016-02-11 12:11:11 UTC
I have the same issue. Seems that okular won't open files if the file, or the folders itself, contains any spaces. If I move the file to a folder without spaces it opens as normal.

I also get QCommandLineParser: option not defined: "raise" if I run it from terminal.

The previous version worked, so I think this is a new bug.
Comment 3 Yi Yang 2016-02-13 14:57:24 UTC
Same for me. This is actually one of the more annoying bugs for me, since most of my files reside on paths with spaces in it, making Okular nearly unusable. Worse, it seems to try to expand symlinks so I can't even use symlinks to circumvent this bug.
Comment 4 Christoph Feck 2016-02-14 03:45:43 UTC
*** Bug 359319 has been marked as a duplicate of this bug. ***
Comment 5 Albert Astals Cid 2016-02-16 00:07:30 UTC
(In reply to Yi Yang from comment #3)
> Same for me. This is actually one of the more annoying bugs for me, since
> most of my files reside on paths with spaces in it, making Okular nearly
> unusable. Worse, it seems to try to expand symlinks so I can't even use
> symlinks to circumvent this bug.

You should not be using the frameworks branch if you need to use Okular reliably, the frameworks branch is not supported, so if you're using it, is because you want, we appreciate you report bugs and people that created those bugs in the frameworks branch may eventually fix them, but don't complain it doesn't work.
Comment 6 Stas 2016-02-19 11:52:33 UTC
Hello, from AUR site I got this hint to patch the bug:

https://git.reviewboard.kde.org/r/126192/

See the comments here:
https://aur.archlinux.org/packages/okular-frameworks-git/

Would be great, if it could be fixed in the git branch...
Comment 7 Aleix Pol 2016-02-26 16:15:38 UTC
Should be fixed as of:
http://commits.kde.org/okular/154c98fdaab2e593091fe644cfaeed96dd9fefaf