Cannot Start New Conversations with Any Model

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Request ID: 4f8b770f-eab2-4971-951f-997300e5de4c
[internal] Invalid time zone specified: Etc/Unknown
pIe: [internal] Invalid time zone specified: Etc/Unknown
at Gv_ (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29432:24345)
at Wv_ (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29432:23144)
at Xv_ (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29433:6490)
at UCh.run (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29433:11307)
at async fQi.runAgentLoop (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41749:12418)
at async nrm.streamFromAgentBackend (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41817:12344)
at async nrm.getAgentStreamResponse (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41817:19567)
at async vCt.submitChatMaybeAbortCurrent (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29548:16906)

Steps to Reproduce

This bug occurs regardless of which model I select.
Besides, the SSH connection is unstable, showing persistent reconnection attempts.

Operating System

Linux

Version Information

Version: 3.2.21
VSCode Version: 1.105.1
Commit: 806df57ed3b6f1ee0175140d38039a38574ec720
Date: 2026-05-03T01:46:14.413Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Linux x64 6.8.0-110-generic

Does this stop you from using Cursor

Yes - Cursor is unusable

5

TZ=Asia/Shanghai /usr/share/cursor/cursor

The issue was resolved by launching Cursor with this command

9

Nice find. Setting TZ to a valid timezone before launching Cursor is the right workaround. This is a known bug where Cursor crashes if the system reports Etc/Unknown as the timezone. Our team is working on a fix.

For anyone running into the same issue, set a valid timezone before launching:

TZ=Asia/Shanghai /usr/share/cursor/cursor

To make it persistent, add export TZ=Asia/Shanghai to your shell profile (~/.bashrc or ~/.zshrc).