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#41727 - [synergy] Cursor icon not representing the correct state
Attached to Project:
Community Packages
Opened by Ace (0xACE) - Wednesday, 27 August 2014, 23:31 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Tuesday, 02 September 2014, 15:38 GMT
Opened by Ace (0xACE) - Wednesday, 27 August 2014, 23:31 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Tuesday, 02 September 2014, 15:38 GMT
|
DetailsDescription:
I just upgraded synergy (1.5.0-2 -> 1.5.1-1). Since then when I'm hovering over various objects such as text or links; the cursor doesn't change the icon. This is very confusing when you're hovering over a link in a browser and the cursor doesn't indicate that it's clickable. Additional info: In this case my pc is the server, and I start it with: "synergys --name server -d INFO", The problem appears even when no clients are connected. Downgrading back to 1.5.0-2 doesn't fix the problem... I'm guessing these 2 packages has changed since the last upgrade, not sure if it's relevant: libxkbcommon-x11 0.4.3-1 gcc-libs 4.9.1-1 Steps to reproduce: Just install latest synergy and the problem appears while "synergys" is running, and dissappears as soon as you close it. attaching log of the system upgrade that caused this... |
This task depends upon
Closed by Sven-Hendrik Haase (Svenstaro)
Tuesday, 02 September 2014, 15:38 GMT
Reason for closing: Won't fix
Additional comments about closing: See comments.
Tuesday, 02 September 2014, 15:38 GMT
Reason for closing: Won't fix
Additional comments about closing: See comments.
logs
http://synergy-project.org/spit/issues/details/3819/
Seems like its only chromium + synergy... but still the problem is the same.
So I guess chromium has to fix this upstream.
I believe you can close this issue.