sealert?

[Ronlane]

Hi,
I am running Fedora 10 on my own hardware - AMD dual processor, and so forth. This system has been stable for over 16 months. Now when I login as local user, I receive the following error:

Opps, sealert hit an error!
Traceback (most recent call last):
File "/usr/bin/sealert", line 949, in <module>
print >> sys.stderr, "could not attach to desktop process"
IOError: [Errno 28] No space left on device

There is another box that only displays for a short time in the upper left of the screen:
Left click to disconnect the input method
Right click to show up the input method

Right or left clicking the mouse in the box has no effect except making the box disappear faster.

A third box does not display long enough for me to read, it says it failed to get a value...

After a minute or two a box stating my Photosmart=8100-series may not be connected appears. This is true, my printer is not presently connected. The screen is black except for the two boxes mentioned. After I hit the OK button for the error message, the box disappears and nothing else happens, the mouse pointer is visible and and has the little string of dots circling. When I close the printer notification, all that is left is the pointer. If I wait long enough the pointer will disappear, but pops back when i touch the keyboard of mouse. The system acts like it is running but not displaying. When I turn the system off the kerneloops is red and says it failed. All other process's are green - OK
http://forums.fedoraforum.org//forum/images/smilies/confused.gif

[bob]

moved to EOL

[PabloTwo]

I don't know if this will help your situation, but on more than one occasion it has restored my F12 system back from a "half dead, some services won't start at boot, some applications won't run, and all manner of weird behavior" state. And since you state that sealert pops up, that means you are running with SELinux enabled. It very well may be that SELinux is both the problem and the fix.

Right after you turn on the computer, enter the grub menu by hitting the A key at just the right time. I think that should give you a cursor to enter data on the first kernel line. Enter the number 1, or a lowercase s, hit ENTER then type B and hit enter. That should bring you to a console as root.

If I've forgotten the proper method as described above and it doesn't work, then hit the E key when the grub menu appears, use the arrow keys to put the cursor on the first Linux kernel line, Hit E again (to edit that line), then add either a 1 or s to the end and hit ENTER, then type B (to continue booting), then ENTER.

Once, and if, you get into single user mode as root, type this:
touch /.relabel
reboot
Take note that the name ".relabel" begins with a period ".". On reboot, SELinux will intervene and relabel all the files on the system to the proper security context early in the boot process. If this fixes most or all of the problems, then you should arrive at a normal log-in prompt.

[Ronlane]

Thanks for the reply. After several hours, I gave up and now installing Fedora 14.

Roner