xpra icon
Bug tracker and wiki

Opened 5 months ago

Last modified 4 months ago

#2606 closed defect

Evolution-flatpak questions — at Version 1

Reported by: stdedos Owned by: stdedos
Priority: major Milestone: 4.0
Component: client Version: 3.0.x
Keywords: Cc:

Description (last modified by Antoine Martin)

Because Xenial-shipped Evolution is quite old, I decided to install the flatpak version of it as soon as I discovered it.

Only 4 commands to set it up

sudo apt-get install flatpak gnome-software-plugin-flatpak
flatpak --user remote-add --if-not-exists flathub https://flathub.org/repo/
flatpak install --user flathub org.gnome.Evolution
env GTK_MODULES="${GTK_MODULES//:unity-gtk-module/}" flatpak run org.gnome.Evolution
# ^^^ hides one of the numerous warnings

1) I have configured a mail account, and the password is stored in gnome-keyring. However, when I am opening it in an xpra session (concurrently with :0), it will always ask me for a password for said account.

It pairs that with an error message like: org.freedesktop.secrets: Timeout was reached

I am wondering:

  • If that makes any sense to you
  • If you would know what it means
  • If it's fixable
  • Or it is a "security" feature and works as-expected

2) When said password prompt comes up, I cannot raise or switch the terminal window.
There is only one alternative - minimize or remove everything else in front of it; and even then, sometimes, clicking it makes Evolution and Evolution-PasswordPrompt to come up. At that time, I definitely cannot interact the parent gnome-terminal by mouse (I haven't tried what happens if I start another sibling gnome-terminal)

[2] is maybe related to #2604

Change History (1)

comment:1 Changed 5 months ago by Antoine Martin

Description: modified (diff)
Owner: changed from Antoine Martin to stdedos

It pairs that with an error message like: org.freedesktop.secrets: Timeout was reached

From what I found: What applications provide org.freedesktop.secrets.service, you need to start gnome-keyring-daemon.
You may need to start it in such a way that its output is loaded into the current session, as on my system it prints out:


Maybe we should have a special --start-env-daemon= command line option to make it easier to do this? (we already do this for the dbus daemon automatically)

Does that work for you?

The list of applications that need to be started to get a fully functional session is ever changing..

Note: See TracTickets for help on using tickets.