[MacBookPro8,2] Trackpad single clicks nearly always double clicks

[Lars Noodén]

On a MacBookPro8,2, the track pad does not respond properly. Single clicks are nearly always interpreted as double clicks.

Attachments as per https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_at_least_one_of_Touchpad_features_works_but_does_not_work_correctly_and_as_expected :
+ xmodmap: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/881830/+attachment/3399935/+files/xmodmap
+ xev: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/881830/+attachment/3408611/+files/xev.log
+ xinput: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/881830/+attachment/3399937/+files/xinput
+ evtest: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/881830/+attachment/3403873/+files/evtest

Ubuntu kernel version bisect revealed a regression from Ubuntu-2.6.38-8.39 to Ubuntu-2.6.38-7.40 .
---
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
DistroRelease: Ubuntu 11.10
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64+mac (20111012)
Package: linux (not installed)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Tags: oneiric running-unity
Uname: Linux 3.1.0-999-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: cdrom dialout lpadmin plugdev sambashare
---
ApportVersion: 2.6.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: lars 2156 F.... pulseaudio
 /dev/snd/controlC0: lars 2156 F.... pulseaudio
 /dev/snd/controlC1: lars 2156 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
CurrentDmesg:
 Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
 dmesg: write failed: Broken pipe
DistroRelease: Ubuntu 12.10
InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Alpha amd64+mac (20120920)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: Apple Inc. MacBookPro8,2
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-15-generic root=UUID=a8a325fd-0b63-4f6f-92c2-53eff4b3fc05 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
Tags: quantal
Uname: Linux 3.5.0-15-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

WifiSyslog:

dmi.bios.date: 01/24/12
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP81.88Z.0047.B27.1201241646
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-94245A3940C91C80
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro8,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-94245A3940C91C80
dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80:
dmi.product.name: MacBookPro8,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

[Lars Noodén (larsnooden)]

This is in Unity

[Fabio Marconi (fabiomarconi)]

Hello Lars
Seems to me something kernel related, so can you please reproduce the bug and type in a terminal:
apport-collect 881830
Can also be useful take a look at others log, then please attach here, using the button below 'Add attachment or patch' the file
/var/log/Xorg.0.log
/var/log/kern.log
Thanks
Fabio
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[Lars Noodén (larsnooden)]

apport seems not to be working because of the kernel.. What information can I collect manually?

$ uname -a
Linux xubuntu 3.1.0-999-generic #201111070407 SMP Mon Nov 7 09:08:05 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

[Fabio Marconi (fabiomarconi)]

Nov 7 13:15:19 xubuntu kernel: [ 5.969683] input: Apple Inc. Apple Internal Keyboard / Trackpad as /devices/pci0000:00/0000:00:1a.7/usb1/1-1/1-1.2/1-1.2:1.0/input/input7
Nov 7 13:15:19 xubuntu kernel: [ 5.969847] apple 0003:05AC:0245.0001: input,hidraw3: USB HID v1.11 Keyboard [Apple Inc. Apple Internal Keyboard / Trackpad] on usb-0000:00:1a.7-1.2/input0
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[Fabio Marconi (fabiomarconi)]

Nov 7 13:15:19 xubuntu kernel: [ 5.973122] apple 0003:05AC:0245.0002: hidraw4: USB HID v1.11 Device [Apple Inc. Apple Internal Keyboard / Trackpad] on usb-0000:00:1a.7-1.2/input1
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[Fabio Marconi (fabiomarconi)]

From Xorg log:

[ 12.466] (II) config/udev: Adding input device bcm5974 (/dev/input/event6)
[ 12.466] (**) bcm5974: Applying InputClass "evdev touchpad catchall"
[ 12.466] (**) bcm5974: Applying InputClass "touchpad catchall"
[ 12.466] (II) LoadModule: "synaptics"
[ 12.466] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 12.492] (II) Module synaptics: vendor="X.Org Foundation"
[ 12.492] compiled for 1.10.4, module version = 1.4.1
[ 12.492] Module class: X.Org XInput Driver
[ 12.492] ABI class: X.Org XInput driver, version 12.3
[ 12.492] (II) Using input driver 'synaptics' for 'bcm5974'
[ 12.492] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 12.492] (**) bcm5974: always reports core events
[ 12.492] (**) Option "Device" "/dev/input/event6"
[ 12.600] (--) bcm5974: x-axis range 0 - 1280
[ 12.600] (--) bcm5974: y-axis range 0 - 800
[ 12.600] (--) bcm5974: pressure range 0 - 256
[ 12.600] (--) bcm5974: finger width range 0 - 16
[ 12.600] (--) bcm5974: buttons: left double triple
[ 12.716] (--) bcm5974: touchpad found
[ 12.716] (**) bcm5974: always reports core events
[ 12.820] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-1/1-1.2/1-1.2:1.2/input/input10/event6"
[ 12.825] (II) XINPUT: Adding extended input device "bcm5974" (type: TOUCHPAD)
[ 12.825] (**) bcm5974: (accel) MinSpeed is now constant deceleration 2.5
[ 12.825] (**) bcm5974: MaxSpeed is now 1.75
[ 12.825] (**) bcm5974: AccelFactor is now 0.133
[ 12.825] (**) bcm5974: (accel) keeping acceleration scheme 1
[ 12.825] (**) bcm5974: (accel) acceleration profile 1
[ 12.825] (**) bcm5974: (accel) acceleration factor: 2.000
[ 12.825] (**) bcm5974: (accel) acceleration threshold: 4
[ 12.826] (--) bcm5974: touchpad found
[ 12.827] (II) config/udev: Adding input device bcm5974 (/dev/input/mouse2)
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[Andy Whitcroft (apw)]

Does this problem occur when running with official ubuntu kernels? We do have a number of mouse/touchpad fixes in our tree.

[Lars Noodén (larsnooden)]

Yes, the problem occurs with the official Ubuntu kernels. It also occurs with the Mainline kernels.
http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: kernel-bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Lars Noodén (larsnooden)]

Present in both newest kernels:

- 3.1.0-999-generic #201111070407 SMP Mon Nov 7
  09:08:05 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

- 3.1.0-2-generic #3-Ubuntu SMP Fri Oct 28
  20:28:07 UTC 2011 i686 i686 i386 GNU/Linux

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test the latest v3.2-rcN kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the others). 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.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.2-rc1 fixed and issue, the tag would be: 'kernel-fixed-upstream-v3.2-rc1'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Thanks in advance.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-rc2-oneiric/

[Lars Noodén (larsnooden)]

The problem still exists in the new mainline kernel:

$ uname -a
Linux xubuntu 3.2.0-999-generic #201111170405 SMP Thu Nov 17 09:07:10 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

[Lars Noodén (larsnooden)]

It's still not possible to click-and-drag

[Lars Noodén (larsnooden)]

Still present in Precise:

$ lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04

[Lars Noodén (larsnooden)]

In one kernel, the trackpad does not respond at all:
Linux 3.2.0-1-generic #3-Ubuntu SMP Tue Nov 22 11:30:27 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

[Lars Noodén (larsnooden)]

In a recent kernel, the track pad responds partially. It is not possible to click-and-drag and single clicks are often interpreted as double clicks.

Linux xubuntu 3.2.0-999-generic #201112040405 SMP Sun Dec 4 09:06:01 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

[penalvch (penalvch)]

Lars Noodén, 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 the latest upstream kernel available? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. 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. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Lars Noodén (larsnooden)]

It's still a problem in 12.10beta though less severe. The movement is jittery and hops. When typing on the keyboard, rapid bursts are often misinterpreted as mouse clicks even though the trackpad was not touched. What further data can be collected?

[penalvch (penalvch)]

Lars Noodén, I refocused this bug down to one of your two trackpad problems as per https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue . While a fix for one could fix the other, we would want to treat the two issues of single clicks are treated as doubles most of the time, and how click-and-drag does not work seperate for now.

Also, while booted into the Ubuntu repo kernel, could you please execute the following at a terminal:
apport-collect 881830

As well, could you please provide the information following https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_at_least_one_of_Touchpad_features_works_but_does_not_work_correctly_and_as_expected ?

Thank you for your understanding.

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

$ xmodmap -pp >~/xmodmap
$ xinput --list-props <id> >~/xinput
bash: syntax error near unexpected token `>'

$ xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ bcm5974 id=10 [slave pointer (2)]
⎜ ↳ Mouseemu virtual mouse id=13 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Power Button id=6 [slave keyboard (3)]
    ↳ Power Button id=7 [slave keyboard (3)]
    ↳ Sleep Button id=8 [slave keyboard (3)]
    ↳ Apple Inc. Apple Internal Keyboard / Trackpad id=9 [slave keyboard (3)]
    ↳ FaceTime HD Camera (Built-in) id=11 [slave keyboard (3)]
    ↳ Logitech Logitech USB Headset id=12 [slave keyboard (3)]

t 'xev | grep -i button > ~/xev' does nothing either. Keystrokes are still counting as mouse clicks making it all but impossible to type

[penalvch (penalvch)]

Lars Noodén, unfortunately we did not get the information the article requested. However, it has been reworded to clear the confusion. Could you please provide the information following https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_at_least_one_of_the_Touchpad_features_work.2C_but_does_not_work_correctly_and_as_expected ?

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[penalvch (penalvch)]

Lars Noodén, thank you for providing the requested information. 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 kernel in 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 and remove the tag:
needs-upstream-testing

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 text:
needs-upstream-testing

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.

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

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Please let us know your results. Thank you for your understanding.

[Lars Noodén (larsnooden)]

Typing is still often interpreted as a mouse click.

[penalvch (penalvch)]

Lars Noodén, regarding what this bug report is focused on:
>"Single clicks are nearly always interpreted as double clicks."

Is this problem reproducible in 3.7.0-030700rc1-generic ?

[Lars Noodén (larsnooden)]

Yes, I should have added a comment to go with the tag kernel-bug-exists-upstream-3.7.0-030700rc1-generic, but the problem is still there and the system virtually unusable.

[Lars Noodén (larsnooden)]

How about the typing that is interpreted as a single click? Should that be split off into a separate bug or is it part of the same problem?

[penalvch (penalvch)]

Lars Noodén, regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/881830/comments/52 :
>"How about the typing that is interpreted as a single click? Should that be split off into a separate bug or is it part of the same problem?"

If this is reproducible in the Ubuntu repo kernel, please feel free to report a separate bug and subscribe me to it. If it is only reproducible in mainline, then Ubuntu does not support fixing this. For more on this, please see https://wiki.ubuntu.com/Kernel/MainlineBuilds#Kernel.2BAC8-FAQ.2BAC8-DebuggingMainlineBuildsSupport.Does_the_kernel_team_support_the_mainline_kernel_builds.3F .

[penalvch (penalvch)]

Lars Noodén, regarding the problem "single clicks are nearly always interpreted as double clicks", did this issue not occur in a Ubuntu release prior to Oneiric?

[Lars Noodén (larsnooden)]

That I do not recall. I started with this hardware in 2011. I can't clear it right now.

[penalvch (penalvch)]

Lars Noodén, could you please test for this in a Lucid live environment via http://releases.ubuntu.com/lucid/ ?

[Lars Noodén (larsnooden)]

Christopher, thanks. Lucid seems to work very well in regards to the mouse and keyboard. Typing, clicking, click-and-drag, and double clicking all work as expected. It feels good to use. Unfortunately, the live session seemed not to find my network hardware. Otherwise, I could use 10.04.1 for a while.

[penalvch (penalvch)]

Lars Noodén, thank you for testing Lucid. Regarding your comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/881830/comments/46 :
evtest Edit (34 bytes, text/plain)

When one opens the attachment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/881830/+attachment/3399936/+files/evtest it notes:
evtest: No such file or directory

When you followed https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_at_least_one_of_the_Touchpad_features_work.2C_but_does_not_work_correctly_and_as_expected did you have the package installed before you generated this file? If so, did you follow the evtest instructions at https://wiki.ubuntu.com/DebuggingTouchpadDetection/evtest ?

[Lars Noodén (larsnooden)]

Here's a second try at evtest

[penalvch (penalvch)]

Lars Noodén, thank you for attaching the requested file. Regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/881830/comments/33 :
>"'xev | grep -i button > ~/xev' does nothing either. Keystrokes are still counting as mouse clicks making it all but impossible to type"

As per https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_at_least_one_of_the_Touchpad_features_work.2C_but_does_not_work_correctly_and_as_expected could you please excute instead:
xev > ~/xev.log

then perform the relevant actions noted in https://wiki.ubuntu.com/DebuggingTouchpadDetection/xev , and attach xev.log to this report?

[Lars Noodén (larsnooden)]

Multi-touch mouse actions don't work either in Unity.

[penalvch (penalvch)]

Lars Noodén, thank you for providing the requested information. The next step is to perform a Ubuntu kernel bisect from Lucid to Oneiric, in order to identify the last good Ubuntu kernel version, and first bad one. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

[Lars Noodén (larsnooden)]

Is there a way to do that with dpkg instead of git? If I understand the process correctly it is to build the old kernels one version at a time. That seems inefficient. Also, is there a way to narrow down the span to check so that the bisect needs only a few steps?

[Lars Noodén (larsnooden)]

I tried some other Live CDs. 10.04 with the 2.6.32-8-generic kernel worked ok, as reported above, as did the 2.6.35-22-generic kernel in 10.10. The 2.6.38-8 kernel in 11.04 definitely was messed up. Does that help narrow things down?

[Lars Noodén (larsnooden)]

I'm looking at the instructions from bisect (https://wiki.ubuntu.com/Kernel/KernelBisection)
When I get to the step, "Take a look first to see what you can learn", I get stuck.

I know that kernel 2.6.35-22 in 10.10 was ok and that kernel 2.6.38-8 in 11.04 was bad.
How do I translate the known good and known bad kernel to something that can be used by git. I need something like this, but for the versions above:

git log --oneline Ubuntu-2.6.35-24.42..Ubuntu-2.6.35-25.43

[penalvch (penalvch)]

Lars Noodén, thank you for working on bisecting. Following section https://wiki.ubuntu.com/Kernel/KernelBisection#Bisecting_Ubuntu_kernel_versions , in order to bisect Ubuntu kernel commits via git, one would first want to further bisect the known regression range 2.6.35-22 - 2.6.38-8 as far as possible. Consulting https://launchpad.net/ubuntu/maverick/+source/linux we have:
 2.6.35-22.32
2.6.35-22.33
2.6.35-22.34
2.6.35-22.35
2.6.35-23.36
2.6.35-23.37
2.6.35-23.39
2.6.35-23.40
2.6.35-23.41
2.6.35-24.42
2.6.35-25.43
2.6.35-25.44
2.6.35-26.46
2.6.35-27.47
2.6.35-27.48
2.6.35-28.49
2.6.35-28.50
2.6.35-29.51
2.6.35-30.53
2.6.35-30.54
2.6.35-30.55
2.6.35-30.56
2.6.35-30.57
2.6.35-30.58
2.6.35-30.59
2.6.35-30.60
2.6.35-30.61
2.6.35-31.62
2.6.35-31.63
2.6.35-32.64
2.6.35-32.65
2.6.35-32.66
2.6.35-32.67
2.6.35-32.68
2.6.38-10.44

Hence, could you please test 2.6.35-28.50 via https://launchpad.net/~canonical-kernel-team/+archive/ppa/+build/2297929 ?

Then one should be able to continue the process until the Ubuntu kernel regression version is found.

Thank you for your understanding.

[Lars Noodén (larsnooden)]

> Hence, could you please test 2.6.35-28.50 via https://launchpad.net
/~canonical-kernel-team/+archive/ppa/+build/2297929 ?

That gave the kernel 2.6.35-28-generic only. That kernel seems to
work fine. How do I get the next kernel in the series to test?

On 10/31/12, Christopher M. Penalver <email address hidden> wrote:
> Lars Noodén, thank you for working on bisecting. Following section
> https://wiki.ubuntu.com/Kernel/KernelBisection#Bisecting_Ubuntu_kernel_versions
> , in order to bisect Ubuntu kernel commits via git, one would first want to
> further bisect the known regression range 2.6.35-22 - 2.6.38-8 as far as
> possible. Consulting https://launchpad.net/ubuntu/maverick/+source/linux we
> have:
> 2.6.35-22.32
> 2.6.35-22.33
> 2.6.35-22.34
> 2.6.35-22.35
> 2.6.35-23.36
> 2.6.35-23.37
> 2.6.35-23.39
> 2.6.35-23.40
> 2.6.35-23.41
> 2.6.35-24.42
> 2.6.35-25.43
> 2.6.35-25.44
> 2.6.35-26.46
> 2.6.35-27.47
> 2.6.35-27.48
> 2.6.35-28.49
> 2.6.35-28.50
> 2.6.35-29.51
> 2.6.35-30.53
> 2.6.35-30.54
> 2.6.35-30.55
> 2.6.35-30.56
> 2.6.35-30.57
> 2.6.35-30.58
> 2.6.35-30.59
> 2.6.35-30.60
> 2.6.35-30.61
> 2.6.35-31.62
> 2.6.35-31.63
> 2.6.35-32.64
> 2.6.35-32.65
> 2.6.35-32.66
> 2.6.35-32.67
> 2.6.35-32.68
> 2.6.38-10.44
>
> Hence, could you please test 2.6.35-28.50 via https://launchpad.net
> /~canonical-kernel-team/+archive/ppa/+build/2297929 ?
>
> Then one should be able to continue the process until the Ubuntu kernel
> regression version is found.
>
> Thank you for your understanding.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/881830
>
> Title:
> [MacBookPro8,2] Trackpad single clicks nearly always double clicks
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/881830/+subscriptions
>

[penalvch (penalvch)]

Lars Noodén, thank you for testing the requested kernel. Regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/881830/comments/67 :
>" That kernel seems to work fine. How do I get the next kernel in the series to test?"

Continuing to follow the Ubuntu kernel bisecting instructions at https://wiki.ubuntu.com/Kernel/KernelBisection#Bisecting_Ubuntu_kernel_versions , given we now know 2.6.35-28.50 works, we again consult https://launchpad.net/ubuntu/maverick/+source/linux , which notes:
2.6.35-28.50
2.6.35-29.51
2.6.35-30.53
2.6.35-30.54
2.6.35-30.55
2.6.35-30.56
2.6.35-30.57
2.6.35-30.58
2.6.35-30.59
2.6.35-30.60
2.6.35-30.61
2.6.35-31.62
2.6.35-31.63
2.6.35-32.64
2.6.35-32.65
2.6.35-32.66
2.6.35-32.67
2.6.35-32.68
2.6.38-10.44

The midpoint between the last known good Ubuntu kernel (2.6.35-28.50) and last known bad (2.6.38-10.44) is 2.6.35-30.59. Hence, we click on "2.6.35-30.59", then under "Builds" click "amd64" which brings us to https://launchpad.net/~canonical-kernel-team/+archive/ppa/+build/2755232 . Could you please test this kernel?

Thank you for your understanding.

[Lars Noodén (larsnooden)]

Thanks. 2.6.35-30.59 works, too. 2.6.35-32.64 is next, right?

[Lars Noodén (larsnooden)]

2.6.35-32.67, if it overwrote 2.6.35-32.64 when I installed it, was good.

2.6.38-10.44 was definitely bad.

What next?

[Lars Noodén (larsnooden)]

$ git log --oneline Ubuntu-2.6.35-32.67..Ubuntu-2.6.35-10.44
fatal: ambiguous argument 'Ubuntu-2.6.35-32.67..Ubuntu-2.6.35-10.44': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions

[Lars Noodén (larsnooden)]

$ git log --oneline Ubuntu-2.6.35-32.67..Ubuntu-2.6.38-10.44
fatal: ambiguous argument 'Ubuntu-2.6.35-32.67..Ubuntu-2.6.38-10.44': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions

[penalvch (penalvch)]

Lars Noodén, thank you for working on the Ubuntu kernel version bisect. Regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/881830/comments/69 :
>"Thanks. 2.6.35-30.59 works, too. 2.6.35-32.64 is next, right?"

Yes.

Regarding https://bugs.launchpad.net/ubuntu/+source/linux/+bug/881830/comments/70 :
>"2.6.35-32.67, if it overwrote 2.6.35-32.64 when I installed it, was good."

One may check what kernel they have booted into via a terminal. For example, mine is:
uname -a
Linux moniker-PC 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:32:08 UTC 2012 i686 i686 i686 GNU/Linux

>"2.6.38-10.44 was definitely bad. What next?"

Assuming 2.6.35-32.64 was good, and then you checked 2.6.35-32.67, and that was good, we would want to test 2.6.35-32.68 next.

Regarding https://bugs.launchpad.net/ubuntu/+source/linux/+bug/881830/comments/71 :
>"$ git log --oneline Ubuntu-2.6.35-32.67..Ubuntu-2.6.35-10.44
fatal: ambiguous argument 'Ubuntu-2.6.35-32.67..Ubuntu-2.6.35-10.44': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions"

Because we have not found the last known Ubuntu kernel version, followed consecutively in version by the first known bad one, we would not want to be git bisecting just yet.

Thank you for your understanding.

[Lars Noodén (larsnooden)]

Ok. I see the # is also given by uname. Thanks for the explanations.

2.6.35-32.68 was good. It also runs cool, the 2.6.35-10.44 kernel is not only bad but also runs hot. We're now out of kernels to try on https://launchpad.net/ubuntu/maverick/+source/linux

What next?

[Doug Smythies (dsmythies)]

I added notes to your Ubuntu forums thread on this, which I guess you didn't see.
Now, you would switch to the natty kernels and continue.

https://launchpad.net/ubuntu/natty/+source/linux

I would start with 2.6.36-0.1 as a starting point for the natty successive approximation. If that works then 2.6.37-8.21 as an approximate mid-point of the 42 or 43 kernels in between, and so on...

[penalvch (penalvch)]

Lars Noodén, thank you for further bisecting the Ubuntu kernel version. Since we know 2.6.35-32.68 was good, and 2.6.38-8 is bad, we would want to further bisect the Ubuntu kernel version via https://launchpad.net/ubuntu/natty/+source/linux :
 2.6.35-22.34
2.6.36-0.1
2.6.36-0.2
2.6.36-0.3
2.6.36-0.4
2.6.36-1.5
2.6.36-1.6
2.6.36-1.7
2.6.36-2.8
2.6.37-2.9
2.6.37-2.10
2.6.37-3.11
2.6.37-4.12
2.6.37-5.13
2.6.37-5.14
2.6.37-6.15
2.6.37-6.16
2.6.37-6.17
2.6.37-7.18
2.6.37-7.19
2.6.37-8.20
2.6.37-8.21
2.6.37-9.22
2.6.37-9.23
2.6.37-10.24
2.6.37-11.25
2.6.37-12.26
2.6.38-1.27
2.6.38-1.28
2.6.38-2.29
2.6.38-3.30
2.6.38-4.31
2.6.38-5.32
2.6.38-6.33
2.6.38-6.34
2.6.38-7.35
2.6.38-7.36
2.6.38-7.37
2.6.38-7.38
2.6.38-7.39
2.6.38-8.40
2.6.38-8.41
2.6.38-8.42

Hence, could you please test 2.6.37-8.20 via https://launchpad.net/ubuntu/+source/linux/2.6.37-8.20/+build/2079395 ?

Thank you for your understanding.

[Lars Noodén (larsnooden)]

Ok. I've walked through the kernels at smaller and smaller intervals. The most recent good kernel in the sequence was 2.6.38-7.39 and the first bad one is 2.6.38-8.40. The bad kernel runs quite hot, too.

[penalvch (penalvch)]

Lars Noodén, thank you for finding the Ubuntu kernel version regression. The next step is commit bisecting Ubuntu kernel versions. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#Commit_bisecting_Ubuntu_kernel_versions ?

Thank you for your understanding.

[Lars Noodén (larsnooden)]

$ git clone git://kernel.ubuntu.com/ubuntu/ubuntu-natty.git
$ cd ubuntu-natty/
$ git checkout -b mybisect origin/master
$ git log --oneline Ubuntu-2.6.38-7.39..Ubuntu-2.6.38-8.40 | wc -l
704

git bisect produces no output:

$ git bisect start Ubuntu-2.6.38-7.39..Ubuntu-2.6.38-8.40

The wiki page shows that I should expect some output from git bisect.

[Doug Smythies (dsmythies)]

Lars,
The order is bad good for that step.

$ git bisect start Ubuntu-2.6.38-7.40..Ubuntu-2.6.38-8.39

[Doug Smythies (dsmythies)]

Note that in the changelog there are touchpad specific notes: "* eeepc-wmi: add touchpad sysfs file". I don't recall how to jump to that specific commit ot patch to test with and without it.

[penalvch (penalvch)]

Lars Noodén / Doug Smythies, please be careful with your syntax. As per https://wiki.ubuntu.com/Kernel/KernelBisection#Start_the_bisection the following command you provided is incorrect:
$ git bisect start Ubuntu-2.6.38-7.40..Ubuntu-2.6.38-8.39

it should be without double periods:
git bisect start Ubuntu-2.6.38-8.40 Ubuntu-2.6.38-7.39

[Lars Noodén (larsnooden)]

Thanks for the patience.

Here the output diverges from the guide:

$ git bisect start Ubuntu-2.6.38-8.40 Ubuntu-2.6.38-7.39
Switched to branch 'mybisect'
Bisecting: a merge base must be tested
[521cb40b0c44418a4fd36dc633f575813d59a43d] Linux 2.6.38

[Doug Smythies (dsmythies)]

I think, but am not sure, that you are supposed to test the point that git has suggested. Git can not exactly "bisect" yet, and needs to know the answer if the point it selected is good or bad. For example (and since I can not actually test the kernel for your problem, I just made a "good" answer for this example):

doug@s15:~/temp-lars/ubuntu-natty$ git bisect start Ubuntu-2.6.38-8.40 Ubuntu-2.6.38-7.39
Bisecting: a merge base must be tested
[521cb40b0c44418a4fd36dc633f575813d59a43d] Linux 2.6.38
doug@s15:~/temp-lars/ubuntu-natty$ git bisect good
Bisecting: 351 revisions left to test after this (roughly 9 steps)
[516b498acc786576d4dd4238f7d67812a5c5df86] UBUNTU: SAUCE: hid: ntrig: New ghost-filtering event logic

Christopher: I didn't notice the syntax error before, only the good bad order issue. Sorry.

[Lars Noodén (larsnooden)]

I'm stuck at building the kernel. In the building the kernel instructions (https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel) both modifying the configuration and building the kernel require rules files in the debian subdirectory. However, if the directions (https://wiki.ubuntu.com/Kernel/KernelBisection#Start_the_bisection) are followed (http://ubuntuforums.org/showpost.php?p=12336240&postcount=14) then there is no debian subdirectory and thus the kernel won't build.

[penalvch (penalvch)]

Lars Noodén, thank you for working on the bisect. Regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/881830/comments/85 :

Looking at http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-natty.git;a=shortlog;pg=8 you may have fallen into the non-linear commit pit trap https://wiki.ubuntu.com/Kernel/KernelBisection#Commit_bisecting_Ubuntu_kernel_versions_across_non-linear_tags . Could you please execute the following in a terminal and post the results:
git rev-list Ubuntu-2.6.38-8.40 | \
grep $(git log --pretty=oneline -1 Ubuntu-2.6.38-7.39 | cut -d' ' -f1)

Thank you for your understanding.

[Lars Noodén (larsnooden)]

I'll look more closely at it tomorrow, but looking quickly right now
with a fresh clone, there is no output from the following:

git rev-list Ubuntu-2.6.38-8.40 | \
grep $(git log --pretty=oneline -1 Ubuntu-2.6.38-7.39 | cut -d' ' -f1)

It does not produce even a single line. I think it may be necessary
to solve other problems first. The kernel won't build without
debian/rules, but 'git bisect start' seems to remove that directory's
contents. 'git bisect reset' seems to create the needed files.
Should I be building after 'start' or after 'reset' ? I presume the
former.

On 11/4/12, Christopher M. Penalver <email address hidden> wrote:
> Lars Noodén, thank you for working on the bisect. Regarding your
> comments
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/881830/comments/85
> :
>
> Looking at
> http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-natty.git;a=shortlog;pg=8 you
> may have fallen into the non-linear commit pit trap
> https://wiki.ubuntu.com/Kernel/KernelBisection#Commit_bisecting_Ubuntu_kernel_versions_across_non-linear_tags
> . Could you please execute the following in a terminal and post the
> results:
> git rev-list Ubuntu-2.6.38-8.40 | \
> grep $(git log --pretty=oneline -1 Ubuntu-2.6.38-7.39 | cut -d' ' -f1)
>
> Thank you for your understanding.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/881830
>
> Title:
> [MacBookPro8,2] Trackpad single clicks nearly always double clicks
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/881830/+subscriptions
>

[Doug Smythies (dsmythies)]

The closest "Ubuntu" type kernel beyond the branch point is ecdd48d07f19ea63f8834c4a8cad328bab4f4d3b
The attached file shows how I got to this conclusion.
I.E. to continue with bisection and always get "Ubuntu" kernels (ones with ./debain/rules and such) the start point would be:

git bisect start Ubuntu-2.6.38-8.40 ecdd48d07f19ea63f8834c4a8cad328bab4f4d3b
Bisecting: 279 revisions left to test after this (roughly 8 steps)
[460ca35eb850250cb04416eef94c19b1fb818705] UBUNTU: [Config] build in CONFIG_AGP_AMD

Observation: The word "UBUNTU" will only be there if it is an Ubuntu kernel.

Of course, there no way to know for sure, until it is built and tested, if ecdd48d07f19ea63f8834c4a8cad328bab4f4d3b is actually a "good" starting point.

Now, if it would just compile.

[penalvch (penalvch)]

Lars Noodén, could you please test http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc4-raring/ ?

[Lars Noodén (larsnooden)]

I tried it but the kernel linux-headers-3.8.0-030800rc4-generic_3.8.0-030800rc4.201301172335_amd64.deb doesn't boot on the hardware I have.

[penalvch (penalvch)]

Lars Noodén, could you please confirm this issue exists with the latest development release of Ubuntu Saucy Salamander? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, 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 (v3.10-rc3-saucy) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory 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.10-rc3

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

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

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.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Lars Noodén (larsnooden)]

Still present in Linux lubuntu 3.11.0-031100rc2-generic #201307211535 SMP Sun Jul 21 19:36:42 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

more details to follow

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

apport information

[Lars Noodén (larsnooden)]

Trouble collecting apport information. Sorry for duplicates.

The double click problem seems now to be one where it single clicks occasionally when typing on the keyboard regardless of whether there is any contact with the mouse or trackpad.

[Lars Noodén (larsnooden)]

I don't see where the tags are or can be added.

kernel-bug-exists-upstream
kenrel-bug-exists-upstream-v3.11.0-031100rc2-generic

[penalvch (penalvch)]

Lars Noodén, getting back to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/881830/comments/87 , the bisect documentation has been updated to advise switching to bisecting the mainline kernel instead. Hence, could please resume your bisect via https://wiki.ubuntu.com/Kernel/KernelBisection ?

[Lars Noodén (larsnooden)]

With the 3.11.0-4-generic #9-Ubuntu SMP kernel that is part of Saucy, the errant mouse clicks are less of a problem. They seem not to be present any more when just using the trackpad, but still a problem when typing. Is a bisection still needed? If so between which kernels?

[penalvch (penalvch)]

Lars Noodén, please see http://kernel.ubuntu.com/~kernel-ppa/info/kernel-version-map.html .

[Lars Noodén (larsnooden)]

Christopher, thanks. What should I look at from that page?

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]