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 515340 - Add a way to prioritise plugin load
Add a way to prioritise plugin load
Status: RESOLVED FIXED
Product: gnome-settings-daemon
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks: 466458
 
 
Reported: 2008-02-09 03:10 UTC by Bastien Nocera
Modified: 2008-02-22 23:16 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Fix plugin sorting (700 bytes, patch)
2008-02-11 10:04 UTC, Wouter Bolsterlee (uws)
committed Details | Review

Description Bastien Nocera 2008-02-09 03:10:50 UTC
XrandR, font sizes and sound server setup should probably be high on the list, to avoid resizing/flashing during startup, and allow sounds to be played ASAP.

See also bug 466458 comment 10
Comment 1 Bastien Nocera 2008-02-09 20:32:55 UTC
Maybe the media-keys would need to be in earlier than the sound ;)
http://www.grillbar.org/wordpress/?p=24
Comment 2 Jens Granseuer 2008-02-09 23:04:00 UTC
2008-02-09  Jens Granseuer  <jensgr@gmx.net>

        Support for defining plugin start order got lost in the split from
        gnome-control-center, but it is essential for some plugins to work
        correctly. With this change the "Priority" keyword can be used in the
        ".gnome-settings-plugin" file to set plugin priorities. Priority can
        take values from 1 upwards, with 1 being maximum priority and 100
        being the default if nothing is specified by the plugin. For multiple
        plugins with identical priority start order is undefined. (bug #515340)

        * gnome-settings-daemon/gnome-settings-plugins-engine.c:
        (gnome_settings_plugins_engine_load), (activate_plugin),
        (compare_location), (compare_priority),
        (gnome_settings_plugins_engine_load_file),
        (gnome_settings_plugins_engine_load_all),
        (gnome_settings_plugins_engine_init),
        (gnome_settings_plugins_engine_shutdown),
        (gnome_settings_plugins_engine_get_plugins_list),
        (gnome_settings_plugins_engine_get_plugin_copyright),
        (gnome_settings_plugins_engine_get_plugin_priority):
        * gnome-settings-daemon/gnome-settings-plugins-engine.h: add back
        support for defining plugin start order

What's left now is defining priorities for the plugins we ship. Suggestions welcome.
Comment 3 Wouter Bolsterlee (uws) 2008-02-11 10:04:53 UTC
Created attachment 104907 [details] [review]
Fix plugin sorting

The result of g_slist_sort should be reassigned to the list variable, afaics.
Comment 4 Jens Granseuer 2008-02-11 10:15:50 UTC
Right, thanks. Please apply.
Comment 5 Rodrigo Moya 2008-02-11 10:55:44 UTC
Patch committed to trunk, thanks
Comment 6 Jens Granseuer 2008-02-11 12:12:28 UTC
This bug isn't closed, yet, though. See comment #2.
Comment 7 William Jon McCann 2008-02-22 20:14:08 UTC
So, actually, I think it may be better to define the priority in gconf.  This way gdm can use a different order if necessary.
Comment 8 William Jon McCann 2008-02-22 23:16:38 UTC
I'm going to mark this fixed.  We should consider how to prioritize the plugins separately.

2008-02-22  William Jon McCann  <jmccann@redhat.com>

	* data/gnome-settings-daemon.schemas.in:
	* gnome-settings-daemon/gnome-settings-manager.c: (_load_file):
	* gnome-settings-daemon/gnome-settings-plugin-info.c:
	(gnome_settings_plugin_info_set_priority):
	* gnome-settings-daemon/gnome-settings-plugin-info.h:
	Allow gconf to override priorities.  Set sound plugin
	priority to 1 (highest).
	Fixes #515340