[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: xorg-server (Ubuntu Precise) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in HWE Next: Fix Released Status in HWE Next saucy series: Fix Released Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Precise: Won't Fix Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:51:23,756 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=88133c52-550c-4c43-9da5-15f180bdb767 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to quantal on 2012-06-19 (0 days ago) dmi.bios.date: 09/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: AMD HUDSON-M1 dmi.board.vendor: ZOTAC dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd09/22/2011:svn:pn:pvr:rvnZOTAC:rnAMDHUDSON-M1:rvr:cvn:ct3:cvr: version.compiz:
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
** Changed in: hwe-next Assignee: James M. Leddy (jm-leddy) => (unassigned) ** Also affects: hwe-next/saucy Importance: Undecided Status: In Progress ** Changed in: hwe-next/saucy Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in HWE Next Project: Fix Released Status in HWE Next saucy series: Fix Released Status in X.Org X server: Fix Released Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server” source package in Precise: New Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:51:23,756 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=88133c52-550c-4c43-9da5-15f180bdb767 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to quantal on 2012-06-19 (0 days ago) dmi.bios.date: 09/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: AMD HUDSON-M1 dmi.board.vendor: ZOTAC dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd09/2
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
It should be fixable on precise by installing xserver-xorg-lts-saucy. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in HWE Next Project: In Progress Status in X.Org X server: Fix Released Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server” source package in Precise: New Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:51:23,756 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=88133c52-550c-4c43-9da5-15f180bdb767 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to quantal on 2012-06-19 (0 days ago) dmi.bios.date: 09/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: AMD HUDSON-M1 dmi.board.vendor: ZOTAC dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd09/22/2011:svn:pn:pvr:rvnZOTAC:rnAMDHUDSON-M1:rvr:cvn:ct3:cvr: version.compiz: compiz 1:0.9.7.8-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.33-1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
This is quite a severe bug. If you have a touchscreen connected, and you have touched it at some point: 1) start gitk or tkinfo or a recent Qt Creator (or probably many other Qt 5 programs) 2) scroll some long text with the mouse wheel 3) move the mouse It selects text as if the left mouse button was being pressed. So in other words if you have a touchscreen your mouse wheel isn't very useful anymore in certain applications. I think it should be fixed in 12.04 too, not just in newer releases. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in HWE Next Project: In Progress Status in X.Org X server: Fix Released Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server” source package in Precise: New Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:51:23,756 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=88133c52-550c-4c43-9da5-15f180bdb767 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to quantal on 2012-06-19 (0 days ago) dmi.bios.date: 09/22/20
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
Hi all, The patch I posted previously had a bug in xf86UnrealizeCursor(). I had accidentally used dixLookupScreenPrivate(), when I should have used dixLookupPrivate(). The attached patch is an update with the fix. Chris ** Patch added: "Rev 2 of 12.04 xserver backport patch" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1015183/+attachment/3924358/+files/517-touchscreen_fixes2.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in HWE Next Project: In Progress Status in X.Org X server: Fix Released Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server” source package in Precise: New Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:51:23,756 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=88133c52-550c-4c43-9da5-15f180bdb767 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to quantal on 2012-06-19 (0 days ago) dmi.bios.date: 09/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: AMD H
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
Can someone sum up what we have to do in 13.04 to get rid of the stuck click problem? I am new to ubuntu, I have installed ubuntu 13.04 on my nexus 7. When I dist-upgrade from ppa:canonical-x/x-staging, it just boot up to a black screen. I get notification or error and I have anotification that I am connected to my network but desktop is black. What do I do? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in HWE Next Project: In Progress Status in X.Org X server: Fix Released Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server” source package in Precise: New Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:51:23,756 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=88133c52-550c-4c43-9da5-15f180bdb767 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to quantal on 2012-06-19 (0 days ago) dmi.bios.date: 09/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: AMD HUDSON-M1 dmi.board.vendor: ZOTAC dmi.chass
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
For folks using Ubuntu 12.04LTS, and can't use the quantal/raring/newer X server (due to whatever reasons, like maybe a binary-only video driver for a "legacy" video card), this patch may work for you. It's a first attempt at backporting Peter Hutterer's touch-grab-race- condition-56578-v3 branch. Some sections aren't pretty due to all the indentation changes, but it works for me. :) The patch was done mostly by hand. In order to use the patch you have to comment out the following from the series file: 505_query_pointer_touchscreen.patch 506_touchscreen_pointer_emulation_checks.patch 507_touchscreen_fixes.patch Let me re-state, this patch is for xserver-xorg- core_1.11.4-0ubuntu10.*.deb Specifically I based it off of xserver- xorg-core_1.11.4-0ubuntu10.14_i386.deb Please let me know what you think. Thanks! Chris ** Patch added: "first attempt at 12.04 LTS xserver fix for touchscreen bugs" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1015183/+attachment/3907108/+files/517-touchscreen_fixes2.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in HWE Next Project: In Progress Status in X.Org X server: Fix Released Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server” source package in Precise: New Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:5
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
Upstream marked this as fixed. So this should be fixed in saucy now. Backporting this is non-trivial, and it might be easier to test if using a newer version of onboard fixes this problem. Newer versions of onboard workaround it by using xi2 events directly. ** Also affects: xorg-server (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: In Progress => Fix Released ** Changed in: xorg-server (Ubuntu Precise) Assignee: (unassigned) => Maarten Lankhorst (mlankhorst) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in HWE Next Project: In Progress Status in X.Org X server: Fix Released Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server” source package in Precise: New Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:51:23,756 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=88133c52-550c-4c43-9da5-15f180bdb767 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to quantal on 2012-06-19 (0 da
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
** Changed in: xorg-server Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in HWE Next Project: In Progress Status in X.Org X server: Fix Released Status in “xorg-server” package in Ubuntu: In Progress Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:51:23,756 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=88133c52-550c-4c43-9da5-15f180bdb767 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to quantal on 2012-06-19 (0 days ago) dmi.bios.date: 09/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: AMD HUDSON-M1 dmi.board.vendor: ZOTAC dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd09/22/2011:svn:pn:pvr:rvnZOTAC:rnAMDHUDSON-M1:rvr:cvn:ct3:cvr: version.compiz: compiz 1:0.9.7.8-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.33-1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
** Changed in: hwe-next Status: New => In Progress ** Changed in: hwe-next Assignee: (unassigned) => James M. Leddy (jm-leddy) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in HWE Next Project: In Progress Status in X.Org X server: In Progress Status in “xorg-server” package in Ubuntu: In Progress Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:51:23,756 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=88133c52-550c-4c43-9da5-15f180bdb767 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to quantal on 2012-06-19 (0 days ago) dmi.bios.date: 09/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: AMD HUDSON-M1 dmi.board.vendor: ZOTAC dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd09/22/2011:svn:pn:pvr:rvnZOTAC:rnAMDHUDSON-M1:rvr:cvn:ct3:cvr: version.compiz: compiz 1:0.9.7.8-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.33-1 version.libgl1-mesa-dri: libgl1-
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
I can reproduce this (not reliable) on a Tega v2 (aka Viewpad 10, aka Nexoc Pad 10). Touchscreen is reported as "1d6b:0002 Hanvon 10.1 Touch screen overlay". xev reports a mousebutton release, but no press/keydown/whatever it is shown. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in HWE Next Project: New Status in X.Org X server: In Progress Status in “xorg-server” package in Ubuntu: In Progress Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:51:23,756 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=88133c52-550c-4c43-9da5-15f180bdb767 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to quantal on 2012-06-19 (0 days ago) dmi.bios.date: 09/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: AMD HUDSON-M1 dmi.board.vendor: ZOTAC dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd09/22/2011:svn:pn:pvr:rvnZOTAC:rnAMDHUDSON-M1:rvr:cvn:ct3:cvr: version.compiz: compiz 1:0.9.7.8-0ubuntu3 version.ia32-li
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
Can confirm this bug on a Samsung Series 7 slate. No touch input is recognized for Plasma Active or Unity, however XInput is reporting touch events (acts just like a mouse, instead of a multitouch screen). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in HWE Next Project: New Status in X.Org X server: In Progress Status in “xorg-server” package in Ubuntu: In Progress Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:51:23,756 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=88133c52-550c-4c43-9da5-15f180bdb767 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to quantal on 2012-06-19 (0 days ago) dmi.bios.date: 09/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: AMD HUDSON-M1 dmi.board.vendor: ZOTAC dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd09/22/2011:svn:pn:pvr:rvnZOTAC:rnAMDHUDSON-M1:rvr:cvn:ct3:cvr: version.compiz: compiz 1:0.9.7.8-0ubuntu3 version.ia32-libs: ia32-libs N/A version.li
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
Created a Blueprint about convertibles and the Ubuntu desktop with touch screen: https://blueprints.launchpad.net/ubuntu/+spec/client-1305-convertibles- and-touch-desktop -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in HWE Next Project: New Status in X.Org X server: In Progress Status in “xorg-server” package in Ubuntu: In Progress Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:51:23,756 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=88133c52-550c-4c43-9da5-15f180bdb767 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to quantal on 2012-06-19 (0 days ago) dmi.bios.date: 09/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: AMD HUDSON-M1 dmi.board.vendor: ZOTAC dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd09/22/2011:svn:pn:pvr:rvnZOTAC:rnAMDHUDSON-M1:rvr:cvn:ct3:cvr: version.compiz: compiz 1:0.9.7.8-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.33-1 version.
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
I use the PPA and I have updated and upgraded the system before adding the PPA (but maybe my mirror was not up-to-date). Given your confirmation that it works, I will search for the error on my side. Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in HWE Next Project: New Status in X.Org X server: In Progress Status in “xorg-server” package in Ubuntu: In Progress Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:51:23,756 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=88133c52-550c-4c43-9da5-15f180bdb767 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to quantal on 2012-06-19 (0 days ago) dmi.bios.date: 09/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: AMD HUDSON-M1 dmi.board.vendor: ZOTAC dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd09/22/2011:svn:pn:pvr:rvnZOTAC:rnAMDHUDSON-M1:rvr:cvn:ct3:cvr: version.compiz: compiz 1:0.9.7.8-0ubuntu3 version.ia32-libs: ia32-libs N/A versi
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
Krastanov, is your 13.04 completely up-to-date? I have created and tested the packages on an up-to-date 13.04 and there they work. Are you using the PPA (i386, amd64) or the binary package tarball (Nexus 7/armhf)? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in HWE Next Project: New Status in X.Org X server: In Progress Status in “xorg-server” package in Ubuntu: In Progress Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:51:23,756 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=88133c52-550c-4c43-9da5-15f180bdb767 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to quantal on 2012-06-19 (0 days ago) dmi.bios.date: 09/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: AMD HUDSON-M1 dmi.board.vendor: ZOTAC dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd09/22/2011:svn:pn:pvr:rvnZOTAC:rnAMDHUDSON-M1:rvr:cvn:ct3:cvr: version.compiz: compiz 1:0.9.7.8-0ubuntu3 version.ia32-libs: ia32-libs N/A ve
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
The packages can not be tested on 13.04 because of: xserver-xorg-core: Depends: libaudit1 (>=1:2.2.1) but it is not installable Depends: libc6 (>=2.17) but 2.15-0ubuntu20.1 is to be installed Depends: libudev1 (>=183) but it is not installable -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in HWE Next Project: New Status in X.Org X server: In Progress Status in “xorg-server” package in Ubuntu: In Progress Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:51:23,756 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=88133c52-550c-4c43-9da5-15f180bdb767 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to quantal on 2012-06-19 (0 days ago) dmi.bios.date: 09/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: AMD HUDSON-M1 dmi.board.vendor: ZOTAC dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd09/22/2011:svn:pn:pvr:rvnZOTAC:rnAMDHUDSON-M1:rvr:cvn:ct3:cvr: version.compiz: compiz 1:0.9.7.8-0ubuntu3 ve
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
Launchpad has imported 43 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=56578. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2012-10-30T10:01:15+00:00 Timo Aaltonen wrote: I'm able to "lock up" the Unity session by opening menus quickly by using a touchscreen. Seems as if there's a grab active. I can see the tooltips from launcher icons, interact with focused apps, but that's it. Can't reproduce with plain metacity, because the menus open so quickly with it, whereas with Unity on this hw the effects slow it down so that the race is hit. Tried several of the recent patches on top of 1.13, but they haven't helped. Now I see there are newer patches available. I'll give them a try. Filed this one for tracking this particular issue. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1015183/comments/33 On 2012-10-31T16:11:15+00:00 Timo Aaltonen wrote: tried patches from 56558 and 55738, also "Sync TouchListener memory.." from Carlos Garnacho, didn't help. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1015183/comments/34 On 2012-11-14T12:03:34+00:00 Daniel d'Andrada wrote: I just repeatedly tap on the top-most icon (the one which has the Ubuntu logo) of Ubuntu's launcher in a touchscreen. Those taps alternately open and close the dash (a fullscreen window that shows icons for applications, media and other files). Eventually those taps stop having any effect. I.e., the launcher no longer gets ButtonPress and ButtonRelease events out of them. I've added a wealth of logging (see xorg.log attachment) to try to understand what's happening on the server. From looking at it could see the following: >From touches 2 to 26, launcher is the first window in the list of listeners. >From touch 27 onwards, the root window is the first one. Problem is, from >touch 27 onwards, xserver fails to pass the touch ownership down to the >launcher window because there's always an older pointer-emulated touch (touch >26) lying around which it apparently can't get rid of (i.e. properly process). Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1015183/comments/35 On 2012-11-14T12:04:35+00:00 Daniel d'Andrada wrote: Created attachment 70064 log output of the "repeated tapping on ubuntu logo launcher icon" use case Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1015183/comments/36 On 2012-11-19T06:05:14+00:00 Peter Hutterer wrote: Do cross-check with Bug 56557 as well, this can cause issues if any grabs are activated on the root window and I wonder if that influences the behaviour here Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1015183/comments/37 On 2012-11-22T11:28:57+00:00 Daniel d'Andrada wrote: (In reply to comment #4) > Do cross-check with Bug 56557 as well, this can cause issues if any grabs > are activated on the root window and I wonder if that influences the > behaviour here Yes, they are at least closely related (most likely have the same cause) as a pointer-emulated touch gets "stuck" because of failed resource lookups in RetrieveTouchDeliveryData() as well. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1015183/comments/38 On 2012-11-22T12:04:17+00:00 Daniel d'Andrada wrote: Created attachment 70422 log output of use case with patches from bug 56557 applied With the 4 patches mentioned in bug 56557 applied (comments 3 and 4), the bug (missing ButtonPress and ButtonRelease events) manifests itself already on the second tap on the touchscreen. Again, due to a failure in RetrieveTouchDeliveryData() Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1015183/comments/39 On 2012-11-27T01:11:21+00:00 Peter Hutterer wrote: New set of patches, please try those on top of the current set you already tested. http://patchwork.freedesktop.org/patch/12519/ http://patchwork.freedesktop.org/patch/12520/ http://patchwork.freedesktop.org/patch/12521/ http://patchwork.freedesktop.org/patch/12522/ Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1015183/comments/40 On 2012-11-27T12:32:11
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
Binary test packages for the Nexus 7/armhf attached to bug 1068994. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in HWE Next Project: New Status in X.Org X server: Unknown Status in “xorg-server” package in Ubuntu: In Progress Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:51:23,756 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=88133c52-550c-4c43-9da5-15f180bdb767 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to quantal on 2012-06-19 (0 days ago) dmi.bios.date: 09/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: AMD HUDSON-M1 dmi.board.vendor: ZOTAC dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd09/22/2011:svn:pn:pvr:rvnZOTAC:rnAMDHUDSON-M1:rvr:cvn:ct3:cvr: version.compiz: compiz 1:0.9.7.8-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.33-1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-expe
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
I have uploaded a test package (xorg-server 1.13.3-0ubuntu6~ppa1) to my PPA now. Please install it following the instructions to include the PPA as described in the section "Adding this PPA to your system" on https://launchpad.net/~till-kamppeter/+archive/ppa and then running the commands sudo apt-get update sudo apt-get upgrade Does this fix your touch screen click problem? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in HWE Next Project: New Status in X.Org X server: Unknown Status in “xorg-server” package in Ubuntu: In Progress Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:51:23,756 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=88133c52-550c-4c43-9da5-15f180bdb767 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to quantal on 2012-06-19 (0 days ago) dmi.bios.date: 09/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: AMD HUDSON-M1 dmi.board.vendor: ZOTAC dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrends
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
@till-kamppeter, could you provide these modified builds in order to test them on different hardware. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in HWE Next Project: New Status in X.Org X server: Unknown Status in “xorg-server” package in Ubuntu: In Progress Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:51:23,756 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=88133c52-550c-4c43-9da5-15f180bdb767 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to quantal on 2012-06-19 (0 days ago) dmi.bios.date: 09/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: AMD HUDSON-M1 dmi.board.vendor: ZOTAC dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd09/22/2011:svn:pn:pvr:rvnZOTAC:rnAMDHUDSON-M1:rvr:cvn:ct3:cvr: version.compiz: compiz 1:0.9.7.8-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.33-1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3-0ubuntu1 version.libgl1-mesa-dri-
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
I have built xorg-server with my patch also on the Nexus7 now and it works perfectly there with the desktop and all applications, too, and on the Nexu7 XBMC and Chromium's web apps work with touch. It also seems to fix the Nexus 7 (bug 1068994). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in HWE Next Project: New Status in X.Org X server: Unknown Status in “xorg-server” package in Ubuntu: In Progress Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:51:23,756 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=88133c52-550c-4c43-9da5-15f180bdb767 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to quantal on 2012-06-19 (0 days ago) dmi.bios.date: 09/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: AMD HUDSON-M1 dmi.board.vendor: ZOTAC dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd09/22/2011:svn:pn:pvr:rvnZOTAC:rnAMDHUDSON-M1:rvr:cvn:ct3:cvr: version.compiz: compiz 1:0.9.7.8-0ubuntu3 version.
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
Sorry, patch is not complete. Here is the correct one. ** Patch added: "touch-fix.patch" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1015183/+attachment/3646277/+files/touch-fix.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in HWE Next Project: New Status in X.Org X server: Unknown Status in “xorg-server” package in Ubuntu: In Progress Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:51:23,756 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=88133c52-550c-4c43-9da5-15f180bdb767 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to quantal on 2012-06-19 (0 days ago) dmi.bios.date: 09/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: AMD HUDSON-M1 dmi.board.vendor: ZOTAC dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd09/22/2011:svn:pn:pvr:rvnZOTAC:rnAMDHUDSON-M1:rvr:cvn:ct3:cvr: version.compiz: compiz 1:0.9.7.8-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2:
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
Sorry, previous comment was meant for another bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in HWE Next Project: New Status in X.Org X server: Unknown Status in “xorg-server” package in Ubuntu: In Progress Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:51:23,756 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=88133c52-550c-4c43-9da5-15f180bdb767 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to quantal on 2012-06-19 (0 days ago) dmi.bios.date: 09/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: AMD HUDSON-M1 dmi.board.vendor: ZOTAC dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd09/22/2011:svn:pn:pvr:rvnZOTAC:rnAMDHUDSON-M1:rvr:cvn:ct3:cvr: version.compiz: compiz 1:0.9.7.8-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.33-1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A ve
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
Possibly bug 1099289 or bug 1068994 are duplicates of this one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in HWE Next Project: New Status in X.Org X server: Unknown Status in “xorg-server” package in Ubuntu: In Progress Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:51:23,756 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=88133c52-550c-4c43-9da5-15f180bdb767 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to quantal on 2012-06-19 (0 days ago) dmi.bios.date: 09/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: AMD HUDSON-M1 dmi.board.vendor: ZOTAC dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd09/22/2011:svn:pn:pvr:rvnZOTAC:rnAMDHUDSON-M1:rvr:cvn:ct3:cvr: version.compiz: compiz 1:0.9.7.8-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.33-1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experime
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
This bug is perhaps duplicate of bug 1099289 or bug 1068994. I have attached a patch (for xorg-server) to that bugs which solves the problem on the Lenovo Thinkpad Twist. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in HWE Next Project: New Status in X.Org X server: Unknown Status in “xorg-server” package in Ubuntu: In Progress Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:51:23,756 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=88133c52-550c-4c43-9da5-15f180bdb767 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to quantal on 2012-06-19 (0 days ago) dmi.bios.date: 09/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: AMD HUDSON-M1 dmi.board.vendor: ZOTAC dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd09/22/2011:svn:pn:pvr:rvnZOTAC:rnAMDHUDSON-M1:rvr:cvn:ct3:cvr: version.compiz: compiz 1:0.9.7.8-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.33-1 version.libgl
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
I have partial (full) success (on the Lenovo Thinkpad Twist, an Intel- based convertible, see also bug 1068994): I have rebuilt the current Raring package of xorg-server (1.13.3-0ubuntu5) with the following two patches: 1. http://cgit.freedesktop.org/~whot/xserver/commit/?h=touch-grab-race- condition-56578-v2&id=0498a4f0e0b90a850df7022a3356f10adabff855 (found via https://bugs.freedesktop.org/show_bug.cgi?id=56578#c17) 2. http://lists.x.org/archives/xorg-devel/2013-April/035878.html and after that clicking via touch screen on the Lenovo Thinkpad Twist works reliably. Only remaining problems are (but the touch click ability does not get lost by them): a. In Chromium when you create a new tab, the new tab contains icons for web apps (at least the app store and perhaps some examples). These icons cannot be clicked by touch, only with a mouse. All the rest in Chromium is clickable by touch. b. Touch clicks do not work in XBMC, but after using and leaving XBMC with an external mouse on the normal desktop touch-clicking works again. These are probably separate bugs which got revealed by the now working touch click. Complete patch for xorg-server is attached. ** Patch added: "touch-fix.patch" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1015183/+attachment/3646221/+files/touch-fix.patch ** Changed in: xorg-server (Ubuntu) Importance: Medium => High ** Changed in: xorg-server (Ubuntu) Milestone: None => ubuntu-13.04 ** Also affects: xorg-server via https://bugs.freedesktop.org/show_bug.cgi?id=56578 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in HWE Next Project: New Status in X.Org X server: Unknown Status in “xorg-server” package in Ubuntu: In Progress Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lift
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
I had similiar problems with ubuntu 13.04 on an Acer Iconia Tab W500. The patches in https://bugs.freedesktop.org/show_bug.cgi?id=56578#c17 solved the problem for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in HWE Next Project: New Status in “xorg-server” package in Ubuntu: In Progress Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:51:23,756 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=88133c52-550c-4c43-9da5-15f180bdb767 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to quantal on 2012-06-19 (0 days ago) dmi.bios.date: 09/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: AMD HUDSON-M1 dmi.board.vendor: ZOTAC dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd09/22/2011:svn:pn:pvr:rvnZOTAC:rnAMDHUDSON-M1:rvr:cvn:ct3:cvr: version.compiz: compiz 1:0.9.7.8-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.33-1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3-0ubu
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
note recent updates for the xorg bug here: https://bugs.freedesktop.org/show_bug.cgi?id=56578#c17 ** Bug watch added: freedesktop.org Bugzilla #56578 https://bugs.freedesktop.org/show_bug.cgi?id=56578 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in HWE Next Project: New Status in “xorg-server” package in Ubuntu: In Progress Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:51:23,756 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=88133c52-550c-4c43-9da5-15f180bdb767 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to quantal on 2012-06-19 (0 days ago) dmi.bios.date: 09/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: AMD HUDSON-M1 dmi.board.vendor: ZOTAC dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd09/22/2011:svn:pn:pvr:rvnZOTAC:rnAMDHUDSON-M1:rvr:cvn:ct3:cvr: version.compiz: compiz 1:0.9.7.8-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.33-1 version.libgl1-
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
Could you recheck on raring? It seems there have been some touch related fixes in xorg-server since the quantal xserver release. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in “xorg-server” package in Ubuntu: In Progress Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:51:23,756 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=88133c52-550c-4c43-9da5-15f180bdb767 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to quantal on 2012-06-19 (0 days ago) dmi.bios.date: 09/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: AMD HUDSON-M1 dmi.board.vendor: ZOTAC dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd09/22/2011:svn:pn:pvr:rvnZOTAC:rnAMDHUDSON-M1:rvr:cvn:ct3:cvr: version.compiz: compiz 1:0.9.7.8-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.33-1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
** Tags added: blocks-hwcert-enablement -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in “xorg-server” package in Ubuntu: In Progress Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:51:23,756 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=88133c52-550c-4c43-9da5-15f180bdb767 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to quantal on 2012-06-19 (0 days ago) dmi.bios.date: 09/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: AMD HUDSON-M1 dmi.board.vendor: ZOTAC dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd09/22/2011:svn:pn:pvr:rvnZOTAC:rnAMDHUDSON-M1:rvr:cvn:ct3:cvr: version.compiz: compiz 1:0.9.7.8-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.33-1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.3-0ubuntu1 version.xserver-xorg-core
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
Found out something new. I compiled the git version of evdev, xf86 -input-evdev-2.7.0-20-g5af11b6, and when multitouch isn't enabled, the core state problem is gone. The autoconf script doesn't detect XI22 on Precise because the X.org version is too old, so MT isn't enabled by default. Once I modified configure.ac to turn MULTITOUCH back on, then the problem was back as well and state is locked to 0x100 after the touchscreen is used. I've also found that I get far more of the problems Cédric mentions when ginn is running. It seems like what happens is the touchscreen stops generating ButtonPress events, but it still does motion events and state is still locked at 0x100. So the effect is that one is moving the pointer around with the button held down, but never pushing the button. This usually seems like left-click has stopped working. But I imagine the state problem and the resulting "drags with no click" can explain in some strange behavior seen in certain apps. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in “xorg-server” package in Ubuntu: In Progress Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:51:23,756 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
I see this same behavior on a Samsung Slate 7, which has an Atmel maxtouch multitouch touchscreen. Running Precise, with xserver-xorg- input-evdev 1:2.7.0-0ubuntu1.2 and xserver-xorg-core 2:1.11.4-0ubuntu10.8. If I don't touch the touchscreen since the X server has started, xev reports the state of events as expected when using a mouse. 0x000 for the ButtonPress, 0x100 for motion with the button down and the ButtonRelease, then 0x000 after. However, after the touchscreen is touched once, the state becomes 0x100 for the first ButtonPress from the touchscreen and stays at 0x100 thereafter, even after the ButtonRelease. Keyboard keys, mouse clicks, mouse motion, etc. are all state 0x100 until the X server is restarted. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in “xorg-server” package in Ubuntu: In Progress Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:51:23,756 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=88133c52-550c-4c43-9da5-15f180bdb767 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev U
