Hi there! I’m trying to help out a colleague who’s using gnome. It works fine. But it completely fails to reproduce the seamless credential helper experience I’m used to from KDE. I don’t even know how it works there, cause it just works.
We need to use git over https for a particular project.
On gnome, when doing git <pull|clone|...> I first get a very annoying popup saying
**Allow inhibiting shortcuts**
The app ssh-askpass wants to inhibit shortcuts
You can restore shortcuts by pressing <Super>Escape
This is coming up every f****** time, no matter whether I accept or deny.
It then continues with another popup that asks my username, then the first popup again, then popup asking for password. Then git does it’s thing. However, nowhere can I choose to save the password.
I have scoured the Internet to find a solution to this incredibly banal problem just about anybody must have (unless exclusively using ssh-keys which is nice, but not an option for us). There are only partial solutions to sort-of-related issues, but nothing that fixed the issue for me.
So I can not find a working solution. This is very frustrating.
Anyways, here’s my best guess at the relevant config
{ config, pkgs, ... }:
{
environment.systemPackages = with pkgs; [
git
# did not make a difference:
# libsecret
# gnome-keyring
# git-doc
];
# Ensure the Git credential helper is installed and used
programs = {
git = {
enable = true;
config = {
credential = {
helper = "libsecret";
};
};
};
seahorse.enable = true;
};
# Optionally, enable GNOME Keyring (if it's not already enabled)
services.gnome.gnome-keyring.enable = true;
security.pam.services = {
login.enableGnomeKeyring = true;
gdm.enableGnomeKeyring = true;
};
}
I don’t know if something is broken here or if I’m just massively missing something. However, a working credential helper in a desktop environment like gnome should not cause such a headache, no?! Can anybody help? Someone must have got that figured out, I hope!