Bug 490714

Summary:	The program is not restored from a saved session after another update.
Product:	[Applications] okular	Reporter:	Adrian Carver <adrian.carver>
Component:	general	Assignee:	Okular developers <okular-devel>
Status:	REPORTED ---
Severity:	normal	CC:	aacid, postix
Priority:	NOR
Version First Reported In:	24.05.2
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Adrian Carver 2024-07-23 16:24:44 UTC

Recovering previously discovered books is an old issue that we come back to again and again.

Currently (I can't think why it's done this way), you can only restore previously opened books or documents one by one in the File - Recent Files section.

Considering that I usually have 15 or more of them open, opening all of them individually turns into an incredibly boring quest of several minutes (especially if they are in different places).

I've been using session recovery mechanism - and ocular most often opens books again...but there is a nuance - session saving also likes to fail very much and as a result I have to look for the documents I need again in different places.
I've been using session recovery mechanism - and ocular most often opens books again...but there is a nuance - session saving also likes to fail very much and as a result I have to look for the documents I need again in different places.

Is it not possible to make after many years some semblance of session work and still realize a primitive mechanism of history storage with its restoration after a new start? Because crutches, frankly speaking, are tiresome.



SOFTWARE/OS VERSIONS
Linux: 6.10.0-arch1-2
KDE Plasma Version: 6.1.3
KDE Frameworks Version:  6.4.0
Qt Version: 6.7.2

Comment 1 Albert Astals Cid 2024-07-23 22:14:38 UTC

It is also tiresome that you decided your report important is "major" instead of "normal", it's not.

I don't even know what you are reporting.

Are you reporting that saving a session doesn't work? That would be a Plasma bug, not an Okular bug.

Are you wishing Okular had its own session concept? That's not even a bug, that'd be a wish.

Comment 2 Adrian Carver 2024-07-24 09:06:56 UTC

(In reply to Albert Astals Cid from comment #1)

Albert, if you don't understand something, you can always ask clarifying questions to the authors of the two “brilliant” ideas: the one who decided that the idea of redirecting a KDE user to the project's internal bug tracker with mandatory registration there was a very good idea. The second person who can explain to you what's going on is the one who, after the first one, decided not to create a sane registration form with a short introductory FAQ on how to use this bug tracker, sincerely hoping in his heart that an ordinary user wouldn't register here.

I wouldn't, if I hadn't once again started to be annoyed by the non-obvious behavior of the system and its separate component - ocular. I clicked on the “Report a bug...” menu and wrote it down as best I could. Where to redistribute it - to bugs, non-critical bugs, wishes...in general, this is the job of “moderator”, I assume yours. To me, this kind of behavior is critical in use. Well, no one has explicitly familiarized me with what the statuses in your tracker mean.

At the same time, you can start a couple of tasks to finalize the registration form on the basis of the above: the situation shows that it will be useful.

Comment 3 postix 2024-07-27 13:12:40 UTC

Sounds like https://bugs.kde.org/show_bug.cgi?id=479638