Bug 1981815

Summary: Remmina 1.4.19 is unusable , problem fixed upstream, please update to 1.4.20
Product: [Fedora] Fedora Reporter: Antenore Gatta <antenore>
Component: remminaAssignee: Pavel Alexeev <pahan>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: negativo17, pahan
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: remmina-1.4.20-1.fc33 remmina-1.4.20-1.fc34 remmina-1.4.20-1.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-07-30 01:00:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Antenore Gatta 2021-07-13 13:31:06 UTC
Description of problem:

Preferences cannot be saved and there are other bugs been fixed with 1.4.20

Pay attention as in this release we have removed the ST, XDMCP and NX plugins, so you must not package these plugins anymore.

libappindicator or ayatana is now a requirement without it Remmina cannot be built and installed


This would solve 1660515 as NX is not supported anymore

Comment 1 Simone Caronni 2021-07-21 09:35:00 UTC
Hi Antenore, thanks for the heads up!

Building it now. Appindicator has been a prerequisite in the package for a long time so it should not be an issue. I've removed and obsoleted the plugins accordingly.

Comment 2 Fedora Update System 2021-07-21 09:43:03 UTC
FEDORA-2021-2b6a28a75a has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-2b6a28a75a

Comment 3 Fedora Update System 2021-07-21 09:43:21 UTC
FEDORA-EPEL-2021-07bf174fd3 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-07bf174fd3

Comment 4 Fedora Update System 2021-07-21 09:43:38 UTC
FEDORA-2021-e43bf82f83 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-e43bf82f83

Comment 5 Fedora Update System 2021-07-22 01:10:34 UTC
FEDORA-2021-e43bf82f83 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-e43bf82f83`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-e43bf82f83

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2021-07-22 01:44:39 UTC
FEDORA-EPEL-2021-07bf174fd3 has been pushed to the Fedora EPEL 7 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-07bf174fd3

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2021-07-22 01:58:11 UTC
FEDORA-2021-2b6a28a75a has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-2b6a28a75a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-2b6a28a75a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2021-07-30 01:00:25 UTC
FEDORA-2021-2b6a28a75a has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2021-07-30 01:01:21 UTC
FEDORA-2021-e43bf82f83 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2021-11-09 01:51:58 UTC
FEDORA-EPEL-2021-07bf174fd3 has been pushed to the Fedora EPEL 7 stable repository.
If problem still persists, please make note of it in this bug report.