4

I'm currently running Ubuntu 14.04 LTS (not in a VirtualBox) with Chrome, and I have a interesting issue. Currently there is a solution to a similar problem listed here and here, but my problem is just slightly different and none of the known fixes for the other problem are working.

My problem is that the mouse does not change when placed over things such as links where the mouse should turn into a pointing hand, or over text where there should be the I beam. Also, hover states and active states on website elements aren't being triggered either. However, if I'm currently scrolling or the mouse is held down, then everything works fine, but not while only moving the mouse.

I have tried:

  • Purge and reinstall of Chrome
  • Running Chrome with --touch-devices=123
  • Trying to recreate this error on another system (Without success)
  • Trying Opera (since it's also WebKit, which has the same issue)

NOTE: The other more widely seen bug has symptoms that aren't affecting me. For example, my scrolling and text selection is working completely fine.

Chrome Version 42.0.2311.90 (64-bit)

UA Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.90 Safari/537.36 FirePHP/4Chrome

1

2 Answers 2

2
+100

There are a couple of bug reports about this problem.

Issue 465660: Cursor functionality broken in Ubuntu 14.04 since 41 is perhaps the most promising. Its last entry says :

version 43 works fine, just install google-chrome-unstable

Issue 357347: Mouse cursor stopped turning into a pointer while hovering over links has several workarounds that may not pertain to your problem :

  • disable Chrome hardware acceleration
  • disabling Synergy server
  • this happens with Photoshop CC 2014 in the background (the window is open, just behind Chrome). Hiding Photoshop solves the issue.
2
  • This is the first entry I have seen about Synergy, which is the only difference between any of my other computers and this one. I will try this when I get to work tomorrow and check if Synergy is causing the problem. Apr 26, 2015 at 17:19
  • Yup, Synergy server was the problem here, that's too bad, but at least now I know where to start looking for workarounds and fixes. Thanks a ton! Apr 27, 2015 at 13:07
0

I did a little research and found some "nightly builds" on the Synergy website that may also be helpful to others.

I'm currently using:

Google Chrome v46.0.2490.86 (64-bit)
Ubuntu 14.04.3 (64-bit)
Gnome Session Flashback (compiz)

and now, Synergy 1.8.0-alpha-19835b6 on both machines.

I downloaded this "nightly build" from here and worked like a charm. No need to restart the browser or anything.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .