[okular] [Bug 440086] New: Read and closed documents popping up on every reboot

[Bob English]

https://bugs.kde.org/show_bug.cgi?id=440086

            Bug ID: 440086
           Summary: Read and closed documents popping up on every reboot
           Product: okular
           Version: 21.04.3
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: okular-devel at kde.org
          Reporter: bobofenglish at zoho.com
  Target Milestone: ---

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.

-- 
You are receiving this mail because:
You are the assignee for the bug.