[hardy] Cannot unlock touchpad FSC V5505

Bug #227202 reported by cbrmichi
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xserver-xorg-input-synaptics (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I got a Fujitsu Siemens v5505. I can LOCK the touchpad by pressing FN+F6, but I cannot UNLOCK it. so i have to boot windows to be able to unlock the touchpad.

Tags: hardy natty
Revision history for this message
Bryce Harrington (bryce) wrote :

Hi cbrmichi,

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISOs are available from cdimage.ubuntu.com)

If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
Thanks in advance.

The output of lspci -vvnn would also be worth having.

Changed in xorg:
status: New → Incomplete
Revision history for this message
cbrmichi (cbrmichi) wrote :

Hi Bryce,

i attached a zip file with the outputs of 3 different tries.
at first, i locked the touchpad. i could not unlock die touchpad, so i connected my mouse and did a reboot. after reboot the touchpad was unlocked. i disconnected the mouse, did a X restart and then copied the output. so i saved the output (directory "trackpad") and did another try.

so i locked the touchpad one more time and rebootet without connecting a mouse and saved the output (directory "no touchpad").
after that i connected my mouse and rebootet one more time. but now the touchpad was not unlocked. because the Xorg.0.log was a little bit different i attached this outputs, too (directory "no touchpad - reboot with mouse").

Revision history for this message
cbrmichi (cbrmichi) wrote :

now i pressed the lock/unlock button about 20 times and did another reboot with mouse, now the touchpad is unlocked. :-D

here are the 2 output files

Bryce Harrington (bryce)
Changed in xorg:
importance: Undecided → Medium
status: Incomplete → Confirmed
Bryce Harrington (bryce)
tags: added: hardy
Revision history for this message
Igor Wawrzyniak (igor-tumus) wrote :

Still a bug in Karmic.

Revision history for this message
bugbot (bugbot) wrote :

This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?

If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under natty, please tag the bug 'natty'
so it's easier for us to track.

Changed in xserver-xorg-input-synaptics (Ubuntu):
status: Confirmed → New
status: New → Incomplete
Revision history for this message
Igor Wawrzyniak (igor-tumus) wrote :

I've got the same laptop, but it's not running Ubuntu now. However the bug is still present in Debian Squeeze. If nobody else reports in a few days, I'll boot Natty from live CD to confirm.

Bryce Harrington (bryce)
Changed in xserver-xorg-input-synaptics (Ubuntu):
status: Incomplete → New
status: New → Incomplete
Revision history for this message
Igor Wawrzyniak (igor-tumus) wrote :

Confirmed in natty.

tags: added: natty
removed: hardy
Changed in xserver-xorg-input-synaptics (Ubuntu):
status: Incomplete → Confirmed
bugbot (bugbot)
tags: added: hardy
Revision history for this message
Ahmed Shams (ashams) wrote :

Sadly, not always, we have capacity to triage bugs. To be able to forward it to a developer, it needs to be well-documented. If you still can reproduce this bug on one of the supported release, please run the following command from your Terminal(Ctrl+Alt+T):
apport-collect 227202

Changed in xserver-xorg-input-synaptics (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for xserver-xorg-input-synaptics (Ubuntu) because there has been no activity for 60 days.]

Changed in xserver-xorg-input-synaptics (Ubuntu):
status: Incomplete → Expired
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.