[Dell Inspiron 5547] - touchpad locks on select and unable to unlock

[Phil]

I have a new Dell Inspiron 5547, I am dual booting with ubuntu 14.04.1 and win 8.1. When running on ubuntu, I am using touchpad exclusively, and sometimes the touchpad gets locked into selection and I am unable to unlock. I have tried hitting ESC, tabbing to another window, but unable to unlock. I have other symptons (cursor jumps to other lines of text when typing, cusor jumps to last icon on launch pad), but I think those are all related.

I have tried disabling touchpad when typing but to no avail. It also sometimes seems that this sympthon sometimes survies a reboot.

sudo xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ DLL063E:00 06CB:2934 id=11 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad 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)]
    ↳ Video Bus id=7 [slave keyboard (3)]
    ↳ Power Button id=8 [slave keyboard (3)]
    ↳ Sleep Button id=9 [slave keyboard (3)]
    ↳ Integrated_Webcam_HD id=10 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)]
    ↳ Dell WMI hotkeys id=14 [slave keyboard (3)]

pme991@tcllp-1:/usr/local$ lsb_release -rd
Description: Ubuntu 14.04.1 LTS
Release: 14.04

I appreciate any guidance or assistance.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-36-generic 3.13.0-36.63
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Uname: Linux 3.13.0-36-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: pme991 2084 F.... pulseaudio
 /dev/snd/controlC1: pme991 2084 F.... pulseaudio
CurrentDesktop: Unity
Date: Thu Sep 25 16:57:22 2014
HibernationDevice: RESUME=UUID=f38517c4-e36a-4946-9bea-30c050152453
InstallationDate: Installed on 2014-09-16 (9 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Dell Inc. Inspiron 5547
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed root=UUID=af854011-dbd6-4233-843b-7a8178702c5b ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-36-generic N/A
 linux-backports-modules-3.13.0-36-generic N/A
 linux-firmware 1.127.6
SourcePackage: linux
StagingDrivers: rts5139
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/20/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A02
dmi.board.name: 0598GM
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A02
dmi.modalias: dmi:bvnDellInc.:bvrA02:bd03/20/2014:svnDellInc.:pnInspiron5547:pvrA02:rvnDellInc.:rn0598GM:rvrA00:cvnDellInc.:ct8:cvrA02:
dmi.product.name: Inspiron 5547
dmi.product.version: A02
dmi.sys.vendor: Dell Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Phil (pme991)]

sycnclient output is attached.

[Phil (pme991)]

Not sure but maybe related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1272624

[Phil (pme991)]

Chris,

Thank for for the BIOS update information. I dl'd the BIOS update and
applied it to my laptop. I upgraded from A02 -> A04, new Dell laptop
bought in Sep '14 had old BIOS even though BIOS A04 was released in May.

I ran the command you requested:

 >>
sudo dmidecode -s bios-version & sudo dmidecode -s bios-release-date
[1] 2872
A04
05/09/2014

 >>

As I just applied this BIOS so I will run for a day and determine if it
helped any.

Thanks

On 09/28/2014 03:20 PM, Christopher M. Penalver wrote:
> Phil, thank you for reporting this and helping make Ubuntu better. As per http://www.dell.com/support/home/us/en/04/product-support/product/inspiron-15-5547-laptop/drivers an update to your BIOS is available (A04). If you update to this following https://help.ubuntu.com/community/BiosUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command:
> sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
>
> Please note your current BIOS is already in the Bug Description, so
> posting this on the old BIOS would not be helpful. As well, you don't
> have to create a new bug report.
>
> For more on BIOS updates and linux, please see
> https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
> .
>
> Once the BIOS is updated, then please mark this report Status Confirmed.
>
> Thank you for your understanding.
>
> ** Tags added: latest-bios-a04
>
> ** Tags removed: latest-bios-a04
> ** Tags added: bios-outdated-a04
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>

[Phil (pme991)]

BIOS was updated to A04, issue is still occuring, although there does seem to be some minor improvement in severity of issue. Now I don't have to reboot system when cursor is in text selection mode. Issue - When using using touchpad, cursor will select text when moving cursor around, then it will only highlight text selected when cursor is moved using touchpad. It is difficult to get touchpad out of text selection mode, have to hit escape and arrow key. This issue is intermittent.

I ran the command you requested:

 >>
sudo dmidecode -s bios-version & sudo dmidecode -s bios-release-date
[1] 2872
A04
05/09/2014

 >>

[penalvch (penalvch)]

Phil, could you please test the latest upstream kernel available from the very top line at the top of the page (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. 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 exactly shown as:
kernel-fixed-upstream-3.17-rc7

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.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-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.

[Phil (pme991)]

Chris,

I followed instructions in email below, installed latest upstream kernel
packages:

linux-headers-3.17.0-031700-generic_3.17.0-031700.201410060605_i386.deb
<http://kernel.ubuntu.com/%7Ekernel-ppa/mainline/v3.17-utopic/linux-headers-3.17.0-031700-generic_3.17.0-031700.201410060605_i386.deb>

linux-headers-3.17.0-031700_3.17.0-031700.201410060605_all.deb
<http://kernel.ubuntu.com/%7Ekernel-ppa/mainline/v3.17-utopic/linux-headers-3.17.0-031700_3.17.0-031700.201410060605_all.deb>
linux-image-3.17.0-031700-generic_3.17.0-031700.201410060605_i386.deb
<http://kernel.ubuntu.com/%7Ekernel-ppa/mainline/v3.17-utopic/linux-image-3.17.0-031700-generic_3.17.0-031700.201410060605_i386.deb>

Package installation was successful, unfortunately during rebooting I
received a kernel panic, "no init parameters". Unfortunately, I am not
able to proceed further, any guidance is appreciate.

Thanks,

Phil
On 10/01/2014 03:28 AM, Christopher M. Penalver wrote:
> Phil, could you please test the latest upstream kernel available from the very top line at the top of the page (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. 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 exactly shown as:
> kernel-fixed-upstream-3.17-rc7
>
> 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.
>
> If the mainline kernel does not fix this bug, please add the following tags:
> kernel-bug-exists-upstream
> kernel-bug-exists-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.
>
> ** Tags removed: bios-outdated-a04
> ** Tags added: latest-bios-a04
>
> ** Changed in: linux (Ubuntu)
> Importance: Low => High
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>

[penalvch (penalvch)]

Phil, would 3.17-rc7 allow you to do a test?

[Phil (pme991)]

Chris,

I dl'd and installed 3.17-rc7:

linux-headers-3.17.0-031700rc7_3.17.0-031700rc7.201409281835_all.deb
linux-headers-3.17.0-031700rc7-generic_3.17.0-031700rc7.201409281835_i386.deb
linux-image-3.17.0-031700rc7-generic_3.17.0-031700rc7.201409281835_i386.deb

But upon reboot to run new kernel, 3.17-rc7 was worse. Seems that the
after it stated "loading ramdisk" it just provided a blank screen
nothing else. It never loaded the new kernel, not even a panic.

Thanks,

Phil M.

On 10/07/2014 01:26 AM, Christopher M. Penalver wrote:
> Phil, would 3.17-rc7 allow you to do a test?
>

[Phil (pme991)]

Chris,

I found out what my issue was with loading upstream kernel - "user
error". I needed to select correct kernel flavor "amd64". I was able
to install the following upstream kernel.

linux-headers-3.17.0-031700_3.17.0-031700.201410060605_all.deb
linux-headers-3.17.0-031700-generic_3.17.0-031700.201410060605_amd64.deb
linux-image-3.17.0-031700-generic_3.17.0-031700.201410060605_amd64.deb

I will test today and provide you feedback.

Thanks,

Phil M.
On 10/07/2014 01:26 AM, Christopher M. Penalver wrote:
> Phil, would 3.17-rc7 allow you to do a test?
>

[penalvch (penalvch)]

Phil, in order to satisfy upstream's testing requirements, you would want to test successively older kernel versions until you get to something that would be testable.

[Launchpad Janitor (janitor)]

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

[Marcin (marcincelebucki)]

The issue is still there, also on Ubuntu 15.10

[penalvch (penalvch)]

Marcin, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.