Bug 1135447

Summary: [abrt] terminator: configobj.py:567:__getitem__:KeyError: None
Product: [Fedora] Fedora Reporter: kevin.chopra
Component: terminatorAssignee: Dominic Hopf <dmaphy>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: dmaphy, steve
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/fa7ebe41e71c89b2016c1cf105f99745389da076
Whiteboard: abrt_hash:5eb5e5732500119e6652045d997a37e35dfb4a23
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 22:18:45 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
File: backtrace
none
File: environ none

Description kevin.chopra 2014-08-29 10:41:46 UTC
Version-Release number of selected component:
terminator-0.97-4.fc20

Additional info:
reporter:       libreport-2.2.3
cmdline:        /usr/bin/python /usr/bin/terminator
executable:     /usr/bin/terminator
kernel:         3.15.10-200.fc20.x86_64
runlevel:       N 5
type:           Python
uid:            1000

Truncated backtrace:
configobj.py:567:__getitem__:KeyError: None

Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/terminatorlib/prefseditor.py", line 1236, in on_layout_profile_command_changed
    self.layouteditor.on_layout_profile_command_activate(widget)
  File "/usr/lib/python2.7/site-packages/terminatorlib/prefseditor.py", line 1477, in on_layout_profile_command_activate
    layout[self.layout_item]['command'] = command
  File "/usr/lib/python2.7/site-packages/terminatorlib/configobj/configobj.py", line 567, in __getitem__
    val = dict.__getitem__(self, key)
KeyError: None

Local variables in innermost frame:
self: {'child1': {'type': 'Terminal', 'parent': 'window0', 'profile': 'default', 'command': '', 'position': '', 'size': ['-1', '-1']}, 'window0': {'type': 'Window', 'parent': '', 'profile': 'default', 'command': '', 'position': '', 'size': ['-1', '-1']}}
key: None

Comment 1 kevin.chopra 2014-08-29 10:41:48 UTC
Created attachment 932620 [details]
File: backtrace

Comment 2 kevin.chopra 2014-08-29 10:41:49 UTC
Created attachment 932621 [details]
File: environ

Comment 3 Fedora End Of Life 2015-05-29 12:45:30 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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 this bug is closed as described in the policy above.

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 2015-06-29 22:18:45 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.