Description of problem: While doing L10n QA test of system-config-services in Fedora 19 for Assamese language, I found that the 'Help' option doesn't open, neither from the icon button nor from the menu option 'Contents' in menu 'Help'. When the 'Help' icon button or 'Contents' in menu 'Help' is clicked an error message is displayed on the terminal which is as such: (yelp:3989): GLib-GObject-CRITICAL **: g_param_spec_internal: assertion `(name[0] >= 'A' && name[0] <= 'Z') || (name[0] >= 'a' && name[0] <= 'z')' failed Version-Release number of selected component (if applicable): system-config-services-0.101.8-2.fc19.noarch How reproducible: Always Steps to Reproduce: 1. Set locale to Assamese 2. Run system-config-services command from terminal Actual results: 'Help' doesn't open when clicked from 'Help' icon button or from 'Contents' menu option in 'Help' menu. Expected results: Help should open
Actually it's yelp segfaulting when trying to display the help file(s) (which haven't changed in quite a while) -- this works just fine in F18 (yelp-3.6.2-1.fc18.x86_64, webkitgtk3-1.10.2-3.fc18.x86_64) but crashes in F19 (yelp-3.8.0-1.fc19.x86_64, webkitgtk3-2.0.0-1.fc19.x86_64). Even there it doesn't crash when viewing the file /usr/share/gnome/help/system-config-services/as/system-config-services.xml from e.g. an English locale, but only when e.g. executing "LANG=as_IN.UTF-8 yelp ghelp:system-config-services". Here's a rough backtrace, I suspect the problem is somewhere in webkitgtk3: (gdb) bt #0 0x00007ffff4be77cf in g_param_spec_boolean () from /lib64/libgobject-2.0.so.0 #1 0x00007ffff5f14561 in webkit_viewport_attributes_class_intern_init(void*) () from /lib64/libwebkitgtk-3.0.so.0 #2 0x00007ffff4bf710e in g_type_class_ref () from /lib64/libgobject-2.0.so.0 #3 0x00007ffff4be0023 in g_object_newv () from /lib64/libgobject-2.0.so.0 #4 0x00007ffff4be05cc in g_object_new () from /lib64/libgobject-2.0.so.0 #5 0x00007ffff5f346fb in webkit_web_view_init(_WebKitWebView*) () from /lib64/libwebkitgtk-3.0.so.0 #6 0x00007ffff4bf9960 in g_type_create_instance () from /lib64/libgobject-2.0.so.0 #7 0x00007ffff4bde4f8 in g_object_constructor () from /lib64/libgobject-2.0.so.0 #8 0x00007ffff4bdfa79 in g_object_newv () from /lib64/libgobject-2.0.so.0 #9 0x00007ffff4be05cc in g_object_new () from /lib64/libgobject-2.0.so.0 #10 0x0000000000407f27 in yelp_window_set_property () #11 0x00007ffff4bde642 in g_object_constructor () from /lib64/libgobject-2.0.so.0 #12 0x00007ffff4bdfa79 in g_object_newv () from /lib64/libgobject-2.0.so.0 #13 0x00007ffff4be0246 in g_object_new_valist () from /lib64/libgobject-2.0.so.0 #14 0x00007ffff4be05b4 in g_object_new () from /lib64/libgobject-2.0.so.0 #15 0x0000000000405e59 in application_uri_resolved () ---Type <return> to continue, or q <return> to quit--- Changing component.
Can you try it please with webkitgtk3-2.0.0-3.fc19? Thank you
Hi Tomas, The version of webkitgtk3 installed in my machine was webkitgtk3-2.0.0-1.fc19. When I upgraded it, it got upgraded to webkitgtk3-2.0.1-1.fc19 which I suppose is a more recent version. But now I am unable to open system-config-services to try it with this new version of webkitgtk3. Now, I am getting a new error whenever I run the command system-config-services. Here's the error: ImportError: No module named gui It is exactly the same as mentioned in the bug https://bugzilla.redhat.com/show_bug.cgi?id=953884 Thanks, Nilamdyuti
*** Bug 953884 has been marked as a duplicate of this bug. ***
Hi Nilamdyuti 'Help' now opens up as expected on my side with the following version. Can we close this bug? webkitgtk3-2.0.4-1.fc19.x86_64 system-config-services-0.101.8-2.fc19.noarch
(In reply to Noriko Mizumoto from comment #5) > Hi Nilamdyuti > > 'Help' now opens up as expected on my side with the following version. > Can we close this bug? > > webkitgtk3-2.0.4-1.fc19.x86_64 > system-config-services-0.101.8-2.fc19.noarch Hi Noriko, Yes, 'Help' now opens up on my side too with the following versions of webkitgtk3 and system-config-services: * webkitgtk3-2.0.4-1.fc19.x86_64 * system-config-services.noarch 0:0.101.10-1.fc19 The bug is good to be closed.