touch pad mouse is standard locked right after login

[indium]

On a MBP 6,2, Ubuntu 11.04 the touchpad works at the login screen, but after logging in, it is disabled. Have to use an external mouse to open "pointing devices" and click twice on the "disable touchpad" to get the touchpad going again. That is: Please note that the GUI of "pointing devices" shows that touchpad is NOT disabled when it IS disabled.

As a work-around I tried to manipulate the 'disabled' mode with 'synclient', but it is somehow overruled by 'pointing devices'. Any idea how I can access 'pointing devices' without installing an external mouse? Via 'Alt-F2' I cannot find 'pointing devices'.

Problem is there for Unity as well Gnome.
---
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 270.41.06 Mon Apr 18 14:53:56 PDT 2011
 GCC version: gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-8ubuntu4)
Architecture: amd64
DistUpgraded: Log time: 2011-05-05 08:29:27.534574
DistroCodename: natty
DistroRelease: Ubuntu 11.04
DistroVariant: ubuntu
GraphicsCard:
 nVidia Corporation GT216 [GeForce GT 330M] [10de:0a29] (rev a2) (prog-if 00 [VGA controller])
   Subsystem: Apple Computer Inc. Device [106b:00c7]
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
JockeyStatus:
 kmod:wl - Broadcom STA proprietary wireless driver (Proprietary, Enabled, In use) [auto-install]
 xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, Not in use)
MachineType: Apple Inc. MacBookPro6,2
NonfreeKernelModules: wl nvidia
Package: xorg 1:7.6+4ubuntu3
PackageArchitecture: amd64
ProcEnviron:
 LANGUAGE=en_GB:en
 LC_CTYPE=C
 PATH=(custom, user)
 LANG=en_US.utf-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=ef2598d5-1435-49ea-8a14-73ac490bd70f ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Tags: natty ubuntu
Uname: Linux 2.6.38-8-generic x86_64
UpgradeStatus: Upgraded to natty on 2011-05-05 (10 days ago)
UserGroups: adm admin audio cdrom daemon davfs2 dialout dip fuse lp lpadmin netdev plugdev sambashare sudo sys video
dmi.bios.date: 07/26/10
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP61.88Z.0057.B0C.1007261552
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-F22586C8
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro6,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F22586C8
dmi.modalias: dmi:bvnAppleInc.:bvrMBP61.88Z.0057.B0C.1007261552:bd07/26/10:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8:
dmi.product.name: MacBookPro6,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.4+bzr20110415-0ubuntu2
version.ia32-libs: ia32-libs 20090808ubuntu13
version.libdrm2: libdrm2 2.4.23-1ubuntu6
version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7

[Fabio Marconi (fabiomarconi)]

temporarily assigned to xorg to collect data

[Fabio Marconi (fabiomarconi)]

Hello
can you please reproduce the bug then run in a terminal
apport-collect -p xorg 782143
Thanks
Fabio

[indium (indium)]

apport information

[indium (indium)]

apport information

[indium (indium)]

apport information

[indium (indium)]

apport information

[indium (indium)]

apport information

[indium (indium)]

apport information

[indium (indium)]

apport information

[indium (indium)]

apport information

[indium (indium)]

apport information

[indium (indium)]

apport information

[indium (indium)]

apport information

[indium (indium)]

apport information

[indium (indium)]

apport information

[indium (indium)]

apport information

[indium (indium)]

apport information

[indium (indium)]

apport information

[indium (indium)]

apport information

[indium (indium)]

apport information

[indium (indium)]

apport information

[indium (indium)]

apport information

[indium (indium)]

Dear Fabio,

while doing this 'apport', I got an error back in the terminal (so I don't know if you got all the information you needed).

_________terminal output:__________________

The authorization page:
 (https://launchpad.net/+authorize-token?oauth_token=x.....&allow_permission=DESKTOP_INTEGRATION) should be opening in your browser. Use your browser to authorize this program to access Launchpad on your behalf.

Waiting to hear from Launchpad about your decision...
Attempting to load the system libmoon
ERROR: hook /usr/share/apport/package-hooks//source_xorg.py crashed:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/apport/report.py", line 656, in add_hooks_info
    symb['add_info'](self, ui)
  File "/usr/share/apport/package-hooks//source_xorg.py", line 457, in add_info
    attach_2d_info(report, ui)
  File "/usr/share/apport/package-hooks//source_xorg.py", line 319, in attach_2d_info
    'GdmLog2': 'cat /var/log/gdm/:0.log.2'})
  File "/usr/lib/python2.7/dist-packages/apport/hookutils.py", line 359, in attach_root_command_outputs
    f = open(os.path.join(workdir, keyname))
IOError: [Errno 13] Permission denied: '/tmp/tmpppXJvF/GdmLog1'

[Fabio Marconi (fabiomarconi)]

[ 42330.130] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 42330.130] (WW) Disabling Keyboard0
[ 42330.130] (WW) Disabling Mouse0

[indium (indium)]

Dear Fabio,

Comment to #24:
the laptop keyboard is not disabled, so I don't know what 'Keyboard0' means. I have no other keyboard connected.

[Tom Nicholls (pmyteh)]

You can get to the "Pointing Devices" config programme without a mouse by using the command "gpointing-device-settings".

I have a related, but apparently separate issue (bug #783641) as hitting the disable touchpad button twice won't restart my pointer. However, it seems that this button issues something like the following to your hardware:

#! /bin/sh
xinput --set-prop "SynPS/2 Synaptics Touchpad" "Synaptics Off" 0
xinput --set-prop "SynPS/2 Synaptics Touchpad" "Synaptics Off" 1

As a workaround, resetting the touchpad should be quicker if you dump the code above into a shell script file, substituting "SynPS/2 Synaptics Touchpad" for whatever the name of your device is (try xinput --list to find out what it's called)

Hope that helps,
Tom

[indium (indium)]

Dear Tom,

thanks for this, I will try it soon. Do you understand how all these
different 'levels' of controlling the mouse work? I had already tried
similar tricks using the 'synclient' commandline command, but that did
not resolve the problem. Now you say that there's
'gpointing-device-settings' (which is gnome related, I guess) and
'xinput', which is at the 'x11' level. This used to be soo much more
transparent in the old linux days ;o)

indium

On 07/06/11 19:28, Tom Nicholls wrote:
> You can get to the "Pointing Devices" config programme without a mouse
> by using the command "gpointing-device-settings".
>
> I have a related, but apparently separate issue (bug #783641) as hitting
> the disable touchpad button twice won't restart my pointer. However, it
> seems that this button issues something like the following to your
> hardware:
>
> #! /bin/sh
> xinput --set-prop "SynPS/2 Synaptics Touchpad" "Synaptics Off" 0
> xinput --set-prop "SynPS/2 Synaptics Touchpad" "Synaptics Off" 1

> As a workaround, resetting the touchpad should be quicker if you dump
> the code above into a shell script file, substituting "SynPS/2 Synaptics
> Touchpad" for whatever the name of your device is (try xinput --list to
> find out what it's called)
>
> Hope that helps,
> Tom
>

[indium (indium)]

Dear Tom,

your suggested approach using the 'xinput' command (comment #26) does not solve the problem unfortunately. (mouse pad keeps being blocked)

I can call 'gpointing-device-settings' after each login and work with that for the time being, as you also suggested.

I do not understand that/how 'xinput' is somehow "overruled" by 'gpointing-device-settings'.

indium

[Tom Nicholls (pmyteh)]

My impression is that gpointing-device-settings is simply a graphical frontend to the xinput command. Given that it's not part of the default install, I can't see that it has it's own critical function. The code certainly looks like a frontend, given a cursory look.

Having said that, if it were the case, I can't see why the script suggested doesn't work, given it changes the same xinput state that you can see change when gpointing-device-settings is used to disable the device. Have you tried using "xinput watch-props <device>" when trying the script or toggling gpointing-device-settings, to see what's happening.

As you can gather, I'm not an expert on the Linux input stack, just somebody with a similar problem. I hope it's helped a bit, though.

[Bryce Harrington (bryce)]

Hey indium,

You filed this bug report against natty, but I see it's still open and
doesn't appear to have much activity recently. So, now that oneiric
is released and stable, this may be a good point for you to upgrade
and re-test if this issue is still present there.

If it's solved in the new release and you think it's worth backporting
the fix, please indicate that. Or if having the fix in the new release
is good enough, feel free to close out the bug (or let us know and we'll
close it.)

If it's not solved, leave the bug report open. I can't promise we'll
get to it (we get way more bugs filed than we can usually get to), but
your testing and feedback can help out if and when we do.

[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.