Bug 104091 - Mouse cursor hangs
Summary: Mouse cursor hangs
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Beta 1
Hardware: All All
: P5 - None : Major
Target Milestone: ---
Assignee: Hubert Mantel
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-11 12:06 UTC by Sven Lüppken
Modified: 2005-08-12 16:59 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sven Lüppken 2005-08-11 12:06:38 UTC
Installation of SUSE Linux 1.0 beta 1 went well and KDE started up. But it is 
not possible to move the mouse cursor in a smooth way, but it's rather 
difficult to explain. Every second (approximately) the mouse cursor just stops 
for a short time and then moves again. In German I'd call this "haken". When 
switching to a console via CTRL + ALT + F1 and entering something the same 
happens. Every second the console "hangs" and continues working again. This 
happens on a Toshiba Satellite A50 notebook, Pentium M 1.6 Ghz and 512 MB RAM. 
I hope that helps but don't hesitate to ask for more information.

Sven
Comment 1 Hubert Mantel 2005-08-12 10:05:20 UTC
Do you see the kernel flooding the syslog with messages? If yes, please mark
this one as duplicate of 104020. This is probably related to the ACPI_DEBUG
settings which will be disabled soon.
Comment 2 Sven Lüppken 2005-08-12 11:04:36 UTC
I don't know exactly what you meant with "the syslog" but I looked at every 
logfile in /var/log and none of them seems to be flooded.
Comment 3 Sven Lüppken 2005-08-12 16:59:59 UTC
I installed a new "kernel-of-the-day" and that seems to have fixed this bug.  
I'm now running  
  
Linux linux 2.6.13-rc6-git3-20050811165126-default #1 Thu Aug 11 16:51:26 UTC  
2005 i686 i686 i386 GNU/Linux  
  
and the mouse doesn't hang anymore. The system seems to be more responsive and  
much faster so I guess it's ok to close this bug. 
 
Thanks for your help! 
Sven