Bug 448478

Summary: traceback in "suid"
Product: [Fedora] Fedora Reporter: Miloslav Trmač <mitr>
Component: sectoolAssignee: Peter Vrabec <pvrabec>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 9CC: jhrozek
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 0.8.0-1.fc9 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-07-04 03:39:47 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:

Description Miloslav Trmač 2008-05-27 07:23:00 UTC
Description of problem:
The following traceback appeared on the terminal:

stderr from suid: Traceback (most recent call last):
  File "/usr/share/sectool/tests/suid.py", line 114, in <module>
    main()
  File "/usr/share/sectool/tests/suid.py", line 64, in main
    for gen in [ os.walk(dir) for dir in testenv['PATH'].split(':') ]:
  File "/usr/lib/python2.5/UserDict.py", line 22, in __getitem__

Version-Release number of selected component (if applicable):
sectool-0.7.4-1.i386

How reproducible:
This appeared once while running all tests from different levels from the GUI. 
I couldn't reproduce it since.

Comment 1 Jakub Hrozek 2008-05-27 16:25:25 UTC
I can't reproduce the bug myself either, I've also checked the code of the 
suid test and the only UserDict-derived class that is used is the 'testenv' 
variable which is just an alias for os.environ (from os import environ as 
testenv). So, I'm really puzzled about what's going on..

If you encounter this error again, please holler..

Comment 2 Fedora Update System 2008-07-03 10:33:08 UTC
sectool-0.8.0-1.fc9 has been submitted as an update for Fedora 9

Comment 3 Fedora Update System 2008-07-04 03:39:44 UTC
sectool-0.8.0-1.fc9 has been pushed to the Fedora 9 stable repository.  If problems still persist, please make note of it in this bug report.