Failed to open logging app: Unable to open TUI; Unable to initialize notcurses Unknown Error: 316

[gigaimage]

Pre-submit Checks

• [x] I have searched Warp bugs and there are no duplicates
• [x] I have searched Warp known issues page and my issue is not there
• [ ] I have included the logs (optional, but helps expedite the bug fix). Log gathering intructions

Describe the bug

Errors when launching log viewer app (lnav).
Checked iTerm2 and Mac Terminal, the app is working fine. Reinstalled lanv (brew reinstall), but still same issue.

Warp Version: v0.2025.03.12.08.02.stable_03

Error:

To reproduce

Open Warp. Launch lnav from anywhere.

Expected behavior

This (launching lnav) was working fine till yesterday. There were no changes in system or package.

Screenshots, videos, and logs

No response

Operating system (OS)

macOS

Operating system and version

MacOS Monterey 12.7.6

Shell Version

GNU bash, version 5.2.37(1)-release (x86_64-apple-darwin21.6.0)

Current Warp version

v0.2025.03.12.08.02.stable_03

Regression

this bug started recently or with an X Warp version

Recent working Warp date

MARCH-12-2025, 10pm

Additional context

No response

Does this block you from using Warp daily?

No

Is this an issue only in Warp?

Yes, I confirmed that this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None

[juanlopez4691]

Same issue, same error.

[daymade]

Same issue, same error.

[juan-diego]

Same issue, same error.

My system:

• Apple M1 Pro
• macOS Sequoia 15..3.2
• Warp v0.2025.03.12.08.02.stable_03
• zsh version 5.9 on MacOS

[tstack]

It looks like the response to the "device attributes" escape sequence (\e[c) was not recognized. Warp is responding with just \e[?62c whereas, I think, other terminals will include some extra attributes like \e[?62;1c. The lack of the extra attributes was tripping up lnav. I've updated lnav with this change.

It looks like this is a recent change in Warp. I tried a Warp download from late Dec 2024 and it seemed to work with lnav v0.12.4. Whereas it's not working with an updated version of Warp.

[shambodeva]

same error

✘ error: unable to open TUI reason: unable to initialize notcurses Unknown error: 316 = help: The TERM value of “xterm-256color” is not known. Check for your terminal in https://github.com/dankamongmen/notcurses/blob/master/TERMINALS.md or use “xterm-256color”

[tyong920]

Same issue, same error.

[davideuler]

The same error on my warp.

[anil-dewani]

Facing the same error on alacritty

[kawahwookiee]

yes, same in alacritty in tmux

[martinleveille]

Same issue with lnav

[cschoong]

Is there a workaround for lnav outside using something other than Warp?

[DavidAmyot]

+1

[winterfx]

Same issue with lnav

[vaiosx]

same issue

[tyong920]

same issue

[samuelololol]

same issue

[hemna]

yup, I get this as well trying to use lnav with warp

✘ error: unable to open TUI
 reason: unable to initialize notcurses Unknown error: 316
 = help: The TERM value of “xterm-256color” is not known.  Check for your terminal in https://github.com/dankamongmen/notcurses/blob/master/TERMINALS.md or use “xterm-256color”

[villqrd]

same issue

[shanglt]

same issue

[tstack]

lnav v0.13.1 has been released and it seems to work fine on Warp v0.2025.09.03.08.11.stable_02, so this can probably be closed.

[juan-diego]

I confirm that lnav 0.13.1 is working fine on Warp v0.2025.09.10.08.11.stable_01.