SSH Agent Does not Work After Update

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
0
down vote

favorite












Since I installed regular updates on Ubuntu 18.04, the ssh agent does not work anymore. If I try "ssh r146" (or any other host where my key is an authorized key) it prompts me on command line for the passphrase.



With verbose output it returns:



ssh -v r146
OpenSSH_7.6p1 Ubuntu-4, OpenSSL 1.0.2n 7 Dec 2017
debug1: Reading configuration data /home/reichelt/.ssh/config
debug1: /home/reichelt/.ssh/config line 35: Applying options for r146
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Executing proxy command: exec ssh -W 139.18.11.146:22 ilabws
debug1: permanently_drop_suid: 1000
debug1: identity file /home/reichelt/.ssh/id_rsa type 0
debug1: key_load_public: No such file or directory
debug1: identity file /home/reichelt/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/reichelt/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/reichelt/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/reichelt/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/reichelt/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/reichelt/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/reichelt/.ssh/id_ed25519-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_7.6p1 Ubuntu-4
Enter passphrase for key '/home/reichelt/.ssh/id_rsa':


Which seems fine to me.



The agent seems to be running:



ps -aux | grep ssh
root 1007 0.0 0.0 72296 5676 ? Ss 10:05 0:00 /usr/sbin/sshd -D
reichelt 4106 0.0 0.0 11304 316 ? Ss 10:06 0:00 /usr/bin/ssh-agent /usr/bin/im-launch env GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu
reichelt 6214 0.0 0.0 21536 1088 pts/1 S+ 11:00 0:00 grep --color=auto ssh


The same happens if I use other ssh-using tools like scp.



/etc/log/apt/history.log ends with:



Start-Date: 2018-06-05 09:27:56
Commandline: /usr/bin/unattended-upgrade
Upgrade: liblouis-data:amd64 (3.5.0-1, 3.5.0-1ubuntu0.1)
End-Date: 2018-06-05 09:27:57

Start-Date: 2018-06-05 09:28:00
Commandline: /usr/bin/unattended-upgrade
Upgrade: liblouis14:amd64 (3.5.0-1, 3.5.0-1ubuntu0.1)
End-Date: 2018-06-05 09:28:00

Start-Date: 2018-06-05 09:28:04
Commandline: /usr/bin/unattended-upgrade
Upgrade: python3-louis:amd64 (3.5.0-1, 3.5.0-1ubuntu0.1)
End-Date: 2018-06-05 09:28:05

Start-Date: 2018-06-06 01:34:06
Commandline: packagekit role='update-packages'
Upgrade: libpulsedsp:amd64 (1:11.1-1ubuntu7, 1:11.1-1ubuntu7.1), pulseaudio:amd64 (1:11.1-1ubuntu7, 1:11.1-1ubuntu7.1), libncurses5:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), libncurses5:i386 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), libpq5:amd64 (10.3-1, 10.4-0ubuntu0.18.04), libncursesw5:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), libpulse0:amd64 (1:11.1-1ubuntu7, 1:11.1-1ubuntu7.1), libpulse0:i386 (1:11.1-1ubuntu7, 1:11.1-1ubuntu7.1), libtinfo5:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), libtinfo5:i386 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), libpulse-mainloop-glib0:amd64 (1:11.1-1ubuntu7, 1:11.1-1ubuntu7.1), libncurses5-dev:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), libtinfo-dev:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), ncurses-term:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), ncurses-bin:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), ncurses-base:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), pulseaudio-module-bluetooth:amd64 (1:11.1-1ubuntu7, 1:11.1-1ubuntu7.1), pulseaudio-utils:amd64 (1:11.1-1ubuntu7, 1:11.1-1ubuntu7.1)
End-Date: 2018-06-06 01:34:12

Start-Date: 2018-06-06 10:06:16
Commandline: /usr/bin/unattended-upgrade
Upgrade: git-man:amd64 (1:2.17.0-1ubuntu1, 1:2.17.1-1ubuntu0.1), git:amd64 (1:2.17.0-1ubuntu1, 1:2.17.1-1ubuntu0.1)
End-Date: 2018-06-06 10:06:23


I assume the update finished at 2018-06-06 01:34:12 made the change, at least it worked yesterday and stopped working today.



Is this a known issue / can I further debug this issue?




ssh 18.04




share|improve this question















  • 1




    What if you manually add the keys using ssh-add?
    – muru
    Jun 6 at 9:55










  • Manually adding the key works! While this does not solve the UI/Whatever-Problem, at least it makes working comfortable again, thanks a lot!
    – David Georg Reichelt
    Jun 6 at 10:15














up vote
0
down vote

favorite












Since I installed regular updates on Ubuntu 18.04, the ssh agent does not work anymore. If I try "ssh r146" (or any other host where my key is an authorized key) it prompts me on command line for the passphrase.



With verbose output it returns:



ssh -v r146
OpenSSH_7.6p1 Ubuntu-4, OpenSSL 1.0.2n 7 Dec 2017
debug1: Reading configuration data /home/reichelt/.ssh/config
debug1: /home/reichelt/.ssh/config line 35: Applying options for r146
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Executing proxy command: exec ssh -W 139.18.11.146:22 ilabws
debug1: permanently_drop_suid: 1000
debug1: identity file /home/reichelt/.ssh/id_rsa type 0
debug1: key_load_public: No such file or directory
debug1: identity file /home/reichelt/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/reichelt/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/reichelt/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/reichelt/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/reichelt/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/reichelt/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/reichelt/.ssh/id_ed25519-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_7.6p1 Ubuntu-4
Enter passphrase for key '/home/reichelt/.ssh/id_rsa':


Which seems fine to me.



The agent seems to be running:



ps -aux | grep ssh
root 1007 0.0 0.0 72296 5676 ? Ss 10:05 0:00 /usr/sbin/sshd -D
reichelt 4106 0.0 0.0 11304 316 ? Ss 10:06 0:00 /usr/bin/ssh-agent /usr/bin/im-launch env GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu
reichelt 6214 0.0 0.0 21536 1088 pts/1 S+ 11:00 0:00 grep --color=auto ssh


The same happens if I use other ssh-using tools like scp.



/etc/log/apt/history.log ends with:



Start-Date: 2018-06-05 09:27:56
Commandline: /usr/bin/unattended-upgrade
Upgrade: liblouis-data:amd64 (3.5.0-1, 3.5.0-1ubuntu0.1)
End-Date: 2018-06-05 09:27:57

Start-Date: 2018-06-05 09:28:00
Commandline: /usr/bin/unattended-upgrade
Upgrade: liblouis14:amd64 (3.5.0-1, 3.5.0-1ubuntu0.1)
End-Date: 2018-06-05 09:28:00

Start-Date: 2018-06-05 09:28:04
Commandline: /usr/bin/unattended-upgrade
Upgrade: python3-louis:amd64 (3.5.0-1, 3.5.0-1ubuntu0.1)
End-Date: 2018-06-05 09:28:05

Start-Date: 2018-06-06 01:34:06
Commandline: packagekit role='update-packages'
Upgrade: libpulsedsp:amd64 (1:11.1-1ubuntu7, 1:11.1-1ubuntu7.1), pulseaudio:amd64 (1:11.1-1ubuntu7, 1:11.1-1ubuntu7.1), libncurses5:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), libncurses5:i386 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), libpq5:amd64 (10.3-1, 10.4-0ubuntu0.18.04), libncursesw5:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), libpulse0:amd64 (1:11.1-1ubuntu7, 1:11.1-1ubuntu7.1), libpulse0:i386 (1:11.1-1ubuntu7, 1:11.1-1ubuntu7.1), libtinfo5:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), libtinfo5:i386 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), libpulse-mainloop-glib0:amd64 (1:11.1-1ubuntu7, 1:11.1-1ubuntu7.1), libncurses5-dev:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), libtinfo-dev:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), ncurses-term:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), ncurses-bin:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), ncurses-base:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), pulseaudio-module-bluetooth:amd64 (1:11.1-1ubuntu7, 1:11.1-1ubuntu7.1), pulseaudio-utils:amd64 (1:11.1-1ubuntu7, 1:11.1-1ubuntu7.1)
End-Date: 2018-06-06 01:34:12

Start-Date: 2018-06-06 10:06:16
Commandline: /usr/bin/unattended-upgrade
Upgrade: git-man:amd64 (1:2.17.0-1ubuntu1, 1:2.17.1-1ubuntu0.1), git:amd64 (1:2.17.0-1ubuntu1, 1:2.17.1-1ubuntu0.1)
End-Date: 2018-06-06 10:06:23


I assume the update finished at 2018-06-06 01:34:12 made the change, at least it worked yesterday and stopped working today.



Is this a known issue / can I further debug this issue?




ssh 18.04




share|improve this question















  • 1




    What if you manually add the keys using ssh-add?
    – muru
    Jun 6 at 9:55










  • Manually adding the key works! While this does not solve the UI/Whatever-Problem, at least it makes working comfortable again, thanks a lot!
    – David Georg Reichelt
    Jun 6 at 10:15












up vote
0
down vote

favorite









up vote
0
down vote

favorite











Since I installed regular updates on Ubuntu 18.04, the ssh agent does not work anymore. If I try "ssh r146" (or any other host where my key is an authorized key) it prompts me on command line for the passphrase.



With verbose output it returns:



ssh -v r146
OpenSSH_7.6p1 Ubuntu-4, OpenSSL 1.0.2n 7 Dec 2017
debug1: Reading configuration data /home/reichelt/.ssh/config
debug1: /home/reichelt/.ssh/config line 35: Applying options for r146
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Executing proxy command: exec ssh -W 139.18.11.146:22 ilabws
debug1: permanently_drop_suid: 1000
debug1: identity file /home/reichelt/.ssh/id_rsa type 0
debug1: key_load_public: No such file or directory
debug1: identity file /home/reichelt/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/reichelt/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/reichelt/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/reichelt/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/reichelt/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/reichelt/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/reichelt/.ssh/id_ed25519-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_7.6p1 Ubuntu-4
Enter passphrase for key '/home/reichelt/.ssh/id_rsa':


Which seems fine to me.



The agent seems to be running:



ps -aux | grep ssh
root 1007 0.0 0.0 72296 5676 ? Ss 10:05 0:00 /usr/sbin/sshd -D
reichelt 4106 0.0 0.0 11304 316 ? Ss 10:06 0:00 /usr/bin/ssh-agent /usr/bin/im-launch env GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu
reichelt 6214 0.0 0.0 21536 1088 pts/1 S+ 11:00 0:00 grep --color=auto ssh


The same happens if I use other ssh-using tools like scp.



/etc/log/apt/history.log ends with:



Start-Date: 2018-06-05 09:27:56
Commandline: /usr/bin/unattended-upgrade
Upgrade: liblouis-data:amd64 (3.5.0-1, 3.5.0-1ubuntu0.1)
End-Date: 2018-06-05 09:27:57

Start-Date: 2018-06-05 09:28:00
Commandline: /usr/bin/unattended-upgrade
Upgrade: liblouis14:amd64 (3.5.0-1, 3.5.0-1ubuntu0.1)
End-Date: 2018-06-05 09:28:00

Start-Date: 2018-06-05 09:28:04
Commandline: /usr/bin/unattended-upgrade
Upgrade: python3-louis:amd64 (3.5.0-1, 3.5.0-1ubuntu0.1)
End-Date: 2018-06-05 09:28:05

Start-Date: 2018-06-06 01:34:06
Commandline: packagekit role='update-packages'
Upgrade: libpulsedsp:amd64 (1:11.1-1ubuntu7, 1:11.1-1ubuntu7.1), pulseaudio:amd64 (1:11.1-1ubuntu7, 1:11.1-1ubuntu7.1), libncurses5:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), libncurses5:i386 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), libpq5:amd64 (10.3-1, 10.4-0ubuntu0.18.04), libncursesw5:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), libpulse0:amd64 (1:11.1-1ubuntu7, 1:11.1-1ubuntu7.1), libpulse0:i386 (1:11.1-1ubuntu7, 1:11.1-1ubuntu7.1), libtinfo5:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), libtinfo5:i386 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), libpulse-mainloop-glib0:amd64 (1:11.1-1ubuntu7, 1:11.1-1ubuntu7.1), libncurses5-dev:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), libtinfo-dev:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), ncurses-term:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), ncurses-bin:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), ncurses-base:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), pulseaudio-module-bluetooth:amd64 (1:11.1-1ubuntu7, 1:11.1-1ubuntu7.1), pulseaudio-utils:amd64 (1:11.1-1ubuntu7, 1:11.1-1ubuntu7.1)
End-Date: 2018-06-06 01:34:12

Start-Date: 2018-06-06 10:06:16
Commandline: /usr/bin/unattended-upgrade
Upgrade: git-man:amd64 (1:2.17.0-1ubuntu1, 1:2.17.1-1ubuntu0.1), git:amd64 (1:2.17.0-1ubuntu1, 1:2.17.1-1ubuntu0.1)
End-Date: 2018-06-06 10:06:23


I assume the update finished at 2018-06-06 01:34:12 made the change, at least it worked yesterday and stopped working today.



Is this a known issue / can I further debug this issue?




ssh 18.04




share|improve this question











Since I installed regular updates on Ubuntu 18.04, the ssh agent does not work anymore. If I try "ssh r146" (or any other host where my key is an authorized key) it prompts me on command line for the passphrase.



With verbose output it returns:



ssh -v r146
OpenSSH_7.6p1 Ubuntu-4, OpenSSL 1.0.2n 7 Dec 2017
debug1: Reading configuration data /home/reichelt/.ssh/config
debug1: /home/reichelt/.ssh/config line 35: Applying options for r146
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Executing proxy command: exec ssh -W 139.18.11.146:22 ilabws
debug1: permanently_drop_suid: 1000
debug1: identity file /home/reichelt/.ssh/id_rsa type 0
debug1: key_load_public: No such file or directory
debug1: identity file /home/reichelt/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/reichelt/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/reichelt/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/reichelt/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/reichelt/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/reichelt/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/reichelt/.ssh/id_ed25519-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_7.6p1 Ubuntu-4
Enter passphrase for key '/home/reichelt/.ssh/id_rsa':


Which seems fine to me.



The agent seems to be running:



ps -aux | grep ssh
root 1007 0.0 0.0 72296 5676 ? Ss 10:05 0:00 /usr/sbin/sshd -D
reichelt 4106 0.0 0.0 11304 316 ? Ss 10:06 0:00 /usr/bin/ssh-agent /usr/bin/im-launch env GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu
reichelt 6214 0.0 0.0 21536 1088 pts/1 S+ 11:00 0:00 grep --color=auto ssh


The same happens if I use other ssh-using tools like scp.



/etc/log/apt/history.log ends with:



Start-Date: 2018-06-05 09:27:56
Commandline: /usr/bin/unattended-upgrade
Upgrade: liblouis-data:amd64 (3.5.0-1, 3.5.0-1ubuntu0.1)
End-Date: 2018-06-05 09:27:57

Start-Date: 2018-06-05 09:28:00
Commandline: /usr/bin/unattended-upgrade
Upgrade: liblouis14:amd64 (3.5.0-1, 3.5.0-1ubuntu0.1)
End-Date: 2018-06-05 09:28:00

Start-Date: 2018-06-05 09:28:04
Commandline: /usr/bin/unattended-upgrade
Upgrade: python3-louis:amd64 (3.5.0-1, 3.5.0-1ubuntu0.1)
End-Date: 2018-06-05 09:28:05

Start-Date: 2018-06-06 01:34:06
Commandline: packagekit role='update-packages'
Upgrade: libpulsedsp:amd64 (1:11.1-1ubuntu7, 1:11.1-1ubuntu7.1), pulseaudio:amd64 (1:11.1-1ubuntu7, 1:11.1-1ubuntu7.1), libncurses5:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), libncurses5:i386 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), libpq5:amd64 (10.3-1, 10.4-0ubuntu0.18.04), libncursesw5:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), libpulse0:amd64 (1:11.1-1ubuntu7, 1:11.1-1ubuntu7.1), libpulse0:i386 (1:11.1-1ubuntu7, 1:11.1-1ubuntu7.1), libtinfo5:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), libtinfo5:i386 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), libpulse-mainloop-glib0:amd64 (1:11.1-1ubuntu7, 1:11.1-1ubuntu7.1), libncurses5-dev:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), libtinfo-dev:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), ncurses-term:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), ncurses-bin:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), ncurses-base:amd64 (6.1-1ubuntu1, 6.1-1ubuntu1.18.04), pulseaudio-module-bluetooth:amd64 (1:11.1-1ubuntu7, 1:11.1-1ubuntu7.1), pulseaudio-utils:amd64 (1:11.1-1ubuntu7, 1:11.1-1ubuntu7.1)
End-Date: 2018-06-06 01:34:12

Start-Date: 2018-06-06 10:06:16
Commandline: /usr/bin/unattended-upgrade
Upgrade: git-man:amd64 (1:2.17.0-1ubuntu1, 1:2.17.1-1ubuntu0.1), git:amd64 (1:2.17.0-1ubuntu1, 1:2.17.1-1ubuntu0.1)
End-Date: 2018-06-06 10:06:23


I assume the update finished at 2018-06-06 01:34:12 made the change, at least it worked yesterday and stopped working today.



Is this a known issue / can I further debug this issue?





ssh 18.04





share|improve this question










share|improve this question




share|improve this question









asked Jun 6 at 9:05









David Georg Reichelt

251111




251111







  • 1




    What if you manually add the keys using ssh-add?
    – muru
    Jun 6 at 9:55










  • Manually adding the key works! While this does not solve the UI/Whatever-Problem, at least it makes working comfortable again, thanks a lot!
    – David Georg Reichelt
    Jun 6 at 10:15












  • 1




    What if you manually add the keys using ssh-add?
    – muru
    Jun 6 at 9:55










  • Manually adding the key works! While this does not solve the UI/Whatever-Problem, at least it makes working comfortable again, thanks a lot!
    – David Georg Reichelt
    Jun 6 at 10:15







1




1




What if you manually add the keys using ssh-add?
– muru
Jun 6 at 9:55




What if you manually add the keys using ssh-add?
– muru
Jun 6 at 9:55












Manually adding the key works! While this does not solve the UI/Whatever-Problem, at least it makes working comfortable again, thanks a lot!
– David Georg Reichelt
Jun 6 at 10:15




Manually adding the key works! While this does not solve the UI/Whatever-Problem, at least it makes working comfortable again, thanks a lot!
– David Georg Reichelt
Jun 6 at 10:15















active

oldest

votes











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1044082%2fssh-agent-does-not-work-after-update%23new-answer', 'question_page');

);

Post as a guest






















active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes










 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1044082%2fssh-agent-does-not-work-after-update%23new-answer', 'question_page');

);

Post as a guest
































































-

Popular posts from this blog

pylint3 and pip3 broken

Image
Clash Royale CLAN TAG #URR8PPP up vote 0 down vote favorite I have tried sudo apt remove --purge on various packages. I get the same when I reinstall. I have also tried reinstall using aptitude. This does not work. My current workaround is to run pylint3 as root, which works, but is bad practice. pip3 $ pip3 Traceback (most recent call last): File "/usr/lib/python3/dist-packages/pip/_vendor/__init__.py", line 33, in vendored __import__(vendored_name, globals(), locals(), level=0) ImportError: No module named 'pip._vendor.pkg_resources' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/pip3", line 9, in <module> from pip import main File "/usr/lib/python3/dist-packages/pip/__init__.py", line 13, in <module> from pip.exceptions import InstallationError, CommandError, PipError File "/usr/lib/python3/dist-packages/pip/exceptions.py", line 6, ...
Read more

Missing snmpget and snmpwalk

Image
Clash Royale CLAN TAG #URR8PPP up vote 0 down vote favorite I have installed Zabbix appliance, directly preinstalled and found that there is missing snmpwalk and snmpget commands. I tried to install it with: apt-get install net-snmp-utils but I have error message: Unable to locate package. I have also check what from SNMP is preinstalled and there is: libsnmp-base libsnmp30:amd64 snmp-mibs-downloader snmpd snmptrapd snmptrapfmt How can I install snmpget and snmpwalk ? snmp zabbix share | improve this question edited Jan 29 at 10:10 Yaron 8,552 7 18 38 asked Jan 29 at 9:51 Alfista 1 apt install snmp perhaps ? If named differently - apt cache snmp – fugitive Jan 29 at 10:00 add a comment  |  up vote 0 down vote favorite I have installed Zabbix appliance, directly preinstalled and found that there is missing snmpwalk and snmpget commands. I tried...
Read more

How to enroll fingerprints to Ubuntu 17.10 with VFS491

Image
Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I decided to switch from Windows to Ubuntu 17.10, I meet it like 8 years ago and I didn't decided to switch until now (haha). Well, my actual device is an HP Probook 4540s with a Validity fingerprint sensor (VFS491). The fingerprint sensor worked fine on Windows but I can't get it to work in Ubuntu. The device is recognized as 138a:003d but is not detected as a fingerprint scanner by some apps like Fingerprint GUI. I want to use the fingerprint scanner to log in into my user account in Ubuntu but it doesn't supports fingerprints without special software and the drivers of the fingerprint scanner are available for Windows but not for any Linux distribution. I found something on GitHub (https://github.com/eekpie/libfprint) about the integration of the VFS491 in libfprint and I think it can help but I don't know what to do with it, so that's why I need the help of the community to do it since I am...
Read more