search

warpdotdev / Warp

Warp is a modern, Rust-based terminal with AI built in so you and your team can build great software, faster.
https://warp.dev
Other
21.47k stars 376 forks source link

Unexpected loss of permission on macOS #3009

Open markmbaum opened 1 year ago

markmbaum commented 1 year ago

Discord username (optional)

No response

Describe the bug

I was in the process of fairly routine git activity and the Warp shell suddenly lost permission to access files and directories. A screenshot of the error message and failure to even run ls is below.

Screenshot 2023-05-02 at 4 44 22 PM

If I quit and restart, it works fine.

Sometimes sudden permission loss happens in the middle of running a program (in this case Python scripts driving an executable), which makes it crash.

To Reproduce

The last thing I did before the screenshot above was git push --force but sometimes the sudden permission loss happens in the middle of runnig a Python script.

Expected behavior

The shell should keep running with normal permissions.

Screenshots

No response

Operating System

MacOS

Operating System and Version

macOS 13.3.1

Shell Version

zsh 5.9 (x86_64-apple-darwin22.0)

Warp Version

v0.2023.04.25.08.05.stable_00

Additional context

No response

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:b8107fdf-ba31-488d-b103-d271c89cac3e

None

dannyneira commented 1 year ago

Thanks for letting us know @markmbaum Please see our guides on the permissions and updating warp issues that could be affecting your permissions.

Let us know if those helped, if not, we will need a bit more information from you to reproduce this issue, most likely some Logs.

markmbaum commented 1 year ago

Ok thanks for the pointer. I haven't noticed any issues updating Warp, so I'll look into the other troubleshooting.

RobSchilderr commented 1 year ago

Same issue here.

SOLUTION: After a MacOS update, my standard terminal also didn't have access anymore for Full Disk Access in Privacy & Security. So make sure to check this.

zain-mansuri commented 3 weeks ago

Found any solution? Restarting wrap is the only thing I can find.

Running using sudo also won't work

image
jonasms commented 3 weeks ago

I've also been getting this behavior. Over the past 2 - 3 weeks.

dannyneira commented 3 weeks ago

Hey Folks, We're noticing reports of this issue returning recently. We suspect it may be related to auto-updates to Warp. We're going to reopen, investigate further, and post any updates on this thread. As a possible workaround/stopgap measure, please apply and pending Updates to Warp. This should grant Warp the permissions again and resume normal functions.

To anyone else facing this issue, please add a 👍 to the original post at the top or comment with your details, and subscribe if you'd like to be notified.

robbiehobby commented 3 weeks ago

Just happened to me. Shortly after "Update Warp" showed up in the toolbar.

jordanwegener commented 3 weeks ago

Hey Folks, We're noticing reports of this issue returning recently. We suspect it may be related to auto-updates to Warp. We're going to reopen, investigate further, and post any updates on this thread. As a possible workaround/stopgap measure, please grant "old" Warp permission in Mac > System Settings > Privacy & Security > Full Disk Access.

image

To anyone else facing this issue, please add a 👍 to the original post at the top or comment with your details, and subscribe if you'd like to be notified.

Confirming I have been experiencing this and granting permissions to 'old' seems to have been the fix for me.

razanfawwaz commented 3 weeks ago

Hey Folks, We're noticing reports of this issue returning recently. We suspect it may be related to auto-updates to Warp. We're going to reopen, investigate further, and post any updates on this thread. As a possible workaround/stopgap measure, please grant "old" Warp permission in Mac > System Settings > Privacy & Security > Full Disk Access.

image

To anyone else facing this issue, please add a 👍 to the original post at the top or comment with your details, and subscribe if you'd like to be notified.

how if in my devices there's no "old"?

mark-jordanovic-lewis commented 3 weeks ago

Adding to this thread as #5417 was closed. I didn't think it was a duplicate as this issue was closed as completed in March 2023.

There is no "old" in my settings.

dannyneira commented 3 weeks ago

@mark-jordanovic-lewis when you see the issue, is there usually a pending update in Warp? If you do, the best workaround would be to apply the Update, and the new Warp binary should have the right permissions. We've noticed this only on MacOS and when there is a pending update, so just want to confirm.

mark-jordanovic-lewis commented 3 weeks ago

I can't really comment on that, there was an update today and it happened. I encountered it quite a few times before I posted previous issue but I'm not sure it corresponded with an update or not.

dannyneira commented 3 weeks ago

@robbiehobby Yup, this appears to happen after a pending Update in Warp and only on directories that require permissions (i.e. Documents, Downloads, Desktop, etc), even if you've granted Warp "Full Disk Access". If you manage to run commands on those directories while Warp is still Updating in the background, then the issue may not happen. The best workaround for now is to apply any pending updates to Warp.

dannyneira commented 3 weeks ago

@mark-jordanovic-lewis Keep an eye out for this, We suspect it is related to updates with high certainty, but your issue may indeed be different. There will be a fix coming soon (which may cause the issue again ), but updating to the new version will hopefully ensure it doesn't return for future releases. If that's not the case, please reopen https://github.com/warpdotdev/Warp/issues/5417 and let us know.

VanWieren commented 3 weeks ago

Same issue for me while saving local files on mac after updating to OS 15.

jalopez commented 2 weeks ago

In case it helps finding the root cause: I only started to face this issue after upgrading my MacOS version to Sequoia

Conless commented 1 week ago

Same issue for me. Only happens after updating to macOS Sequoia.

mark-jordanovic-lewis commented 1 week ago

@dannyneira As requested (but cannot re-open issue #5434). On Thursday and Friday there was no loss of permissions in warp. Yesterday morning, Monday 11th Nov 2024, permissions to read directories in already open warp sessions have been lost. No changes in OS settings related to Full Disk access of the application.

brew upgrade did not find warp to upgrade. brew upgrade warp re-installed warp. Warp will no longer open.

brew remove warp brew install --cask warp. Warp will no longer open.

Removed warp, rebooted machine, reinstalled warp, warp will still not open.

Checked permissions, Warp.App is read/write for me.

Delving into the Warp.app package and running the stable binary gives me:

15:54:33 [INFO] Initial open file descriptor limit is 2560, with a hard limit of 9223372036854775807
15:54:33 [INFO] Spawning terminal server process...
15:54:33 [INFO] Running terminal server...
15:54:33 [INFO] application will finish launching
15:54:33 [INFO] Removing old executable dir...
15:54:33 [INFO] Removing old executable file...
15:54:33 [WARN] Failed to parse config file at "trunk.yaml" with error: missing field `background` at line 1 column 8
15:54:33 [WARN] Failed to parse config file at "run_themes_generator.yml" with error: missing field `background` at line 2 column 5
15:54:33 [INFO] Initializing crash reporting Some("mac_stable_release") with tag "v0.2024.11.05.08.02.stable_02"...
15:54:33 [INFO] Initializing Sentry for cocoa app with endpoint https://0195a81da0714f55a93ee4624825f9ec@o540343.ingest.sentry.io/5658526
15:54:33 [INFO] Starting warp with channel state ChannelState { channel: Stable, app_id: AppId { qualifier: "dev", organization: "warp", application_name: "Warp-Stable" }, 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.11.05.08.02.stable_02")
15:54:33 [INFO] Performance metrics collector started
15:54:33 [INFO] Dropping empty RudderStack telemetry batch
15:54:33 [INFO] Flushed telemetry events.
15:54:33 [INFO] Initializing app services
15:54:33 [WARN] SQLite error 283 (A WAL mode database file was recovered): recovered 467 frames from WAL file /Users/jail/Library/Application Support/dev.warp.Warp-Stable/warp.sqlite-wal
15:54:33 [INFO] Connecting to SQLite database
15:54:33 [INFO] fetching team tester status
15:54:33 [INFO] Checking for update on channel stable_release. Update id is z4pLDsl
15:54:33 [INFO] Fetching channel versions (without changelogs) from Warp server
15:54:33 [INFO] dispatching global action for root_view:open_from_restored
15:54:33 [INFO] Start to send telemetry events to RudderStack
15:54:33 [INFO] Start to send telemetry events to RudderStack
15:54:33 [INFO] Computing available system fonts
15:54:33 [WARN] Could not find current AIAgentApiType value in dropdown option list
15:54:33 [INFO] Start to send telemetry events to RudderStack
15:54:33 [INFO] Block finished with new state DoneWithExecution
15:54:33 [INFO] Block finished with new state DoneWithExecution
15:54:33 [INFO] Starting shell /bin/zsh
15:54:33 [INFO] Successfully spawned child zsh process with pid 17273
15:54:33 [INFO] Successfully spawned tty with pid: 17273
15:54:33 [INFO] Starting shell /bin/zsh
15:54:33 [INFO] Successfully spawned child zsh process with pid 17275
15:54:33 [INFO] Successfully spawned tty with pid: 17275
15:54:33 [INFO] Block finished with new state DoneWithExecution
15:54:33 [INFO] Block finished with new state DoneWithExecution
15:54:33 [INFO] Starting shell /bin/zsh
15:54:33 [INFO] Successfully spawned child zsh process with pid 17277
15:54:33 [INFO] Successfully spawned tty with pid: 17277
15:54:33 [INFO] Opening window with id 0
15:54:33 [INFO] Fetching channel versions and changelogs from Warp server
15:54:33 [INFO] Using discrete GPU for rendering new window.
15:54:33 [INFO] Computing available system fonts
15:54:33 [WARN] Could not find current AIAgentApiType value in dropdown option list
15:54:33 [INFO] Block finished with new state DoneWithExecution
15:54:33 [INFO] Block finished with new state DoneWithExecution
15:54:33 [INFO] Block finished with new state DoneWithExecution
15:54:33 [INFO] Starting shell /bin/zsh
15:54:33 [INFO] Successfully spawned child zsh process with pid 17285
15:54:33 [INFO] Successfully spawned tty with pid: 17285
15:54:33 [INFO] Opening window with id 1
15:54:33 [INFO] Using discrete GPU for rendering new window.
15:54:33 [INFO] Received InitShell hook
15:54:33 [INFO] Received InitShell hook
15:54:33 [INFO] Received InitShell hook
15:54:33 [INFO] Received InitShell hook
thread 'main' panicked at ui/src/core/app.rs:391:32:
already borrowed: BorrowMutError
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Failed to send log record to host process: EPIPE: Broken pipe
Failed to send log record to host process: EPIPE: Broken pipe

I removed the yaml that was not formatted as a theme file and the git files from the themes directory and those errors went away.

Backtrace (short)

stack backtrace:
0: _rust_begin_unwind
1: core::panicking::panic_fmt
2: core::cell::panic_already_borrowed
3: _warp_update_layer
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <warpui::platform::mac::window::WindowManager as warpui::platform::WindowManager>::open_window
11: <warpui::core::app::MutableAppContext>::insert_window::<warp::root_view::RootView, warp::root_view::open_from_restored::{closure#3}>
12: warp::root_view::open_from_restored
13: <warpui::core::app::MutableAppContext>::dispatch_global_action
14: <warpui::platform::app::AppBuilder>::run::<warp::run_internal::{closure#1}>::{closure#0}
15: <<warpui::platform::app::AppBuilder>::run<warp::run_internal::{closure#1}>::{closure#2} as core::ops::function::FnOnce<(&mut warpui::core::app::MutableAppContext, core::pin::Pin<alloc::boxed::Box<dyn core::future::future::Future<Output = warpui::core::app::App>>>)>>::call_once::{shim:vtable#0}
16: <warpui::core::app::App>::update::<(), <warpui::platform::app::AppCallbackDispatcher>::initialize_app::{closure#0}>
17: _warp_app_will_finish_launching
18: <unknown>
19: <unknown>
20: <unknown>
21: <unknown>
22: <unknown>
23: <unknown>
24: <unknown>
25: warp::run_internal
26: warp::run
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Backtrace (full)

thread 'main' panicked at ui/src/core/app.rs:391:32:
already borrowed: BorrowMutError
stack backtrace:
0:        0x1037329b4 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h41035ce174e31160
1:        0x10315cf1c - core::fmt::write::h7e946826fce7616b
2:        0x10372def0 - std::io::Write::write_fmt::he3645adfefb23e4a
3:        0x1037327c8 - std::sys_common::backtrace::print::h2efe9ae66fda73dc
4:        0x1037341f8 - std::panicking::default_hook::{{closure}}::hd27200b4fbd3bf40
5:        0x103733f60 - std::panicking::default_hook::hb8656334461229c8
6:        0x1037350e8 - std::panicking::rust_panic_with_hook::h10171cf76e1aed15
7:        0x103734604 - std::panicking::begin_panic_handler::{{closure}}::h9344de43a47cae21
8:        0x103732e48 - std::sys_common::backtrace::__rust_end_short_backtrace::h55013ada3ab9c4e8
9:        0x103734388 - _rust_begin_unwind
10:        0x105659614 - core::panicking::panic_fmt::h0b16bb09366e1f01
11:        0x105659540 - core::cell::panic_already_borrowed::h70948587632deaad
12:        0x1053f76e8 - _warp_update_layer
13:        0x197611afc - <unknown>
14:        0x197611304 - <unknown>
15:        0x19779f858 - <unknown>
16:        0x1975f3888 - <unknown>
17:        0x193289ef4 - <unknown>
18:        0x19345e378 - <unknown>
19:        0x1053f452c - <warpui[6fdbc27bfea42a8a]::platform::mac::window::WindowManager as warpui[6fdbc27bfea42a8a]::platform::WindowManager>::open_window
20:        0x1038ad724 - <warpui[6fdbc27bfea42a8a]::core::app::MutableAppContext>::insert_window::<warp[969e8f8acfeea52]::root_view::RootView, warp[969e8f8acfeea52]::root_view::open_from_restored::{closure#3}>
21:        0x104c928b4 - warp[969e8f8acfeea52]::root_view::open_from_restored
22:        0x1053b354c - <warpui[6fdbc27bfea42a8a]::core::app::MutableAppContext>::dispatch_global_action
23:        0x104f1523c - <warpui[6fdbc27bfea42a8a]::platform::app::AppBuilder>::run::<warp[969e8f8acfeea52]::run_internal::{closure#1}>::{closure#0}
24:        0x104f6adb0 - <<warpui[6fdbc27bfea42a8a]::platform::app::AppBuilder>::run<warp[969e8f8acfeea52]::run_internal::{closure#1}>::{closure#2} as core[cec0bd9d2fc86fa9]::ops::function::FnOnce<(&mut warpui[6fdbc27bfea42a8a]::core::app::MutableAppContext, core[cec0bd9d2fc86fa9]::pin::Pin<alloc[9bfd1da98798fc47]::boxed::Box<dyn core[cec0bd9d2fc86fa9]::future::future::Future<Output = warpui[6fdbc27bfea42a8a]::core::app::App>>>)>>::call_once::{shim:vtable#0}
25:        0x1053ad4dc - <warpui[6fdbc27bfea42a8a]::core::app::App>::update::<(), <warpui[6fdbc27bfea42a8a]::platform::app::AppCallbackDispatcher>::initialize_app::{closure#0}>
26:        0x1053eb928 - _warp_app_will_finish_launching
27:        0x18eb8a800 - <unknown>
28:        0x18ec1b66c - <unknown>
29:        0x18ec1b5b4 - <unknown>
30:        0x18eb5943c - <unknown>
31:        0x18fd01b14 - <unknown>
32:        0x1926b2d30 - <unknown>
33:        0x1926b29fc - <unknown>
34:        0x104ff68c4 - warp[969e8f8acfeea52]::run_internal
35:        0x104ff5adc - warp[969e8f8acfeea52]::run
36:        0x10370ca34 - std[4ec0ba9e3c6d748b]::sys_common::backtrace::__rust_begin_short_backtrace::<fn() -> core[cec0bd9d2fc86fa9]::result::Result<(), anyhow[371c3e780c0d30cb]::Error>, core[cec0bd9d2fc86fa9]::result::Result<(), anyhow[371c3e780c0d30cb]::Error>>
37:        0x10370ca54 - std[4ec0ba9e3c6d748b]::rt::lang_start::<core[cec0bd9d2fc86fa9]::result::Result<(), anyhow[371c3e780c0d30cb]::Error>>::{closure#0}
38:        0x10372696c - std::rt::lang_start_internal::h27a134f18d582a1e
39:        0x10370d104 - _main

cat ./Library/Logs/warp.log

2024-11-12T16:12:14Z [INFO] Initial open file descriptor limit is 256, with a hard limit of 9223372036854775807
2024-11-12T16:12:14Z [INFO] Increased open file descriptor limit to 2560
2024-11-12T16:12:14Z [INFO] Spawning terminal server process...
2024-11-12T16:12:14Z [INFO] Running terminal server...
2024-11-12T16:12:15Z [INFO] application will finish launching
2024-11-12T16:12:15Z [INFO] Removing old executable dir...
2024-11-12T16:12:15Z [INFO] Removing old executable file...
2024-11-12T16:12:15Z [INFO] Initializing crash reporting Some("mac_stable_release") with tag "v0.2024.11.05.08.02.stable_02"...
2024-11-12T16:12:15Z [INFO] Initializing Sentry for cocoa app with endpoint https://0195a81da0714f55a93ee4624825f9ec@o540343.ingest.sentry.io/5658526
2024-11-12T16:12:15Z [INFO] Starting warp with channel state ChannelState { channel: Stable, app_id: AppId { qualifier: "dev", organization: "warp", application_name: "Warp-Stable" }, 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.11.05.08.02.stable_02")
2024-11-12T16:12:15Z [INFO] Performance metrics collector started
2024-11-12T16:12:15Z [INFO] Dropping empty RudderStack telemetry batch
2024-11-12T16:12:15Z [INFO] Flushed telemetry events.
2024-11-12T16:12:15Z [INFO] Initializing app services
2024-11-12T16:12:15Z [WARN] SQLite error 283 (A WAL mode database file was recovered): recovered 479 frames from WAL file /Users/jail/Library/Application Support/dev.warp.Warp-Stable/warp.sqlite-wal
2024-11-12T16:12:15Z [INFO] Connecting to SQLite database
2024-11-12T16:12:15Z [INFO] fetching team tester status
2024-11-12T16:12:15Z [INFO] Checking for update on channel stable_release. Update id is 10DfV2W
2024-11-12T16:12:15Z [INFO] Fetching channel versions (without changelogs) from Warp server
2024-11-12T16:12:15Z [INFO] dispatching global action for root_view:open_from_restored
2024-11-12T16:12:15Z [INFO] Start to send telemetry events to RudderStack
2024-11-12T16:12:15Z [INFO] Start to send telemetry events to RudderStack
2024-11-12T16:12:15Z [INFO] Computing available system fonts
2024-11-12T16:12:15Z [WARN] Could not find current AIAgentApiType value in dropdown option list
2024-11-12T16:12:15Z [INFO] Start to send telemetry events to RudderStack
2024-11-12T16:12:15Z [INFO] Block finished with new state DoneWithExecution
2024-11-12T16:12:15Z [INFO] Block finished with new state DoneWithExecution
2024-11-12T16:12:15Z [INFO] Starting shell /bin/zsh
2024-11-12T16:12:15Z [INFO] Successfully spawned tty with pid: 21496
2024-11-12T16:12:15Z [INFO] Successfully spawned child zsh process with pid 21496
2024-11-12T16:12:15Z [INFO] Starting shell /bin/zsh
2024-11-12T16:12:15Z [INFO] Successfully spawned child zsh process with pid 21497
2024-11-12T16:12:15Z [INFO] Successfully spawned tty with pid: 21497
2024-11-12T16:12:15Z [INFO] Block finished with new state DoneWithExecution
2024-11-12T16:12:15Z [INFO] Block finished with new state DoneWithExecution
2024-11-12T16:12:15Z [INFO] Starting shell /bin/zsh
2024-11-12T16:12:15Z [INFO] Successfully spawned child zsh process with pid 21499
2024-11-12T16:12:15Z [INFO] Successfully spawned tty with pid: 21499
2024-11-12T16:12:15Z [INFO] Opening window with id 0
2024-11-12T16:12:15Z [INFO] Fetching channel versions and changelogs from Warp server
2024-11-12T16:12:15Z [INFO] Using discrete GPU for rendering new window.
2024-11-12T16:12:15Z [INFO] Computing available system fonts
2024-11-12T16:12:15Z [WARN] Could not find current AIAgentApiType value in dropdown option list
2024-11-12T16:12:15Z [INFO] Block finished with new state DoneWithExecution
2024-11-12T16:12:15Z [INFO] Block finished with new state DoneWithExecution
2024-11-12T16:12:15Z [INFO] Block finished with new state DoneWithExecution
2024-11-12T16:12:15Z [INFO] Starting shell /bin/zsh
2024-11-12T16:12:15Z [INFO] Successfully spawned child zsh process with pid 21507
2024-11-12T16:12:15Z [INFO] Successfully spawned tty with pid: 21507
2024-11-12T16:12:15Z [INFO] Opening window with id 1
2024-11-12T16:12:15Z [INFO] Using discrete GPU for rendering new window.
2024-11-12T16:12:15Z [INFO] Received InitShell hook
2024-11-12T16:12:15Z [INFO] Received InitShell hook
2024-11-12T16:12:15Z [INFO] Received InitShell hook
2024-11-12T16:12:15Z [INFO] Received InitShell hook
2024-11-12T16:12:15Z [INFO] Received channel versions from Warp server: dev: ChannelVersion { version_info: VersionInfo { version: "v0.2024.11.11.08.02.dev_00", update_by: None, soft_cutoff: Some("v0.2023.05.12.08.03.dev_00") }, overrides: [] }; preview: ChannelVersion { version_info: VersionInfo { version: "v0.2024.11.11.08.02.preview_00", update_by: None, soft_cutoff: None }, overrides: [] }; canary: ChannelVersion { version_info: VersionInfo { version: "v0.2022.09.29.08.08.canary_00", update_by: None, soft_cutoff: None }, overrides: [] }; beta: ChannelVersion { version_info: VersionInfo { version: "v0.2024.11.05.08.02.beta_00", update_by: None, soft_cutoff: None }, overrides: [] }; stable: ChannelVersion { version_info: VersionInfo { version: "v0.2024.11.05.08.02.stable_02", update_by: None, soft_cutoff: Some("v0.2024.09.17.08.02.stable_01") }, overrides: [] }
2024-11-12T16:12:15Z [INFO] Received channel versions from Warp server: dev: ChannelVersion { version_info: VersionInfo { version: "v0.2024.11.11.08.02.dev_00", update_by: None, soft_cutoff: Some("v0.2023.05.12.08.03.dev_00") }, overrides: [] }; preview: ChannelVersion { version_info: VersionInfo { version: "v0.2024.11.11.08.02.preview_00", update_by: None, soft_cutoff: None }, overrides: [] }; canary: ChannelVersion { version_info: VersionInfo { version: "v0.2022.09.29.08.08.canary_00", update_by: None, soft_cutoff: None }, overrides: [] }; beta: ChannelVersion { version_info: VersionInfo { version: "v0.2024.11.05.08.02.beta_00", update_by: None, soft_cutoff: None }, overrides: [] }; stable: ChannelVersion { version_info: VersionInfo { version: "v0.2024.11.05.08.02.stable_02", update_by: None, soft_cutoff: Some("v0.2024.09.17.08.02.stable_01") }, overrides: [] }

I completely purged my system of warp assets inc. DBs, config and themes and re-installed it.

Warp works now.

dannyneira commented 1 week ago

@mark-jordanovic-lewis Thanks for sharing the details. As far as I'm aware, the fix for this issue went out last weeks release. We're fairly confident it won't return in future releases, but please keep an eye out for this issue and let us know.

mark-jordanovic-lewis commented 1 week ago

@dannyneira good to know. I can't pin down what it was that was causing the problem, and I was annoyed at having to set up my config again - however the UI is intuitive and it was easy to get back up and running once I could sort of work out what was going on.

Thanks for staying on this and replying. I will post if this happens again and the solution above does not fix things.

dannyneira commented 3 days ago

Hi Folks, this issue should be resolved in the latest release of Warp! Note that you may still see the issue if you're on an older build and updating to v0.2024.11.12.08.02 and beyond. Once you're on version v0.2024.11.12.08.02 or higher, the permission issue should not persist.

Please update and let us know if you continue seeing the issue in this week's Thursday release.