Bug 187219 - gconf-editor goes unresponsive when you check or uncheck a tick box
Summary: gconf-editor goes unresponsive when you check or uncheck a tick box
Keywords:
Status: CLOSED DUPLICATE of bug 186834
Alias: None
Product: Fedora
Classification: Fedora
Component: gconf-editor
Version: 5
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-03-29 10:57 UTC by Dave Tapley
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-03-31 03:10:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Terminal output when checking the trash_visible from true to false. (4.00 KB, application/octet-stream)
2006-03-29 10:57 UTC, Dave Tapley
no flags Details

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 ***


Note You need to log in before you can comment on or make changes to this bug.