SUMMARY STEPS TO REPRODUCE 1. Read a .pdf file (opened via Firefox) 2. Close all instances of Okular 3. Reboot OBSERVED RESULT Any closed documents open, and have to be closed again, repeat and it happens again. EXPECTED RESULT No documents, unless left open for whatever reason, should not open on reboot. SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.12.15-arch1-1 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-2500K CPU @ 3.30GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050/PCIe/SSE2 ADDITIONAL INFORMATION I have had this problem a few times before with KDE applications. Strangely it also happens (more often) that System trey applications (not necessarily KDE apps) don't load on boot, and I have a strange one right now, just in case you are interested (I know that KDE may not even have anything to do with it: The download manager Persepolis every once in a while doesn't load to the system trey on boot, although set in the app to do so. There is no entry in the system trey settings for it; Any app that does launch to the trey through any method should, as it wold be an easy way to enable and disable all of them in one place, and may be of help in trouble shooting too. It would be nice; if that's even possible. When it does work, it strangely also opens to the desktop which is annoying. When it shows this behavior (not loading on boot), it also doesn't load when launched via the Application Launcher, but. For the first tome today it launched as usual to the desktop (didn't look in the trey, but this time when I closed it, it was also missing from the trey as well, and would not launch any which way again. This program has the problem off and on for months now, possibly always. I know that it's independent from KDE, but it may just be that you could look into how easy it is for developers to implement the underlying procedures, or how they are handled... and streamline and improve implementing it (I know it may not have to do with KDE). I for one have always had a problem with KDE documentation, as there's very little info for many programs, plenty of outdated and no longer applicable info making me try stuff for things to either fail, or cause trouble, mostly find several possible locations for files to make changes in for the very same thing, only to realize they have changed yet again! There are few howto's... and when there is information, it is mostly geared toward developers, and way over the heads of anyone with little to no understanding of programming (Me), even when they are settings and customization's us users would love to implement and possibly share, like making any of the various themes, which is why so many on your app store are utterly useless, and often cause problems. I have never been able to make an Icon theme following any of your or anyone else's documentation that works right, often not at all. I guess I will have to send you guys a long list of suggestions (from a user perspective), which sounds strange for the desktop with the most and best options, settings, features, and gadgets over any other, at least in my experience, and why I have been using KDE for so long, and love it so much. Just looking at "Possible Duplicates below" doesn't tell me muvh because of the programmers lingo; I think it may help all of KDE a lot, to have two bug reporting sections or sites: One for developers and contributors, and one for users specifically, and yes I understand it is a huge amount of work, but will cut down on work in the long run, and so "pay" for itself.
AFAIK Okular does not have any session management logic integrated. So this is probably caused by the desktop environment. I don’t know what could cause this or how to debug this. Someone else? In the meantime, you can try to empty the list of recent documents. In Okular: File -> Open Recent -> Clear List. Or open the file ~/.config/okularrc and remove the entries manually. > STEPS TO REPRODUCE > 1. Read a .pdf file (opened via Firefox) Just a weird idea: If the documents need to be opened via Firefox, maybe you have some startup script like `okular Documents/*`?
> ADDITIONAL INFORMATION > [...] Thanks for the feedback. However, in this bug report it will probably become lost. I think you should send it to a mailing list instead. See: https://kde.org/support/mailinglists/
(In reply to David Hurka from comment #1) > AFAIK Okular does not have any session management logic integrated. Yes it does. main.cpp line 84 and Shell::saveProperties/readProperties
I have some more info to add: Seems that other apps may also be effected, giving David Hurka's theory more weight, as the app Persopolis (*a download app) As described in my initial report, showed similar odd behavior: This morning it opened on reboot, and this time I didn't close it which is supposed to just minimize it to the system trey, which it didn't do yesterday, but rather closed altogether and couldn't be launched by any means, after which I opened dolphin only to find many tabs and duplicates of often navigated places, and sluggish behavior, and "running progress indicator popups in separate dolphin I had also closed for sure back the tab bar, which I closed and then closed dolphin itself, to see if it would reoccur on open, which revealed 2 dolphin windows (much smaller than I keep it with never seen before running progress indicators with red slanted stripes and tabs open to persopolis download location tabs referring to the two last downloads I had not yet cleared from Persopolos's interface, for which I would have taken a screen shot of, but it already gave me a heap of trouble last night too, and didn't launch on [PrtScn] to select a portion of the screen, and would only work on [Shift]+[PrtScn] and reported "Whole screen image saved to Default location, which I had set to a sub-folder thereof, but once open It did let me open the advanced interface, and select a portion of the screen, and in trying all kinds of stuff, including resetting it to my lost preferences, but only to flip out in more than one new and odd ways, like not recognizing cursor movement, position and mouse clicks! I have also had the cursor go missing in LibreOffice writer, and wild clicking at random seemed to help it recover, sluggish performance, and one one document was loaded, no aditional documents could be opened after the first when trying to open them from Dolphin, as well as LO writer not launching at all after close, and other strange problems I can't really remember in detail which I didn't suspect were, but now do may be related. So in short: HEEEEEEEEEEEEELP My Linux is having a mental breakdown!!! (<: So I don't think clearing Okular's recent list can fix all that! Hope this can steer someone in the know in the right direction. I would love to use KDE's built in bug reporting facility, to gather all the right logs, but so far it has never worked on Arch for as long as I knew of it's existence, and am lost as to what all to copy or generate copies, let alone which ones to send, or where exactly to find them... but will be glad to if asked, with the details as how to, and of course take note of them for the future. Thanks for any help!
By "David Harka's theory", I wasn't talking about Okular, but the DE.