button1 gets stuck after a while

there's a thread on xorg-devel@ about turning off support for multitouch by default, and the discussion led to the main input developer reproducing the issue himself. We might have a patch early next week.

..it's a bug in the xserver.

Note this is easy to reproduce after running xrotate

My findings show that it's trivial to reproduce with unity by opening menus quickly (indicator menus for instance). Can't reproduce it with plain metacity. One way to mitigate the issue is to use the gui in a more "relaxed" manner :) That should make it harder to hit the race condition with input grabs.

and the issue seen after using xrotate to switch to portrait mode is something else (cursor jumping here and there), since it works fine after rotating back to landscape.

lilstevie on #ubuntu-arm says they saw the same behaviour on the Transformer Prime when running Unity.

I'm able to reproduce the issue in a reasonably reliable manner on a Dell XPS L502X laptop (it has a touchscreen) by rapidly tapping on the indicators in the top right corner of the screen.

Hi Daniel,

Don't use In Progress to mean you are trying to reproduce the bug, only if you are actually working on fixing it.

I was actually working on fixing it, but a couple of days ago I've moved to work on something else. Thus the status change.

Sorry if the above comment seemed rather blunt - I was only trying to discover if you've changed the status to Confirmed because you're no longer working on it? If you are still working on it then it should remain at 'In Progress' - and thanks either way :) !

Assigning to the Desktop team as Daniel is being move to work on something else

Is there a way to reset or free this lock via command line, so you do not have to log out/restart.
One could use this as a "snippet" for onboard since this seems to work during that condition.

sadly no, once it is stuck, it is stuck

you probably thought everything through, but i can't help to ask. would it help as a temporary solution to disable multitouch and allow single touch input only. Then distinguishing only between single click (long as right click) and dragging.

I can reproduce this bug with 100% reliability in E17.

http://www.enlightenment.org/p.php?p=download

well ok - i'm using svn development, but i think last release (0.17.1 and efl 1.7.5) should produce the bug too as i noticed this issue just before 0.17 release too. install that (sorry source - there are ppa's but i dont know if there's an arm build. i compiled). i also have set up my n7 to run in portrait mode by default (~/.xsession sets it up).

now its installed, select enlightenment as your desktop (u may have to ln -s enlightenment.desktop from /usr/local/share/xsessions if u compiled into /usr/share/xsessions). go through the wizard and choose "mobile" profile. you pretty much can ignore everything except the small white arrow pointing down on the top-0left once the wizard is done...

DONT TOUCH that arrow... yet. notice u can click on most things and they work... now press that top-left arrow. its the "start button"... up comes a start menu... u can interact with it... and after that... clicks cease to work. this is 100% reliably reproduces on my nexus7/... it ALSO happens on my exopc too. so this is a general issue with xorg/xinput etc.

anyway - now i've spent some time digging into what's going on, and here's the low-down. wm's use passive button grabs (XGrabButton) for focus handling. they then do an XAllowEvents to allow the button grab to proceed to a child. after some sequence of mouse grabbing is done by popping up that menu, XAllowEvents ceases to ever work again (it never forwards a held button press event ever agin) for the duration of the xserver lifetime. i wrote a "test case" (attached) to show that the parent gets the events, simply calls xallowevents and it never goes to the child window ever again. this test client works fine until the "bug is triggered" then fails. (i shut down the wm but kept x alive and ran the test client to "prove this" - it works fine until the bug is triggered). unfortunately at this point i have yet to make a simple "trigger the bug" client, BUT i am sure it has something to do with a combination of:

1. button press handled after an xallowevents allowed it through
2. an xgrabpointer (unlikely an xgrabkeyboard).
3. some combination of user events (eg mouse/finger not being releases while the above allowevents and grab is going on).

after this "magic sequence" which also likely is race-condition sensitive, the xservers internal input handling is "busted" and xallowevents are broken until an xserver restart (restarting wm doesn't fix it - nor does totally killing the wm and bringing up test clients in its place as above).

so i'll have to say "sorry" in that i'm going to waste some peoples time by only having "more info" without a simple "reproduction case" in a simple contained src blob. i'd hope to have that, but currently don't. what i DO have is a 100% reliable "big fat bulky" reproduction case (e17+efl) AND... i have a simple test client to prove/show what the "stuck" thing is (allowevents of button press fails forever after triggering of the bug). given some more time/weekends i might be able to make such a client. the above was a saturday spent hunting for "what on earth is wrong", so...

please test the xserver from this ppa once it's built, it has a few proposed fixes merged from the upstream bug:

https://launchpad.net/~ubuntu-nexus7/+archive/ppa

It failed:

 Build status

[image: [FAILEDTOBUILD]] Failed to build on
hamsa<https://launchpad.net/builders/hamsa>

   - Started 18 minutes ago
   - Finished 11 minutes ago (took 7 minutes, 43.4 seconds)
   - buildlog<https://launchpad.net/%7Eubuntu-nexus7/+archive/ppa/+build/4300026/+files/buildlog_ubuntu-raring-armhf.xorg-server_2%3A1.13.2-0ubuntu2.1_FAILEDTOBUILD.txt.gz>(16.2
KiB)

On Thu, Feb 14, 2013 at 3:58 AM, Timo Aaltonen <email address hidden> wrote:

> please test the xserver from this ppa once it's built, it has a few
> proposed fixes merged from the upstream bug:
>
> https://launchpad.net/~ubuntu-nexus7/+archive/ppa
>
> ** Changed in: ubuntu-nexus7
> Status: Confirmed => Incomplete
>
> ** Changed in: ubuntu-nexus7
> Assignee: Canonical X.org (canonical-x) => Timo Aaltonen (tjaalton)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1068994
>
> Title:
> button1 gets stuck after a while
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-nexus7/+bug/1068994/+subscriptions
>

--
Cláudio "Patola" Sampaio
IRC: ptl - Yahoo: patolaaa
Campinas, SP - Brazil.

bah, messed up with the patch, will fix it soon

new build is there, but I was able to test it myself and it's still broken.

On Thu, Feb 14, 2013 at 11:19 AM, Timo Aaltonen <email address hidden> wrote:

> new build is there, but I was able to test it myself and it's still
> broken.
>

Same here. However, it really seemed that the bug took longer than usual to
appear.

Should I keep this repository "just in case" (the bug will be solved on it
first, I suppose) or it might wreck my Ubuntu anytime?
--
Cláudio "Patola" Sampaio
IRC: ptl - Yahoo: patolaaa
Campinas, SP - Brazil.

Patola: shouldn't wreck, but maybe disable to be safe.

Carsten: I built e17 0.17.1 and libs 1.7.5 from this ppa: https://launchpad.net/~efl/+archive/trunk/+packages
and couldn't reproduce the bug with xserver 1.13.99.901. Is the e17 release fresh enough? It did have the mobile profile to select, so guess it support touch..

also, I have the deb's built for raring armhf here if someone wants to try reproduce the bug with them:

http://people.canonical.com/~tjaalton/e17-deb/

Is this bug still going to be worked on? It was a surprise to see that Ubuntu "phablet" did not use X. Is this why this bug has not been resolved yet? What is the status of "complete Ubuntu under Nexus 7" vs. "Ubuntu Phablet under Nexus 7"?

upstream has a testcase for this now, should get fixed within the next week..

suffering from same issue :(
my tablet x86 tested distros
android-x86 - all ok
bodhi 2.3 - E17 same issue, after theme choose lc not works
ubuntu
-- unity mouse0 hang after 1-4 clicks
-- awn (Avant Window Navigator if im not mistaken) ... strange but no hungs .. just works
-- netbook-remix some controls works, some not (Qt framework issues?)
plasma active (KDE+Qt)
-- kubuntu .. not working, some icons can be clicked(+right sidebar rotates and drags) but dragging down main menu fails
-- basyskom-plasma-active-three-wetab-exopc-tablet-mer-relase.iso ( distro based on meego,mer,zypper) all works, uses Xorg 1.10

This change looks pretty big, is there any chance that we can SRU this for precise? The reason I ask is because it's a LTS release and we have a fair amount of hardware that is failing here: http://patchwork.freedesktop.org/patch/13650/

What are the steps to test this regarding the two comments above? I'm assuming:

1) Download and flash the latest saucy preinstalled image.
2) Add the x-staging PPA and do an update/upgrade.
3) Use the newest onboard <--- How do I do this?

This is fixed in the X version in the x-staging PPA. Will this fix make it into Saucy (and so make tablet mode of convertibles usable)?

I got this bug on my laptop running 13.04 (BTW I think bug #946417 is a duplicate of this one). It causes the touchscreen to not work after several clicks.

I tried running the X from x-staging PPA (add-apt-repository ...; apt-get update; apt-get dist-upgrade; service lightdm restart). After I login, the screen shows a background for some seconds and then a blank screen. ~/.xsession-errors shows these lines:

[several lines about loading/starting plugins...]
compiz (core) - Info: Loading plugin: unityshell
gnome-session[2238]: WARNING: Child process 2352 was already dead.
gnome-session[2238]: WARNING: Application 'compiz.desktop' killed by signal 11
gnome-session[2238]: WARNING: App 'compiz.desktop' respawning too quickly
gnome-session[2238]: CRITICAL: We failed, but the fail whale is dead. Sorry....

Do I need to use any other PPA to avoid the compiz crash?

Hi again,

After some investigation, I found that the compiz segfault was due to an undefined symbol:

compiz (core) - Debug: dlopen failed: /usr/lib/compiz/libunityshell.so: undefined symbol: XFixesSelectBarrierInput

I downgraded libxfixes3 to 1:5.0-4ubuntu5.13.04.1 and was able to start Unity properly... But now I found out that the x-org-server package on the x-staging PPA was not updated for raring, only saucy :(

Will try to compile myself, but if you could backport it to raring, I would appreciate.

I gave up and simply upgraded to saucy. So far, I did not have any touchscreen issues, so I've not tried the x-staging PPA for saucy yet.

the nexus7 either works or not, there might still be a chance of hitting another race but closing anyway

This also affects me on Asus S400CA with Ubuntu 13.04

This is reportedly fixed in saucy, I've set up a preliminary backport of the saucy xserver in ppa:ubuntu-x-swat/s-lts-backport can you verify that using this xserver fixes the bug?

We have confirmed that the current s-lts-backport fixes the issues as we have seen them.

So, marking as Fix Released for Saucy and we will wait for 12.04.4 for a fix in Precise.

Thanks!

Will there be a fix for 13.04 64-bit as well?

LJ: no, too big set of patches to backport

ok, so upgrading to 13.10 is the only option?

Tracked on Precise for 12.04.4

12.04.4 is now released. Marking as Fix Released in the OEM priority project

In ubuntu 14.04 everything seems to be normal.
But when i tried kubuntu 14.04 there was a big similar to this. I can tap the screen but there is no click event. Also some of the windows are "running away" if you're clicking on them. (similar button-stuck behaviour on suse (especially when I tried toucegg (in terminal there was one key repeated constantly))).
My device is acer W700.

Hi all,
Would really love to get my N7 running ubuntu normally.
I just tried a dist upgrade and the issue still remains in Raring.

Please can someone provide more instructions on getting this fix into the N7 ?

raring is EOL, and later versions don't have a working tegra3 X driver anymore, so you're out of luck

I'm on 13.04 on a Nexus7 too and I really would love to find a way to apply these patches, even manually.
Is someone willing to point me to the right direction?
Thank you in advance!