Crouton: Not starting

Created on 18 Dec 2016  Â·  17Comments  Â·  Source: dnschneid/crouton

name: precise
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/precise...
crouton: version 1-20161129162558~master:5f2f11f9
release: precise
architecture: amd64
xmethod: xorg
targets: xfce
host: version 8872.70.0 (Official Build) stable-channel auron_yuna 
kernel: Linux localhost 3.14.0 #1 SMP PREEMPT Wed Dec 7 23:31:20 PST 2016 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
Not unmounting /mnt/stateful_partition/crouton/chroots/precise as another instance is using it.

#

I get two errors when I type sudo startxfce4
I get these two errors:
img_4621
img_4620

This is the output from the console:

Entering /mnt/stateful_partition/crouton/chroots/precise...
Failed to start message bus: Failed to open "/etc/selinux/targeted/contexts/dbus_contexts": No such file or directory
WARNING: starting chroot system dbus daemon failed with code 1
/usr/bin/startxfce4: Starting X server

_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root

X.Org X Server 1.15.1
Release Date: 2014-04-13
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.42-75-generic x86_64 Ubuntu
Current Operating System: Linux localhost 3.14.0 #1 SMP PREEMPT Wed Dec 7 23:31:20 PST 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=219f73b7-dd91-a54d-9d98-cfaa10455411/PARTNROFF=1 hashtree=PARTUUID=219f73b7-dd91-a54d-9d98-cfaa10455411/PARTNROFF=1 hashstart=3584000 alg=sha1 root_hexdigest=64e6f59ae407fcc371eed1c9f85372d92c720719 salt=02d5b4be442b9963eb05401cdf9c6525b0cfe78f6136d220be30cbe4bac1cc49" noinitrd vt.global_cursor_default=0 kern_guid=219f73b7-dd91-a54d-9d98-cfaa10455411 add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic  
Build Date: 12 February 2015  03:37:52PM
xorg-server 2:1.15.1-0ubuntu2~precise5 (For technical support please see http://www.ubuntu.com/support) 
Current version of pixman: 0.30.2
        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: "/tmp/Xorg.crouton.1.log", Time: Sat Dec 17 18:05:24 2016
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
setversion 1.4 failed: Permission denied
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension SECURITY
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
setversion 1.4 failed: Permission denied
crouton: version 1-20161129162558~master:5f2f11f9
release: precise
architecture: amd64
xmethod: xorg
targets: xfce
host: version 8872.70.0 (Official Build) stable-channel auron_yuna 
kernel: Linux localhost 3.14.0 #1 SMP PREEMPT Wed Dec 7 23:31:20 PST 2016 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
Failed to start message bus: Failed to open "/etc/selinux/targeted/contexts/dbus_contexts": No such file or directory
EOF in dbus-launch reading address from bus daemon
/etc/xdg/xfce4/xinitrc: 1: /etc/xdg/xfce4/xinitrc: ssh-agent: not found

** (xfce4-session:14227): CRITICAL **: Unable to contact D-Bus session bus: Unknown error

** (xfce4-session:14227): CRITICAL **: Unable to contact D-Bus session bus: //bin/dbus-launch terminated abnormally with the following error: EOF in dbus-launch reading address from bus daemon


(xfce4-session:14227): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf!
** (xfce4-session:14227): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed

** (xfce4-session:14227): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed

(xfce4-session:14227): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf!

** (xfce4-session:14227): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed

(xfce4-session:14227): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed

(xfce4-session:14227): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf!

** (xfce4-session:14227): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed

(xfce4-session:14227): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed

(xfce4-session:14227): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf!

** (xfce4-session:14227): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed

** (xfce4-session:14227): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed

(xfce4-session:14227): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf!

** (xfce4-session:14227): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed

(xfce4-session:14227): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed

(xfce4-session:14227): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf!

** (xfce4-session:14227): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed

** (xfce4-session:14227): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed

(xfce4-session:14227): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf!

** (xfce4-session:14227): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed

(xfce4-session:14227): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
_IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root

(xfce4-session:14227): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf!

** (xfce4-session:14227): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed

(xfce4-session:14227): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed

(xfce4-session:14227): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf!
** (xfce4-session:14227): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed

(xfce4-session:14227): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed

(xfce4-session:14227): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf!

** (xfce4-session:14227): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed

(xfce4-session:14227): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed

(xfce4-session:14227): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf!

** (xfce4-session:14227): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed

(xfce4-session:14227): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed

(xfce4-session:14227): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf!

** (xfce4-session:14227): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed

(xfce4-session:14227): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed

(xfce4-session:14227): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf!

** (xfce4-session:14227): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed

(xfce4-session:14227): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
Failed to connect to Xfconf daemon: //bin/dbus-launch terminated abnormally with the following error: EOF in dbus-launch reading address from bus daemon

running 'ssh-agent -s -k'
/etc/xdg/xfce4/xinitrc: 1: eval: ssh-agent: not found
Running exit commands...
/usr/bin/xinit: connection to X server lost

waiting for X server to shut down xscreensaver: 18:05:55: SIGHUP received: restarting...
xscreensaver: 18:05:55: running as mtmaster/mtmaster (1000/1000)

Hangup
xscreensaver: 18:05:55: Can't open display: :1
xscreensaver: 18:05:55: running as mtmaster/mtmaster (1000/1000)

xscreensaver: 18:05:55: Errors at startup are usually authorization problems.
              But you're not logging in as root (good!) so something
              else must be wrong.  Did you read the manual and the FAQ?

              http://www.jwz.org/xscreensaver/faq.html
              http://www.jwz.org/xscreensaver/man.html
(EE) Server terminated successfully (0). Closing log file.

Not unmounting /mnt/stateful_partition/crouton/chroots/precise as another instance is using it.

#

It happens when I just type sudo startxfce4

Most helpful comment

Well, as an update to my earlier post. I can't believe it, but I can start AND use LXDE normally. XFCE and Unity are not functioning normally but LXDE is working fine, at least on my chromebook.

You can install LXDE even if you already have Unity installed by going to CROSH and typing:

sudo sh -e ~/Downloads/crouton -t lxde -u

then after installation you can run it by typing

sudo startlxde

I use crouton to run the Arduino IDE on chromebooks for about 20 high school students, so it looks like I have a lot of chromebooks to reconfigure. ;D

enjoy,

Doc P

All 17 comments

Yeah, this just started for me too. There was an update a few days ago, I know because the chromebook had "Restart and Apply Updates" in place of "Sign Out" in the menu. Ever since then, I have been getting the same problems as the above person when they enter the chroot. I am running precise and xfce, I'll try running unity and lxde, and if it works I'll let you know, but I do not have high hopes.

Already updated crouton (sudo sh ~/Downloads/crouton -u) and even reinstalled it on another chromebook but no dice.

It must be the latest update, I really hate those things ;)
Hopefully a fix will come soon,
Thanks!
-Doc P
screenshot 2016-12-18 at 2 12 15 pm

Well, as an update to my earlier post. I can't believe it, but I can start AND use LXDE normally. XFCE and Unity are not functioning normally but LXDE is working fine, at least on my chromebook.

You can install LXDE even if you already have Unity installed by going to CROSH and typing:

sudo sh -e ~/Downloads/crouton -t lxde -u

then after installation you can run it by typing

sudo startlxde

I use crouton to run the Arduino IDE on chromebooks for about 20 high school students, so it looks like I have a lot of chromebooks to reconfigure. ;D

enjoy,

Doc P

@sparrino
Thanks for this info! I dislike lxde so I don't want to do use that. The three that I would want to use is xfce, KDE, and unity. So I might have to test if KDE works.

I had this same issue (something about SELinux and DBus was broken by a recent ChromeOS update) and updating the chroot fixed the issue for me.

Specifically, I ran

  • croutonversion -u -d -c from within the chroot, then
  • sudo sh ~/Downloads/crouton -u -n chrootname from outside the chroot. After doing that startxfce4 works again.

For reference, my setup:

name: trusty
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/trusty...
crouton: version unknown
release: unknown
architecture: unknown
xmethod: xiwi
targets: xiwi,xfce
host: version 8872.70.0 (Official Build) stable-channel gandof 
kernel: Linux localhost 3.14.0 #1 SMP PREEMPT Wed Dec 7 23:28:43 PST 2016 x86_64 x86_64 x86_64 GNU/Linux
freon: yes

Well, I did what @hinnefe2 suggested but unfortunately I am getting the exact same errors. Any other suggestions?

@hinnefe2

I bet your problem being fixed has to do with the fact that you are running trusty, I have the earlier release (precise, 12.04) and updating hasn't changed a thing: the only thing that remains functional (somewhat) is lxde :(

Any idea when a fix will come? Is someone still actively developing crouton? Thanks!

I have the same issue. Please let me know if you guys find the solution.

I'm having the same problem with my Toshiba Chromebook 2 2015 model. I powerwashed and tried building a new chroot from scratch and nothing worked. I couldn't add the file as recommended in this thread https://github.com/dnschneid/crouton/issues/2843, as I got a read-only filesystem error (with sudo).

I had a problem with trusty (I can't remember what), and I'm on the road and don't have time to mess with an upgrade, so I'm using LXDE.
@wesleytsang are you able to run LXDE? If so, is that not sufficient? Have you tried Pixel?

same issues here (acer CB15) ... even LXDE not running here :(

Problem solved with this thread:
https://github.com/dnschneid/crouton/issues/2926

@brundizzle am I correct in assuming you have lxde working, but not xfce? If you got xfce working, was it just adding the file from the KDE/Minecraft guy in the other thread?

@jbgross nope... neither worked for me.
but the solution was as described by the guy mentioning minecraft. (i actually didn't have to add the file because it was already there. . i just had to edit it) . . . editing can be a bit tricky because you are in a shell. . . . full proces of what i did (hope i recall well :) :

1) ctrl-alt-t
2) shell
3) sudo enter-chroot -n
4) cd
5) sudo vi . . . ok, i didnt know how else to edit the file, so i used vi. . if you r not familiair with vi, you are going to get stuck here. . . so you either google the vi editor first, or yoy find another way to edit files in shell mode. . I made sure the [Option "AccelMethod"] was set to "uxa" (see other thread) . . . i think the guy copied/overwrote the file because the other file had the parameter set to "uxa" already .

6) exit
7) sudo startfxce4

and it worked !

good luck!

I'm pretty sure the OPs 'precise' selinux/dbus errors are different than the blackscreen errors that https://github.com/dnschneid/crouton/issues/2926#issuecomment-269165182 addresses.

That said, I don't think there are currently any fixes for the 'precise' selinux/dbus errors other than upgrading or installing a newer release. I have been using 'trusty', which is supported, and 'xenial' successfully but both may be experiencing the 'blackscreen issue' at the moment.

Hope this helps,
-DennisL

@sparrino Very happy that I can at the very least, have linux on my chromebook, I'm just super upset xfce does not work, thank you for the help though! 🥇

@Yerffy,

xfce4 should work on releases newer than 'precise', with a little work that is...

Hope this helps,
-DennisL

xfce4 works great on trusty (on an Asus C201) for me. At least until I get around to making spectrwm or fvwm work that is :)

Yes, this appears to be an entirely different problem; in my case, there is
no blank screen because the WM does not even start.

On Fri, Jan 6, 2017 at 12:51 PM, DennisL notifications@github.com wrote:

I'm pretty sure the OPs 'precise' selinux/dbus errors are different than
the blackscreen errors that #2926 (comment)
https://github.com/dnschneid/crouton/issues/2926#issuecomment-269165182
addresses.

That said, I don't think there are currently any fixes for the 'precise'
selinux/dbus errors other than upgrading or installing a newer release. I
have been using 'trusty', which is supported, and 'xenial' successfully but
both may be experiencing the 'blackscreen issue'
https://github.com/dnschneid/crouton/issues/2926#issuecomment-269165182
at the moment.

Hope this helps,
-DennisL

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dnschneid/crouton/issues/2957#issuecomment-270975788,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGsB7ghnm-zV_DqNYjoR3qxB7H5RHdzFks5rPo1NgaJpZM4LQB8L
.

--
Dr. Joshua B. Gross
Professor of Computer Science, Blackburn College
joshua.[email protected]

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Joshua10115 picture Joshua10115  Â·  4Comments

jimmybungalo picture jimmybungalo  Â·  4Comments

tedm picture tedm  Â·  3Comments

kgingging picture kgingging  Â·  5Comments

duck955 picture duck955  Â·  5Comments