Comment 10 for bug 680910

Hi Bhabba,

sorry for your broken christmas gift :-(

Man, to be honest, this bug is making me headaches!

I thought it has something to do with the popper-process starting before having a (wifi)internetconnection - that caused the problems in my reproduced case. I got a notification but no (or sometimes(?!) wrong ordered) entries in the messaging-menu. Starting popper defenitely after having a connection to the web (confirmed by pinging google in popper.sh) solved my reproduced case and would have made sense in your case, too, because you're having no issues after launching the configurator (a new popper-process is started after closing).

If you're still motivated (thank you until now!) you may want to give this trial-script, which Ralf created, a try:
-> http://media.cdn.ubuntu-de.org/forum/attachments/2695326/indi.py
-> http://media.cdn.ubuntu-de.org/forum/attachments/2695326/popper.desktop

Please download this two files, store it in a folder other than popper-folders (for example /tmp/indi ) and start indi.py (for example by typing "python /tmp/indi/indi.py" into your console). There should be shown a popper entry and 10 numbered fake-messages in the messaging-menu and every 10 secound there should be created a new fake-message. You could stop the script by hitting CTRL-C.

Because honestely i don't know where to estimate, could you please try this script in different "environments":
- Keyring closed (by cancelling all request-dialogs) <-> opened
- Internetconnection enabled <-> disabled
- Starting immediately after bootup <-> waiting a few minutes
- ...
... and combinations of these.

Thank you very very much for your patience until now. I'm hoping you're going to "keep it rollin'" with/for us.

Greets

Patrick