Open TomTravis opened 2 years ago
Please give the output of step 1 and 2, along with the output of sudo edit-chroot -all
. It also helps if you provide the following:
Try it there is no logs and step 1 ,2 , you enter "code" or open the app on the desktop it kills the machine
i working with MS for some debug steps it create a dirty file system is the log
it really does not matter, it kills the xserver and reset the chorme book
jammy bullseye and my own debootstrap
The latest Xerver is now running
x-help.txt
xrdb.txt
Xserver is working again stable no reset Xresources can be local the performance is great, xiwi has issues and needs work I will update my fork this week lots of new work done.
This is not crouton copyright work Penguin 2022 copyright xorg linux rules of conduct
I can tell you no logs are made the debug status is unknown, vscode init starts fails and the chrome book resets. vscode create a dirty file system on exit. You must umount, fsck the FS and then enter chroot again, if you do not clean the FS the chromebook just resets on chroot entry. vscode is now removed from my chroot the git repo is installed still with yarn and npm nodejs also this is needed to chromeOS build nodejs, You are required to do pull request to keep current on vscode for build, yarn is a verbose build app, it is strange to work with. Many versions and it gets confused. nodejs yarn and npm.
maybe a Azure Repo could be better i have yet to attempt a build on github arm64 builds maybe
Are there not any Visual Studio Code logs in ~/.config/Code/logs
? Does the problem still persist if you use another Electron application, like Slack, Atom, or Notion? It still helps if you give the output of sudo edit-chroot -all
or uname -a
.
no logs,vscode never starts, it causes many FS errors there is no config.code it never gets created
Electron application, like Slack, Atom, or Notion? have not tried this? i use gedit with plugins for low lever work
this one of the CR chronos@localhost /media/removable/sd200 $ cd bull chronos@localhost /media/removable/sd200/bull $ sudo edit-chroot -c /media/removable/sd200/bull/chroots -all name: bullseye encrypted: no Entering /media/removable/sd200/bull/chroots/bullseye... crouton: version 1-20220512214808 release: bullseye architecture: arm64 xmethod: xorg targets: audio,xiwi,xorg host: version 14588.123.0 (Official Build) stable-channel jacuzzi kernel: Linux localhost 5.10.106-15290-g6e9d70c8a9b4 #1 SMP PREEMPT Wed May 18 19:34:18 PDT 2022 aarch64 GNU/Linux freon: yes Unmounting /media/removable/sd200/bull/chroots/bullseye... chronos@localhost /media/removable/sd200/bull $
name: bullseye encrypted: no Entering /media/removable/sd200/deb/chroots/bullseye... crouton: version 1-20220512214808 release: bullseye architecture: arm64 xmethod: xorg targets: xorg,xiwi,core,audio host: version 14588.123.0 (Official Build) stable-channel jacuzzi kernel: Linux localhost 5.10.106-15290-g6e9d70c8a9b4 #1 SMP PREEMPT Wed May 18 19:34:18 PDT 2022 aarch64 GNU/Linux freon: yes Unmounting /media/removable/sd200/deb/chroots/bullseye.
the vscode issue was submitted the robot asked to install the latest version of vscode it was 1.67.2
yes good hopeful
the electron build is unknown. it electron I may have to build on amd64 and cross compile the src has been downloading for 8hr gclient takes forever
Electron puts Mac OS and Linux together not so bad arm64 Debian build may have issues
running cli tests did not reset from npm binaries, running .src/scripts/test.sh did reset the machine. the ChromeOS VScode was likely built for it to run,
the electron build is unknown. it electron I may have to build on amd64 and cross compile the src has been downloading for 8hr gclient takes forever
Electron puts Mac OS and Linux together not so bad arm64 Debian build may have issues
running cli tests did not reset from npm binaries, running .src/scripts/test.sh did reset the machine. the ChromeOS VScode was likely built for it to run,
I'm sorry if I don't really understand what you are trying to get at here but, are you attempting you build everything from source? If that is the case I don't think there is that much we can do to help you.
yes VScode has it unique Electron node_module, the proposed it has nothing to do with Vscode and electron is at fault is complete BS
BetaPictoris mentioned this issue 3 days ago vscode X11 chroot on ChromeOS, init fail reset HW microsoft/vscode#150500
the electron build is unknown. it electron I may have to build on amd64 and cross compile the src has been downloading for 8hr gclient takes forever Electron puts Mac OS and Linux together not so bad arm64 Debian build may have issues running cli tests did not reset from npm binaries, running .src/scripts/test.sh did reset the machine. the ChromeOS VScode was likely built for it to run,
I'm sorry if I don't really understand what you are trying to get at here but, are you attempting you build everything from source? If that is the case I don't think there is that much we can do to help you.
the test now run after days of saying I'm spamming microsoft, issues out of scope some folks are helpful crouton did a great work 8 years ago. i working on a Multiuser - work station install Pengiun android studio and Vscode arm64 still fails x86_64 builds
now working on systemd and crouton /usr/local/bin scripts for update the newest Xserver config
Crouton did hack it , it still works with the X hack
npm-sh.log
yes VScode has it unique Electron node_module, the proposed it has nothing to do with Vscode and electron is at fault is complete BS
BetaPictoris mentioned this issue 3 days ago vscode X11 chroot on ChromeOS, init fail reset HW microsoft/vscode#150500
It was an idea, and you didn't give us any logs or error messages to work off of! You also didn't say if you even tested other Electron applications. For all I know it could've been an issue with Electron.
im laughing now
Electron puts Mac OS and Linux together not so bad arm64 Debian build may have issues running cli tests did not reset from npm binaries, running .src/scripts/test.sh did reset the machine. the ChromeOS VScode was likely built for it to run,
maybe Simula you not remember A/UX and Apple, or NeXT systems and small talk, the Mac OS is Unix made to run Mac Binaries
this was a long time ago, SUN microsytem still was building computers Bought by Oracle
Like chromeOS and android it will come together. SW
There is no log or error messages none, this was the challenge, Binaries made to Mac arm64 (M1) do not run on Debian Linux this was the reset, The arm64 is still not working i may not work. I have compiled Node for arm64 now vscode Visual Studio Code requires x64 node for some reason, Chromium is the same, cross compile is the only option
IBM AiX, Microsoft Unix DEC Ultrix DEC
Chromuim now reset the chromebook just like vscode did, no logs now error messages vscode make the crouton src tree easy to look at now work can happen lot of work to do now, Android Studio is next
Please describe your issue:
If known, describe the steps to reproduce the issue: