![]() Registered Member ![]()
|
go to kde settings and switch all mouse settings to defaults
if this does not help you may have to delete a config file. wait for some1 to say which file |
![]() Administrator ![]()
|
Also, you may wish to see if you can reproduce under a new user, in case there is any configuration files that KDE causes to be loaded ( Synaptics configuration for instance )
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Registered Member ![]()
|
tried that, same behavior. the only config file that I know of whom is loaded is the hal fdi file, here is it:
tried that too, no affect, my only change in the mouse section was replacing the cursor theme. |
![]() Registered Member ![]()
|
correction, if I plug the usb mouse before the kde gui is up, then I get fluid cursor motion with the pad until I get to the splash screen.
if I don't plug the usb mouse, the movement is still sluggish even in logion before the splash |
![]() Administrator ![]()
|
In which case you need to check your X configuration. Your mouse pad is likely being misidenitified leading to the wrong driver being used or the driver being passed the wrong parameters. Your distribution will likely have more information on issues such as this.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Registered Member ![]()
|
tried with svn version of synaptics, no go, my current hal (cause I don't use xorg for inputs anymore) is minimal and looks like this:
I'm out of ideas, though, I saw this in my dmesg output:
which is the output for the pad identification, can that be the problem? maybe the computer mis identificate the device?
Last edited by dagg on Fri Jun 12, 2009 4:57 pm, edited 1 time in total.
|
![]() Administrator ![]()
|
It is quite possible your trackpad is being misidentified. Please try testing with another DE to verify this. ( KDE 3, Xfce, etc )
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Registered Member ![]()
|
I think I can confirm that the issue isn't kde related, after booting into my E17 WM and seeing the same behavior, I deduce that it was another package that was upgraded with kde 4.2 on the way unless E17 and kde share atleast one package.
closing the thread but still unresolved. |
Registered users: Bing [Bot], Google [Bot], q.ignora, watchstar