search

sublimehq / sublime_merge

Issue tracker for Sublime Merge
https://www.sublimemerge.com
276 stars 14 forks source link

Password caching doesn't work between sessions on Fedora 37 #1699

Open debsidian opened 1 year ago

debsidian commented 1 year ago

OS: 

NAME="Fedora Linux"
VERSION="37 (Workstation Edition)"
ID=fedora
VERSION_ID=37
VERSION_CODENAME=""
PLATFORM_ID="platform:f37"
PRETTY_NAME="Fedora Linux 37 (Workstation Edition)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:37"
DEFAULT_HOSTNAME="fedora"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f37/system-administrators-guide/"
SUPPORT_URL="https://ask.fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=37
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=37
SUPPORT_END=2023-11-14
VARIANT="Workstation Edition"
VARIANT_ID=workstation

Steps to reproduce the behavior:

  1. Click Tools→ Password Caching → 1 week
  2. Pull from Private Repo
  3. Authenticate (username/password) via Sublime Merge (I'm using a private repo on gitlab.com)
  4. Work locally. Push changes, works fine.
  5. Close Sublime Merge
  6. Reopen Sublime Merge
  7. Pushing or pulling from the private repo will require a repeat of the authentication process despite having selected cache password for 1 week.

Expected behavior

I expect not to need to re-authenticate for each new session of Sublime Merge. The password caching behavior does work as expected (normally) on my macOS machine, but it does not work on as expected on both machines running Fedora 37.