[Bug 121084] Changed - Segmentation fault when trying to edit or set an unset value
bugzilla-daemon@widget.gnome.org
bugzilla-daemon@widget.gnome.org
Tue, 11 Nov 2003 09:14:38 -0500 (EST)
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=121084
Changed by seb128@debian.org.
--- shadow/121084 Fri Oct 31 10:25:42 2003
+++ shadow/121084.tmp.24495 Tue Nov 11 09:14:38 2003
@@ -1,13 +1,13 @@
Bug#: 121084
Product: gconf-editor
Version: unspecified
OS: other
OS Details:
-Status: NEW
-Resolution:
+Status: RESOLVED
+Resolution: FIXED
Severity: critical
Priority: High
Component: general
AssignedTo: gconf-editor-maint@bugzilla.gnome.org
ReportedBy: unknown@bugzilla.gnome.org
TargetMilestone: ---
@@ -106,6 +106,14 @@
gconf_value_free() should not be called with an empty argument. I've
attached a another patch with a simple modification (the patch work
fine and has been tested by 2 people).
I would like to commit it (the fix is pretty easy and the bug opened
for 2 months).
+
+------- Additional Comments From seb128@debian.org 2003-11-11 09:14 -------
+2003-11-11 Sebastien Bacher <seb128@debian.org>
+
+ * src/gconf-editor-window.c: (gconf_editor_new_key_response),
+ (gconf_editor_popup_window_edit_key):
+ Commited patch to fix the crash with unset values
+ (Closes: 121084).