Warp tries install kubernetes client? Why? I not needs it.

[NTMan]

Discord username (optional)

No response

Describe the bug

Every time when I quit Warp I see this in gnome terminal.

20:24:57 [INFO] application will terminate
20:24:57 [INFO] Shutting down SQLite writer thread
20:24:57 [INFO] Shut down SQLite writer in 526.562µs
20:24:57 [INFO] Writing queued events to disk because telemetry is enabled.
20:24:57 [INFO] Successfully wrote telemetry events to disk
20:24:57 [INFO] Tearing down app services...
20:24:57 [INFO] Received empty message; assuming the connection has been closed.
20:24:57 [ERROR] EPIPE: Broken pipe
20:24:57 [ERROR] Failed to kill PTY process EPIPE: Broken pipe
20:24:57 [INFO] Tried to exit the alternate screen, but it was already inactive
20:24:57 [INFO] Block finished with new state DoneWithNoExecution
20:24:57 [WARN] Could not hand the clipboard contents over to the clipboard manager. The request timed out.
mikhail@primary-ws ~> 
Install package 'kubernetes-client' to provide command 'kubectl'? [N/y] 
[A

To reproduce

1. Launch Warp from Gnome Terminal.
2. Quit Warp
3. Press <Enter> until terminal would have empty answer
4. Look at terminal output

Expected behavior

No response

Screenshots

No response

Operating system

Linux

Operating system and version

Fedora Rawhide

Shell Version

fish, version 3.7.0

Current Warp version

v0.2024.03.05.08.02.stable_01

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

No response

Additional context

I am on Wayland

> glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: AMD (0x1002)
    Device: AMD Radeon RX 7900 XTX (radeonsi, navi31, LLVM 18.1.0, DRM 3.57, 6.8.0-0.rc7.20240308git3aaa8ce7a335.60.fc41.x86_64+debug) (0x744c)
    Version: 24.1.0
    Accelerated: yes
    Video memory: 24576MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
Memory info (GL_ATI_meminfo):
    VBO free memory - total: 17186 MB, largest block: 17186 MB
    VBO free aux. memory - total: 27555 MB, largest block: 27555 MB
    Texture free memory - total: 17186 MB, largest block: 17186 MB
    Texture free aux. memory - total: 27555 MB, largest block: 27555 MB
    Renderbuffer free memory - total: 17186 MB, largest block: 17186 MB
    Renderbuffer free aux. memory - total: 27555 MB, largest block: 27555 MB
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 24576 MB
    Total available memory: 52352 MB
    Currently available dedicated video memory: 17186 MB
OpenGL vendor string: AMD
OpenGL renderer string: AMD Radeon RX 7900 XTX (radeonsi, navi31, LLVM 18.1.0, DRM 3.57, 6.8.0-0.rc7.20240308git3aaa8ce7a335.60.fc41.x86_64+debug)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 24.1.0-devel
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 24.1.0-devel
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 24.1.0-devel
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

Does this block you from using Warp daily?

No

Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)

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

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

None

[dannyneira]

Thats odd, I wonder if its a part of supporting the kubernetes context chip in Warps prompt? https://docs.warp.dev/appearance/prompt#kubernetes

If you have the option, just ignore that as part of the install, then you should be able to use Warp as normal, just that context chip in the prompt won't work.