Description of problem: Using synergy on mga4 as server and synergy on cauldron as client won't work. So we should backport it for mga4 or release an update. Version-Release number of selected component (if applicable): 1.4.12 on mga4 and 1.4.15 on cauldron. How reproducible: Every time Steps to Reproduce: 1. Start mga4's synergy as server 2. Start cauldrons synergy as client 3. See that you can't use synergy Reproducible: Steps to Reproduce:
Assignee: bugsquad => jani.valimaa
Hardware: i586 => All
As we have backports media nowadays, I guess I'll push latest synergy to there.
Keywords: (none) => BackportSummary: Cauldrons synergy doesn't play nice with mga4's synergy => Backport request: synergy 1.4.16 for mga4
Assigning to QA team. RPMs: ====== synergy-1.4.16-2.mga4 synergy-gui-1.4.16-2.mga4 SRPM: ====== synergy-1.4.16-2.mga4
Assignee: jani.valimaa => qa-bugs
CC: (none) => remiDepends on: (none) => 12766
Adding feedback tag until there is a fix for bug 12766. It should maybe also be removed from backport_testing until that time. Adding sysadmin in CC.
CC: (none) => sysadmin-bugsWhiteboard: (none) => feedback
Assigning back to you for now Jani, sorry. We're unable to accept backports sadly until bug 12766 has been tackled. Please reassign when ready. Thanks The packages should probably be removed from backports_testing until such time. Sysadmin are in CC.
CC: (none) => qa-bugsAssignee: qa-bugs => jani.valimaaWhiteboard: feedback => (none)
I think this could probably be pushed as an update rather than a backport, as it's currently incompatible with mga5.
CC: (none) => eeeemail
Changing to a bug from a backport. Anybody upgrading the remote system will lose keyboard/mouse so this should be pushed through mga4 updates before mga5 release ideally.
Keywords: Backport => (none)Priority: Normal => HighComponent: Backports => Release (media or process)Summary: Backport request: synergy 1.4.16 for mga4 => Synergy in mga4 incompatible with mga5 so upgrades of remote system will lose keyboard/mouse
Component: Release (media or process) => RPM Packages
Depends on: 12766 => (none)
Blocks: (none) => 15013
Blocks: (none) => 14069
Blocks: 14069 => (none)
Priority: High => release_blocker
Ping. This bug will cause upgrade issues, and as such it should really be fixed before the mga5 release.
Jani has pushed an updated synergy build to Mageia 4 updates_testing. Perhaps Claire or Rémi or Sander could help with the advisory. synergy-1.5.0-1.mga4 synergy-gui-1.5.0-1.mga4 from synergy-1.5.0-1.mga4.src.rpm
CC: qa-bugs => jani.valimaaAssignee: jani.valimaa => qa-bugs
Priority: release_blocker => High
Severity: normal => major
Summary: Synergy in mga4 incompatible with mga5 so upgrades of remote system will lose keyboard/mouse => Synergy in Mageia 4 incompatible with Mageia 5 so upgrades of remote system will lose keyboard/mouse
-MGA4-32 on AcerD620 Xfce versus MGA5-64 on HP Probook 6555b KDE. No installation issues. Machines can ping each other with FQDN anf both have firewall switched off. Tried both machines as each others server-client but none connected: MGA4 as server gives at MGA5 client (using the FQDN) : failed to connect: connection refused while MGA5 as server gives at MGA4 client: failed to connect to server: server refused client with our name. The problem was that in both 4 and 5, when you use MCC-Security to switch off the firewall, it switches off only the shorewall service, but leaves the shorewall6 running. Once this one is stopped, both configurations seem to work.
CC: (none) => herman.viaeneWhiteboard: (none) => MGA4-32-OK
MGA4-64 on HP Probook 6555b KDE versus MGA5-32 on AcerD620 Xfce. No installation issues. Machines can ping each other with FQDN anf both have firewall switched off. Tried both machines as each others server-client, both configurations seem to work.
Whiteboard: MGA4-32-OK => MGA4-32-OK MGA4-64-OK
Advisory: ========= Updated synergy packages fix compatibility with Mageia 5 version synergy 1.4.12 in Mageia 4 is not compatible with the version provided in the upcoming Mageia 5 release. This incompatibility induces that upgrading a remote system using synergy from Mageia 4 to Mageia 5 would lose control of the keyboard and mouse. This update puts Mageia 4's synergy packages to the same version as their Mageia 5 counterparts, ensuring a safe upgrade path. References: - https://bugs.mageia.org/show_bug.cgi?id=12678
Keywords: (none) => validated_updateWhiteboard: MGA4-32-OK MGA4-64-OK => MGA4-32-OK MGA4-64-OK advisory
Advisory uploaded, validating. Please push to 4 core/updates.
An update for this issue has been pushed to Mageia Updates repository. http://advisories.mageia.org/MGAA-2015-0027.html
Status: NEW => RESOLVEDResolution: (none) => FIXED