Bug 231233 - Opps, sealert hit an error
Opps, sealert hit an error
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: setroubleshoot (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: John Dennis
Ben Levenson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-03-06 16:38 EST by Deji Akingunola
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-06-16 19:26:24 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Deji Akingunola 2007-03-06 16:38:53 EST
Description of problem:
I got the message in Summary, while updating to rawhide today. Detailed error
message below;
<<
Opps, sealert hit an error
Traceback (most recent call last):
  File "/usr/bin/sealert", line 771, in <module>
    run_as_dbus_service(username)
  File "/usr/bin/sealert", line 85, in run_as_dbus_service
    app = SEAlert(username, dbus_service.presentation_manager)
  File "/usr/bin/sealert", line 489, in __init__
    self.browser = BrowserApplet(self.username, self.alert_client)
  File "/usr/lib/python2.5/site-packages/setroubleshoot/browser.py", line 295,
in __init__
    glade_file = cfg.get('alert','browser_glade_file')
  File "/usr/lib64/python2.5/ConfigParser.py", line 520, in get
    raise NoOptionError(option, section)
NoOptionError: No option 'browser_glade_file' in section: 'alert'
>>

Version-Release number of selected component (if
applicable):setroubleshoot-1.9.3-1.fc7


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 John Dennis 2007-03-06 17:28:26 EST
The config file changed and rpm did not replace it, but rather left it as
/etc/setroubleshoot/setroubleshoot.cfg.rpmnew. Please copy or rename
setroubleshoot.cfg.rpmnew to setroubleshoot.cfg, that should fix the problem as
a quick workaround, in the mean time I'll make sure rpm replaces the file but
leaves the old one a .rpmsave

You'll have to restart things again.

service setroubleshoot restart
sealert -q
sealert -s

If that does not fix the problem for you let me know. Thanks.
Comment 2 Deji Akingunola 2007-03-06 20:21:33 EST
It seems rpm actually replaced etroubleshoot.cfg for me as I don't have
etc/setroubleshoot/setroubleshoot.cfg.rpmnew; I checked the timestamp on the
file, and it look like the right one:
[deji@agape ~]$ ll /etc/setroubleshoot/setroubleshoot.cfg
-rw-r--r-- 1 root root 5007 2007-03-05 18:42 /etc/setroubleshoot/setroubleshoot.cfg
Comment 3 Deji Akingunola 2007-06-16 19:26:24 EDT
This bug is stale, and is most like fixed by now, no?

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