Open JeShGrCa opened 8 months ago
Hey, thanks for letting us know!
Seems like some sort of issue relating to SSL certificates. Out of curiosity - do you have the ca-certificates
package installed?
https://github.com/warpdotdev/Warp/issues/4223#issuecomment-1960073612
@vorporeal, note that this doesn't occur for me on cpe:/o:opensuse:tumbleweed:20240220
using https://releases.warp.dev/stable/v0.2024.02.20.08.01.stable_01/warp-terminal-v0.2024.02.20.08.01.stable_01-1.x86_64.rpm, and I have ca-certificates
installed:
```.log PS /home/RokeJulianLockhart> sudo zypper refresh && zypper search ca-certificates Repository 'coolercontrol-coolercontrol' is up to date. Repository 'coolercontrol-coolercontrol-noarch' is up to date. Repository 'coolercontrol-coolercontrol-source' is up to date. Repository 'Copr repo for onedriver owned by jstaf' is up to date. Repository 'Main Repository (NON-OSS)' is up to date. Repository 'Main Repository (OSS)' is up to date. Repository 'Main Update Repository' is up to date. Repository 'google-chrome' is up to date. Repository 'openSUSE:Factory' is up to date. Repository 'utilities' is up to date. Repository 'openSUSE:Tumbleweed' is up to date. Repository 'microsoft-edge' is up to date. Repository 'openSUSE-20230920-0' is up to date. Repository 'Packman' is up to date. Repository 'Open H.264 Codec (openSUSE Tumbleweed)' is up to date. Repository 'snappy' is up to date. Repository 'TeamViewer - x86_64' is up to date. Repository 'vscode' is up to date. Repository 'warpdotdev' is up to date. All repositories have been refreshed. Loading repository data... Reading installed packages... S | Name | Summary | Type ---+----------------------------------+-------------------------------------------------------+-------- i+ | ca-certificates | Utilities for system wide CA certificate installation | package | ca-certificates-cacert | CAcert root certificates | package i+ | ca-certificates-mozilla | CA certificates for OpenSSL | package | ca-certificates-mozilla-prebuilt | Pre-built CA certificates for OpenSSL | package i+ | ca-certificates-steamtricks | Provides /etc/ssl/certs/ca-certificates.crt | package PS /home/RokeJulianLockhart> ```
I'm not familiar with SUSE - what does cpe:/o:opensuse:tumbleweed:20240220
represent and how does it differ from what you normally use?
If you're downgrading to an older set of packages and things are working, it's possible it's this known issue with Mesa 24 and nVidia drivers - https://gitlab.freedesktop.org/mesa/mesa/-/issues/10624
Seems like some sort of issue relating to SSL certificates. Out of curiosity - do you have the
ca-certificates
package installed?
I do. There were some more certificate packages that I didn't have installed, but installing them fixed nothing.
A few more details that might be of note:
I have two GPUs installed in my system; one is an Nvidia RTX A4000, while the other is an old Quadro K2200. When I attempt to run Warp with both enabled it fails with an out of memory error, while disabling the K2200 in software leads to this error.
I am also running KDE Plasma over Xrdp.
Not sure if this is related but when I try and run emacs-ng compiled with Winit my entire X session crashes.
Ah, it must be Xrdp - we've gotten reports of Warp not working properly when using it.
I have the same problem
warp-terminal 07:10:19 [INFO] Spawning terminal server process... 07:10:19 [INFO] Running terminal server... 07:10:19 [INFO] Running app with windowing system: X11 07:10:19 [WARN] Unable to fetch Linux system color scheme: MethodError( OwnedErrorName( ErrorName( Str( Owned( "org.freedesktop.portal.Error.NotFound", ), ), ), ), Some( "Requested setting not found", ), Msg { type: Error, sender: UniqueName( Str( Borrowed( ":1.77", ), ), ), reply-serial: 2, body: Signature( "s", ), }, ) 07:10:19 [INFO] Failed to read User from secure storage NotFound 07:10:19 [INFO] Initializing crash reporting Some("linux_stable_release") with tag "v0.2024.09.24.08.02.stable_01"... 07:10:19 [INFO] Starting warp with channel state ChannelState { channel: Stable, app_id: AppId { qualifier: "dev", organization: "warp", application_name: "Warp" }, additional_features: {}, firebase_api_key: "AIzaSyBdy3O3S9hrdayLJxJ7mriBR4qgUaUygAs", server_root_url: "https://app.warp.dev", ws_server_url: "wss://rtc.app.warp.dev/graphql", session_sharing_server_url: Some("wss://sessions.app.warp.dev"), rudderstack_write_key: "2iyG8S1RaV4XTX6SEypetFSEbLK", rudderstack_root_url: "https://warpianwzlfqdq.dataplane.rudderstack.com", releases_base_url: "https://releases.warp.dev", sentry_url: "https://0195a81da0714f55a93ee4624825f9ec@o540343.ingest.sentry.io/5658526", logfile_name: "warp.log", show_autoupdate_menu_items: true } and version Some("v0.2024.09.24.08.02.stable_01") 07:10:19 [INFO] Start to send telemetry events to RudderStack 07:10:19 [INFO] Performance metrics collector started 07:10:19 [INFO] Start to send telemetry events to RudderStack 07:10:19 [INFO] Initializing app services 07:10:19 [INFO] Start to send telemetry events to RudderStack Erreur de segmentation (core dumped)
Discord username (optional)
jeshgrca
Describe the bug
Warp fails to launch and segfaults.
Console log:
To reproduce
Run Warp
Expected behavior
I expect the program to launch successfully.
Screenshots
No response
Operating system
Linux
Operating system and version
openSUSE Tumbleweed
Shell Version
zsh 5.9
Current Warp version
v0.2024.02.20.08.01.stable_01-1
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
Never
Additional context
I have attempted to use both the RPM and AppImage; both failed with the same error.
Does this block you from using Warp daily?
Yes, this issue prevents me from using Warp daily.
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