You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I installed Logseq through Snap (https://snapcraft.io/install/logseq/ubuntu) and setup Github using the tutorial in this repo. After completing it, I noticed that changes were automatically created in the local git repo, but were not pushed to remote. The issue was that the snap package did not have a slot for the ssh-keys interface, which was required to make the connection to the Github servers.
(I believe the reason this error shows up at all, is that I added echo "precommit" to the pre-commit hook, causing it to show the output in Logseq as a notification. I did this to verify it was actually working through Logsec, as a regular git commit from the terminal did trigger the pre- and post-commits as expected.)
I fixed this by manually adding the ssh-keys slot to Logseq, through
sudo snap connect logseq:ssh-keys
Checking the snap package interfaces can be done with snap connections logseq.
I am posting this in the hope that anyone else running into this problem can find the solution.
This was on Ubuntu 24.04.
The text was updated successfully, but these errors were encountered:
I installed Logseq through Snap (https://snapcraft.io/install/logseq/ubuntu) and setup Github using the tutorial in this repo. After completing it, I noticed that changes were automatically created in the local git repo, but were not pushed to remote. The issue was that the snap package did not have a slot for the ssh-keys interface, which was required to make the connection to the Github servers.
The resulting error that was shown in Logseq is
(I believe the reason this error shows up at all, is that I added
echo "precommit"
to the pre-commit hook, causing it to show the output in Logseq as a notification. I did this to verify it was actually working through Logsec, as a regulargit commit
from the terminal did trigger the pre- and post-commits as expected.)I fixed this by manually adding the ssh-keys slot to Logseq, through
Checking the snap package interfaces can be done with
snap connections logseq
.I am posting this in the hope that anyone else running into this problem can find the solution.
This was on Ubuntu 24.04.
The text was updated successfully, but these errors were encountered: