latest on arm64 fails

[sdetweil]

Please paste the output of the following command here: sudo edit-chroot -all
sudo edit-chroot -all
name: sid
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/sid...
/usr/local/bin/crash_reporter_wrapper: 119: exec: /var/run/crw/crw: Permission denied
WARNING: Unable to register core dump handler.
crouton: version 1-20221028180332~main:a7e79071
release: sid
architecture: arm64
xmethod: xorg
targets: xfce
host: version 15117.86.0 (Official Build) stable-channel jacuzzi 
kernel: Linux localhost 5.10.142-19740-g3a142da07016 #1 SMP PREEMPT Wed Oct 26 19:07:59 PDT 2022 aarch64 GNU/Linux
freon: yes
Unmounting /mnt/stateful_partition/crouton/chroots/sid...

Please describe your issue:

startxfce fails sudo startxfce4 Entering /mnt/stateful_partition/crouton/chroots/sid... /usr/local/bin/crash_reporter_wrapper: 119: exec: /var/run/crw/crw: Permission denied WARNING: Unable to register core dump handler. /usr/bin/startxfce4: Starting X server

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

X.Org X Server 1.21.1.4 X Protocol Version 11, Revision 0 Current Operating System: Linux localhost 5.10.142-19740-g3a142da07016 #1 SMP PREEMPT Wed Oct 26 19:07:59 PDT 2022 aarch64 Kernel command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure drm.trace=0x106 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 5324800 verity payload=PARTUUID=e126afc4-c536-45b2-bcaa-5416ba6573c0/PARTNROFF=1 hashtree=PARTUUID=e126afc4-c536-45b2-bcaa-5416ba6573c0/PARTNROFF=1 hashstart=5324800 alg=sha256 root_hexdigest=f32ce7371222a1aab6eba03e51131cd74666b25511314055c7cae92a35efd635 salt=402fafe052d3e937291ee4ead7628201b76765cf76b39947a9049bf2c5c72c36" noinitrd vt.global_cursor_default=0 kern_guid=e126afc4-c536-45b2-bcaa-5416ba6573c0 cpuidle.governor=teo
xorg-server 2:21.1.4-2 (https://www.debian.org/support) Current version of pixman: 0.40.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: "/tmp/Xorg.crouton.1.log", Time: Fri Nov 4 09:53:03 2022 (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) Fatal server error: (EE) AddScreen/ScreenInit failed for driver 0 (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.

If known, describe the steps to reproduce the issue:

install and then try to start had to manually create /tmp/crouton.xxx for install (or crouton -help) to work

lenovo arm64 ip flex 3

[TomTravis]

very strange post maybe mixed up maybe it is easy to do sudo mount -o remount,symfollow -o exec # fle system /media/removable/sd200 will clear the exec message arm64 ? lenovo amd64 ip flex 3 ? what?

Bookworm installs fine for me Xorg need config help it does not start Xiwi does start with color pallet(map) is not correct for some apps

[sdetweil]

command output

sudo mount -o remount,symfollow -o exec # fle system /media/removable/sd200
mount: bad usage
Try 'mount --help' for more information.

typo above arm64..

[sdetweil]

/media/removable?? I am not doing this with any usb stick... just terminal window and shell

[sdetweil]

Xorg need config help it does not start Xiwi does start with color pallet(map) is not correct for some apps

don't know what that means in real terms.. not a linux geek.. i have gallium installed on my intel chromebook/boxes..

[TomTravis]

yes ok so where is the install I know this is confusion /mnt/statefull.... You need to make the mounts exec sid is unstable is the what you want ? that # is a comment you need to add you own FS

[sdetweil]

ls /mnt
empty stateful_partition

[sdetweil]

sudo mount -o remount,symfollow -o exec /mnt/stateful_partition/            
chronos@localhost / $ sudo startxfce4
Entering /mnt/stateful_partition/crouton/chroots/sid...
/usr/local/bin/crash_reporter_wrapper: 119: exec: /var/run/crw/crw: Permission denied
WARNING: Unable to register core dump handler.
/usr/bin/startxfce4: Starting X server

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

X.Org X Server 1.21.1.4
X Protocol Version 11, Revision 0
Current Operating System: Linux localhost 5.10.142-19740-g3a142da07016 #1 SMP PREEMPT Wed Oct 26 19:07:59 PDT 2022 aarch64
Kernel command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure drm.trace=0x106 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 5324800 verity payload=PARTUUID=e126afc4-c536-45b2-bcaa-5416ba6573c0/PARTNROFF=1 hashtree=PARTUUID=e126afc4-c536-45b2-bcaa-5416ba6573c0/PARTNROFF=1 hashstart=5324800 alg=sha256 root_hexdigest=f32ce7371222a1aab6eba03e51131cd74666b25511314055c7cae92a35efd635 salt=402fafe052d3e937291ee4ead7628201b76765cf76b39947a9049bf2c5c72c36" noinitrd vt.global_cursor_default=0 kern_guid=e126afc4-c536-45b2-bcaa-5416ba6573c0 cpuidle.governor=teo  
xorg-server 2:21.1.4-2 (https://www.debian.org/support) 
Current version of pixman: 0.40.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: "/tmp/Xorg.crouton.1.log", Time: Fri Nov  4 11:01:51 2022
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE) 
Fatal server error:
(EE) AddScreen/ScreenInit failed for driver 0
(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/sid...

[TomTravis]

ok yes now you have mounts great now use the mount exec cmds

you trying to start xorg is not working yes this is known go back and install target xiwi

[sdetweil]

ok, don't know what I am doing

sudo startxiwi
startxiwi [options] chroot_app [parameters]

Wraps enter-chroot to launch a window or tab in Chromium OS for any graphical application.
Applications launched in this way show in independent windows or tabs.

By default, it will use the primary user on the first xiwi-enabled chroot found and launch
the chroot_app in a window.

Options:
    -b          Fork and run the specified command silently in the background.
    -c CHROOTS  Directory the chroots are in. Default: /mnt/stateful_partition/crouton/chroots
    -k KEYFILE  Override the auto-detected encryption key location.
    -n NAME     Name of the chroot to enter. Default: first one found in CHROOTS
    -t TARGET   Only enter the chroot if it contains the specified TARGET.
    -u USERNAME Username (or UID) to log into. Default: 1000 (the primary user)
    -F          Launch the chroot_app full-screen.
    -T          Launch the chroot_app in a tab.
    -f          Prevent xiwi from quitting automatically. (see NOTE below)

NOTE:
xiwi will normally close when the application returns. Some gui applications
fork before or during normal operation, which can confuse xiwi and cause it to
quit prematurely. If your application does not have a parameter that prevents
it from forking, and crouton is unable to automatically detect the fork, you can
use -f to prevent xiwi from quitting automatically.
xiwi will quit if you close the Chromium OS window when nothing is displayed.

You can cycle through multiple windows inside the application
via Ctrl-Alt-Tab/Ctrl-Alt-Shift-Tab, or close them via Ctrl-Alt-Shift-Escape.
If the chroot_app begins with 'start' but you still want to
use the default window manager, specify the full path of the application.

[TomTravis]

yes you are confused no doubt go out of the change root back to the shell and update the chroot root wiith the xiwi target like sudo crouton -r sid -t xiwi -u you have to be sure to mounts exec and followsym

[sdetweil]

thx. I had done that already. without -u, said update or delete. as I don't know how to delete, did update.

the output above is after update

[TomTravis]

i have no idea to start the xorg server with xiwi the file in /etc/crouton/xmethod need to contain xiwi just edit it using nano sudo nano /etc/crouton/xmethod I use xint

[TomTravis]

to delete the chroot sudo rm -rf #path to changeroot what ever it is or sudo delete-chroot

[DennisLfromGA]

@sdetweil,

If you have more than one xmethod installed in your chroot you can choose which xmethod to use when launching your desktop, in your case to start your XFCE Desktop using the xiwi xmethod use this:

• sudo startxfce4 -X xiwi

-DennisLfromGA

[sdetweil]

thx. deleted, start over..

what is the chroot_app when I want to run desktop

[TomTravis]

i use cli xint to start Xorg up via xiwi in sid - bookworm if you have xfce4 installed your .xinitrc file will contain

pulseaudio -D exec xfce4-session

this a dot file in your user dir .xinitrc then issue CLI xinit and xorg in xiwi should start

[sdetweil]

ok, thanks.. that file didn't exist for the default user in xfce startxfce -n xfce (I installed second chroot)

i don't understand CLI, i mean i know what it is, but I wasnt (dont think) starting system that way

sorry, don't understand the chroot stuff.. understand virtual machine and docker, and pi's all over, should have bought an intel box..

[TomTravis]

xinit start what you want for xorg could be anything not just pulseaudio and the xfce4 xinit is not change root not even close

i normal use mate desktop exec mate-session sudo apt install mate it does not work with xiwi so well xorg does not start on bookworm and sid i use icewm and xiwi for bookworm chroot is still linux it has some things a normal linux install does not amd64 supports development much better chrome vscode ... many others

[sdetweil]

sadly all Greek to me

[TomTravis]

lol this is X11 xorg not chroot