[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: no mouse cursor unless manual X config 'Option "HWCursor" "off"' in Jessie



On Sat 05 Dec 2015 at 23:38:32 +0000, Lisi Reisz wrote:

> On Saturday 05 December 2015 23:25:20 Brian wrote:
> > On Sat 05 Dec 2015 at 17:56:14 -0500, Felix Miata wrote:
> > > Brian composed on 2015-12-05 20:52 (UTC):
> > > > On Sat 05 Dec 2015 at 12:38:38 -0500, Felix Miata wrote:
> > > >> Fresh Jessie installation about a week ago, TDE added last night.
> > > >> Normally using startx rather than any DM, but DM when used, has no
> > > >> pointer either.. Mouse could be used to select and click, but no way
> > > >> to tell where pointer was until it hovered something that changes on
> > > >> hover. Same problem in IceWM. I have other machines that use this same
> > > >> Intel 945G/ICH7 chipset, so it's hard to imagine why this is needed
> > > >> here but not elsewhere, nor in openSUSE 13.1/KDE4 nor openSUSE
> > > >> Leap/IceWM nor Mageia 5/KDE4 on same machine. I've never before on any
> > > >> post-XFree86 installation needed to turn off HWCursor. Naturally as
> > > >> the problem is same in IceWM, this must be a Jessie problem, not a TDE
> > > >> or hardware problem. Any ideas on how to eliminate need for disabling
> > > >> HWCursor?
> > > >
> > > > Did the pointer work before you added TDE
> > >
> > > I don't remember whether I tried IceWM before installing TDE. I rarely
> > > use anything other than [K,T]DE except to determine whether a problem
> > > belongs to Xorg or [K,T]DE.
> >
> > You could start from scratch and refresh your memory.
> >
> > > > (whatever that is)?
> > >
> > > It's what KDE could have been:
> > > https://wiki.trinitydesktop.org/Trinity_Desktop_Environment
> >
> > Ah; it's non-Debian. All the more reason to re-install Jessie and
> > investigate.
> 
> We'd love to be Debian.  We are too short of money (for lots of 
> infrastructure) and developers quite to get there.

There is a RFP.

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742958

Not that is of any help to the OP.


Reply to: