Red Hat Bugzilla – Bug 485613
Sealert No gui
Last modified: 2009-04-03 16:29:07 EDT
Created attachment 331959 [details]
Description of problem: Clicking on taskbar "star" doesn't display window.
could not attach to desktop process
GNU gdb (GDB) Fedora (18.104.22.16890210-1.fc11)
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu".
For bug reporting instructions, please see:
"/usr/bin/sealert": not in executable format: File format not recognized
Version-Release number of selected component (if applicable):
How reproducible: always gnome\lxde co-install
on lxde login
Steps to Reproduce:
1. wait for any alert
Actual results: Nothing
Expected results: Alert window displayed
If you type
Does the browser come up?
(In reply to comment #1)
> If you type
> sealert -b
> Does the browser come up?
no, no errors shown just goes back to prompt.
Is sealert running
ps auxww | grep sealert
Anything being reported in /var/log/messages or /var/log/setroubleshoot/*
ps auxww | grep sealert
frank 8461 0.0 0.1 4232 704 pts/1 S+ 19:15 0:00 grep sealert
ps auxww | grep sealert
root 8439 1.0 0.1 4232 700 pts/0 S+ 19:14 0:00 grep sealert
there are some sealerts in /var/log/messages
SELinux is preventing the logrotate from using potentially mislabeled files (/root)
SELinux is preventing consoletype (consoletype_t) "read" to inotify (inotifyfs_t)
SELinux is preventing loadkeys (loadkeys_t) "read" to frank (user_home_dir_t)
All I get with -l switch for all above
/usr/bin/sealert -l d637eee9-3e7a-4355-b55e-ff2008cb29bb
query_alerts error (1003): id (d637eee9-3e7a-4355-b55e-ff2008cb29bb) not found
last date Saturday empty 0 bytes
Have tried fixfiles onboot
The AVC's I can fix and the sealert should be fixed if it was reported in the newer version of setroubelshoot.
If you log out and log back in, does the sealer start to work?
If I log out\in reboot.
If I then see a task bar alert "star".
clking on it goes nowhere, the same if the text Show\hide" is clicked.
Similar if log out\in and /usr/bin/sealert -b
Created attachment 332350 [details]
Since yesterdays rawhide updates. Have now managed to get a crash report.
Files versions above are still the same.
Can you edit /etc/setroubleshoot/setroubleshoot.cfg
And change the level to DEBUG
# level: Global logging level. Levels are the same as in the python logging
# module, but are case insenstive. The level may also be specified as an
# integer. The defined levels in severity order are:[CRITICAL, ERROR, WARNING,
# INFO, DEBUG]
level = DEBUG
Then see if sealert creates a /tmp/sealert.log file.
(In reply to comment #8)
> Not related.
> Can you edit /etc/setroubleshoot/setroubleshoot.cfg
> And change the level to DEBUG
> # level: Global logging level. Levels are the same as in the python logging
> # module, but are case insenstive. The level may also be specified as an
> # integer. The defined levels in severity order are:[CRITICAL, ERROR, WARNING,
> # INFO, DEBUG]
> level = DEBUG
Changed this: level = DEBUG
now /usr/bin/sealert -b brings up the correct window.
(The original "warning", was in lower-case, any relevance?)
> Then see if sealert creates a /tmp/sealert.log file.
No /tmp/sealert.log file.
There are a few avc's, one of which is preventing network connection,
will post to test-list later, as a job lot.
Click SELinux Troubleshooter in panel menu.
Traceback (most recent call last):
File "/usr/bin/sealert", line 108, in <module>
from setroubleshoot.analyze import *
File "/usr/lib/python2.6/site-packages/setroubleshoot/analyze.py", line 36, in <module>
from setroubleshoot.avc_audit import *
File "/usr/lib/python2.6/site-packages/setroubleshoot/avc_audit.py", line 26, in <module>
File "/usr/lib/python2.6/site-packages/audit.py", line 19, in <module>
_audit = swig_import_helper()
File "/usr/lib/python2.6/site-packages/audit.py", line 17, in swig_import_helper
if fp is not None: fp.close()
UnboundLocalError: local variable 'fp' referenced before assignment
This is a bug in the audit system
On 64 bit platforms the audit.py file is being installed in
WHile the shared libraries are in
If you copy /usr/lib/python2.6/site-packages/audit.py to
It should work.
(In reply to comment #11)
> If you copy /usr/lib/python2.6/site-packages/audit.py to
This works on current Rawhide, can we move this BZ to audit-libs-python guys, so, they can fix it?
This bug was fixed in bz 491327. Closing as duplicate. Thanks for reporting the bug.
*** This bug has been marked as a duplicate of bug 491327 ***