Bug 242652 - Revelation: Error when selecting entry
Summary: Revelation: Error when selecting entry
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: revelation
Version: el5
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Thorsten Leemhuis
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 237077
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-06-05 10:04 UTC by Heiko Adams
Modified: 2008-06-27 17:41 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-06-27 17:41:49 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Heiko Adams 2007-06-05 10:04:14 UTC
Description of problem:
When selecting an Entry in Revelation the following error message appears:

Traceback (most recent call last):
  File "/usr/bin/revelation", line 406, in <lambda>
    self.tree.selection.connect("changed", lambda w:
self.__state_entry(self.tree.get_selected()))
  File "/usr/bin/revelation", line 445, in __state_entry
    e = self.entrystore.get_entry(iter)
  File "/usr/lib/python2.4/site-packages/revelation/data.py", line 400, in get_entry
    e = self.get_value(iter, COLUMN_ENTRY)
  File "/usr/lib/python2.4/warnings.py", line 61, in warn
    warn_explicit(message, category, filename, lineno, module, registry)
  File "/usr/lib/python2.4/warnings.py", line 82, in warn_explicit
    for item in filters:
TypeError: unknown type (null)
When selecting an entry after this message appears the program crashes

Version-Release number of selected component (if applicable):
revelation-0.4.11-2.el5

How reproducible:
allways

Comment 2 Heiko Adams 2007-06-13 19:27:15 UTC
So the only solution at the moment is to sit around and wait until red hat comes
down to fix this bug or am I wrong?

Comment 3 Thorsten Leemhuis 2007-09-01 11:26:02 UTC
(In reply to comment #2)
> So the only solution at the moment is to sit around and wait until red hat comes
> down to fix this bug or am I wrong?

Yes. (And sorry for the late reply)

From Bug 237077, comment #4: "proposing this for 5.2."

Comment 4 Thorsten Leemhuis 2008-06-27 17:41:49 UTC
Some cleanups

(In reply to comment #3)
> > So the only solution at the moment is to sit around and wait until red hat 
> > comes down to fix this bug or am I wrong?
> Yes. (And sorry for the late reply)
> From Bug 237077, comment #4: "proposing this for 5.2."

Bug 237077 got closed as ERRATA, so this should be fixed as well.



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