On Thu, 2021-05-13 at 09:46 -0500, Daffy Duck via evolution-list wrote:
> I'm not sure what "first mail" you are referring to
Hi,
I meant my first mail in this thread, the lengthy one:
https://mail.gnome.org/archives/evolution-list/2021-May/msg00025.html
Hope it helps,
I'm not sure what "first mail" you are referring to, or what you are
referring to in your previous reply. This issue is new with the upgrade to
Fedora 34 and the newest evolution. My "first mail" on this is May 7th.
The dbus workaround from months ago does not work now.
On Thu, May 13, 2021 at
On Wed, 2021-05-12 at 18:25 -0500, Daffy Duck via evolution-list wrote:
> however, this no longer works.
Hi,
yes, I understood it from your first mail and I gave you some hints in
my previous reply.
Bye,
Milan
___
evolution-list
Yes, I had a thread about it before the upgrade and I had a solution:
#!/bin/bash
unset DBUS_SESSION_BUS_ADDRESS
WEBKIT_FORCE_SANDBOX=0 evolution &
##END OF FILE
however, this no longer works.
When I log in from x2go, it prompts me for gnome-keyring password. If
I enter it or hit cancel, the
On Fri, 2021-05-07 at 10:37 -0500, Daffy Duck via evolution-list wrote:
> But this doesn't seem to work anymore. I have to completely reboot
> the
> machine, it seems, to just get evolution working on the local machine
> once I log in once from x2go remotely.
Hi,
I've no idea how x2go
Hello,
I just upgraded to the new fedora 34, and now evolution is:
evolution-3.40.1-1.fc34.x86_64
If i log in remotely from x2go, it immediately prompts me for my gnome
keyring password.
If I put it in, or cancel, it doesn't matter, because when I try using
evolution on the local machine
