Hi Patrick

I know several months have passed since my last post, but nevertheless I'd still like to have this terrible annoying bug fixed – so I changed the bug status back to "Incomplete". In the meantime I'm using popper 0.27, but the problem is still the same.

I installed popper on two other machines (both with Ubuntu 10.04 LTS), whose main users also use autologin instead of the gnome login screen. On these two computers exactly the same problem as on my desktop computer occurs. On all machines the login password is the same as the gnome-keyring password.
I'm writing this because I doubt the problem is caused by a (delayed) internet connection. On one machine the internet is established through WLAN, on the other through ADSL (PPP over Ethernet) and on the third through a cable router. So I guess on those 3 machines the internet connection isn't established at exactly the same time during/after boot-up, but the malfunction of popper is identical!

To be 100% sure you know which malfunction I mean I attached 2 screenshots of the gnome indicator applet: 
· the first was taken directly after boot-up and typing in the correct password (the actual malfunction I mean)
· the second after opening and closing poppers configuration (which leads popper to work as supposed)

Before the password is typed in (or if a wrong one was entered) no popper entry appears at all.

Another little misbehaviour I discovered (which could be in relation to the main bug) is that popper only notifies about a wrong password when I launch popper_config.sh. If I type in a wrong password after boot-up nothing happens at all! Besides that, the password dialog box of popper_config.sh is in german while the one after boot-up is in english (system language is german). 
To me it seems the whole problem lies somewhere in the way popper is launched after boot-up (obviously through popper.sh) ... this seems different to the way it is launched through popper_config.sh. If I lock the keyring, kill popper's python process and type into the terminal "nohup ./usr/share/popper/popper.sh &" the english password dialog box appears. After typing in a wrong password nothing happens. After typing in the correct password, the popper entry appears, but no mail accounts an no green letter symbol -> same behaviour as after boot-up. Either way it outputs "Zeile 18: kill: %-: Kein solcher Job.", but of course I don't know what that means :p

I also tried your trial script (while popper wasn't running). I didn't really figure out what exactly I have to report... 
There are always 7 messages displayed at the maximum and no popup messages. The letter symbol is always green. Every 10 seconds the oldest message is replaced by a new one. All messages consist of a number and "(10:33)". As far as I can tell it doesn't matter if the script is started directly after boot-up or only after a few minutes. Also it makes no difference if the keyring is locked or not or if the internet connection is established or not. 
The only abnormality I noticed was the first 7 messages (10 are generated de facto, but 7 is the maximum at one time) sometimes not being displayed after the launch of the script (sometimes 1, sometimes 2 or more messages showed up). I couldn't find any regularity why they didn't show up. But every newly generated message (# 100+) was correctly displayed (filling up the list until 7, then replacing the last message).
To run the script while popper is already (correctly) running causes only a little difference: the total number of generated fake messages is displayed in the popper entry. To run the script while popper is started through popper.sh (malfunctioning) results in exactly the same behaviour (incl. coloring the letter symbol green).

Greets!
Bhabba

Btw, is there any progress concerning the bug in pythons gnomekeyring-library?