Bug 127039 - "Properties" fails with a Gtk error
Summary: "Properties" fails with a Gtk error
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-bind
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jason Vas Dias
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: FC3Target FC4Target
TreeView+ depends on / blocked
 
Reported: 2004-06-30 22:25 UTC by Moritz Barsnick
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version: system-config-bind-4.0.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-05-17 22:21:54 UTC


Attachments (Terms of Use)

Description Moritz Barsnick 2004-06-30 22:25:22 UTC
Description of problem:
When selecting "Properties" in system-config-bind(-gui), nothing 
happens in the GUI, and there are errors on the console.

Version-Release number of selected component (if applicable):
system-config-bind-2.0.2-8

How reproducible:
always

Steps to Reproduce:
1. run system-config-bind
2. press the "Properties" button
or
3. select File -> Properties
  
Actual results:
root@sunshine:/usr/local/Fedora_update/new > system-config-bind
Traceback (most recent call last):
  File "/usr/sbin/system-config-bind", line 436, in 
on_properties_activate
    on_bindconf_edit_button_clicked (None)
  File "/usr/sbin/system-config-bind", line 1374, in 
on_bindconf_edit_button_clicked
    zone = model.get_value (iter, COLUMN_DATA)
TypeError: iter must be a GtkTreeIter
Traceback (most recent call last):
  File "/usr/sbin/system-config-bind", line 1374, in 
on_bindconf_edit_button_clicked
    zone = model.get_value (iter, COLUMN_DATA)
TypeError: iter must be a GtkTreeIter

Expected results:
No errors, see a new window (?)

Additional info:
I haven't done _any_ bind config on this machine yet, and was hoping 
for help with a caching nameserver...

Comment 1 Moritz Barsnick 2004-11-03 19:30:16 UTC
I'm the original bug poster. I currently can't reproduce in 2.0.2-10, 
but the traceback given in the original bug description might be of 
help to track a potential issue.


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