Okular and Samba Server

I am seeking some help with a problem I am having with Okular. I have installed Leap 42.1. I can open pdf files that are on the local drive. When I try to open files on a Samba server I get a message saying the I do not have permissions to open the file. I can copy the file to my local drive and open it. I have other Linux installations and they do not have any problems opening any files from the server. Other Leap 42.1 programs do not have any issues opening respective files from the server. The problem seems to be only with Okular. I would appreciate any assistance.

I can confirm the same behviour (via my openSUSE Leap guest to a remote samba share)

Could not open smb://user@server/path/to/file.pdf. Reason: Access denied to smb://user@server/path/to/file.pdf.

A little more digging and I found that while trying to open a different kind of file (JPG in this case) by clicking on the file icon within dolphin to open with the default app, I was then presented with an authorization dialogue box. After editing the required credentials, I found that I could subsequently open PDF files with okular without issue.

Following the authentication dialog where I provided the necessary authentication credentials (and saved password), I’m no longer getting prompted and PDF files open with okular as expected. I’m not sure why this wasn’t getting triggered when okular was involved, but it was when attempting to open a JPEG file with gwenview. Maybe it is similar for you - once kwallet has saved the credentials all should be good.

It seems that kwalletd is involved (required?) for this authentication, as opposed to kwalletd5.

FWIW, nrickert’s blog on the subject is interesting…

https://nwrickert2.wordpress.com/2015/12/20/notes-on-kdewallet/

Thank you for the information. I will see what I can find.

Yes, once you get prompted to add your authentication credentials (which for example I triggered by clicking on a JPEG file while navigating with dolphin), then you should find there are no further issues when opening a PDF file.

Your instructions worked perfectly. Thank you for your help!

Glad to have been of help. (It’s obviously a minor bug, but easy enough to work around.)