After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 654843 - MultiLoadAppletFactory::MultiLoadApplet
MultiLoadAppletFactory::MultiLoadApplet
Status: RESOLVED FIXED
Product: gnome-panel
Classification: Other
Component: libpanel-applet
2.32.x
Other Linux
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
: 637219 650017 669781 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-07-18 11:58 UTC by Martin Lukeš
Modified: 2012-06-25 12:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.31/2.32


Attachments
Possible fix. (1.32 KB, patch)
2011-11-13 19:08 UTC, Joachim Breitner
committed Details | Review

Description Martin Lukeš 2011-07-18 11:58:50 UTC
Virtually every time I login to GNOME the System Load applet disappears and the following window pops-out.

The panel encountered a problem while loading MultiLoadAppletFactory::MultiLoadApplet
Do you want to delete the applet from your configuration?

A always hit Don't remove button and after I relogin, the System Load applet is back and running OK.

My configuration is:
Unbuntu 11.04
GNOME 2.32.1
System Load applet 2.32.1.1
Comment 1 André Klapper 2011-08-22 20:17:49 UTC
Did you file a bug report against your distribution?
As I see Ubuntu 11.04, do you use Unity?
Comment 2 Akhil Laddha 2011-10-07 06:00:19 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 3 Martin Lukeš 2011-10-07 10:57:30 UTC
Sorry, previous mail must have slipped through my inbox.

To answer your questions André.
No, I do not use Unity, just GNOME (with default Compiz).
And no, I did not report it on Launchpad because there are number of similar bugs (some of them really old) and are unresolved.

I hope someone of GNOME devs may have help me.
Comment 4 André Klapper 2011-10-07 11:02:23 UTC
(In reply to comment #3)
> because there are number of similar
> bugs (some of them really old) and are unresolved.

Links are welcome...
Comment 5 Martin Lukeš 2011-10-07 11:07:43 UTC
He is list http://goo.gl/mp7g1

Can I do something on my side when bug occurs? Do you want some logs or configuration of something?

Thanks for your help!
Comment 6 ccprog 2011-10-16 11:25:02 UTC
I see the same error, but with randomly changing applets that will not load - on every occurence it is only one of them. Here is a list:
MultiLoadAppletFactory::MultiLoadApplet
GWeatherAppletFactory::GWeatherApplet
MixerAppletFactory::MixerApplet
ClockAppletFactory::ClockApplet (that is the only one where I am not sure it was ever affected)
NotificationAreaAppletFactory::NotificationArea
WnckletFactory::ShowDesktopApplet
TrashAppletFactory::TrashApplet

NullApplet is also loaded.

~.xsessionerrors reports
** (gnome-panel:1525): WARNING **: Failed to load applet MixerAppletFactory::MixerApplet:
GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Keine derartige Schnittstelle »org.gnome.panel.applet.AppletFactory« des Objekts im Pfad /org/gnome/panel/applet/MixerAppletFactory

System is the same, Ubuntu 11.04 with Gnome 2.32.1(.1), Classical Desktop

See also the report here:
http://ubuntuforums.org/showthread.php?t=1844026
Comment 7 Joachim Breitner 2011-11-13 14:54:15 UTC
I can confirm this on Debian, gnome-panel-3.0.2-1, usually with either the gnote or the link-monitor-applet, but also occasionally with the multiload applet.
Comment 8 Joachim Breitner 2011-11-13 14:56:11 UTC
This might be a duplicate of 650017.

https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/727660 mentions that it might be related to auto-login, which I do use, but I also observe this when re-logging in.
Comment 9 Joachim Breitner 2011-11-13 18:28:40 UTC
The race condition might be between panel_applet_factory_register_service, which registers the dbus service, and sets up a callback for GBusNameAcquiredCallback and the callback function on_name_acquired(), which actually registers the object with the service.

On the gnome-panel side, the method is called in on_factory_appeared(). This is triggered when the PANEL_APPLET_BUS_NAME "org.gnome.panel.applet.%s" becomes available.

So indeed, it is possible that the dbus server will flag the availability of the busname to the gnome-panel before the applet had time to register the object.
Comment 10 Joachim Breitner 2011-11-13 19:08:09 UTC
According to the documentation http://developer.gnome.org/gio/2.26/gio-Owning-Bus-Names.html#g-bus-own-name one can add object before the name is available by using another callback function. The attached patch implements this. It’s a bit hard to test that a callback function does not exist any more, but at least stuff still works.
Comment 11 Joachim Breitner 2011-11-13 19:08:35 UTC
Created attachment 201328 [details] [review]
Possible fix.
Comment 12 Joachim Breitner 2011-12-13 08:03:12 UTC
Just a quick query: What is the status of this bug? I have to keep patching my distribution packages to get that fix, and it is getting annoying...
Comment 13 Joachim Breitner 2012-05-17 21:21:57 UTC
I have been using the patch for several months now and it reliably makes the problem disappear, while it reliably appears without it. I’d appreciate if the patch could be applied to libpanel-applets.

Maybe this bug needs to be reassigned to the correct component first?
Comment 14 Vincent Untz 2012-05-21 06:54:23 UTC
Comment on attachment 201328 [details] [review]
Possible fix.

Thanks, this looks good, I've pushed this!
Comment 15 Vincent Untz 2012-05-21 06:55:03 UTC
*** Bug 669781 has been marked as a duplicate of this bug. ***
Comment 16 Vincent Untz 2012-05-24 11:22:37 UTC
I forgot to close the bug, sorry for the spam.
Comment 17 Vincent Untz 2012-05-24 11:22:58 UTC
*** Bug 650017 has been marked as a duplicate of this bug. ***
Comment 18 Vincent Untz 2012-06-25 12:42:27 UTC
*** Bug 637219 has been marked as a duplicate of this bug. ***