Gnome-panel fails to load applets after re-login

[Jeffrey Knockel]

Binary package hint: gnome-applets

After logging in, then logging out, and then logging back in again (or logging in, pressing ctrl-alt-backspace, and logging back in again), gnome-panel fails to load some applets with errors such as the following:

"The panel encountered a problem while loading 'OAFIID:GNOME_GWeatherApplet'. Do you want to delete the applet from your configuration?"

When I run gnome-panel from the terminal, it outputs:

** (gnome-panel:6140): WARNING **: panel-applet-frame.c:1278: failed to load applet OAFIID:GNOME_GWeatherApplet:
Failed to resolve, or extend '!prefs_key=/apps/panel/applets/applet_1/prefs;background=none:;orient=up;size=x-small;locked_down=false

** (gnome-panel:6140): WARNING **: panel-applet-frame.c:1278: failed to load applet OAFIID:GNOME_MixerApplet:
Failed to resolve, or extend '!prefs_key=/apps/panel/applets/applet_0/prefs;background=none:;orient=up;size=x-small;locked_down=false

Deleting and re-adding the applets does not seem to help. I can only get them back by doing a full reboot. I can reproduce this on two gutsy machines that are all up-to-date. I'm running gnome-panel 2.20.0.1.

[Jeffrey Knockel (jeff250)]

Accidentally assigned to wrong package.

[Pedro Villavicencio (pedro)]

Thanks for your report. I cannot reproduce this behavior, not confirming for now.

[Sebastien Bacher (seb128)]

Thank you for your bug. Does it happen if you stop bonono-activation-server and evolution-data-server before the new login?

[Ernst Persson (ernstp)]

I've got the same issue.
No, if I kill those after logout applets load fine when I log in.
It does not happen for a newly created user.

[Stephen (sjspams)]

Confirming that stopping the above processes before logging in again fixes the problem.

[Jeffrey Knockel (jeff250)]

Yes, when I kill those processes before logging in again, I cannot reproduce the bug.

[Javier Cabezas (javier-cabezas)]

I confirm this bug. Killing eds and bonobo processes before logging in fixes the problem for me, too.

[Sebastien Bacher (seb128)]

that's a duplicate of bug #90258

[Herman Jongkind (herman-jongkind)]

I had the same problem. A workaround that worked for me is that I removed my old account from another admin account without removing my home folder. After that I re-created my old account with a new USER ID (it was 1000, I changed it to 1010).