[Pkg-gajim-maintainers] Bug#874791: gajim: Crash on startup with python-gnupg >= 0.4 without gpg1

[Antonio Ospite]

Package: gajim
Version: 0.16.8-4
Followup-For: Bug #874791

Dear Maintainer,

I am afraid the fix in 0.16.8-4 is not complete.

Now gajim sets GPG_BINARY to '/usr/bin/gpg2', but this binary is only
provided by the "gnupg2" package which is a transitional package and it
may not be always installed.

For example, on my system I end up with this error:

------------------------------------------------------------------------------
$ gajim
14/09/2017 08:53:34 (E) gajim.c.gnupg Unable to run gpg - it may not be available.
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/gnupg.py", line 755, in __init__
    p = self._open_subprocess(["--version"])
  File "/usr/lib/python2.7/dist-packages/gnupg.py", line 831, in _open_subprocess
    startupinfo=si)
  File "/usr/lib/python2.7/subprocess.py", line 390, in __init__
    errread, errwrite)
  File "/usr/lib/python2.7/subprocess.py", line 1025, in _execute_child
    raise child_exception
OSError: [Errno 2] File o directory non esistente
Traceback (most recent call last):
  File "gajim.py", line 512, in <module>
    interface = Interface()
  File "/usr/share/gajim/src/gui_interface.py", line 2926, in __init__
    gajim.connections[account] = Connection(account)
  File "/usr/share/gajim/src/common/connection.py", line 785, in __init__
    CommonConnection.__init__(self, name)
  File "/usr/share/gajim/src/common/connection.py", line 150, in __init__
    self.gpg = gpg.GnuPG()
  File "/usr/share/gajim/src/common/gpg.py", line 37, in __init__
    gnupg.GPG.__init__(self, gpgbinary=gajim.GPG_BINARY, use_agent=use_agent)
  File "/usr/lib/python2.7/dist-packages/gnupg.py", line 759, in __init__
    raise OSError(msg)
OSError: Unable to run gpg - it may not be available.
------------------------------------------------------------------------------

A workaround is to install the gnupg2 package (if this is your preferred
solution then gajim should depend on the gnupg2 package), but I am not
sure this is the right solution, maybe setting GPG_BINARY = 'gpg' is
better? The original reporter of this bug was suggesting this too.

IIUC the versioned dependency on python-gnupg (>= 0.4.1) should assure
that the installed gnupg package (as an indirect dependency) is indeed
version 2.x and that the 'gpg' binary is indeed gpg2.

Ideally python-gnupg could make this clearer adding a versioned
dependency on gnupg (>= 2) but it's not a big deal.

Thanks,
   Antonio

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (900, 'unstable'), (500, 'unstable-debug')
Architecture: amd64 (x86_64)

Kernel: Linux 4.12.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8), LANGUAGE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gajim depends on:
ii  dnsutils        1:9.10.3.dfsg.P4-12.6
ii  python          2.7.13-2
ii  python-gtk2     2.24.0-5.1
ii  python-nbxmpp   0.5.4-1
ii  python-openssl  16.2.0-1
ii  python-pyasn1   0.1.9-2

Versions of packages gajim recommends:
ii  alsa-utils                             1.1.3-1
ii  ca-certificates                        20170717
ii  dbus                                   1.11.16+really1.10.22-1
ii  gnome-flashback [notification-daemon]  3.24.0-2
ii  gnome-shell [notification-daemon]      3.22.3-3
ii  notification-daemon                    3.20.0-1+b1
ii  pulseaudio-utils                       11.0-2
ii  python-crypto                          2.6.1-7+b1
ii  python-dbus                            1.2.4-1+b2
ii  python-gnupg                           0.4.1-1
ii  sox                                    14.4.1-5+b2

Versions of packages gajim suggests:
ii  aspell-it [aspell-dictionary]  2.4-20070901-0-2.1
ii  avahi-daemon                   0.6.32-2
ii  dvipng                         1.14-2+b3
ii  gnome-keyring                  3.20.1-1
pn  gstreamer0.10-plugins-ugly     <none>
pn  kwalletcli                     <none>
ii  libgtkspell0                   2.0.16-1.1
ii  libxss1                        1:1.2.2-1+b2
pn  nautilus-sendto                <none>
pn  network-manager                <none>
pn  python-avahi                   <none>
ii  python-gconf                   2.28.1+dfsg-1.2
ii  python-gnome2                  2.28.1+dfsg-1.2
ii  python-gnomekeyring            2.32.0+dfsg-4
pn  python-gupnp-igd               <none>
pn  python-kerberos                <none>
ii  python-pycurl                  7.43.0-2+b1
ii  texlive-latex-base             2017.20170818-1

-- no debconf information
-- 
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?