Bug 677408

Summary: [abrt] policycoreutils-2.0.83-33.10.fc14: main: Process /usr/sbin/restorecond was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Jim Fischer <fischerjd>
Component: policycoreutilsAssignee: Daniel Walsh <dwalsh>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: dwalsh, emanuelg, mgrepl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:b5e46d01bc4050255c080e902112d9f2c40c7b4d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-07-27 13:22:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Jim Fischer 2011-02-14 17:04:12 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/sbin/restorecond -u
component: policycoreutils
crash_function: main
executable: /usr/sbin/restorecond
kernel: 2.6.35.10-74.fc14.x86_64
package: policycoreutils-2.0.83-33.10.fc14
rating: 4
reason: Process /usr/sbin/restorecond was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1297702594
uid: 560

How to reproduce
-----
1. Login manager is KDM.
2. As soon as I log in and see the KDE desktop, there is a delay of about one minute when the system is unresponsive (menus don't open, applications don't start, etc.), and then the `restorecond' crash report appears.
Comment 1 Jim Fischer 2011-02-14 17:04:14 UTC 
Created attachment 478669 [details]
File: backtrace
Comment 2 Daniel Walsh 2011-02-18 21:21:04 UTC 
I think restorecond is a side effect of what every is wrong with your homedir.

If you disable destorecond does everything work ok?

Do the menus appear after restorecond crashes?  What kind of homedir are you using?
Comment 3 Greg Emanuel 2011-03-02 17:50:54 UTC 
(In reply to comment #2)
> I think restorecond is a side effect of what every is wrong with your homedir.
> 
> If you disable destorecond does everything work ok?
> 
> Do the menus appear after restorecond crashes?  What kind of homedir are you
> using?

The original poster--Jim Fischer--is my coworker so I can answer your questions.

I have not tried disabling restorecond.

Yes, the system works fine after restorecond crashes it's just a delay after login. The homedir's are automounted via autofs and a RHEL 6 NFS server.
Comment 4 Greg Emanuel 2011-03-02 18:13:47 UTC 
(In reply to comment #2)
> I think restorecond is a side effect of what every is wrong with your homedir.
> 
> If you disable destorecond does everything work ok?
> 
> Do the menus appear after restorecond crashes?  What kind of homedir are you
> using?

The original poster--Jim Fischer--is my coworker so I can answer your questions.

I have not tried disabling restorecond.

Yes, the system works fine after restorecond crashes it's just a delay after login. The homedir's are automounted via autofs and a RHEL 6 NFS server.
Comment 5 Greg Emanuel 2011-03-02 18:17:24 UTC 
(In reply to comment #2)
> I think restorecond is a side effect of what every is wrong with your homedir.
> 
> If you disable destorecond does everything work ok?
> 
> Do the menus appear after restorecond crashes?  What kind of homedir are you
> using?

The original poster--Jim Fischer--is my coworker so I can answer your questions.

I have not tried disabling restorecond.

Yes, the system works fine after restorecond crashes it's just a delay after login. The homedir's are automounted via autofs and a RHEL 6 NFS server.
Comment 6 Daniel Walsh 2011-03-02 19:16:50 UTC 
Ok since restorecond does not support NFS directories, it should be closing down anyways.  Not sure why it would crash though.
Comment 7 Greg Emanuel 2011-03-02 19:24:15 UTC 
(In reply to comment #6)
> Ok since restorecond does not support NFS directories, it should be closing
> down anyways.  Not sure why it would crash though.

Is it "safe" to turn it off? I've noticed there is a file in /etc/xdg/autostart/restorecond.desktop that invokes "EXec=/usr/sbin/restorecond -u" when a user logs in.

Also, in the /etc/selinux/restorecond_user.conf there are two lines that read
~/*
~/public_html/*

I've seen some posts where people have removed the ~/public_html/* line, but it seems to me the ~/* does a more exhaustive search and would take more time and/or have more of a tendency to cause an error. Thoughts?
Comment 8 Daniel Walsh 2011-03-02 19:52:28 UTC 
If you have nfs homedirs neither restorecond -u or restorecond as a service does anything on an nfs homedir.  So turn them off.
Comment 9 Greg Emanuel 2011-03-02 20:10:31 UTC 
(In reply to comment #8)
> If you have nfs homedirs neither restorecond -u or restorecond as a service
> does anything on an nfs homedir.  So turn them off.

I noticed in chkconfig restorecond is off for levels 0 - 6. Is there another way to turn them off?
Comment 10 Daniel Walsh 2011-03-02 20:29:17 UTC 
Yes it is disabled by default. In order to disable restorecond at login, you can go to the preferred apps screen and turn it off.
Comment 11 Daniel Walsh 2012-07-27 13:22:15 UTC 
Since this version of Fedora is no longer supported I am closing this bugs.  If you are still seeing this bug in a current version of fedora, please reopen the bugzilla with the appropriate version number.