turning touchpad on and off intefears with GDM

[Ian Paterson]

Binary package hint: xserver-xorg-input-synaptics

Hardware:
HP Pavilion dv6-2005tx Notebook PC
Synaptics touchpad
This has a little button and light to turn the mouse pad on and off

1) 10.10 RC
2) xserver-xorg-input-synaptics 1.2.2
3) Pressing the button above the touchpad should turn the light to red and deactivate the touchpad. Pressing it again turns to light to white reactivating it (its there so you can turn it off so you don't bump the mouse while typing)
-it remembers its state after a restart

4) Since installing lucid(same install as this one, but it has affected fresh installs of lucid) I have noticed that after turning the mouse pad off and then on again it no longer functions. Logging off then back on fixes this.
The problem is that when I try to do things in Gnome (like click on menus and stuff) all I get is a highlighted button (no menu)
And also buttons do not work. The range of this extends to anything using GTK+ but not applications like Firefox which use different toolkits. So all qt applications work fine, as do Thunderbird and Firefox etc. (im doing this clicking and stuff with another mouse, a USB one)
This problem occurs both with and without compiz.
To fix it is easy. Switch to any TTY (ctrl + alt +F1) and then back to X and everything is fixed.
But here's the thing, this will only ever happen once per session, once it is fixed, it won't happen again until you reboot.

This is the process for reproducing the bug on effected machines:
- Turn the touchpad off
- click up on main panel menu , it doesn't drop down. The rest of gnome is also broken as described above
- do a ctrl-alt-F1, then ctrl-alt-F7 (gnome works fine now and will for the remainder of the session -until a reboot)
                          No matter what I do gnome is fine. (any number of touchpad on off cycles)
-the touch pad will not work at all for the remainder of the session -until a log off (although pressing it lots of time used to work it doesn't seem to now)

-Then I log off, log back on, mouse pad works. gnome is still fine
-Turn the touch pad off, gnome is still fine
-Turn the touch pad back on, mouse pad does not work, gnome is still fine.

-Then I reboot and we are back to the start with a working GDM and touchpad. That both break when the touch pad is turned off

-BTW I just picked out the most relevant package for the package hint from the package manager so I hope somebody who knows about this package can correct it if is wrong. It does seem like quite a hard bug to pin down due to it affecting lots of things.
I have attached a GDM log as well since apport suggested it. I made sure that I cause the bug and corrected it just before I uploaded so that it could be most helpful to anybody looking at the log (you only have to look back about 20 second or so to see it, I don't know what you would look for though so I'm not sure if it is there or not)

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xserver-xorg-input-synaptics 1.2.2-2ubuntu5
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic-pae 2.6.35.4
Uname: Linux 2.6.35-22-generic-pae i686
NonfreeKernelModules: nvidia
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86 Kernel Module 260.19.06 Mon Sep 13 06:35:06 PDT 2010
 GCC version: gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5)
Architecture: i386
Date: Wed Oct 6 20:21:35 2010
DkmsStatus:
 vhba, 20100822, 2.6.35-22-generic-pae, i686: installed
 nvidia-current, 260.19.06, 2.6.35-22-generic-pae, i686: installed
 virtualbox-ose, 3.2.8, 2.6.35-22-generic-pae, i686: installed
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate i386 (20100419.1)
MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic-pae root=UUID=30a28cc3-0077-4bab-a93a-1a24298895ef ro quiet splash nomodeset video=uvesafb:mode_option=1366x768-24,mtrr=3,scroll=ywrap
ProcEnviron:
 LANGUAGE=en_NZ:en_AU:en_GB:en
 PATH=(custom, no user)
 LANG=en_NZ.utf8
 SHELL=/bin/bash
SourcePackage: xserver-xorg-input-synaptics
dmi.bios.date: 09/10/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.04
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 363E
dmi.board.vendor: Quanta
dmi.board.version: 32.16
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.04:bd09/10/2009:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr039F200000241210000020000:rvnQuanta:rn363E:rvr32.16:cvnQuanta:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv6 Notebook PC
dmi.product.version: 039F200000241210000020000
dmi.sys.vendor: Hewlett-Packard
system:
 distro: Ubuntu
 codename: maverick
 architecture: i686
 kernel: 2.6.35-22-generic-pae

[bugbot (bugbot)]

Hey Ian,

Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?

If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.

If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.

If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.

[bugbot (bugbot)]

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.