Xephyr: Unsupported screen depth 32

[jeffmendoza]

I'm having the issue that some commenters on #615 have. I'm on the samsung arm chromebook, dev channel.

chronos@localhost / $ sudo enter-chroot
Password: 
Entering /usr/local/chroots/saucy...
(saucy)jeffm@localhost:~$ croutonversion
crouton: version 1-20140129115028~master:caadc6ce
release: saucy
architecture: armhf
targets: xfce
host: version 5339.1.0 (Official Build) dev-channel daisy 
(saucy)jeffm@localhost:~$ exit
logout
Unmounting /usr/local/chroots/saucy...
Sending SIGTERM to processes under /usr/local/chroots/saucy...
Sending SIGKILL to processes under /usr/local/chroots/saucy...
Sending SIGKILL to processes under /usr/local/chroots/saucy...
Sending SIGKILL to processes under /usr/local/chroots/saucy...
^Cchronos@localhost / $ 
chronos@localhost / $ 

chronos@localhost / $ sudo enter-chroot startxfce4
Password: 
Entering /usr/local/chroots/saucy...
/usr/bin/startxfce4: Starting X server

ratpoison:manage.c:236: error: XGetWMName failed
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 SELinux
Initializing built-in extension GLX

Xephyr: Unsupported screen depth 32
(EE) 
(EE) Backtrace:
(EE) 
(EE) Segmentation fault at address 0x4
(EE) 
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE) 
/usr/bin/xinit: giving up
/usr/bin/xinit: unable to connect to X server: Connection refused
/usr/bin/xinit: server error
Unmounting /usr/local/chroots/saucy...
Sending SIGTERM to processes under /usr/local/chroots/saucy...
Sending SIGKILL to processes under /usr/local/chroots/saucy...
^Cchronos@localhost / $ 

The chroot was just created with

sudo sh -e ~/Downloads/crouton -t xfce -r saucy

[hannibalhuang]

got the same problem, i'm at canary channel

[dnschneid]

OK, I can reproduce this on dev. If you add -screen 1x1x16 to the XARGS list in /etc/crouton/xserverrc-xephyr, you can get some output, although it's incorrect. The error is being hit in Xephyr here, but I'm not sure what's changed in ARM. I'll ask around.

[drinkcat]

Depth should be 24 bits (8 bit * 3 (R, G, B)), even though the number of bit per pixel is usually 32-bit (with 8-bit alpha). At least that's what other display drivers do from what I can see.

I suspect this commit: https://chromium.googlesource.com/chromiumos/third_party/xf86-video-armsoc/+/2c4cb0c1529ac638f5538e189c60522648b00e9f%5E!/#F0 (note the commit date is only Sat Jan 25 09:07:12 2014, even though is was first created in 2012).

[dnschneid]

crbug.com/345511

[dnschneid]

A patch is being merged!

[drinkcat]

Merged from build 5528 onwards.

@hannibalhuang: Since you're on canary, you might want to confirm that it is fixed.

[dnschneid]

It's fixed in canary. Waiting for merge approval..

[dnschneid]

Fix should be merged into dev at the next push.

[hannibalhuang]

thx a lot, after the latest push everything works fine now. BTW I switched back to dev since there is sth wrong with update_engine_client in canary channel

[jeffmendoza]

Cool!