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 644571 - critical assertion due to wrong variant type
critical assertion due to wrong variant type
Status: RESOLVED FIXED
Product: gnome-settings-daemon
Classification: Core
Component: plugins
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2011-03-12 16:20 UTC by Adam Dingle
Modified: 2011-03-14 13:07 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
patch (1.07 KB, patch)
2011-03-12 16:20 UTC, Adam Dingle 		none Details | Review

Description Adam Dingle 2011-03-12 16:20:13 UTC 
Created attachment 183217 [details] [review]
patch

gnome-settings-daemon emits a critical assertion on startup:

(gnome-settings-daemon:6205): GLib-CRITICAL **: the GVariant format string `(u)' has a type of `(u)' but the given value has a type of `u'

Patch attached.
Comment 1 Matthias Clasen 2011-03-12 22:33:46 UTC 
Another good catch, thanks
Comment 2 Adam Dingle 2011-03-13 17:08:46 UTC 
Thanks for taking this patch, Matthias.  Unfortunately the patch I submitted was improperly applied.  My patch changed "(u)" to "u" in gsd_updates_refresh_init, but when you committed this you instead changed "(u)" to "u" in session_presence_signal_cb, so the critical assertion is still occurring.

Not sure how to reopen this bug (or whether that's even something I can do).
Comment 3 Matthias Clasen 2011-03-14 13:07:01 UTC 
Thanks for paying attention. Hopefully fixed now.