Bug 415332 - [Snap] Okular does not show the dialogue to let me load a file
Summary: [Snap] Okular does not show the dialogue to let me load a file
Status: REPORTED
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: 1.7.2
Platform: Snap Linux
: NOR normal
Target Milestone: ---
Assignee: Scarlett Moore
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-18 19:51 UTC by adalbert.hanssen
Modified: 2022-10-23 12:04 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Messages in a terminal window when starting Okular with a command (365 bytes, text/plain)
2019-12-18 20:24 UTC, adalbert.hanssen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description adalbert.hanssen 2019-12-18 19:51:56 UTC
SUMMARY


STEPS TO REPRODUCE
1. With Okular started, I do Datei>Öffnen (file>open) or Ctl-O
2. 
3. 

OBSERVED RESULT no dialogue box which lets me input the file to load.


EXPECTED RESULT
a dialogue box which lets me input the file to load.


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: KDE Frameworks 5.61.0
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: Qt 5.12.3 (kompiliert gegen 5.12.3)
Das xcb Fenstersystem

ADDITIONAL INFORMATION

To avoid having to make all mark pen definitions a second time, I just copied all those settings from another user: copy /home/user/snap/okular to ~/snap/okular and then I did a chown -R to it for the current user.

I can open a file with okular when I give it the filename as a command line argument.

The bug happens in Xubuntu 18.04.3 LTS.
Comment 1 adalbert.hanssen 2019-12-18 20:24:08 UTC
Created attachment 124577 [details]
Messages in a terminal window when starting Okular with a command

When I start okular in a terminal adding the file to load, I see these messages in the terminal after closing okular. Maybe this plays a role in the error or not, I don't know.
Comment 2 Albert Astals Cid 2019-12-18 23:33:36 UTC
Are you saying that you did some crazy copying of snap stuff by hand, things don't work and now you're opening a bug?
Comment 3 adalbert.hanssen 2019-12-19 07:18:06 UTC
(In reply to Albert Astals Cid from comment #2)
> Are you saying that you did some crazy copying of snap stuff by hand, things
> don't work and now you're opening a bug?

If you call this crazy: yes, I did so. This method worked well before (with ~/.kde/share/config/okularpartrc) and I only noticed that this is a snap install after it did not work. First I tried to copy the whole directory ~/.kde/share/config/ to my place (followed by chowning it) and after that did not work, I changed one pen and looked for files that had changed in the last minutes. Then I found out that this is a snap install and that the proper place must have been ~/snap/okular/63/.config/okularrc. Since I had copied the whole surrounding, I did so with the whole directory ~/snap/okular/63/.config/.

The presence of ~/.kde/share/config/okularpartrc despite the snap installation now was a leftover from before, when okular was running under Xubuntu 16.03. /home lives on a separate partition, so upgrading the operating system maintained all my files and the settings of all programs - if they were not destroyed in the new installation of my application programs. Most of them kept  existing settings untouched.

By the way: copying the whole set of annotation pen definitions worked well, it is just the strange thing with the file>open file command which is missing its dialogue.
Comment 4 adalbert.hanssen 2019-12-21 08:35:10 UTC
I found out that okular has the same syndrome for the user whose profile I copied to the other user.

Since the error is present there too, this has nothing to do with copying ~/.kde/share/config/ as described in my ADDITIONAL INFORMATION. I was unaware of that when I reported the bug.
Comment 5 Albert Astals Cid 2019-12-24 11:24:02 UTC
So maybe you can close this bug, and open a new one with more clear information of what you did and what is wrong?

At this point i'm not sure what's your setup
Comment 6 adalbert.hanssen 2019-12-26 17:18:33 UTC



(In reply to Albert Astals Cid from comment #5)
> So maybe you can close this bug, and open a new one with more clear
> information of what you did and what is wrong?

Why should I close it? The bug is persistent and has nothing to do with Comment2's assumption:

In order to exclude any effect of Comment2's assumption, I first uninstalled okular (which was a snap installed version, but since I had used the standard installation before too, I uninstalled that too just to be sure (there was none left):

v@v:~$ sudo snap remove okular
okular entfernt
v@v:~$ sudo apt-get purge okular
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Paket »okular« ist nicht installiert, wird also auch nicht entfernt.
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
v@v:~$ sudo snap install okular
okular 19.04.2 aus KDE✓ installiert
v@v:~$ okular --version
Qt: Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
okular 1.7.2
v@v:~$ snap list --all
Name                     Version   Rev   Aufzeichnung  Herausgeber  Hinweise
core18                   20191126  1279  stable        canonical✓   base,deaktiviert
core18                   20191212  1288  stable        canonical✓   base
kde-frameworks-5-core18  5.61.0    32    stable        kde✓         -
okular                   19.04.2   63    stable        kde✓         -
snapd                    2.42.4    5643  stable        canonical✓   snapd,deaktiviert
snapd                    2.42.5    5754  stable        canonical✓   snapd
v@v:~$

I expected that after installation that okular --version gives me version 19.04.2. Surprisingly in Hilfe>Über Okular it identifies itself as version 1.7.2, like okular --help does. However snap list all tells about okular 19.04.2! That's strange.

The other strange thing is: If I select Datei>Öffnen, no dialogue comes up. I would expect that the file to display would be asked for.

However, I can start okular from a terminal window and let it open a pdf file for me like this (however, I see some error messages then)

v@v:~$ okular "~/Downloads/gnupg-anleitung-seite-1.pdf"
Qt: Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
Icon theme "Adwaita" not found.
Icon theme "Adwaita" not found.
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
v@v:~$

(the  Icon theme message is also shown if I switch the display theme to Numix).

> 
> At this point i'm not sure what's your setup


If you need more information on the setup beyond what is told in my first posting, I'd provide it if you tell me exactly what you are after (e.g. let me issue some command which identifies what you are looking for).
Comment 7 Albert Astals Cid 2019-12-26 18:23:20 UTC
I'm not involved in the snap creation nor have access to a snap based system.

Adding a few people that may care.
Comment 8 adalbert.hanssen 2019-12-30 20:07:00 UTC
Now I have uninstalled the snap-installed version (`sudo snap remove okular`) and replaced it by one installed with `sudo apt install okular`. Version 1.3.3 came up which does not have this bug.
Comment 9 Ben Creasy 2020-01-25 07:15:02 UTC
Adalbert, it would probably help if you attached a copy of the settings that you have when the bug appears - apparently copied from from the snap?