lubuntu 20.04 daily: qtpass reports "GnuPG not found"

[Chris Guiver]

Currently I'm convinced this has been reported before, but I cannot find it.

Lubuntu 20.04 daily QA-test, running through all menu options.

Assessories -> QtPass causes the dialog

"Please install GnuPG on your system. Install gpg using your .."

However package appears to be installed

lubuntu@lubuntu:~$ apt-cache policy gnupg
gnupg:
  Installed: 2.2.17-3ubuntu1
  Candidate: 2.2.17-3ubuntu1
  Version table:
 *** 2.2.17-3ubuntu1 500
        500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
        100 /var/lib/dpkg/status

Expected Results are no error message.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: qtpass 1.3.2-1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CasperVersion: 1.439
CurrentDesktop: LXQt
Date: Tue Feb 25 09:59:08 2020
LiveMediaBuild: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200224)
SourcePackage: qtpass
UpgradeStatus: No upgrade log present (probably fresh install)

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1864631

[Hans Joachim Desserud (hjd)]

> Currently I'm convinced this has been reported before, but I cannot find it.

Looks similar to bug 1829693 which was reported (and presumably fixed) a while back.

[Chris Guiver (guiverc)]

I had a re-occurance of this issue today and, yeah the 1829693 is what I found first in searches..

A `dpkg -l|grep gnupg2` (gnupg2 is mentioned in 1829693 report as workaround) shows NO RESULTS, however installed are

gnupg, gnupg-utils & gnupg-l10n

[Leó Kolbeinsson (leok)]

I can confirm this - also occurred in test today on my Acer Aspire E3-111

[Matthew Miller (matt-dwg05)]

I can replicate this and the fix for bug 1829693 might be slightly different as I found in settingsconstants.cpp on line 36:

const QString SettingsConstants::gpgExecutable = "gpgExecutable";

Changing the value to read anything other than gpgExecutable allows qtpass to start without any issues on 20.04. Not exactly sure why this would be, as I can set it to "foo" or "gpg2Executable", either way it works. Setting SettingsConstants::gpgExecutable to "gpgExecutable" causes the following line 288 from qtpasssettings.cpp to show a blank path to gpg2 in Lubuntu 20.04:

QString gpgExecutable =
      QtPassSettings::getGpgExecutable(Util::findBinaryInPath("gpg2"));

[Matthew Miller (matt-dwg05)]

There is no symlink called gpg2 on a stock system until the package gnupg2 is installed. When I ran the change in my previous post, I had gnupg2 installed, this is not the case on a fresh install of lubuntu. However, qtpasssettings.cpp could check for the binary gpg if it cannot find gpg2 and qtpass will start successfully without gnupg2 installed (around line 288 in qtpasssettings.cpp:

  QString gpgExecutable =
      QtPassSettings::getGpgExecutable(Util::findBinaryInPath("gpg2"));
  if(!QFile(gpgExecutable).exists()){
    gpgExecutable =
      QtPassSettings::getGpgExecutable(Util::findBinaryInPath("gpg"));
  }

This mimics a similar check in configdialog.cpp.

[Philip Rinn (rinni)]

I commented on the upstream bug report, let's hope it get's fixed: https://github.com/IJHack/QtPass/issues/433

Workarounds from https://bugs.launchpad.net/ubuntu/+source/qtpass/+bug/1829693 should still work.

[Launchpad Janitor (janitor)]

This bug was fixed in the package qtpass - 1.3.2-2

---------------
qtpass (1.3.2-2) unstable; urgency=medium

  * Fix detection of gnupg (closes: LP: #1864631)
  * Depend on gnupg and move pass to Recommends
  * Bump Standards-Version to 4.5.0 (no changes necessary)
  * Bump debhelper compat level to 13 (no changes necessary)

 -- Philip Rinn <email address hidden> Tue, 12 May 2020 16:38:14 +0200

[Chris Guiver (guiverc)]

Lubuntu 20.04 QA-test (live)
Look for this issue but error has gone; Qtpass opened without errors
http://iso.qa.ubuntu.com/qatracker/milestones/413/builds/213002/testcases/1303/results/