Bug#253280: gtk2-engines-industrial: problems with new xcursors default

[ROBERTOJIMENOCA]

Josselin Mouette wrote=3A
=3E Le mar 08/06/2004 =E0 12=3A37=2C ROBERTOJIMENOCA a =E9crit =3A
=3E =3E Package=3A gtk2-engines-industrial
=3E =3E Version=3A 0=2E2=2E36-2
=3E =3E Severity=3A minor
=3E =3E =

=3E =3E The default of using the gtk2-engines-industrial xcursors in X ca=
uses
=3E =3E problems in graphic cards with bad hardware mouse pointer support=
=2E
=3E =3E =

=3E =3E I have a S3 Inc=2E VT8636A TwisterK and I see two cursors the X
=3E =3E default one and the gtk2-engines-industrial one=2C but only the
=3E =3E gtk2-engines-industrial one moves=2E
=3E =3E =

=3E =3E It=27s a bad idea to integrate a mouse theme with a metacity/gtk =
theme
=3E =3E because of this problem=2E
=3E =

=3E There are 2 issues here=3A the bug in the X server=2C and the fact th=
at
=3E gtk2-engines-industrial could be split out in a package containing th=
e
=3E GTK+/GNOME data and a package containing the X cursor theme=2E

Thanks for splitting it=2E I should have done that in the first place but=
 I
wanted to show the bug=2E

=3E Note that you can probably work around the first by disabling the
=3E hardware cursor feature=2C

Why would someone that doesn=27t care about pretty cursor themes would
like to disable the hardware cursor feature=3F
I don=27t like hardware cursor disabled because that makes the cursor
blink when something changes in the background (indeed=2C that=27s why
hardware cursor was invented)

=3E and that you can also disable this cursor theme
=3E by using update-alternatives --config x-cursor-theme=2E

Should at least this cursor theme not be set by default=3F