[okular] [Bug 400089] Previously closed PDF's open at startup, accompanied by an error message

[Tobias Deiminger]

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

--- Comment #3 from Tobias Deiminger <haxtibal at posteo.de> ---
(In reply to dustin.fenster from comment #2)
> they are under the section [Session: saved at previous
> logout]--maybe that is what you meant.
No, I guessed "saved by user", because you initially wrote okular documents
"were all closed after use". If okular had actually been closed when you logged
out, okular can't appear in "saved at previous logout". That's at least how I
understand the XSMP protocol and ksmserver. We can discuss details in the
mailing list if you want.

But you also write "now open upon each restart". That's wired. Can you check
the timestamp of ksmserverrc for when it was last modified, and reconsider if
that timestamp matches with the last time you logged out/shutdown? On logout
ksmserver should update the "saved at previous logout" section, and possibly
existing okular entries should be vanished (unless okular is still open).

> There are also some lines such as:
> discardCommand14[$e]=rm,$HOME/.config/session/
> okular_102b23022f7285000153793688600000013880083_1538059437_972466.  Just
> pointing this out because it references okular, don't know if that's normal.
That's fine, ksmserver needs the entries to clean up old sessions.

> > Do you still get "Could not open file" this way?
> 
> Doing this does not produce the error.
Ok, sounds like your cloud service is also started during KDE login, and the
local storage is not yet available at the early stage when ksmserver restores
application sessions. Might that be?

> There are several with one of two url's, which is odd because 6 or 7 files
> are opening
Sorry, no idea about that.

> Should I simply delete all of the
> "restartCommand13=/usr/bin/okular,-session,
> 102b23022f7285000153793686000000013880082_1538059437_972580", etc. lines?
The cleanest way is probably to backup ~/.config/ksmserverrc and
$HOME/.config/session/*, then remove all those files, and restart. You should
start with a "clean" session again.

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