Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
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!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
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#42732 - [synergy] Cursor change on hover in chrome stops working
Attached to Project:
Community Packages
Opened by Miller Larson (millerl) - Monday, 10 November 2014, 15:07 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 10 November 2014, 15:43 GMT
Opened by Miller Larson (millerl) - Monday, 10 November 2014, 15:07 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 10 November 2014, 15:43 GMT
|
DetailsDescription:
Cursor hover change is not working in chrome while synergy server is running. There is a patch from upstream synergy, and if included fixes this issue: Additional info: * package version(s) - 1.5.1 - 1.6.0 * Fixed in Synergy Beta 1.6.1 * config and/or log files etc. - Goolge Chrome with hardware acceleration enabled I've followed the steps in the upstream synergy bug, and left a comment for patching with Arch. This works to patch 1.5.1 and I just tested and works in 1.6.0 as well: https://github.com/synergy/synergy/issues/3749#issuecomment-58855823 Synergy bug: https://github.com/synergy/synergy/issues/3749 Chrome bug(s): https://code.google.com/p/chromium/issues/detail?id=386015 https://code.google.com/p/chromium/issues/detail?id=313427 Steps to reproduce: Use synergy 1.5.1 or 1.6.0 and use chrome with hardware acceleration enabled. |
This task depends upon
Closed by Doug Newgard (Scimmia)
Monday, 10 November 2014, 15:43 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#41727
Monday, 10 November 2014, 15:43 GMT
Reason for closing: Duplicate
Additional comments about closing:
Comment by Miller Larson (millerl) -
Monday, 10 November 2014, 15:28 GMT
Forgot to mention, disabling hardware acceleration in Chrome seems to work around this issue.