Bug 426380

Summary:	Okular forgets the open documents when closed normally and reopened
Product:	[Applications] okular	Reporter:	Jaime Torres <jtamate>
Component:	general	Assignee:	Okular developers <okular-devel>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	nate, postix
Priority:	NOR
Version:	1.11.0
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:

Description Jaime Torres 2020-09-10 17:14:42 UTC

SUMMARY
When the session is closed and reopened, okular remembers the open documents and everything is restored as if nothing happened.
But if I close and open again in the same session, okular forgets the previous open documents and I have to restore them manually from the recent documents  (if they are still there).

STEPS TO REPRODUCE
1. Close normally okular
2. Open normally okular

OBSERVED RESULT
The opened documents are lost, okular is empty

EXPECTED RESULT
The opened documents are there, okular is restored like in the session start.

SOFTWARE/OS VERSIONS
KDE Frameworks 5.73.0
Qt 5.15.0 (compilado con 5.15.0)
El sistema de ventanas xcb

Comment 1 Laura David Hurka 2020-09-10 18:43:07 UTC

I am not sure what you mean. I want to close a document, and when I open Okular again, the document is open again? Why do I close Okular at all then? Web browsers sometimes do stuff like that, I don’t really understand why.

I think you need some session management feature that lets you control which documents are opened automatically, like in Kate. So I close this as duplicate of “session management” for now, note especially the last comment there.

*** This bug has been marked as a duplicate of bug 397463 ***

Comment 2 Jaime Torres 2020-09-11 12:25:31 UTC

Just answering the question
Why do I close Okular at all then? Web browsers sometimes do stuff like that, I don’t really understand why.

Sometimes I need to run some memory hungry programs, therefore I close almost all the other programs and then reopen them again. I guess I can not get the same effect with Activities.

Comment 3 Nate Graham 2021-05-13 16:18:23 UTC


*** This bug has been marked as a duplicate of bug 364680 ***