It's an option that could be explicitly disabled or enabled via xorg.conf; it or another similar sort of option could be enabled by default and in effect even if you don't actually have a config file (most people don't have an actual xorg.conf at this point at this point--everything just gets autoprobed/auto configured every time, and that *normally* works but sometimes doesn't work right...). I *think* you can find the evidence in the *logfiles*.... -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
On March 25, 2016 2:56:23 PM EDT, Tyson Sawyer <ty...@j3.org> wrote: >Would HWCursor an option in /etc/X11? > >On Fri, Mar 25, 2016 at 2:37 PM, Joshua Judson Rosen ><roz...@hackerposse.com> wrote: >> Alternately, maybe a problem due to the use of "HWCursor" option in >Xorg? I >> somewhat doubt that's something that can actually mess w/ behaviour >other >> than rendering, but maybe? > >Is HWCursor an option in an /etc/X11 file? I don't seem to be using it. > >tyson@STOL:X11$ pwd >/etc/X11 >tyson@STOL:X11$ ls >app-defaults rgb.txt xkb Xresources >Xsession.options >default-display-manager X Xreset Xsession xsm >fonts xinit Xreset.d Xsession.d Xwrapper.config >tyson@STOL:X11$ grep -r HWCursor >tyson@STOL:X11$ > >I'm not as close to this stuff as I used to be. ...I don't see an >XF86Config or xorg.conf file there. > >-- >Tyson D Sawyer > >A strong conviction that something must be done is the parent >of many bad measures. - Daniel Webster
_______________________________________________ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/