Bug 698630 – GLib-CRITICAL **: g_key_file_set_value: assertion `g_key_file_is_key_name (key)' failed

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 698630 - GLib-CRITICAL **: g_key_file_set_value: assertion `g_key_file_is_key_name (key)' failed


Summary:	GLib-CRITICAL **: g_key_file_set_value: assertion `g_key_file_is_key_name (ke...


Status:	RESOLVED FIXED

Product:	libgoffice
Classification:	Other
Component:	General
Version:	GIT
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Jody Goldberg
QA Contact:	Jody Goldberg

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2013-04-23 01:44 UTC by Andreas J. Guelzow
Modified:	2014-03-12 18:37 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Andreas J. Guelzow 2013-04-23 01:44:22 UTC

new gnumeric
print preview

yields

GLib-CRITICAL **: g_key_file_set_value: assertion `g_key_file_is_key_name (key)' failed

bt:

+ Trace 231834

#0 g_log
from /lib/i386-linux-gnu/libglib-2.0.so.0
#1 g_return_if_fail_warning
from /lib/i386-linux-gnu/libglib-2.0.so.0
#2 g_key_file_set_value
from /lib/i386-linux-gnu/libglib-2.0.so.0
#3 g_key_file_set_string
from /lib/i386-linux-gnu/libglib-2.0.so.0
#4 add_value_to_key_file
at /build/buildd/gtk+3.0-3.2.0/./gtk/gtkprintsettings.c line 1916
#5 g_hash_table_foreach
from /lib/i386-linux-gnu/libglib-2.0.so.0
#6 gtk_print_settings_foreach
at /build/buildd/gtk+3.0-3.2.0/./gtk/gtkprintsettings.c line 513
#7 gtk_print_settings_to_key_file
at /build/buildd/gtk+3.0-3.2.0/./gtk/gtkprintsettings.c line 1946
#8 _gtk_print_operation_platform_backend_launch_preview
at /build/buildd/gtk+3.0-3.2.0/./gtk/gtkprintoperation-unix.c line 256
#9 preview_print_idle_done
at /build/buildd/gtk+3.0-3.2.0/./gtk/gtkprintoperation.c line 555
#10 gdk_threads_dispatch_free
at /build/buildd/gtk+3.0-3.2.0/./gdk/gdk.c line 767
#11 ??
from /lib/i386-linux-gnu/libglib-2.0.so.0
#12 ??
from /lib/i386-linux-gnu/libglib-2.0.so.0
#13 g_main_context_dispatch
from /lib/i386-linux-gnu/libglib-2.0.so.0
#14 ??
from /lib/i386-linux-gnu/libglib-2.0.so.0
#15 g_main_loop_run
from /lib/i386-linux-gnu/libglib-2.0.so.0
#16 print_pages
at /build/buildd/gtk+3.0-3.2.0/./gtk/gtkprintoperation.c line 3059
#17 gtk_print_operation_run
at /build/buildd/gtk+3.0-3.2.0/./gtk/gtkprintoperation.c line 3233
#18 gnm_print_sheet
at print.c line 1861
#19 cb_file_print_preview
at wbc-gtk-actions.c line 309

Comment 1 Morten Welinder 2013-04-23 01:53:29 UTC

No critical here.

Looks non-gnumeric anyway.

Comment 2 Andreas J. Guelzow 2013-04-23 02:06:25 UTC

I didn't find any bug report in gtk that remotely matched...

Comment 3 Matthias Clasen 2013-04-24 01:20:44 UTC

could you tell us what the key in question was ? I don't see that information in the backtrace

Comment 4 Andreas J. Guelzow 2013-04-24 02:34:56 UTC

I can just look for that in the trace:

+ Trace 231837

#4 add_value_to_key_file
at /build/buildd/gtk+3.0-3.2.0/./gtk/gtkprintsettings.c line 1916


obviously that is an invalid key, but it seems to be generated somewhere within gtk.

Comment 5 Marek Kašík 2014-03-12 15:39:47 UTC

Hi,

this is a bug in gnumeric.

The key/values pairs of GtkPrintSettings are stored as [value_1, key_1, value_2, key_2, ...] list in org.gnome.gnumeric.printsetup's gtk-setting key.

gnm_conf_get_print_settings() of gnumeric-conf.c supposes this ordering but it has changed somewhere so that when I print it it shows as [key_1, value_1, key_2, value_2, ...] list. So the gnm_conf_get_print_settings() swaps key and value when it calls gtk_print_settings_set().

I'm reassigning this back to gnumeric.

Regards

Marek

Comment 6 Morten Welinder 2014-03-12 18:37:23 UTC

This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.