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 578677 - Registered property name in BraseroDriveSelectionClass is translated on runtime.
Registered property name in BraseroDriveSelectionClass is translated on runtime.
Status: RESOLVED FIXED
Product: brasero
Classification: Applications
Component: libbrasero-media
git master
Other Linux
: Normal normal
: 2.26
Assigned To: Brasero maintainer(s)
Brasero maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-04-11 01:50 UTC by Takeshi AIHANA
Modified: 2009-04-14 16:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description Takeshi AIHANA 2009-04-11 01:50:10 UTC
The 'sound-jucer' claimed the follows at starting up with own locale (ja_JP.UTF-8):

$ sound-juicer
(sound-juicer:19434): GLib-GObject-CRITICAL **: 
g_param_spec_internal: assertion `(name[0] >= 'A' && name[0] <= 'Z') || (name[0] >= 'a' && name[0] <= 'z')' failed

So I retrieved backtrace on gdb and traced the code of BraseroDriveSelectionClass in libbrasero-media,
then I found the incorrect code with i18N:

611 static void
612 brasero_drive_selection_class_init (BraseroDriveSelectionClass *klass)
613 {
(snip)
624 
625     g_object_class_install_property (object_class, PROP_DRIVE,
626                      g_param_spec_object (_("Drive"),
627                                   "Selected drive",
628                                   "The currently selected drive",
629                                   BRASERO_TYPE_DRIVE, G_PARAM_READWRITE));

This code looks incorrect because the property name would be translated on runtime then caused above assertion. It should be

625     g_object_class_install_property (object_class, PROP_DRIVE,
626                      g_param_spec_object ("Drive",
Comment 1 Luis Medinas 2009-04-14 16:02:56 UTC
Thanks for the heads up.

Fixed in trunk and gnome-2-26 branch.