I have installed okular using lastest KDE for Windows installer (v1.0.0). But when I try to open a PDF, I receive error like "Could not open C:/mydir/myfile.pdf". Interestingly path separator shown here is not the one Windows use, I think it might be the problem. I had no problem opening other image files such as png's. Reproducible: Always Steps to Reproduce: 1. Install Okular using KDE windows installer (v1.0.0) 2. Try to open a PDF file 3. Error pops up giving a path with wrong path seperator Latest executables downloaded by KDE Windows Installer are a bit old (okular v0.16.2). Maybe this problem will be solved if repository is updated. I have been using Okular on Windows since a few years without problem but after an update this error showed up.
Windows guys, any idea?
Hm, this should work, I am using okular myself for pdf viewing. Some things of interest: - Have you only installed okular? - Do you have other open source products in your path, e.g. can you show us the output of 'set PATH' in the Windows console? - Which windows version do you have? The path shouldn't be a problem at all.
(In reply to comment #2) > Hm, this should work, I am using okular myself for pdf viewing. > Some things of interest: > - Have you only installed okular? I have only selected okular to be installed. > - Do you have other open source products in your path, e.g. can you show us > the output of 'set PATH' in the Windows console? Output of 'set PATH': Path=C:\Program Files (x86)\AMD APP\bin\x86_64;C:\Program Files (x86)\AMD APP\bi n\x86;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System3 2\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft\Web Platform Installer\;C:\ Program Files (x86)\Microsoft ASP.NET\ASP.NET Web Pages\v1.0\;C:\Program Files ( x86)\Windows Kits\8.0\Windows Performance Toolkit\;C:\Program Files\Microsoft SQ L Server\110\Tools\Binn\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-St atic PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC > - Which windows version do you have? Sorry for not mentioning this. I have Windows 7 Professional SP1 64bit > > The path shouldn't be a problem at all. I think that path may not be the problem, as you said. Path shown in the error window might be a typing mistake. I'll try to get some debugging information, if can't, I continue to use older version or wait for a new build.
(In reply to comment #3) > (In reply to comment #2) > > Hm, this should work, I am using okular myself for pdf viewing. > > Some things of interest: > > - Have you only installed okular? > I have only selected okular to be installed. Hm, I retried that locally, and it seems all required libraries are installed (I thought that maybe there was a missing dependency in our installer). > > - Do you have other open source products in your path, e.g. can you show us > > the output of 'set PATH' in the Windows console? > Output of 'set PATH': > Path=C:\Program Files (x86)\AMD APP\bin\x86_64;C:\Program Files (x86)\AMD > APP\bi > n\x86;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C: > \Windows\System3 > 2\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft\Web Platform > Installer\;C:\ > Program Files (x86)\Microsoft ASP.NET\ASP.NET Web Pages\v1.0\;C:\Program > Files ( > x86)\Windows Kits\8.0\Windows Performance Toolkit\;C:\Program > Files\Microsoft SQ > L Server\110\Tools\Binn\;C:\Program Files (x86)\ATI > Technologies\ATI.ACE\Core-St > atic Doesn't seem to contain other open source software, so should be ok. > > - Which windows version do you have? > Sorry for not mentioning this. I have Windows 7 Professional SP1 64bit Same here. > > > > The path shouldn't be a problem at all. > > I think that path may not be the problem, as you said. Path shown in the > error window might be a typing mistake. I'll try to get some debugging > information, if can't, I continue to use older version or wait for a new > build. We will have a newer build available soon (around christmas I hope).
Not sure if the new builds happened, but could you please check and try again? Windows team: did you ship a new build?
(In reply to comment #5) > Not sure if the new builds happened, but could you please check and try > again? I've just checked and seen that its still the same and there isn't a new build yet. I haven't been using windows for months anyway. If there is not anyone else having this error we can just ignore this for now. Okular is working perfectly on my friends computer. So it has to do with my windows installation and I don't know how to reproduce this on somewhere else.
Ok, let's leave it as needs info and see if there's a new update soon-ish or if you can find out what's the difference between your install and your friends install, if not we'll close it in a few months.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!