Hi,
I use evolution on openSUSE Tumbleweed with KDE. When I save attachments Evolution uses the gtk file picker. When I save a mail as file or import something it uses the kde file picker.
Is this a bug or do I miss something?
Best regards
Kay
Hi,
the portals should be used only if you run a Flatpak version (basically
when you run a version which requires the portals), otherwise it’s only
a common open/save dialog, which knows nothing about the portals, at
least as far as Evolution is concerned (it’s up to the gtk3 internals).
The attachment save/load chooses either a “native” dialog (which might
be the KDE dialog for you), or the gtk3 dialog, depending whether it’s
a Flatpak or not. It’s because when compiled with gnome-autoar you get
some additional options, which cannot be added to the “native” dialog.
Saving to a file uses the “native” dialog unconditionally, similar to
some other parts in the code.
I agree it can be confusing to see the two different file dialogs,
though I won’t call it a bug as such, it’s just that Evolution tries to
offer more options in some cases, which would be unavailable otherwise.
Bye,
Milan
Thanks for your explanations. It is really a little bit confusion, same action (save a file), different behavior. Maybe I will try it with the flatpak version.
I tried the flatpak version. Every file dialogs using the kde file picker. The problem with the flatpak version is: I can not log in to my google accounts. The oauth2 doesn’t work. 
That “doesn’t work” means precisely what, please?
I am able to use a Google account in a Flatpak version of Evolution.
Google server added some limitations semi-recently, though the last
time I tried it did work, I could log in the account in the OAuth2
wizard shown in an embedded browser, where I just confirmed I trust
Evolution to not do any harm to my account data and it was it.
Nonetheless, the Flatpak version has many limitations in compare to the
packaged version, thus whenever possible, I suggest to prefer the non-
Flatpak version.
I think, it is a problem with the flatpak sandbox. Evolution seams to need a flatpak browser. I tested it with Vivaldi as flatpak. I set Vivaldi (flatpak) as default browser in the KDE-settings. The oauth2-mechanism works. If I use my standard-browser (non-flatpak) oauth2 didn’t work (because of the sandbox?). After entering the password in the build-in-webview the side loads forever.
My problem is, I can not use a flatpak-Browser because than, plugins like keepassxc don’t work. I have to device: Using Evolution as flatpak with a flatpak-browser without password-manager or use the normal evolution package from my distro with this little file picker problem. I have decided for the last.
I think, it is a problem with the flatpak sandbox.
I agree with you, the Flatpak sandbox causes many problems. Some
bigger, some smaller. Dealing with external browser executed from the
Evolution Flatpak sandbox is a nightmare, it does not work well with
the Flatpak, I’m sorry. No idea why sometimes the OAuth2 wizard (looks
like) frozen in the builtin window.
Using Evolution as flatpak with a flatpak-browser without
password-manager or use the normal evolution package from my
distro with this little file picker problem. I have decided
for the last.
I agree here with you too, the later is a better option. it can be
annoying, but it at least works in other parts much better than the
Flatpak version.
This topic was automatically closed 45 days after the last reply. New replies are no longer allowed.