Trackpad killswitch won't kill trackpad in Lucid

I suspect the killswitch is implemented by the kernel, so reassigning to linux.

Hi Matt,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

Jeremy, I'll be more than happy to do that... as it is, I happen to compile John's mainline aa kernel for testing, however, I haven't done that on lucid since I've been very busy. I will get on that as soon as I'm done moving over the weekend so expect results sometime in the next week or two. Thanks for you guys taking the time to help me with this bug. Yet another reason for running Ubuntu. ;)

Matt

oooh Just read the link and I see what you did there. :) Just made my job easier. heh

Matt,
     Happy moving! :-) RE: the link, we aim to please. ;-)

~JFo

Ok, here's the news. I have the mainline installed and running now... it's the current daily... Just tried the trackpad kill switch and it's still not working. :/ I'm kinda grasping at straws now as to where I can look and maybe tweak to get this switch working. Any other ideas?

meskes@Neptune:~$ uname -a
Linux Neptune 2.6.34-999-generic #201005051005 SMP Wed May 5 09:08:40 UTC 2010 x86_64 GNU/Linux
meskes@Neptune:~$

Hi Matt,
     I'm going to ask one of the Kernel Team members to take a look at this when they get a chance. In the meantime, this is a quicksearch I did on the Kernel Bugzilla. As you can see, there are not many bugs relating to the trackpad, but it may be worthwhile to search a bit more to see if someone has reported an issue like yours there. if you find something, let us know here too so we can watch it.

Thanks!

~JFo

Thanks Jeremy.

I also have this problem on a fresh install of Maverick.

The killswitch doesn't change color, however a graphic in the top-right corner informs me that the trackpad has been toggled off (or back on) when no real change has occurred.

I also found out that changing settings in gconf (/desktop/gnome/peripherals/touchpad/) such as tap to click, scroll method, and so on, have no effect either.

Laptop is an HP Pavilion dm3

Matt Eskes, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Chris, I'm sorry but that would be a no go, as I don't have the affected hardware anymore nor do I run Ubuntu anymore. At all. Not in my Desktop deployments, not in my Server Deployments, not even in my VPS deployments. The fact that this bug was filed THREE years ago, and is just *now* getting another hit, asking me for an upstream confirmation is bit a ludicrous and one of the many reasons I lost faith with Ubuntu as a distro. I'm quite happy where I am now and I'm sorry I can't be of further assistance. However, since you ask, no, this was not an upstream issue as I compiled my own mainline image, per the Debian Handbook and it worked just fine. It was an issue with one of the kernel drivers that not even installing hp-tools, I think name of the package was, could fix. Please either delete this bug or mark it as invalid, as it clearly not reproducible on my end.

M

Matt Eskes, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/520288/comments/12 regarding you no longer have the hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.