Le mardi 19 juillet 2016 à 15:04 +0200, Michael Biebl a écrit : > Am 19.07.2016 um 14:42 schrieb David Guyot: > > Have you tried running the applications from a console so you get the > output from stdout/stderr? Do you have any specific error messages? > > Does journalctl list any errors?
Well, maybe the problems are not related after all: the SSH agent is currently unreachable, but URL clicks are still functional. After checking, I've 2 SSH agents: the official one, and the GPG agent running as the SSH one. I think this is a remainder of several tries I did to circumvent the Gnome keyring bug regarding the ECDSA keys (https://bugzilla.gnome.org/show_bug.cgi?id=641082): I had to try several agents before having one functional, but there seems to be disrupting remainders. I should try to disable the GPG SSH agent and let the official one do the job, but I can't find how it activated: penegal@Aethelthryth ~ {⌗0/⬓52}[0]> grep -ri ssh .gnupg/ Fichier binaire .gnupg/pubring.gpg~ correspondant Fichier binaire .gnupg/private-keys-v1.d/DEFF567497D9CEE0B6739CE796A1657810FC4422.key correspondant Fichier binaire .gnupg/private-keys-v1.d/094ACDE0C1EC2CF724C7DD4D5E21ACF66CEBACB6.key correspondant .gnupg/sshcontrol:# List of allowed ssh keys. Only keys present in this file are used .gnupg/sshcontrol:# in the SSH protocol. The ssh-add tool may add new entries to this Fichier binaire .gnupg/pubring.gpg correspondant I was under the impression that the SSH agent mode was to be activated in one of these files, but it doesn't seem to be the case. Where can it be enabled? Awaiting your answers, Regards. -- David Guyot Administrateur système, réseau et télécom / Sysadmin Europe Camions Interactive / Stockway Moulin Collot F-88500 Ambacourt 03 29 30 47 85
signature.asc
Description: This is a digitally signed message part
