Don Buchholz wrote: > On 12/26/2016 4:01 PM, Ken Stephens wrote: >> Mike C. wrote: >>>> All the Google searches show how to use semanage, but with no status for >>>> the selinux user that is created the Dbus cannot send messages to the X >>>> window system. The >>>> message I get is: >>>> >>>> Unable to contact settings server >>>> >>>> THE QUESTION, finally: >>>> How do I get out of this ChromeOS jail? I want X windows to work so I >>>> an use OpenCPN on my sailboat. >>>> >>>> >>> A quick and easy way to get out of the ChromeOS jail is to disable SELInux >>> temporarly and put it into permissive mode which shouold allow to use >>> OpenCPN and give you time to research the problem more or just be able to >>> toggle SELinx for when you use OpenCPN. >>> >>> >>> - *Permissive* - switch the SELinux kernel into a mode where every >>> operation is allowed. Operations that would be denied are allowed and >>> a >>> message is logged identifying that it would be denied. The mechanism >>> that >>> defines labels for files which are being created/changed is still >>> active. >>> >>> Temporarily switch off enforcement >>> You can switch the system into permissive mode with the following command: >>> >>> echo 0 >/selinux/enforce >>> >>> You'll need to be logged in as root, and in the sysadm_r role: >>> >>> newrole -r sysadm_r >>> >>> To switch back into enforcing mode: >>> >>> echo 1 >/selinux/enforce >>> >>> To check what mode the system is in, >>> >>> cat /selinux/enforce >>> >> Mike, >> >> Tried the echo 0 > /selinux/enforce >> # cat /selinux/enforce >> 0 >> # >> no joy, same behavior even after reboot. >> # sestatus >> SELinux status: enabled >> SELinuxfs mount: /sys/fs/selinux >> Current mode: permissive >> Mode from config file: permissive >> Policy version: 15 >> Policy from config file: default >> >> Any other ideas? >> >> Thanks for the reply, >> Ken > Because everytime you reboot, it resets the "enforce" > setting. There's a config file in /etc which you can use > to disable SELinux enforcement permanently. Don't > have a system with your distro though to figure out > exactly which one it is ... > > Your distro may or may not have the 'getenforce' and > 'setenforce' commands. But those again tend to be > temporary and "setenforce 0" will have to be executed > at every reboot. > > My old-time favorite is to edit grub.conf|grub.cfg so > the linux kernel boots with the option "selinux=0" > ... that usually does a pretty good job of permanently > disabling SELinux. (Albeit, this advice is along the lines > of "here's a gun. it's loaded. round is in the chamber. > the safety is off.") YMMV. > > And, of course, it seems that for pretty much all of > the stuff I've seen above ... you need to have 'root' > level permissions to change the SELinux setting ... > So not really understanding your issues/ChromeOS > very well, it sounds as if this could be a chicken-egg > kind of problem ... > > > _______________________________________________ > PLUG mailing list > PLUG@lists.pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug > Ended up using the trusty distribution instead of the jesse for Debian. Used the following to load the distribution: sudo ~chronos/Downloads/crouton -r trusty -i touch,xfce
Followed the instructions and now I am looking at Debian trusty distribution in an X window environment. Yepeeeee Regards, Ken _______________________________________________ PLUG mailing list PLUG@lists.pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug