Xfce Forum

Sub domains
 

You are not logged in.

#1 2017-04-27 11:19:00

asadislove
Member
Registered: 2017-04-27
Posts: 1

Just got xfce for my chromebook but theres a problem switching to it.

i have a chromebook in which using crouton and typing sudo sh -e ~/Downloads/crouton -t xfce, for an hour or two it was done and i typed new username and password afterwards i typed sudo startxfce4 and for a moment my srcreen turned black and then back to crouton and this is the message what i got. I also pdated it aswell as tried getting other distributions such as kde. The same messge occurs so i think somethings wrong with my laptop BUT a month or two ago i did install xfce without any problems. Now i powerwashed it got the following message after hours of trying to powerwashing, and getting installing linux the same message occurs, any help would be higly appreciated.




Entering /mnt/stateful_partition/crouton/chroots/xenial...
/usr/bin/startxfce4: Starting X server

_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: Linux 4.4.0-59-generic armv7l Ubuntu
Current Operating System: Linux localhost 3.8.11 #1 SMP Tue Mar 21 22:01:49 PDT 2017 armv7l
Kernel command line: cros_secure console= 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 2539520 verity payload=PARTUUID=943d823b-c549-f941-adfc-0e29c1acb0f5/PARTNROFF=1 hashtree=PARTUUID=943d823b-c549-f941-adfc-0e29c1acb0f5/PARTNROFF=1 hashstart=2539520 alg=sha1 root_hexdigest=516076913a47b6f5be369f376a919960adff1872 salt=2a232cf4ad872eb17b5ac362c7508a568ba5197c60c2d19502fe5cfaab06563d" noinitrd vt.global_cursor_default=0 kern_guid=943d823b-c549-f941-adfc-0e29c1acb0f5 
Build Date: 26 January 2017  12:27:19AM
xorg-server 2:1.18.4-1ubuntu6.1~16.04.1 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.33.6
        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: Thu Apr 27 15:14:19 2017
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
gbm: failed to open any driver (search paths /usr/lib/arm-linux-gnueabihf/dri:${ORIGIN}/dri:/usr/lib/dri)
gbm: Last dlopen error: /usr/lib/dri/exynos_dri.so: cannot open shared object file: No such file or directory
failed to load driver: exynos
EGL_MESA_drm_image required.
(EE)
Fatal server error:
(EE) AddScreen/ScreenInit failed for driver 1
(EE)
(EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
for help.
(EE) Please also check the log file at "/tmp/Xorg.crouton.1.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
/usr/bin/xinit: giving up
/usr/bin/xinit: unable to connect to X server: Connection refused
/usr/bin/xinit: server error
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...

Please, please any help would be appreciated.

Offline

#2 2017-04-27 14:02:17

ToZ
Administrator
From: Canada
Registered: 2011-06-02
Posts: 11,485

Re: Just got xfce for my chromebook but theres a problem switching to it.

gbm: Last dlopen error: /usr/lib/dri/exynos_dri.so: cannot open shared object file: No such file or directory

https://github.com/dnschneid/crouton/issues/3164

Seems like it's a crouton issue. Probably best to follow the issue there.


Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki  |  Community | Contribute ---

Offline

Registered users online in this topic: 0, guests: 1
[Bot] ClaudeBot

Board footer

Powered by FluxBB
Modified by Visman

[ Generated in 0.013 seconds, 8 queries executed - Memory usage: 525.94 KiB (Peak: 526.78 KiB) ]