Description of problem: After installing keychain and openssh-askpass-qt5-2.0.3-1.mga6, I did not get a prompt for my ssh passphrase on login or when starting a terminal emulator. To troubleshoot, I ran: [bgmilne@localhost ~]$ ssh-add < /dev/null ssh_askpass: exec(/usr/libexec/openssh/ssh-askpass): No such file or directory ssh_askpass: exec(/usr/libexec/openssh/ssh-askpass): No such file or directory [bgmilne@localhost ~]$ All ssh askpass packages should be installing alternatives, the way the openssh-askpass-gnome package does. For example, installing openssh-askpass-gnome and trying the above again results in: [bgmilne@localhost ~]$ ssh-add < /dev/null Gtk-Message: Failed to load module "canberra-gtk-module" (ssh-askpass:9838): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita", (ssh-askpass:9838): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita", Identity added: /home/bgmilne/.ssh/id_rsa (/home/bgmilne/.ssh/id_rsa) Identity added: /home/bgmilne/.ssh/id_dsa (/home/bgmilne/.ssh/id_dsa) [bgmilne@localhost ~]$ readlink -f /usr/libexec/openssh/ssh-askpass /usr/libexec/openssh/gnome-ssh-askpass [bgmilne@localhost ~]$ Version-Release number of selected component (if applicable): Current cauldron, see srpm How reproducible: Always Steps to Reproduce: 1. ssh-keygen 2. sudo rurpmi keychain openssh-askpass-qt5 3. keychain 4. ssh-add </dev/null #error 5. ln -s $(rpm -ql openssh-askpass-qt5) /usr/libexec/openssh/ssh-askpass 6. ssh-add </dev/null # qt5 passphrase dialog 7. sudo rurpmi openssh-askpass-gnome 8. ssh-add </dev/null # prompted for passphrase with Gnome dialog without manual symlink
Assignee: bugsquad => mageia
Actually there are more that Do Not use /usr/libexec/openssh than that do. openssh-askpass-qt5, lxqt-openssh-askpass, gaskpass, and ksshaskpass all use /usr/bin/* but ksshaskpass does work with alternatives. If you want a qt interface choose openssh-askpass-qt4. Personally I use openssh-askpass which provides /usr/libexec/openssh/x11-ssh-askpass [root@SuperSize x86_64]# alternatives --config ssh-askpass There are 4 programs which provide 'ssh-askpass'. Selection Command ----------------------------------------------- 1 /usr/lib64/seahorse/seahorse-ssh-askpass + 2 /usr/libexec/openssh/x11-ssh-askpass 3 /usr/libexec/openssh/gnome-ssh-askpass * 4 /usr/bin/ksshaskpass
CC: (none) => cae
BTW., the -qt5 package provides ssh-askpass. Surely, any package with this provides should have working alternatives (and the reverse)? Yes, I noted some others to look at (e.g. lxqt-openssh-askpass etc.). I was pleasantly surprised by ksshaskpass (although it could have some more features), maybe at some point we should also try and install it by default on KDE?
Most of them I have only a rudimentary familiarity. I boot all my systems to init 3. Login as user and ssh password is required and entered, and I need only have openssh-askpass installed. BTW, if autogen.sh is of the 'boilerplate' design and imparts nothing "special" the same no-warning outcome would be provided by instead using autoreconf -vfi
The package openssh-askpass-qt5-2.0.3-1.mga6 does not have any scripts, which is why it does not add itself as an alternative. The -qt4 variant does have a post and postun scripts, see http://svnweb.mageia.org/packages/updates/6/openssh-askpass-qt4/current/SPECS/openssh-askpass-qt4.spec?view=markup#l37 So I suppose equivalent %post and %postun should be added to the openssh-askpass.spec (which is the one creating the openssh-askpass-qt5 package). http://svnweb.mageia.org/packages/updates/6/openssh-askpass/current/SPECS/openssh-askpass.spec?view=markup Also, the executable in openssh-askpass-qt5 is named qt4-ssh-askpass, and is located in /usr/bin. The name is clearly wrong, it should be qt5-ssh-askpass (but ldd tells me it is linked to the qt5 libs, so the building was correct, only the install part is wrong). And I suppose it should be located in /usr/libexec/openssh/ like other askpass programs, but maybe that part is intentional?
CC: (none) => r.h.michel+mageia
Version: Cauldron => 6
This message is a reminder that Mageia 6 is end of life. Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as OLD (EOL). Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 6's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot be able to fix it before Mageia 6 was end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLDCC: (none) => ouaurelien