[SOLVED] lspci is attempting to access sys_admin. Is this bad?
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
lspci is attempting to access sys_admin. Is this bad?
Sorry for what are probably basic questions. I installed Fedora 17 with Gnome in my Dell Latitude 600 laptop a couple of days ago. Each time I turn it on I get a warning at the top of the gnome screen. When I open it, it says the following:
This source process : lspci
Attempted this access : sys_admin
Reading the info in the warning window it says if I really want to do this I should:
Do
Setsebool -P allow_polyinstantiation 1
My questions are what does all this mean and do I want to do what is suggested? From what info I have been able to find I believe it has something to do with the pci buss and system admin privileges. And I can't find anything about polyinstantiation. This is the first version of Linux I have ever been able to get up and running so obviously I am very much a newbie.
OK I have been researching and trying to understand what is going on. I understand now that SeLinux is a security enhanced version of the Linux kernal. And I understand it works be keeping different parts of the OS from having unneeded access to the other parts of the OS. This prevents an infected or defective program from infecting or corrupting another program of the OS. Is this all correct? But I still don't understand why lspci is trying to access sys_admin. And I don't know if I should let it or not. Is this a bug in Fedora 17 or is it just the way my system is set up. Or is it even possibly a hardware problem.
Well I am not sure what happened but the problem seems to be fixed. I had to leave for a while and shut the computer completely down. When I booted it back up the problem did not come back. Apparently when I ran the command the first time it installed something through Yum that fixed the problem. Thanks for the info about the bug because trying to install the fix for the bug fixed my problem even though I got the message that said there was no package with that number. Thanks for the help.
Now I am even more confused because the problem has come back. When I turned the computer on again the exact same error message came up. So I guess I am back to the question of will one of the files I listed in my previous post fix this problem or should I be looking for something else? Being totally new to Linux I am hesitant to download a file if I don't understand what it will do.
This might be a good time to point out that Fedora is RedHat's bleeding edge R&D distro, & therefore this kind of thing is not unknown.
Its generally stable-ish, but its not supposed to be used for serious stuff eg at work.
If you want free RHEL+stable, go Centos or Scientific Linux.
I understand that Fedora is a test bed for Redhat, however it is the first version of Linux that has installed and run without crashing on my laptop. It also found my wifi card and got it working without any major help from me except to tell the card to turn on. So to say the least I am highly impressed with Fedora 17 compared to the other distros I have tried.
Ok back to the subject of the thread, I did an update yesterday of several megs of data. Since that update I have turned the laptop off and back on several times. The error has not come back in any of those times. It appears the updates solved the problem. Thanks for the help.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.