BAD stuff happens when gpg is uninstalled
When GPG is uninstalled, really bad stuff happens when connecting to an account for which a key is configured. The 'connecting' icon for the account keeps moving. Accounts which started to connect before the gpg account are seemingly getting connected, even though nothing is printed on standard output, (with -v). Other accounts are not connected to.
When pressing Ctrl-Q on the roster, Gajim produces part of the missing standard output (but no xml stanzas), and this error is printed:
The program 'gajim.py' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 4919 error_code 3 request_code 4 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Quick workaround: create fake gpg. (Shell script containing "exit 1".)
How to reproduce: Configure a key, rename/remove/uninstall gpg, restart Gajim, log into account.
Also, when gpg is uninstalled, it is no longer possible to disable gpg, except maybe through ACE. (See #1210 (closed)).