Disable Touchpad (Fn-F8) forces logout

Bug #976290 reported by Tony Espy
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xserver-xorg-input-synaptics (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

I just updated my 12.04 system and after the udpate, the Disable Touchpad function combination ( Fn + F8 ) causes my session to logout instead of disabling the touchpad. It seems to work once every few attempts, but when it does, it doesn't seem to persist across Suspend/Resume.

This is a regression as this was working fine previously ( at least the main description of disabling the touchpad ).

My system is a Lenovo Thinkpad 410s with Intel graphics, it has an SSD for it's main drive. It has the following CPU:

Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 976290

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Tony Espy (awe) wrote :

Note I tried to run apport-collect and it displayed a dialog with a spinner, and a stack trace displayed in the terminal. See attached output.

Revision history for this message
Tony Espy (awe) wrote :
Revision history for this message
Tony Espy (awe) wrote :
Revision history for this message
Tony Espy (awe) wrote :
Revision history for this message
Tony Espy (awe) wrote :
Revision history for this message
Tony Espy (awe) wrote :

Please see comment #1 regarding the stack trace produced when I tried to run apport-collect for this bug.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Tony Espy, thank you for reporting this and helping make Ubuntu better. This sounds like an X crash. Could you please obtain a backtrace following http://wiki.ubuntu.com/X/Backtracing ?

affects: linux (Ubuntu) → xorg (Ubuntu)
Changed in xorg (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Tony Espy (awe) wrote :

@Christopher

I haven't been able to reproduce the problem since this weekend.

There is an X crash in /var/crash with the corresponding date, but I'm not sure the what the proper steps are to include it's contents in the bug. There doesn't appear to be a way to point apport-collect at a crash file. Ideas?

I'll continue to try and reproduce the bug as well.

Revision history for this message
penalvch (penalvch) wrote :

Tony Espy, you may file a bug report against the crash file by executing at the Terminal:
ubuntu-bug /var/crash/_my_crash_report.crash

Please feel free to subscribe me to this new report.

Thanks!

bugbot (bugbot)
affects: xorg (Ubuntu) → xserver-xorg-input-synaptics (Ubuntu)
Revision history for this message
Tony Espy (awe) wrote :

OK, I ran ubuntu-bug and it pointed me at lp: 943880. I'll make this a dup.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.