-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Terminal not working #5218
Comments
Do you have bash installed? I've seen this happen when I don't have zsh installed. You can also change the default shell in the VS Code Settings UI. I would try that. |
I confirm this issue, after updating to 4.4.0 terminal is not working |
It was working before update, but yup i have bash installed. |
Can you share the logs for the browser and the server? I'm not sure what could be going on here. |
I'm getting a similar error, but not anymore when using chrominum. Server: raspberry pi 4, Manjaro-ARM, code-server AUR package (yeah i know manjaro and AUR). Client: Fedora 35, normal amd64 chipset, Firefox 100.0.2 vs Chrominum Version 100.0.4896.127 (Official Build) Fedora Project (64-bit)
Browser log (a lot of other errors that dont directly seem related excluded, of course firefox only):
|
I have the same issue after updating to 4.4.0. I used the docker image on an arm64 machine. |
New installation 4.4.0, Ubuntu 20.04 on arm64, "The terminal process failed to launch: A native exception occurred during launch (forkpty(3) failed.)." [IPC Library: Pty Host] WARN Shell integration cannot be enabled for executable "/bin/bash" and args [] It appears that my issue appears with code-server is run from a chroot/jailkit account. Seems to work fine on a regular user; non-root account on Ubuntu. Wondering if it's a missing dependency issue of something simply not copied over to the jailed account. |
@code-asher any ideas? |
I found out that you can mount your /dev and /dev/pts folders to your jailkit account and it works. I.e. mount -o bind /dev /[your jailkit root]/dev However, this mounts everything in your root /dev to the jailkit and may defeat the purpose of jailkit altogether; to provide isolation. Other forums have indicated that /dev/pts is the only device necessary and doesn't pose a "big risk" as each device has it's own owner/group; but I couldn't get it to work with just that. I'm wondering what else is actually needed and is a dependency? I don't want to give full access to items like /dev/mem (memory) to a jailkit'd user. |
Does anything in this issue help? microsoft/vscode-remote-release#4233 At first glance seems like |
Can confirm. Running code-server on OSX, with a vanilla docker-code-server, running on Docker locally. No terminal start, nothing in any of the logs that I could find. Downgrading to 4.3.0 seems to fix it |
@bcotton nothing in the browser logs either? I'm on OSX and have 4.4.0 running locally (not in Docker) and the terminal works |
Nope, I checked the "window" logs. Tailed all logs in the running image, in addition to the output of coder command line. is there somewhere else to check? |
If you open up code-server in a browser like Chrome, then View > Developer > Developer Tools and look in the Console tab there might be something helpful |
wait are you using code-server or |
I'm using |
@jsjoeio I had the same issue today after upgrade code-server from 4.4.0 to 4.5.0 and I don't use 'coder'. The background steps for the upgrade:
I could open more terminals, but I didn't see the content and titles of the terminals and otherwise exactly as the description/screenshot. Likewise, I think it was caused by browser some cache or cookies. Because after I returned from a few local errands, the problem magically resolved itself. I had problem on client node with Safari and Chrome, server side RHEL 8.6, logs from the systemd coda-server service are clean, and I can't give you any more information backwards from the browsers, unfortunately. |
Using code-server 4.5.0, as started directly via
I've installed |
@jsjoeio for me, the base path was not |
I hope we're right then 🤞🏼 Hoping to get 4.5.1 out soon. Sorry for all the trouble! |
@consideRatio I would bet so! CI just finished and now i'm testing 4.5.1 (what we'll publish) locally. I'll run it behind Caddy and check syntax highlighting now. Thanks for mentioning it! |
The same bug occurs on FreeBSD. |
Hmm...any ideas for ways we can fix that? Would it be worth raising upstream? |
My problem was in configuration of flags in chrome, so i think that wasn't code-server bug. |
That's helpful! Do you remember which flag it was? |
If I remember correctly, something with canvas. I can check that in about 3 hours. |
I have no idea how to fix it by now. Maybe raising upstream is viable. |
@moqsien do you mind opening an issue upstream and linking here? |
I'm having same issue on FreeBSD. Terminal does not work. Some languages, like Python, there is no syntax highlighting but JavaScript is highlighted correctly. The errors from the code-server server on FreeBSD 13.1 and code-server v4.7.1 look like: [20:42:29] ptyHost was unable to resolve shell environment Error: Unable to resolve your shell environment: Unexpected exit code from spawned shell (code 1, signal null)
...
[20:45:18] [Unknown channel: Channel name 'ptyHost' timed out after 1000ms]
rejected promise not handled within 1 second: Unknown channel: Channel name 'ptyHost' timed out after 1000ms Also, when installed on FreeBSD via npm, I keep getting missing module errors after starting code-server. I had to keep killing/restarting to install the packages it was asking for until I stopped getting those errors. I ended having to manually install: |
I got watcher working by installing watchman(!) and using @parcel/watcher from pr parcel-bundler/watcher#128 . Steps:
Eventually got terminal, searching, watchers working. |
这是来自FoxMail邮箱的假期自动回复邮件。
您好,我是Mo-Qsien,最近正在休假中,无法亲自回复您的邮件。我将在假期结束后,尽快给您回复!
|
Closing since it looks like the original issue was resolved? Check #5741 for the FreeBSD issue, although not sure there is anything actionable on our end. |
Is there an existing issue for this?
OS/Web Information
code-server --version
: 4.4.0Steps to Reproduce
Expected
Terminal window should open.
Actual
Terminal window is blank.
Logs
[IPC Library: Pty Host] WARN Shell integration cannot be enabled for executable "/usr/bin/bash" and args undefined
...
[22:22:15] Terminal process launching on remote agent {
shellLaunchConfig: {
name: undefined,
executable: '/usr/bin/bash',
args: undefined,
cwd: '/root/sandbox/StatusPage',
env: undefined,
useShellEnvironment: true
},
Screenshot/Video
Does this issue happen in VS Code?
Are you accessing code-server over HTTPS?
Notes
I tried to reinstall code-server, and even I ran the docker version from linuxservers with the same results. It's weird because 2 days ago it was working, and I didn't update anything on that server.
The text was updated successfully, but these errors were encountered: