Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#58018 - [remmina] Split package for plugin secret

Attached to Project: Community Packages
Opened by Muflone (muflone) - Thursday, 29 March 2018, 10:08 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 29 March 2018, 16:03 GMT
Task Type General Gripe
Category Packages
Status Assigned
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No



The current format of the remmina package contains both the main application and the optional plugin secret:

$ pacman -Ql remmina
remmina /usr/lib/remmina/plugins/

The issue with the secret plugin is that remmina behaves in different ways whether a secret exists.

If you have a secret library like gnome-keyring the passwords are saved into the GNOME Keyring.
If you have not a secret library the passwords are saved into the profile file.

Whether the connection profiles are shared among two environments some passwords are lost (moved from the profile file to the keyring when the connections are changed or added).

Splitting the package and then removing the optional secret plugin from the main package the user can choose to not install the secret plugin in order to keep the passwords saved into the profile.
At the actual state it's not possibile to isolate the optional secret plugin.

Additional info:
* remmina 1:1.2.0rcgit.27-1

Steps to reproduce:

1) install remmina
2) create a profile in an environment (ENV1) with a secret library (like GNOME), saving the passwords
3) use the same remmina profile in an environment (ENV2) without a secret library
4) for ENV2 the password are absent, as they are into the ENV1 keyring


1) install remmina
2) create a profile in an environment (ENV2) without a secret library, saving the passwords
3) change the same remmina profile in an environment (ENV1) with a secret library
4) the passwords are automatically moved from the profile file to the ENV1 keyring
5) ENV2 will lack the previously saved passwords

All the major others Linux distributions splitted the plugins in separated packages

This task depends upon

Comment by Doug Newgard (Scimmia) - Thursday, 29 March 2018, 16:01 GMT
This sounds like a problem with your local system setup being inconsistent, not a remmina problem.
Comment by Antenore Gatta (tmow) - Sunday, 28 July 2019, 15:42 GMT
Upsteam maintainer here, I agree, moreover we are releasing a new plugin for KDE wallet.
Users should have a choice. None of the plugins is obligatory except SSH.
Comment by Eli Schwartz (eschwartz) - Sunday, 28 July 2019, 23:21 GMT
It's fairly common practice with plugins to enable them to be configured as either on or off -- rather than requiring them to be enabled if they are installed. It seems like adding such configurability would be more effective in the long run.

For example, I'm curious how you'd provide a flatpak that didn't include the plugin at all, unless you installed a second flatpak that contained the plugin.
Comment by Antenore Gatta (tmow) - Monday, 29 July 2019, 13:20 GMT
Eli, yes, you are correct, my comment was more generic, but at the end in the flatpak and in the snap is what we do, we have one package with everything.
Plugins are used at runtime, the secret plugin is a bit a different word, but, we are adding an additional kde-wallet plugin and soon we will add an option to force the use of simple passwords in Remmina, so there's not reason to stress about this problem.

I let you decide whatever to close or not this (non)bug.