Description of problem: On a X11 gnome-shell session, the mouse cursor can be moved without problems. On a gnome-wayland session, a machine previously affected by bug #1173801 experiences a flickering cursor whenever the mouse is moved around. It does not matter what kind of cursor is selected, and it happens over both X11 and wayland applications, and even on top of the bare desktop. Version-Release number of selected component (if applicable): xorg-x11-server-Xwayland-1.17.2-1.fc22.x86_64 kernel-core-4.0.5-300.fc22.x86_64 gnome-shell-3.16.2-1.fc22.x86_64 mutter-3.16.2-1.fc22.x86_64 How reproducible: Always Steps to Reproduce: 1. Start gnome-wayland session 2. Move cursor around 3. Actual results: Cursor rapidly appears and disappears when moved around Expected results: Cursor should not flicker as it is moved. Additional info:
On Wayland, the cursor is managed by the Wayland compositor, ie mutter in this case => moving to mutter.
Note that on the same hardware (assuming this is still the same Netbook with an Atom N270 as reported in bug 1173801), I do not witness flicking, but more like lags in pointer movements which may be simply due to the machine being quite underpowered by today standards. See also https://bugzilla.gnome.org/show_bug.cgi?id=749783 There's been a similar discussion around that topic on wayland-devel ML recently: http://lists.freedesktop.org/archives/wayland-devel/2015-June/022895.html
Results on three machines with updated packages. All machines were previously affected by bug 1173801. Day job workstation, x86_64, 4GB RAM, Intel graphics chipset. Cursor flickers. I opened the bug for this machine, not the Aspire One. Home workstation, x86_64, 4GB RAM, Intel graphics chipset. Cursor flickers. Acer Aspire One ZG5, i686, 1GB RAM, Intel graphics chipset. Cursor does NOT flicker. Of the three machines, the Acer Aspire One is the underpowered one, but does not have the flicker. The other two machines do. Any additional information I can provide for this?
I think I can reproduce that as well on the x61 (8086:2a02 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller). The cursor flickers, sometimes disappear or jump to some random place and may show corruption in the pointer image as well (like random pixels appearing for a fraction of second)
I experience similar cursor flicker and jumping on 8086:0152 (Intel(R) Celeron(R) CPU G1620 @ 2.70GHz). Right click on terminal window can cause that. Also, right click menu is appearing all over the screen, not on spot clicked on and on that spot some flickering with pixelated graphics occurs sometimes.
(In reply to Olivier Fourdan from comment #4) > The cursor flickers, sometimes disappear or jump to some random place and > may show corruption in the pointer image as well (like random pixels > appearing for a fraction of second) Probably stating the obvious, but if I disable hardware support in mutter, cursor flickering and corruption disappear so it could be a problem with the dri/drm driver in the kernel as well. (In reply to semiRocket from comment #5) > Also, right click menu is appearing all over the screen, not on spot > clicked on [...] The problem with popup menu being misplaced is another issue already addressed upstream (with fixes in mutter, gnome-terminal and gtk+)
(In reply to Olivier Fourdan from comment #6) > Probably stating the obvious, but if I disable hardware support in mutter, > cursor flickering and corruption disappear so it could be a problem with the > dri/drm driver in the kernel as well. Also, worth noting that Weston has disable hardware cursor: http://cgit.freedesktop.org/wayland/weston/commit/?id=685838 Yet re-enabling hardware cursor in Weston (either by reverting the patch or using the debug key Super-Shift-Space + C) does not cause the same flickering as in mutter/gnome-shell.
The flickering is caused by the update of the cursor, not updating the cursor (ie just moving it) shows no flickering afaict.
Filed bug upstream https://bugzilla.gnome.org/show_bug.cgi?id=751835
(In reply to Olivier Fourdan from comment #8) > The flickering is caused by the update of the cursor, not updating the > cursor (ie just moving it) shows no flickering afaict. That is not exactly what happens in my case. Now the bug is a little different. when moving the cursor over the wayland gnome-shell desktop, the cursor does not flicker. However, when moved over an application window, it flickers, regardless of the cursor shape or whether the cursor shape is updated. However, the flickering is worse if the application is updating the window at the same time.
(In reply to Alex Villacís Lasso from comment #10) > (In reply to Olivier Fourdan from comment #8) > > The flickering is caused by the update of the cursor, not updating the > > cursor (ie just moving it) shows no flickering afaict. > > That is not exactly what happens in my case. > > Now the bug is a little different. when moving the cursor over the wayland > gnome-shell desktop, the cursor does not flicker. However, when moved over > an application window, it flickers, regardless of the cursor shape or > whether the cursor shape is updated. However, the flickering is worse if the > application is updating the window at the same time. I reckon this is the same, because the cursor is updated at every move when on an application window (reproduced with gtk+ dunno about other apps/toolkits), even if it's not modified, thus causing the flickering.
By "not updating the cursor" in comment 8, I meant changing the code to make sure it remains the same whatsoever, ie a hack to help identify the problem.
Upgrade to Fedora 23 fixed this bug for me. As far as I know it still happens on Fedora 22.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.