Bug 910987 - [abrt] edsadmin-1.0-10.fc18: EDSAdmin.py:390:OnPropertiesClicked:AttributeError: 'NoneType' object has no attribute 'get_value'
Summary: [abrt] edsadmin-1.0-10.fc18: EDSAdmin.py:390:OnPropertiesClicked:AttributeErr...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: edsadmin
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ignacio Vazquez-Abrams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d9b349fc84a894fbfe8f87b54f2...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-14 06:55 UTC by Moritz Baumann
Modified: 2014-02-05 19:09 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 19:09:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (585 bytes, text/plain)
2013-02-14 06:55 UTC, Moritz Baumann
no flags Details
File: environ (2.57 KB, text/plain)
2013-02-14 06:55 UTC, Moritz Baumann
no flags Details

Description Moritz Baumann 2013-02-14 06:55:03 UTC
Version-Release number of selected component:
edsadmin-1.0-10.fc18

Additional info:
cmdline:        /usr/bin/python /usr/share/edsadmin/EDSAdmin.py
core_backtrace: 2ea2e8631c4ee67c9cc8e2e06279de38e7e3207d 0x186 OnPropertiesClicked /usr/share/edsadmin/EDSAdmin.py -
executable:     /usr/share/edsadmin/EDSAdmin.py
kernel:         3.7.2-201.fc18.x86_64
uid:            1000

Truncated backtrace:
EDSAdmin.py:390:OnPropertiesClicked:AttributeError: 'NoneType' object has no attribute 'get_value'

Traceback (most recent call last):
  File "/usr/share/edsadmin/EDSAdmin.py", line 390, in OnPropertiesClicked
    container = model.get_value(iter, 2)
AttributeError: 'NoneType' object has no attribute 'get_value'

Local variables in innermost frame:
model: None
selection: <gtk.TreeSelection object at 0x2dec370 (GtkTreeSelection at 0x2e66c00)>
toolbutton: <gtk.ImageMenuItem object at 0x2dec190 (GtkImageMenuItem at 0x283c600)>
self: <__main__.Main instance at 0x2dd4ef0>
iter: None

Potential duplicate: bug 722586

Comment 1 Moritz Baumann 2013-02-14 06:55:06 UTC
Created attachment 697076 [details]
File: backtrace

Comment 2 Moritz Baumann 2013-02-14 06:55:08 UTC
Created attachment 697077 [details]
File: environ

Comment 3 Fedora End Of Life 2013-12-21 11:23:28 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2014-02-05 19:09:35 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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