Open J5 opened 8 years ago
Hey, thanks for reporting this. Did you update your system recently?
Please try doing the steps from the FAQ section of the readme (X as non root).
As a last advice, please try to set SELinux to permissive or off and see if it would work that way.
Let me know what model of Chromebook do you have and which chromeos version are you using.
Good luck!
I'm on a Pixel 2 Version 53.0.2785.103 beta (64-bit) Platform 8530.81.0 (Official Build) beta-channel samus ARC Version 3251841 Firmware Google_Samus.6300.174.0 I did the steps in the FAQ and it still doesn't work. Fedora is completely up to date.
Could be I am on a beta build
I turned off selinux also (sudo setenforce 0)
Interesting, setenforce 0 doesn't turn selinux off in crouton
selinuxenabled && echo enabled || echo disabled
still shows enabled
What about modifying /etc/selinux/config
?
It may also be worth trying to reinstall, but I doubt it would make any difference. :(
Can you run X as root at least? sudo freonx
I get the same output trying to run as root.
Any updates on this?
When I installed for the first time X worked but then I reboot my machine and I couldn't get it to work getting this error:
Another instance of croutontriggerd running, waiting... xauth: file /home/fedora/.serverauth.22957 does not exist
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
X.Org X Server 1.18.4 Release Date: 2016-07-19 X Protocol Version 11, Revision 0 Build Operating System: 4.6.4-301.fc24.x86_64 Current Operating System: Linux localhost 3.14.0 #1 SMP PREEMPT Wed Aug 31 23:35:12 PDT 2016 x86_64 Kernel command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 3584000 verity payload=PARTUUID=8f7f09fd-3fa9-c04b-8582-dd9473131ef9/PARTNROFF=1 hashtree=PARTUUID=8f7f09fd-3fa9-c04b-8582-dd9473131ef9/PARTNROFF=1 hashstart=3584000 alg=sha1 root_hexdigest=d7754d60a9f14a01ffd72cd342a039f8c2886a14 salt=17abee684068ae41b1caa42785370c95d55f9f3f22a8c86abd516b3d9abd09d7" noinitrd vt.global_cursor_default=0 kern_guid=8f7f09fd-3fa9-c04b-8582-dd9473131ef9 add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic i915.enable_psr=1
Build Date: 25 August 2016 05:27:31PM Build ID: xorg-x11-server 1.18.4-4.fc24 Current version of pixman: 0.34.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/home/fedora/.local/share/xorg/Xorg.0.log", Time: Sat Sep 10 20:32:33 2016 (==) Using config file: "/etc/X11/xorg.conf" (==) Using system config directory "/usr/share/X11/xorg.conf.d" Error getting authority: Error initializing authority: Could not connect: No such file or directory (WW) /etc/selinux/targeted/contexts/x_contexts: has invalid context system_u:object_r:seclabel_xproperty_t:s0 SELinux: a property label lookup failed! (EE) Fatal server error: (EE) SELinux: Failed to set label property on window! (EE) (EE) Please consult the Fedora Project support at http://wiki.x.org for help. (EE) Please also check the log file at "/home/fedora/.local/share/xorg/Xorg.0.log" for additional information. (EE) (II) AIGLX: Suspending AIGLX clients for VT switch (EE) Server terminated with error (1). Closing log file.
^Cxinit: giving up xinit: unable to connect to X server: Connection refused xinit: unexpected signal 2 Couldn't get a file descriptor referring to the console
Using the install script to install xfce fixed the issue but then it returned after another reboot. It seems the faq command:
grep -F -m 1 -boa 'geteuid' "$inteldrv"
Returns an empty string. Is something getting rewritten on reboot?