sublimehq / sublime_merge

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

Permission denied on pulling with build 2096 #1906

Open p0rphyr opened 2 months ago

p0rphyr commented 2 months ago

Version info

Description

After upgrading to build 2096 a permission denied error occurs on pulling from a remote that worked before. It doesn't even ask for a password before the error message appears. It happens with different repositories (on the same remote). Using 'system' git binary is and always was configured in the Sublime Merge preferences. Pulling with git directly from the terminal still works. After downgrading the flatpak to build 2091 (commit on flathub: e22c60de44d92d091dda1663743a1323dc46fa9a2fdc83392d2a67e33200d60c) pulling works as expected. Testing on two machines (both Fedora Silverblue 39 with flatpak) resulted in the exact same bevahiour. Testing on Fedora Workstation 39 with flatpak, but with a different remote repository, does not throw an error and works as expected.

Steps to reproduce

Steps to reproduce the behavior:

  1. Open repository and click 'Pull' button or press F7 to pull from remote

Expected behavior

Asking for the users password and then pull from remote.

Debug Information

=== App Version Information === Build: 2096

=== Git Version Information === Using Git: git (system) git version 2.44.0 PATH: /usr/bin:/app/bin:/app/llvm/bin:/app/libexec/git-lfs

=== Browse Page Information === HEAD: 63d33af1212e3fefa886d52ef6931abee18b360c Is in merge: 0 Is in cherry_pick: 0 Is in rebase: 0 Is in revert: 0

=== Git Status Information === ?? [removed]

=== Our Status Information === ?? [removed]

=== Git Config Information === branch.master.merge=refs/heads/master branch.master.remote=origin core.bare=false core.filemode=false core.logallrefupdates=true core.repositoryformatversion=0 credential.helper=cache --timeout=3600 remote.origin.fetch=+refs/heads/:refs/remotes/origin/ remote.origin.url=[user removed]@[host removed]:[repo path removed] user.email=[removed] user.name=[removed]

=== Our Config Information === Git Config Path Information Using config path: /usr/etc/gitconfig Using config path: /var/home/[removed]/.var/app/com.sublimemerge.App/config/git/config Using config path: /var/home/[removed]/.gitconfig Using config path: /home/[removed]/[local repo path removed]/.git/config

Our config output is identical to the Git config output

=== Git Attributes Information === git check_attr --all output

=== Our Modified Files Newline Normalisation and EOL Information ===

=== Our Modified Files Flag Information === Ignoring symlinks: 0

Screenshots

sublime-merge-2096

The german text says: Severe: could not read from remote repository Make sure you have correct access permissions and that the repository exists.

git-terminal

dpjohnst commented 1 month ago

Hi @p0rphyr,

Thanks for reaching out!

The flatpak is not actually distributed by us, so this may cause unexpected issues.

Could you confirm if a fresh install of Sublime Merge via the official instructions located here resolves the issue: https://www.sublimemerge.com/docs/linux_repositories

Kind regards, - Dylan from Sublime HQ

p0rphyr commented 1 month ago

Hi @dpjohnst,

I couldn't find a way to contact someone who does the Flatpak/Flathub packaging.

In Fedora Silverblue it's not possible to install packages via dnf, nor to add a thirdparty repo (the base system image is read-only). Graphical third-party apps are installed via Flatpak, which worked until build 2096 with Sublime Merge.

I managed to add the Sublime repo in a toolbox (container) and installed build 2096 in there. This way it's working und Sublime Merge works as expected.

This is a workaround, but I can understand that you cannot support all environments.

Kind regards