Gitkraken stuck at opening repo

Question

Every time I open gitkrarken it gets stuck at opening repo icon. I can\'t open/clone/init repo. I heard some others have the same problem but no one seems to know why this i

Answer 1

I had the same issue and couldnt fix it until I deleted the repo I knew was causing the issue and then created it again.

Working fine now

Answer 2

Close gitkraken and go to your home directory. Delete the hidden folder ".gitkraken". The folder ".gitkraken" will be created automatically upon restart. This solution works for me.

For mac and linux users: rm -r ~/.gitkraken

Answer 3

I just had a similar (maybe the same) problem with GitKraken V2.7.0 x64 on Windows. GitKraken crashed and tried to open the repo after that. This never finished. I assume this is caused by visual studio which was open at the time and VS and GitKraken are not exactly friends. I killed GitKraken, closed VS. After that, when opening the repo in GitKraken, it said something like "there is no repo, do you want to initialize it?". This also failed. Not sure what the root cause for the problem is.

The solution however was to checkout another branch from the CLI. After that GitKraken magically worked again. Maybe this helps someone.

Answer 4

For me hanging GitKraken, if i delete branches in local or origin place. After this start hanging in main window or changes lister in right. Little help is if you run "GIT GC" (https://git-scm.com/docs/git-gc)

Answer 5

I manually removed all files had [conflict] in their names from .git folder and its subfolders. Then, I performed a git gc to compress the database and finally git fsck to make sure everything is just fine. Now, I can open the repo in GitKraken.

Notes:

1. This might be helpful to remove all files marked as '[conflict]'.
2. The combination worked for me but you may not need to perform all these steps. For example, you may not have conflict files, or you just want to resolve them differently rather than removing them.

Answer 6

Fixed mine by

1. Quit GitKraken
2. Open terminal/command prompt and do a git status on the repo

3. Found that there were a few files/folders uncommited/unstaged:

   1. A symlink pointing to a folder outside of my repo was renamed
   2. A copy of my repo inside the same repo
   3. A new folder with images

4. Renamed #1 back to its original name, and removed #2 & #3 manually

5. Opened gitkraken and it was able to load my repo without any problems