Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Re: Mouse cursor becomes invisible
20 views
Skip to first unread message
Loki Harfagr
Oct 4, 2012, 12:43:02 PM10/4/12
to
Thu, 04 Oct 2012 13:31:35 +0200, joop g clickety-clicked :
> Hello, *
>
> I have installed Slack 14. Had my problems with kmail, and kalarm, but
> could solve them... Occasionally, however, my mouse cursor under KDE
> "vanishes". AFAICT, it is still there, in the sense that I can move it
> over the screen, and see buttons light up if I pass them, but the arrow
> is gone. Logging out of KDE, and back in, does not help, so I have to
> reboot.
>
> Anyone here who can suggest a more efficient recovery method?
About the recovery I have no idea but if if I had this
kind of bug I'd try a few quick points:
- xpost to comp.windows.x.kde (FU2 setup)
- turn off any desktop effect (and if stable then enable them back
one by one until the culprit rings)
- create a brand new user, set it up to use KDE then use this user
and see if the bugs is off (hence pointing to your ~/.kde* dirs)
- switch your WM to fluxbox or xfce (at least for testing the mouse
but beware that reason will out and you'll never switch back to kde ;-)
some other tests are possible(*) but these are plain easy and should
suffice :-)
(*) as cloning your user dir to an installation using the same KDE and
libs on another distro (which would identify the bug as strictly
slackware or not)
> Hello, *
>
> I have installed Slack 14. Had my problems with kmail, and kalarm, but
> could solve them... Occasionally, however, my mouse cursor under KDE
> "vanishes". AFAICT, it is still there, in the sense that I can move it
> over the screen, and see buttons light up if I pass them, but the arrow
> is gone. Logging out of KDE, and back in, does not help, so I have to
> reboot.
>
> Anyone here who can suggest a more efficient recovery method?
About the recovery I have no idea but if if I had this
kind of bug I'd try a few quick points:
- xpost to comp.windows.x.kde (FU2 setup)
- turn off any desktop effect (and if stable then enable them back
one by one until the culprit rings)
- create a brand new user, set it up to use KDE then use this user
and see if the bugs is off (hence pointing to your ~/.kde* dirs)
- switch your WM to fluxbox or xfce (at least for testing the mouse
but beware that reason will out and you'll never switch back to kde ;-)
some other tests are possible(*) but these are plain easy and should
suffice :-)
(*) as cloning your user dir to an installation using the same KDE and
libs on another distro (which would identify the bug as strictly
slackware or not)
Geoff Clements
Oct 8, 2012, 4:13:38 AM10/8/12
to
As a further suggestion I would try restarting your X server and see if that cures the problem. This is not a suggested work-around, rather it's all part of the data collection for a possible bug report.
And as for "reason" and not going back to KDE, well feel free to have as many desktop environments on your PC as you want, you don't need to stick with just one!
--
Geoff
And as for "reason" and not going back to KDE, well feel free to have as many desktop environments on your PC as you want, you don't need to stick with just one!
--
Geoff
0 new messages