Red Hat Bugzilla – Bug 1290905
[abrt] obmenu: minidom.py:522:__getitem__:KeyError: 'name'
Last modified: 2016-11-24 09:44:26 EST
Version-Release number of selected component:
cmdline: /usr/bin/python /bin/obmenu
runlevel: N 5
Traceback (most recent call last):
File "/bin/obmenu", line 614, in <module>
File "/bin/obmenu", line 607, in init
File "/bin/obmenu", line 41, in createTree
if self.menu.getMenu(it["id"]) and it["action"] == "":
File "/usr/lib/python2.7/site-packages/obxml.py", line 340, in getMenu
d = self._get_item_props(i)
File "/usr/lib/python2.7/site-packages/obxml.py", line 117, in _get_item_props
accion = it.attributes["name"].nodeValue
File "/usr/lib64/python2.7/xml/dom/minidom.py", line 522, in __getitem__
Local variables in innermost frame:
self: <xml.dom.minidom.NamedNodeMap object at 0x7fef00a98f80>
Created attachment 1104832 [details]
Created attachment 1104834 [details]
I experience the exact same error on Fedora 22/x86_64 (obmenu-1.0-17/python -2.7.10-8).
I found that my custom menu.xml file (in ~/.config/openbox/) was triggering the problem. To test, I removed it and obmenu read /etc/xdg/openbox/menu.xml and worked as expected. My custom menu.xml file had a key inside <item> that should not have been there.
Basically, I had this syntax, which caused the error:
When I moved the comment key to be nested in action, all was well:
This page helped me:
My comment key is being ignored, I think - I am not sure it is valid...but that is beside the point.
At any rate, it would be nice if obmenu was more clear about the syntax error, or could at least tell the user that it failed to parse the XML file, and supplied the file name.
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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'
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 23 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.