OK, this is wierd. Everything has been working fine on my system until about 15 minutes ago. I rebooted to Windows for a few minutes to run an app... booted back to Linux, and now my mouse pointer is invisible. The pointer is still there and mouse events are being recognized (I can see buttons raise etc as the invisible pointer moves across them) but the pointer is not being drawn. I've tried a few things like poking around in the mouse config file, and running Sax2 (just in case). Everything looks OK though. I have the same config file that's been working since day 1 with SuSE8.2... Nothing's changed that I know of... Anyone have an idea - or can point me at the obvious - what can I do to restore my mouse pointer? C.
On Monday 15 September 2003 16:21, Clayton Cornell wrote:
OK, this is wierd. Everything has been working fine on my system until about 15 minutes ago. I rebooted to Windows for a few minutes to run an app... booted back to Linux, and now my mouse pointer is invisible. The pointer is still there and mouse events are being recognized (I can see buttons raise etc as the invisible pointer moves across them) but the pointer is not being drawn. I've tried a few things like poking around in the mouse config file, and running Sax2 (just in case). Everything looks OK though. I have the same config file that's been working since day 1 with SuSE8.2... Nothing's changed that I know of... Anyone have an idea - or can point me at the obvious - what can I do to restore my mouse pointer?
C.
OK... here's what I've done... and it seemed to fix things. Simply switched to tty2, did an init 3 and then an init 5 and the pointer was back. Strange that this worked but a reboot dodn't do the same. C.
The 03.09.15 at 18:42, Clayton Cornell wrote:
OK... here's what I've done... and it seemed to fix things. Simply switched to tty2, did an init 3 and then an init 5 and the pointer was back. Strange that this worked but a reboot dodn't do the same.
I assume you did a reboot, but not a power-off-on cycle. Once I booted from Linux to windows, and this would not start. I even reinstalled windows from a CD image, to no use. Finally, I power cycled the modem, and windows booted ok. The external modem was in a mode that did not allow windows to boot up. So... Power cycle! Or at least, use the reset button. By the way: that modem failure occurred also in Linux once or twice. There, it causes the init program to go up in CPU usage to be more than 80%. -- Cheers, Carlos Robinson
participants (2)
-
Carlos E. R. -
Clayton Cornell