Inactive touchpad randomly on HP Pavillon dv6800

[phendrax]

- By turning on the computer, the touchpad is recognized, it runs on the login screen. Very rarely (in an apparently random), the touchpad does not work once logged into the account of the user A (can not move the cursor or click). If we return to the login screen or we log on to the account of user B, the touchpad works again, but still does not work in the user's session A.
- A solution has been found to temporarily fix the bug: deactivate / reactivate the touchpad, click with a mouse on the gnome-menu (Application, Shortcuts, System): the menu highlights as if it was selected but not is opened. Now we log on to the terminal (Ctrl + Alt + F1) then we return to the graphical session (Ctrl + Alt + F7) and the touchpad works.
- Each time the touchpad was recognized by xinput.
- This bug has appeared on two HP Pavilion dv6800 with Ubuntu Lucid Lynx (never had this bug in previous versions of Ubuntu).

[phendrax (phendrax)]

Bug also appeared on HP Pavilion dv6 1225ef

[Leo Arias (elopio)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.
Please try to follow the instructions at [1] and upload the files as separate attachments.

[1] https://wiki.ubuntu.com/DebuggingTouchpadDetection#In%20case%20your%20touchpad%20stops%20working%20after%20a%20while

[Leo Arias (elopio)]

This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in xserver-xorg-input-synaptics.

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.