After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 646108 - Cursor setting is broken
Cursor setting is broken
Status: RESOLVED FIXED
Product: gnome-shell
Classification: Core
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2011-03-29 14:44 UTC by Dan Winship
Modified: 2011-07-05 16:26 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
shell_global_set_cursor: Fix this (4.80 KB, patch)
2011-03-29 14:44 UTC, Dan Winship 		none Details | Review

Description Dan Winship 2011-03-29 14:44:06 UTC 
The gtk3 XI2 merge broke support for setting the cursor on foreign windows
(or maybe just "foreign windows that don't use XI2"?). While this may be
just a bug, the fix in gtk is probably much bigger that the fix in
gnome-shell.
Comment 1 Dan Winship 2011-03-29 14:44:08 UTC 
Created attachment 184590 [details] [review]
shell_global_set_cursor: Fix this

In gtk3 (at least for the moment), gdk_window_set_cursor() no longer
works on foreign windows, so we can't use it to set the cursor on the
stage. Work around this by using XDefineCursor directly (but still
using GdkCursor to do the complicated loading/theming stuff).
Comment 2 Jonathan Strander 2011-03-29 23:43:36 UTC 
Glad(???) to know I was right. This patch appears to fix all instances where the cursor type was the incorrect default.
Comment 3 Owen Taylor 2011-04-05 22:17:00 UTC 
My understanding is that the XI2 cursor setting problem was a bug somewhere between GTK and XI2, and has been resolved there. Certainly things work correctly here with GTK+ 3.0.6 and recent Fedora 15 Xserver/libs. If there was a regression with versions *after* I have running here, I think we'd just fix it in the correct placing. Resolving NOTGNOME. (I was, if I recall, reproducing the bug here early, so I suspect it's been fixed.)
Comment 4 Owen Taylor 2011-05-03 19:44:56 UTC 
Turns out this wasn't reliably fixed, it only worked if GDK had processed a pointer event before - see bug 649313. (So probably using a window menu made it work.)
Comment 5 Matthias Clasen 2011-06-17 21:43:32 UTC 
Fixed in GDK now, I hope.