Comment 11 for bug 680910

I got a at least very similar bug, hopefully the same:

Actually, there are 3 different cases:

a) popper works (quite often)
b) popper does not ?start, crashes?
c) popper runs, displays messages, but the main popper entry in the messages menu is lost. Only messages are displayed.

Popper log says:

Keyring.get(self, user): not in Keyring.

It maybe a race condition at startup because the system runs on a SSD.
My keyring has an empty password and i am using autologin.

Manually starting it with "nohup <popperscript.sh> &" works always!

Version 22 worked perfectly for me.