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:
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
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:
GNOME_KEYRING_CONTROL=/run/user/1000/keyring SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
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..
2) When said password prompt comes up, I cannot raise or switch the terminal window.
This one is not a bug, see #1895 and use --modal-windows=no or use one application per xpra session only.
Replying to Antoine Martin:
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:
GNOME_KEYRING_CONTROL=/run/user/1000/keyring SSH_AUTH_SOCK=/run/user/1000/keyring/sshMaybe 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?
xpra start --attach --start=gnome-keyring-daemon --start='env GTK_MODULES="${GTK_MODULES//:unity-gtk-module/}" flatpak run org.gnome.Evolution' --modal-windows=no works for me.
I mean, I still need to unlock the gnome-keyring (maybe I need to explicitly set the env variables you showed?) but I'll definitely call it working.
The list of applications that need to be started to get a fully functional session is ever changing..
I am absolutely fine you doing nothing about it.
Perhaps there could be different "levels" of starting stuff? One that's plain, the current one you have now (I'm assuming only dbus?), and the next one that contains gnome-keyring-daemon?
Replying to Antoine Martin:
2) When said password prompt comes up, I cannot raise or switch the terminal window.
This one is not a bug, see #1895 and use
--modal-windows=noor use one application per xpra session only.
I did add it to the command line while testing; however, I don't know if it's working as expected - the gnome-keyring-daemon "Please unlock me" prompt does not appear to be modal.
I'll keep it in mind for future testing though
btw:
From remote start, gnome-terminal seems to start in different CWD all the time.
Local start seems to "inherit" CWD
Are invocations "sanitized"?
What invocation?
Is local invocation "equivalent" to what I would get if I did it remotely?
I'm not sure I understand the question. Is it related to this ticket?
From remote start, gnome-terminal seems to start in different CWD all the time.
It depends what type of remote start you are using.
Unless you change the chdir option, the server starts does not change the CWD, so this will be set by the caller. (ie: for ssh start, whatever sshd + shell are using)
s/invoke/start a new server instance e.g. gnome-terminal/g
I'm not sure I understand the question. Is it related to this ticket?
Not strictly, no. While testing this, my cwd kept moving around every time I started a new instance (which made commands with relative paths complicated)
Please open a new ticket for questions unrelated to 'Evolution-flatpak'.
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/2606