Hi all,
Just finished installing Tumbleweed with Gnome DE. Evolution (v3.56.1) was installed as email client, and I started to use it.
I noticed a very long delay for the email composer to appear, when trying to create new email or replying to.
I found old bug reports with similar problems, one in particular relating to xdg-desktop-portal-gnome… but with Gnome DE it makes sense to have this installed and I don’t want to mess up the whole system (I didn’t install any xdg-desktop portal myself, it’s part of the default Gnome install on Tumbleweed).
Is anyone experiencing the same or having any clues?
Thanks
I think the issue in Evolution is actually relating to keys and GPG, despite the fact I haven’t defined any keys to encrypt emails… this is is close to this bug, which relates to flatpak version but it looks very similar, and the problem disappears when unticking the “send own public key in outgoing emails” in Evolution’s preferences.
In addition, the “Passwords and keys” apps also hangs at startup, which means there is definitely an issue with keys… I still can’t find a solution at this stage.
In the linked bug report I see a gpg2 command:
gpg2 --verbose --no-secmem-warning --no-greeting --no-tty --batch --yes --export --export-options export-minimal,no-export-attributes "<myemail@provider.org>"
I would try to run this command replacing the email adress by your own one and see what that does.
Thank you for your suggestion!
I started with a simple gpg command… and he shows a problem straight away:
~> gpg --list-keys --with-colons
gpg: Note: database_open 134217901 waiting for lock (held by 5799) ...
gpg: Note: database_open 134217901 waiting for lock (held by 5799) ...
gpg: Note: database_open 134217901 waiting for lock (held by 5799) ...
gpg: Note: database_open 134217901 waiting for lock (held by 5799) ...
gpg: Note: database_open 134217901 waiting for lock (held by 5799) ...
gpg: DBG: kbx_client_data_cmd: finished command with error: Connection timed out
gpg: keydb_search_first failed: Connection timed out
This is pretty much the issue described in this bug report. Now trying to find a fix…
Is that not just a matter of finding out which process has PID 5799? I.e. what does ps 5799 return?
Well yes more or less… there wasn’t a live process with pid 5799 but there was an old gnuPG lock file relating to this dead process, preventing GnuPG to work properly. This weird situation is actually described in the aforementioned bug report, and even more weirdly, relates to the host name!
Basically in Tumbleweed, at least with default Gnome DE install, there is no static hostname defined, so the systemd-hostnamed service defines a transient hostname that by definition, can change. This actually doesn’t go well with GnuPG that creates public keys linked to the hostname, and can end up creating these lock files, locking itself out of function!
At the end, I just defined a static hostname for my computer (with hostnamectl), and deleted the old GnuPG public keys and lock files. Everything now works as it should.
Thank you @marel for your guidance - much appreciated.
+
1 Like
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.