Bug 187219

Summary: gconf-editor goes unresponsive when you check or uncheck a tick box
Product: [Fedora] Fedora Reporter: Dave Tapley <dukedave>
Component: gconf-editorAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-03-31 03:10:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Terminal output when checking the trash_visible from true to false. none

Description Dave Tapley 2006-03-29 10:57:17 UTC 
Description of Problem:
gconf-editor goes unresponsive when you check or uncheck a tick box

Steps to reproduce the problem:
1. Run gconf-editor
2. Navigate to apps/nautilus/desktop
3. Click checkbox on <something>_visible

Actual Results:
Update to gconf appears to be made (icon disappears from desktop),
however the program does not update the checkbox to show it unchecked
and the program goes un-responsive.

Expected Results:
Checkbox changes to unchecked and program remain responsive.

How often does this happen?
Tested quite a few checkboxes, happens when toggling both ways, noted
the program also hangs when one attempts to edit a string variable. 

Additional Information:
Attached file is output when checking the trash_visible from true to
false.
Comment 1 Dave Tapley 2006-03-29 10:57:17 UTC 
Created attachment 126970 [details]
Terminal output when checking the trash_visible from true to false.
Comment 2 Tim Mayberry 2006-03-31 03:04:10 UTC 
I also noticed this but after updating the gconf-editor package using yum update
I no longer can reproduce this bug.

If there is a newer version in fc5 updates can you see if you still experience
the problem after an upgrade.
Comment 3 Ray Strode [halfline] 2006-03-31 03:10:40 UTC 
Hi Dave,

As Tim mentioned, this bug was fixed in an FC5 update.  I'm going to close this
report, but if after updating you still problems, feel free to reopen.

Thanks much!

*** This bug has been marked as a duplicate of 186834 ***