[Acer Aspire 5749] Mouse cannot click on items that have focus

[Sebastiaan]

With my Acer Aspire 5749 using Ubuntu 11.10 through 12.10, when I start, and login, everything works fine for a short moment, but after a while, my mouse doesn't seem to click anymore. When this arises I can still click on the sidebar, and in the menu of the application that has focus. However, clicking on an icon on my desktop doesn't work and clicking on a button, textfield, etc. inside an application does not work either.
I can still move around in the app (using <tab> and <enter>), but my mouse clicks do nothing. No left or right click, and no double click. I can still move the mouse and use the scroll part on my touchpad.

---
ApportVersion: 2.12.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: sabes 1897 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=02a1a7ef-d31f-4940-9f42-0f3da2e28e35
InstallationDate: Installed on 2013-12-29 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131229)
Lsusb:
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 04fc:2800 Sunplus Technology Co., Ltd
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire 5749
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-7-generic root=/dev/mapper/Volume00-lv_ubuntu ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
RelatedPackageVersions:
 linux-restricted-modules-3.12.0-7-generic N/A
 linux-backports-modules-3.12.0-7-generic N/A
 linux-firmware 1.117
Tags: trusty
Uname: Linux 3.12.0-7-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 07/28/2011
dmi.bios.vendor: INSYDE
dmi.bios.version: V1.05
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: HMA51_HR
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDE:bvrV1.05:bd07/28/2011:svnAcer:pnAspire5749:pvrV1.05:rvnAcer:rnHMA51_HR:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire 5749
dmi.product.version: V1.05
dmi.sys.vendor: Acer

[Sebastiaan (nebas)]

As i told, I had this issue during installation also, so I'm sure it's not all Guake, but using Guake, I saw that Guake had focus, but I could click on firefox instead. Seems that the mouseclick doesn't know what has focus.

[Sebastiaan (nebas)]

Just to inform. I restarted my laptop without guake, and had similar issues.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Sebastiaan (nebas)]

I have also appended to bug 41301 #197.
Furthermore Ive experienced this issue also with fedora (gnome) and Arch (KDE).

[penalvch (penalvch)]

Sebastiaan, could you please confirm this issue exists with the latest development release of Ubuntu? 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>

If reproducible, could you also please test the latest upstream kernel available (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. For example:
kernel-fixed-upstream-v3.13-rc5

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

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.

[Sebastiaan (nebas)]

apport information

[Sebastiaan (nebas)]

apport information

[Sebastiaan (nebas)]

apport information

[Sebastiaan (nebas)]

apport information

[Sebastiaan (nebas)]

apport information

[Sebastiaan (nebas)]

apport information

[Sebastiaan (nebas)]

apport information

[Sebastiaan (nebas)]

apport information

[Sebastiaan (nebas)]

apport information

[Sebastiaan (nebas)]

apport information

[Sebastiaan (nebas)]

apport information

[Sebastiaan (nebas)]

apport information

[Sebastiaan (nebas)]

apport information

[Sebastiaan (nebas)]

apport information

[Sebastiaan (nebas)]

apport information

[Sebastiaan (nebas)]

I have installed the iso that was pointed out:
http://cdimage.ubuntu.com/daily-live/current/
Issue still exists.

What I find interesting is this:
- The buttons bellow the touchpad seem to work worse than clicking on the touchpad itself. Sometimes, the left button does not work, while tapping the pad does. Furthermore, right click does not seem to work at all..
- I had the issue with the left button, but while I was typing (on my other laptop), the left button seemed the repair itselve: After a few minutes I tested it and it worked again.
- After regression it also seems that the focus issue arises (clicking on my desktop colored the circles in touchpad test thingy...).

I have 'apport-collect'ed as was requested.
B.t.w.: It returned the message: dpkg-query no package found matching linux...

I will test with the newest kernel tomorrow and then update tags e.a..

[Sebastiaan (nebas)]

I got a bit carried away and tested with mainstream kernel too. SImilar results. Can it be that the touchpad on my laptop is in conflict with the TP driver? It shure seems to look that way. ANyway,
- leftclick regresses after using
- rightclick does not seem to work,
- scroll does not seem to work either
- after a while clicking on desktop is a click in the TP test app...

I will update the status and tags as asked. (please let me know how to proceed.

P.s. I tested with 3.13.0-031300-rc5-generic (uname -a)...
And at first I could not even log in (coukd not select password box / typing did not work, etc.).
Up/Down buttons helped, and after that I could select and type PW...

P.p.s. I will try to get a Windwos version on my laptop tomorrow.
I will update firmware and test again. I'll get back to you on that one too...

[Sebastiaan (nebas)]

I just read your mail, and your right:
 sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
returns:
 V1.05 and 07/28/2011

As I allready pointed out, updating is a real bummer, since it needs WIndows,
And I don't have any working version available. But I will try to obtain one
and get back after I have updated the bios...
Sorry to be of any inconvenience (if I have been)...

Op zondag 29 december 2013 21:23:43 schreef u:
> Sebastiaan, thank you for apport-collect'ing in Trusty. As per
> http://us.acer.com/ac/en/US/content/drivers an update is available for your
> BIOS (1.08). 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 just 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.
>
> For more on BIOS updates and linux, please see
> https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
> .
>
> Thank you for your understanding.
>
> ** Description changed:
>
> With my Acer Aspire 5749 using Ubuntu 11.10 through 12.10, when I start,
> and login, everything works fine for a short moment, but after a while, my
> mouse doesn't seem to click anymore. When this arises I can still click on
> the sidebar, and in the menu of the application that has focus. However,
> clicking on an icon on my desktop doesn't work and clicking on a button,
> textfield, etc. inside an application does not work either. I can still
> move around in the app (using <tab> and <enter>), but my mouse clicks do
> nothing. No left or right click, and no double click. I can still move the
> mouse and use the scroll part on my touchpad.
>
> - ProblemType: Bug
> - DistroRelease: Ubuntu 12.10
> - Package: unity 6.10.0-0ubuntu2
> - ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
> - Uname: Linux 3.5.0-21-generic x86_64
> - ApportVersion: 2.6.1-0ubuntu9
> - Architecture: amd64
> - CompizPlugins:
> [core,bailer,detection,composite,opengl,decor,move,regex,place,gnomecompat,
> animation,snap,compiztoolbox,mousepoll,workarounds,vpswitch,session,grid,res
> ize,imgpng,unitymtgrabhandles,wall,expo,ezoom,fade,scale,unityshell] - Date:
> Fri Jan 4 13:33:55 2013
> - InstallationDate: Installed on 2012-02-04 (334 days ago)
> - InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64
> (20111012) - MarkForUpload: True
> - SourcePackage: unity
> - UpgradeStatus: Upgraded to quantal on 2012-12-22 (12 days ago)
> - ---
> + ---
> ApportVersion: 2.12.7-0ubuntu3
> Architecture: amd64
> AudioDevicesInUse:
> - USER PID ACCESS COMMAND
> - /dev/snd/controlC0: sabes 1897 F.... pulseaudio
> + USER PID ACCESS COMMAND
> + /dev/snd/controlC0: sabes 1897 F.... pulseaudio
> CurrentDesktop: Unity
> DistroRelease: Ubuntu 14.04
> HibernationDevice: RESUME=UUID=02a1a7ef-d31f-4940-9f42-0f3da2e28e35
> InstallationDate: Installed on 2013-12-29 (0 days ago)
> InstallationMedia: Ubuntu 14.04 LTS "T...

[Sebastiaan (nebas)]

Updating BIOS was a real headbanger.
In the end I downloaded a dos live usb image and have succesfully updated my BIOS.
It now all seems better. dmi-decode thingies say:
  V1.08
  11/29/2011
and touchpad seem to function rather great (with Arch, with latest upstream kernel and with latest development release).
Seems I've also been derailled by the touchpad acting differently than on my other laptop.
Scroll is two-fingers, as is right click. I guess button below is a single mouse button (or at least it acts like that).

Anyway, thing I keep having is that on boot I cannot login. The password box seems to have focus, but typing does nothing.
Workaround I use is:
-> CTL-ALT-F1 ALT-F7 (After wich I can change focus to other elements)
-> wander around at the top right corner (change focus from password box???)
-> reselect password box

Thing is that in Arch I have a simillar focus issue that I can only resolve by CTL-ALT-F1 ALT-F7.
So I still can only use Linux after 'resetting some things' by the WA.
And this WA was the only thing that helped me when I had the focus issue.
So, I guess that the issue could have been resolved for about 90% with bios update, but now only needs a one-time reset with the WA?

Could be that the login issue is a different one. I will try without login and I will try with Ubuntu Desktop 13-10. If that helps, I will retry with a reinstall of the latest development release...

[Sebastiaan (nebas)]

Latest update: Even without login screen, I cannot shift focus without Workaround (CTL-ALT-F1 ALT-F7). I could start the touchpad test app, but clicking did nothing in the app. After WA all seemed ok.
i think that for now it is only an 'initial setting' thing (after boot)...

[penalvch (penalvch)]

Sebastiaan, thank you for updating your BIOS. Just to clarify your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096042/comments/26 and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096042/comments/27 :
+ What release are you now testing specifically?
+ In this release you are testing, with the logging in issue, and having to perform a WORKAROUND (not WA), is this new or has it always been this way?

[Sebastiaan (nebas)]

Just to summarize:
I have tested the following:
- Ubuntu 12.04 / 12.10 with BIOS 1.06: Initialization issue, with Regression
- Fedora F16 with BIOS 1.06: Initialization issue, with Regression
- Arch (since nov 2013) with BIOS 1.06: Initialization issue, with Regression
- Ubuntu 13.10 LiveCD with BIOS 1.06: Initialization issue, with Regression
- Ubunu Trusty Daily Live (29/12/2013) with BIOS 1.06: Initialization issue, with Regression
- Ubunu Trusty Daily Live (29/12/2013) with kernel 3.13rc5 and BIOS 1.06: Initialization issue, with Regression
- Ubunu Trusty Daily Live (29/12/2013) with kernel 3.13rc5 and BIOS 1.08: Initialization issue
- Ubunu Trusty Daily Live (29/12/2013) with original kernel (3.12.07) and BIOS 1.08: Initialization issue
- Arch (29/12/2013) with BIOS 1.08: Initialization issue

Initialization issue means, that just after boot focus cannot shift to another object. You can move the mouse, but cannot select another object by clicking on it. Not with button and not with tipping the pad. Furthermore: Scrolling does not work either. And tipping with both fingers (right click) doesn't work either. It looks as if the pad works for moving the mouse, but nothing else. Work around for this is to switch to console (CTRL-ALT-F1) and switch back (ALT-F7). After that the touchpad works as it should.

Regression means that by using the touchpad it works less and less. At first, the button starts disfunctioning. Then tapping the pad disfunctions as well. I have not testes scrolling / right click. It seems to be coupled to usage and not time. If you don't use the pad for a period it will not regress any further. It even seems to 'fix' a little. Workaround for this issue is the same: Switch to console (CTRL-ALT-F1) and switch back (ALT-F7). After that the touchpad works as it should (for a litle while until regression kicks in again).

It is save to say that 'Regression' is fixed by BIOS 1.08 and Initialization issue is not. So lets skip the 'Regression' part from now on.

What I can test from now on is:
- Arch (it's already there, but I don't think you will do tomuch with it... Perhaps for comparison?)
- Install 13.10 (not LiveCD, but installation)
- Reinstall Trusty Daily Live
- Reinstall Trusty Daily Live and add latest upstream kernel.

I can install them all together (Different Logical Volumes), but I guess that in the end 'Trusty Daily Live and add latest upstream kernel' is the way to go from her on, yes?

My suggestion is:
- Install 13.10 and check the outcome with BIOS 1.08
- Reinstall Trusty Daily Live in a new LV. Check the outcome
- Add latest upstream kernel. Check the outcome

Expectation: I think they will all show the same symptom (initialization issue). From there on 'Trusty Daily Live and latest upstream kernel' is the best way to try and fix. Please let me know if I should proceed with this.

P.s. I introduced the workaround in november 2013 and it always seems to fix both 'initialization issue' and 'regression' (in all distributions and all window managers). Don't know for sure, but I think also with Ubuntu 12.10 and even before. And with borth BIOS 1.06 and 1.08.

Let me know how to proceed.

[penalvch (penalvch)]

Sebastiaan, thank you for your comments. Just as an FYI, any tests you did with the old 1.06 BIOS aren't considered valid for the purposes of troubleshooting this bug. Hence, for regression testing purposes, could you please test Lucid via http://old-releases.ubuntu.com/releases/lucid/ and advise to the results?

[Sebastiaan (nebas)]

I figured that much. I'm downloading Lucid right now. I'll get back to you.

[Sebastiaan (nebas)]

I have some exciting news. Been trying to install ubuntu10.04 but ran into some issues (creating usb device).
Anyway, I figured I'd instal 12.04 LTS first, and create usb device with Startup Disk Creator using 12.04LTS.
Thing is that using 12.04 LTS (without updates) the Touchpad seems to work just fine. And even as expected, meening:
- left button click works,
- right button click works,
- scrollbar works (this doesnt work with Ubuntu 13 / 14 and not with Arch).

The mouse/touchpad tester is called differently in 12.04 than in 13 / 14.
And it does not have the test window (but a smiley), but that works fine.
Just installed all updates and no issues have reappeared.

So I can add this to the list:
- Ubuntu 12.04 LTS (kernel 3.8.0-29) with BIOS 1.08: Everything works like a charm...

I will reinstall 14.04 (dev) and test with that later...

[Sebastiaan (nebas)]

Just finished installing Trusty Tahr and guess what. Everything works like a charm. This is:
- left button click works,
- right button click works,
- two finger tap is right click (there are now 2 ways for right click...)
- scrollbar works (if I disable option 'two finger scroll').
- 'two finger scroll' works (if I enable option 'two finger scroll').

Seems to be like this:
- Installed using bios 1.06. Everything broken.
- Upgraded bios to 1.08. Better, but need WorkAround once every boot to initialize.
- Reinstalled. Everything ok.

Could it be that the 1.06 bios presented the touchpad wrong, so that during installation the wrong config was enabled?
Could remove and reinstall of the touchpad driver, or install other kernel fix this?
Anyway, it now works for me. Sorry to bother you (seems that older bios WAS the issue all along).
And thanks for your help in fixing it. Hope this will inform others how to fix if they (already have) run into this issue too.
And, happy new year :)...