Access token for user was deleted from keychain - login is now invalid #5493
Comments
Byron
added
os:linux
|
GitButler uses the Since it's not permanently failing, it feels like either it's keeping secrets for the session only, or the UI saves tokens in its own in-memory store. There is something you could try if you could compile the application on your own with the following patch applied… diff --git a/crates/gitbutler-tauri/src/main.rs b/crates/gitbutler-tauri/src/main.rs
index 5e7465ce4..88de94b3d 100644
--- a/crates/gitbutler-tauri/src/main.rs
+++ b/crates/gitbutler-tauri/src/main.rs
@@ -68,7 +68,7 @@ fn main() {
// the binary is rebuilt. To counter that, use a git-credential based implementation.
// This isn't an issue for actual release build (i.e. nightly, production),
// hence the specific condition.
- if cfg!(debug_assertions) && cfg!(target_os = "macos") {
+ if true {
gitbutler_secret::secret::git_credentials::setup().ok();
}…to see if that fixes the issue. If so, then using Thanks for your help with this. |
|
Sounds like an issue with your system keyring. With KDE this should be Can you open KWalletManager to see if GitButler is listed in there after opening GitButler and signing in? That will tell us if we were able to successfully save it in your keyring at all to begin with and point to the issue being persistence of your keyring between reboots. |
Byron
added
the
feedback requested
Version
0.13.12
Operating System
Linux
Distribution Method
deb (Linux)
Describe the issue
I am using a Fedora Atomic Desktop (https://getaurora.dev/) which means that the base OS is read only.
I am running into the same issue with the flatpak and the rpm. Everything works normally i can push pull merge etc. but if I close Gitbutler and then reopen it I have go to Preferences > Integrations and sign in again and then re authorize github.
I have a feeling that gitbutler is trying to save the Access Token somewhere that is read only. Which directory on the host file system is is the Access token being saved to?
Below are the relevant logs
ui-logs.log
GitButler.2024-11-08.log
How to reproduce
No response
Expected behavior
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: