[Ubuntu-x-swat] [Bug 1046588] [NEW] Dependency on gesture stack must be updated due to rename
Public bug reported: [Impact] The gesture stack has been renamed to Open Input Framework. The dependency on grail must be changed to libgrail-dev. [Test Case] Ensure that the package continues to build and function as normal after installation. Nothing specific needs to be tested. [Regression Potential] Practically zero as long as the package builds. If any issues arise, they will likely be noticed immediately in the form of crashes due to unresolved symbols. ** Affects: xserver-xorg-input-synaptics (Ubuntu) Importance: Undecided Status: Invalid ** Affects: xserver-xorg-input-synaptics (Ubuntu Oneiric) Importance: High Assignee: Chase Douglas (chasedouglas) Status: In Progress ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Status: New = Invalid ** Also affects: xserver-xorg-input-synaptics (Ubuntu Oneiric) Importance: Undecided Status: New ** Changed in: xserver-xorg-input-synaptics (Ubuntu Oneiric) Status: New = In Progress ** Changed in: xserver-xorg-input-synaptics (Ubuntu Oneiric) Importance: Undecided = High ** Changed in: xserver-xorg-input-synaptics (Ubuntu Oneiric) Assignee: (unassigned) = Chase Douglas (chasedouglas) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1046588 Title: Dependency on gesture stack must be updated due to rename To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1046588/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1046592] [NEW] Dependency on gesture stack must be updated due to rename
Public bug reported: [Impact] The gesture stack has been renamed to Open Input Framework. The dependency on grail must be changed to libgrail-dev. [Test Case] Ensure that the package continues to build and function as normal after installation. Nothing specific needs to be tested. [Regression Potential] Practically zero as long as the package builds. If any issues arise, they will likely be noticed immediately in the form of crashes due to unresolved symbols. ** Affects: xserver-xorg-input-evdev (Ubuntu) Importance: Undecided Status: Invalid ** Affects: xserver-xorg-input-evdev (Ubuntu Oneiric) Importance: High Assignee: Chase Douglas (chasedouglas) Status: Fix Committed ** Changed in: xserver-xorg-input-evdev (Ubuntu) Status: New = Invalid ** Also affects: xserver-xorg-input-evdev (Ubuntu Oneiric) Importance: Undecided Status: New ** Changed in: xserver-xorg-input-evdev (Ubuntu Oneiric) Status: New = In Progress ** Changed in: xserver-xorg-input-evdev (Ubuntu Oneiric) Importance: Undecided = High ** Changed in: xserver-xorg-input-evdev (Ubuntu Oneiric) Assignee: (unassigned) = Chase Douglas (chasedouglas) ** Changed in: xserver-xorg-input-evdev (Ubuntu Oneiric) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1046592 Title: Dependency on gesture stack must be updated due to rename To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1046592/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1046588] Re: Dependency on gesture stack must be updated due to rename
** Changed in: xserver-xorg-input-synaptics (Ubuntu Oneiric) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1046588 Title: Dependency on gesture stack must be updated due to rename To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1046588/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1042779] Re: two-finger clicks only register as one finger, unless two-finger scrolling immediately before
** Changed in: xserver-xorg-input-synaptics (Ubuntu) Assignee: Chase Douglas (chasedouglas) = (unassigned) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1042779 Title: two-finger clicks only register as one finger, unless two-finger scrolling immediately before To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1042779/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1007575] Re: SB Arena USB headset causes X BUG, can't click outside window
** Changed in: xorg-server (Ubuntu) Assignee: Chase Douglas (chasedouglas) = Chris J Arges (christopherarges) ** Changed in: xorg-server (Ubuntu Precise) Assignee: Chase Douglas (chasedouglas) = Chris J Arges (christopherarges) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1007575 Title: SB Arena USB headset causes X BUG, can't click outside window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1007575/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 966619] Re: Provide emulated three-touch gesture support for two-touch trackpads
** Package changed: utouch-frame (Ubuntu) = frame (Ubuntu) ** Package changed: utouch-grail (Ubuntu) = grail (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/966619 Title: Provide emulated three-touch gesture support for two-touch trackpads To manage notifications about this bug go to: https://bugs.launchpad.net/frame/+bug/966619/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 880591] Re: Support for semi-multitouch devices in utouch
** Package changed: utouch-grail (Ubuntu) = grail (Ubuntu) ** Package changed: utouch-frame (Ubuntu) = frame (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/880591 Title: Support for semi-multitouch devices in utouch To manage notifications about this bug go to: https://bugs.launchpad.net/frame/+bug/880591/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 747835] Re: Add support for independent devices
** Package changed: utouch-frame (Ubuntu) = frame (Ubuntu) ** Package changed: utouch-geis (Ubuntu) = grail (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/747835 Title: Add support for independent devices To manage notifications about this bug go to: https://bugs.launchpad.net/frame/+bug/747835/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 972727] Re: Synaptics Clickpad functionalities incomplete: Right button area
** Changed in: xserver-xorg-input-synaptics (Ubuntu Precise) Status: Fix Released = Won't Fix -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/972727 Title: Synaptics Clickpad functionalities incomplete: Right button area To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/972727/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
On 07/04/2012 03:30 AM, Martin von Gagern wrote: Is the patch you referenced intended as a replacement for both my patches? Working with the touch screen alone, things work out fairly well. But if I also use a mouse, then the lack of a TOUCH_END event still causes the mouse moves to register as drags, i.e. with state 0x100. So I feel like your patch might be a suitable replacement for the one in comment #12, but the one in comment #11 is still required. If you aren't receiving a TouchEnd event, then there is something wrong. The patch you are reverting is needed to fix a different bug. If you can reproduce the issue easily, please describe how. Then we can look to resolve it. Thanks! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1015183/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
On 07/04/2012 03:37 AM, Martin von Gagern wrote: With that patch by Chase, I also wonder what would happen if two touch devices were used simultaneously. When I both touch my screen and click my conventional mouse button, I get two button events, but the state is the bitwise or of both, so the second click will be pressed button 1 while button 1 was pressed. Makes sense, in a certain way, although it might well confuse some applications. But what if I had two touch devices controlling the core pointer? I believe it is likely with the current setup that in this case, the second device would generate a ButtonPress with state 0x000. Or is it impossible for more than one touch device to control the core pointer at a given time? I don't have more than one device, so I can't test this. I'll agree that given current technology, this seems a rather rare corner case, and probably not worth the effort to deal with properly. But any shortcomings in that respect should perhaps at least be documented somewhere. Great point here :). I had to look at the code to determine the correct answer. I worried that, like you said, it would be buggy if you had two touchscreens. However, this should not be a problem. Input devices have a two-layer hierarchy. There are slave devices and master devices. Slave devices represent a physical device, like a touchscreen. Master devices represent a group of slave devices. Most people only have one master device configured, and all the slave devices are attached to it. If you have two mice, you can create a second master and attach one slave mouse to each. Then you'll have two independent pointers on screen :). A client can listen to events from master and/or slave devices. The events look and behave almost exactly the same. When you press your mouse button, a button press event is generated for the slave device and the attached master device. If you have two touchscreens with one master, then each slave device can emulate a button press event. However, there can be only one emulated touch per device (no matter whether it's a slave or a master), so the first touch is emulated for the master, and the second touch is not. Thanks! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1015183/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
Upstream patch has been posted here: http://lists.x.org/archives/xorg-devel/2012-July/032280.html -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1015183/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
Hi Martin,
Thanks for finding this issue. Good work on making some patches, but I
don't think they are quite right. We need to set the internal button
state of the device when the touch begin comes in, otherwise we will not
get the right result when we call {X,XI}QueryPointer().
A simpler solution would be to modify DeliverTouchEmulatedEvent(). There
is the following line:
ptrev-device_event.corestate = event_get_corestate(dev, kbd);
We need to modify it so that it also passes in a boolean to
event_get_corestate() to determine whether to mix the touch emulated
button state in with the normal button state. Then, we tell the function
to mix in the touch emulated state only on touch update and end events.
We can reason that this is correct because only one touch may be
emulated at a time per device, and because only one window may receive
an emulated button press for the touch begin at a time.
I will attempt to make a test and a patch for this tomorrow.
Thanks!
** Changed in: xorg-server (Ubuntu)
Status: Confirmed = In Progress
** Changed in: xorg-server (Ubuntu)
Importance: Undecided = Medium
** Changed in: xorg-server (Ubuntu)
Assignee: (unassigned) = Chase Douglas (chasedouglas)
** No longer affects: xserver-xorg-input-evdev (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1015183
Title:
Inconsistent mouse events for Acer T231H multitouch monitor
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1015183/+subscriptions
___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 973297] Re: Xorg recognizes Logitech Headset USB dongle as input device then segfaults in XIChangeDeviceProperty
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/973297 Title: Xorg recognizes Logitech Headset USB dongle as input device then segfaults in XIChangeDeviceProperty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/973297/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1007575] Re: SB Arena USB headset causes X BUG, can't click outside window
** Changed in: xorg-server (Ubuntu) Status: Incomplete = Triaged ** Changed in: xorg-server (Ubuntu Precise) Status: Incomplete = Triaged -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1007575 Title: SB Arena USB headset causes X BUG, can't click outside window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1007575/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 973297] Re: Xorg recognizes Logitech Headset USB dongle as input device then segfaults in XIChangeDeviceProperty
** Description changed: SRU Justification = [Impact] - On i386 machines, plugging a headset with buttons in will crash an existing X session or prevent an X session from starting. + On i386 machines, plugging a Logitech headset with buttons in will crash an existing X session or prevent an X session from starting. - [Stable Fix] - The crash is due to an ABI mismatch between xserver-xorg-input-evdev and xorg-server. A rebuild of the evdev input module fixes the issue. + The crash is due to a stack buffer overrun write that corrupts the + stack. This occurs because the buffer is not allocated with enough room + to hold records for all input device valuators when multitouch valuators + are present. [Development Fix] Rebuild will be pocket copied from Precise [Test Case] - Plug in a headset and see if X crashes. + Plug in the headset and see if X crashes. Alternatively, use utouch-evemu to create a virtual headset using the attached Logitech_Wireless_Headset.prop file: + + $ sudo utouch-evemu device Logitech_Wireless_Headset.prop [Regression Potential] - Practically zero. + The fix touches code that affects how input device axes are labelled. These labels are used primarily for the GIMP and a few other drawing tools when using a tablet drawing device. It is possible that a regression could occur, causing the axes to not be labeled correctly. Original bug report === On Precise, when I plug in the USB dongle that comes with a Logitech H800 headset, xorg segfaults. The following trace is captured in Xorg.log (see attachment XorgOldLog.txt) 45.488] (II) config/udev: Adding input device Logitech Logitech Wireless Headset (/dev/input/event7) [45.488] (**) Logitech Logitech Wireless Headset: Applying InputClass evdev keyboard catchall [45.488] (II) Using input driver 'evdev' for 'Logitech Logitech Wireless Headset' [45.488] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so [45.488] (**) Logitech Logitech Wireless Headset: always reports core events [45.488] (**) evdev: Logitech Logitech Wireless Headset: Device: /dev/input/event7 [45.488] (--) evdev: Logitech Logitech Wireless Headset: Vendor 0x46d Product 0xa29 [45.488] (--) evdev: Logitech Logitech Wireless Headset: Found absolute axes [45.488] (--) evdev: Logitech Logitech Wireless Headset: Found absolute multitouch axes [45.488] (--) evdev: Logitech Logitech Wireless Headset: Found keys [45.488] (II) evdev: Logitech Logitech Wireless Headset: Configuring as mouse [45.488] (II) evdev: Logitech Logitech Wireless Headset: Configuring as keyboard [45.488] (**) Option config_info udev:/sys/devices/pci:00/:00:1d.0/usb5/5-2/5-2:1.3/input/input7/event7 [45.488] (II) XINPUT: Adding extended input device Logitech Logitech Wireless Headset (type: KEYBOARD, id 9) [45.488] (**) Option xkb_rules evdev [45.488] (**) Option xkb_model pc105 [45.488] (**) Option xkb_layout fr [45.488] (**) Option xkb_variant oss [45.489] (II) evdev: Logitech Logitech Wireless Headset: initialized for absolute axes. [45.489] Backtrace: [45.489] 0: /usr/bin/X (xorg_backtrace+0x37) [0x983037] [45.489] 1: /usr/bin/X (0x7fb000+0x18bdba) [0x986dba] [45.489] 2: /lib/i386-linux-gnu/libpthread.so.0 (0x11b000+0xef30) [0x129f30] [45.489] 3: /lib/i386-linux-gnu/libc.so.6 (0x4fe000+0x1324ba) [0x6304ba] [45.489] 4: /usr/bin/X (XIChangeDeviceProperty+0x16c) [0x91b50c] [45.489] 5: /usr/lib/xorg/modules/input/evdev_drv.so (0x2b2000+0x634e) [0x2b834e] [45.489] 6: /usr/lib/xorg/modules/input/evdev_drv.so (0x2b2000+0x6595) [0x2b8595] [45.489] 7: /usr/bin/X (ActivateDevice+0x66) [0x8272d6] [45.489] 8: /usr/bin/X (0x7fb000+0x8cad5) [0x887ad5] [45.489] 9: /usr/bin/X (0x7fb000+0x9b012) [0x896012] [45.489] 10: /usr/bin/X (0x7fb000+0x9b883) [0x896883] [45.489] 11: /usr/bin/X (config_init+0x14) [0x8958e4] [45.489] 12: /usr/bin/X (InitInput+0xba) [0x875daa] [45.490] 13: /usr/bin/X (0x7fb000+0x2523e) [0x82023e] [45.490] 14: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x5174d3] [45.490] 15: /usr/bin/X (0x7fb000+0x255d9) [0x8205d9] [45.490] Segmentation fault at address 0x120 [45.490] Caught signal 11 (Segmentation fault). Server aborting ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.0-0ubuntu4 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Wed Apr 4 13:09:19 2012
[Ubuntu-x-swat] [Bug 1007575] Re: SB Arena USB headset causes X BUG, can't click outside window
Hi Mike, There's nothing in the recording that should cause your focus to be locked. It is possible that the device is emitting one of the mouse buttons when it is plugged in, which we won't capture using this approach, as you noted. Let's try something else. Pull up a terminal. Run xinput test-xi2 and capture the output to a file. Position your mouse cursor over the black box in the window that is created by xinput. Then, plug in your headset. Hit ctrl-c to kill xinput, and then attach the file to this bug. This will show us what input events are being seen and generated by the X server. Thanks! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1007575 Title: SB Arena USB headset causes X BUG, can't click outside window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1007575/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 972727] Re: Synaptics Clickpad functionalities incomplete: Right button area
I'm using this bug to track the enablement of the right button area on clickpads. I am removing references to the tap-to-disable area. Please file another bug for that issue. Thanks! ** Summary changed: - Synaptics Clickpad functionalities incomplete: Right button area, two-tap disabling + Synaptics Clickpad functionalities incomplete: Right button area ** Description changed: I use a Synaptics Clickpad touchpad. It has no physical buttons, the entire pad works like a button, and there is a right-click area where pressing the pad should register a right click. This feature does not - work. In OpenSuSE 11.4 and 12.1, this worked. At the same time, double- - tapping a white dot in the left-top corner should disable the touchpad. - This does not work either. + work. In OpenSuSE 11.4 and 12.1, this worked. I saw somewhere that right-button area was marked as too late for Precise by Chase Douglas. When can we expect this functionality to work? Is there any workaround, like using the OpenSuSE package? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xinput 1.5.99.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic-pae 3.2.13 Uname: Linux 3.2.0-21-generic-pae i686 .tmp.unity.support.test.0: - + ApportVersion: 2.0-0ubuntu2 Architecture: i386 CompizPlugins: [core,composite,opengl,decor,mousepoll,gnomecompat,regex,imgpng,compiztoolbox,wall,snap,vpswitch,unitymtgrabhandles,move,grid,resize,place,animation,fade,session,scale,workarounds,expo,ezoom,unityshell] CompositorRunning: compiz Date: Tue Apr 3 20:21:45 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DpkgLog: - + InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120328) MachineType: Hewlett-Packard HP ProBook 4420s ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-21-generic-pae root=UUID=A2661C4C661C2417 loop=/hostname/disks/root.disk ro quiet splash vt.handoff=7 SourcePackage: xinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68AHH Ver. F.0E dmi.board.name: 1423 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 53.34 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68AHHVer.F.0E:bd02/11/2011:svnHewlett-Packard:pnHPProBook4420s:pvr:rvnHewlett-Packard:rn1423:rvrKBCVersion53.34:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4420s dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.7.2-0ubuntu4 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/972727 Title: Synaptics Clickpad functionalities incomplete: Right button area To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/972727/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 972727] Re: Synaptics Clickpad functionalities incomplete: Right button area
** Changed in: xserver-xorg-input-synaptics (Ubuntu Quantal) Status: Triaged = Fix Committed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/972727 Title: Synaptics Clickpad functionalities incomplete: Right button area To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/972727/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 780961] Re: Xorg crash in PlayReleasedEvents with Sawfish when using keyboard-based window management
** Changed in: xorg-server (Ubuntu) Assignee: Chase Douglas (chasedouglas) = (unassigned) ** Changed in: xorg-server (Ubuntu) Status: Triaged = Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/780961 Title: Xorg crash in PlayReleasedEvents with Sawfish when using keyboard- based window management To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/780961/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1007575] Re: SB Arena USB headset causes X BUG, can't click outside window
Hi Mike, Please capture the input properties of your headset input device (your headset is acting as an input device because it has buttons). After plugging in your headset, follow https://wiki.ubuntu.com/Multitouch/Testing/uTouchEvEmu#Debugging. You only need to perform steps 1, 2, and 5, the rest can be skipped for this bug. When it asks you to find your multitouch device, look for your headset instead. Once you have a device.prop file for your headset, attach it to this bug. Also, please attach the output of xinput list --long when the headset is plugged in. Thanks! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1007575 Title: SB Arena USB headset causes X BUG, can't click outside window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1007575/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 973297] Re: Xorg recognizes Logitech Headset USB dongle as input device then segfaults in XIChangeDeviceProperty
I believe I have found the issue, and the patch sent upstream is: http://lists.x.org/archives/xorg-devel/2012-June/031541.html. I have applied the patch to the package and uploaded a test package to ppa:chasedouglas/jupiter. Please test it out after it has finished building. The version of the package is 2.7.0-0ubuntu1.2~jupiter1. If it resolves the issue, I will create a new SRU package for it. Thanks! ** Changed in: xserver-xorg-input-evdev (Ubuntu) Status: Triaged = In Progress ** Changed in: xserver-xorg-input-evdev (Ubuntu Precise) Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/973297 Title: Xorg recognizes Logitech Headset USB dongle as input device then segfaults in XIChangeDeviceProperty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/973297/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1007575] Re: SB Arena USB headset causes X BUG, can't click outside window
Hi Mike, I can't reproduce the issue by merely instantiating a virtual input device based on the device.prop file you gave me. Perhaps the device is sending button or key events? After plugging in the headset, please perform steps 1, 2, and 6 from https://wiki.ubuntu.com/Multitouch/Testing/uTouchEvEmu#Debugging. Let the evemu-record utility run for about a minute, then kill it with ctrl-c. Then attach the file to this bug. Thanks! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1007575 Title: SB Arena USB headset causes X BUG, can't click outside window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1007575/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1007575] Re: SB Arena USB headset causes X BUG, can't click outside window
** Package changed: xserver-xorg-input-evdev (Ubuntu) = xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New = In Progress ** Changed in: xorg-server (Ubuntu) Assignee: (unassigned) = Chase Douglas (chasedouglas) ** Changed in: xorg-server (Ubuntu) Importance: Undecided = Medium ** Also affects: xorg-server (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu Precise) Importance: Undecided = Medium ** Changed in: xorg-server (Ubuntu Precise) Assignee: (unassigned) = Chase Douglas (chasedouglas) ** Changed in: xorg-server (Ubuntu Precise) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1007575 Title: SB Arena USB headset causes X BUG, can't click outside window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1007575/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 973297] Re: Xorg recognizes Logitech Headset USB dongle as input device then segfaults in XIChangeDeviceProperty
** Tags removed: verification-needed ** Tags added: verification-failed ** Changed in: xserver-xorg-input-evdev (Ubuntu Precise) Status: Fix Committed = Triaged -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/973297 Title: Xorg recognizes Logitech Headset USB dongle as input device then segfaults in XIChangeDeviceProperty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/973297/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1007575] Re: SB Arena USB headset causes X BUG, can't click outside window
Hi Mike, I have uploaded a potential fix to ppa:chasedouglas/mercury. Please add it and upgrade to the X server packages from it. Your xserver-xorg-core package should be version 1.11.4-0ubuntu10.3~jupiter1 after upgrading. Then test if the issue has been resolved. Thanks! ** Changed in: xorg-server (Ubuntu Precise) Status: In Progress = Incomplete ** Changed in: xorg-server (Ubuntu) Status: In Progress = Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1007575 Title: SB Arena USB headset causes X BUG, can't click outside window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1007575/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 973297] Re: Xorg recognizes Logitech Headset USB dongle as input device then segfaults in XIChangeDeviceProperty
It turns out that when one compiles evdev without optimizations, the device initializes properly and nothing bad happens. When one compiles with the normal optimizations used in the Ubuntu archive builds, the device causes the X server to crash. I'm still investigating... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/973297 Title: Xorg recognizes Logitech Headset USB dongle as input device then segfaults in XIChangeDeviceProperty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/973297/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1007575] Re: SB Arena USB headset causes X BUG, can't click outside window
Hi Mike, I'm sorry, I meant ppa:chasedouglas/jupiter. I have two ppas for random bug fix package tests. I accidentally gave you the wrong one. Thanks! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1007575 Title: SB Arena USB headset causes X BUG, can't click outside window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1007575/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 975356] Re: Logging from signal context is unsafe
It is being worked on upstream on xorg-devel. It is moving slowly, but working its way in. When it is accepted upstream we can take a look at any backporting for quantal. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/975356 Title: Logging from signal context is unsafe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/975356/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 971783] Re: 3 touch taps and clicks are broken
Hi Vincent, The configuration is not going to be enabled by default now or in future Ubuntu releases because it conflicts with Unity gestures. If you want to enable it by default, it needs to be set in /etc/X11/xorg.conf like: Section InputClass Identifier touchpad 3-tap Driver synaptics MatchIsTouchpad on MatchDevicePath /dev/input/event* Option TapButton3 2 Option ClickFinger3 2 EndSection I believe that will work, though I haven't tried it myself. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/971783 Title: 3 touch taps and clicks are broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/971783/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 968845] Re: bcm5974 touchpad doesn't work after S3 on MacBookAir
Hi Steve, There's actually a couple more fixes for the remainder of the issues. Since this package resolves some of the issues, I think we should accept it into precise-updates. Then we can create a new bug to track the remaining issues. ** Tags removed: verification-failed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/968845 Title: bcm5974 touchpad doesn't work after S3 on MacBookAir To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-input-synaptics/+bug/968845/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 616891] Re: Wacom Bamboo Fun (056a:00d3 Wacom Co., Ltd): Pen Touch don't work in any way (touch or pencil)
** Changed in: utouch Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/616891 Title: Wacom Bamboo Fun (056a:00d3 Wacom Co., Ltd): Pen Touch don't work in any way (touch or pencil) To manage notifications about this bug go to: https://bugs.launchpad.net/utouch/+bug/616891/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 477105] Re: wacom bamboo pen touch not working
** No longer affects: utouch -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/477105 Title: wacom bamboo pen touch not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/477105/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 973297] Re: Xorg recognizes Logitech Headset USB dongle as input device then segfaults in XIChangeDeviceProperty
Hi Didier, I think it's the same bug. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/973297 Title: Xorg recognizes Logitech Headset USB dongle as input device then segfaults in XIChangeDeviceProperty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/973297/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 973297] Re: Xorg recognizes Logitech Headset USB dongle as input device then segfaults in XIChangeDeviceProperty
** Description changed: - On Precise, when I plug in the USB dongle that comes with a Logitech - H800 headset, xorg segfaults. + SRU Justification + = + [Impact] + On i386 machines, plugging a headset with buttons in will crash an existing X session or prevent an X session from starting. + + [Development Fix] + The crash is due to an ABI mismatch between xserver-xorg-input-evdev and xorg-server. A rebuild of the evdev input module fixes the issue. + + [Stable Fix] + Same as development fix. + + [Test Case] + Plug in a headset and see if X crashes. + + [Regression Potential] + Practically zero. + + Original bug report + === + On Precise, when I plug in the USB dongle that comes with a Logitech H800 headset, xorg segfaults. The following trace is captured in Xorg.log (see attachment XorgOldLog.txt) 45.488] (II) config/udev: Adding input device Logitech Logitech Wireless Headset (/dev/input/event7) [45.488] (**) Logitech Logitech Wireless Headset: Applying InputClass evdev keyboard catchall [45.488] (II) Using input driver 'evdev' for 'Logitech Logitech Wireless Headset' [45.488] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so [45.488] (**) Logitech Logitech Wireless Headset: always reports core events [45.488] (**) evdev: Logitech Logitech Wireless Headset: Device: /dev/input/event7 [45.488] (--) evdev: Logitech Logitech Wireless Headset: Vendor 0x46d Product 0xa29 [45.488] (--) evdev: Logitech Logitech Wireless Headset: Found absolute axes [45.488] (--) evdev: Logitech Logitech Wireless Headset: Found absolute multitouch axes [45.488] (--) evdev: Logitech Logitech Wireless Headset: Found keys [45.488] (II) evdev: Logitech Logitech Wireless Headset: Configuring as mouse [45.488] (II) evdev: Logitech Logitech Wireless Headset: Configuring as keyboard [45.488] (**) Option config_info udev:/sys/devices/pci:00/:00:1d.0/usb5/5-2/5-2:1.3/input/input7/event7 [45.488] (II) XINPUT: Adding extended input device Logitech Logitech Wireless Headset (type: KEYBOARD, id 9) [45.488] (**) Option xkb_rules evdev [45.488] (**) Option xkb_model pc105 [45.488] (**) Option xkb_layout fr [45.488] (**) Option xkb_variant oss [45.489] (II) evdev: Logitech Logitech Wireless Headset: initialized for absolute axes. [45.489] Backtrace: [45.489] 0: /usr/bin/X (xorg_backtrace+0x37) [0x983037] [45.489] 1: /usr/bin/X (0x7fb000+0x18bdba) [0x986dba] [45.489] 2: /lib/i386-linux-gnu/libpthread.so.0 (0x11b000+0xef30) [0x129f30] [45.489] 3: /lib/i386-linux-gnu/libc.so.6 (0x4fe000+0x1324ba) [0x6304ba] [45.489] 4: /usr/bin/X (XIChangeDeviceProperty+0x16c) [0x91b50c] [45.489] 5: /usr/lib/xorg/modules/input/evdev_drv.so (0x2b2000+0x634e) [0x2b834e] [45.489] 6: /usr/lib/xorg/modules/input/evdev_drv.so (0x2b2000+0x6595) [0x2b8595] [45.489] 7: /usr/bin/X (ActivateDevice+0x66) [0x8272d6] [45.489] 8: /usr/bin/X (0x7fb000+0x8cad5) [0x887ad5] [45.489] 9: /usr/bin/X (0x7fb000+0x9b012) [0x896012] [45.489] 10: /usr/bin/X (0x7fb000+0x9b883) [0x896883] [45.489] 11: /usr/bin/X (config_init+0x14) [0x8958e4] [45.489] 12: /usr/bin/X (InitInput+0xba) [0x875daa] [45.490] 13: /usr/bin/X (0x7fb000+0x2523e) [0x82023e] [45.490] 14: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x5174d3] [45.490] 15: /usr/bin/X (0x7fb000+0x255d9) [0x8205d9] [45.490] Segmentation fault at address 0x120 [45.490] Caught signal 11 (Segmentation fault). Server aborting ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.0-0ubuntu4 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Wed Apr 4 13:09:19 2012 DistUpgraded: 2009-11-14 19:02:58,254 DEBUG enabling apt cron job DistroCodename: precise DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu MachineType: ASUSTeK Computer Inc. U3SG ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-21-generic root=UUID=75f23f17-3ace-4485-af57-a7318eb6c2ff ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to precise on 2009-11-14 (871 days ago) dmi.bios.date: 01/28/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U3SG dmi.board.vendor: ASUSTeK Computer Inc.
[Ubuntu-x-swat] [Bug 973297] Re: Xorg recognizes Logitech Headset USB dongle as input device then segfaults in XIChangeDeviceProperty
** Description changed: SRU Justification = [Impact] On i386 machines, plugging a headset with buttons in will crash an existing X session or prevent an X session from starting. - [Development Fix] + [Stable Fix] The crash is due to an ABI mismatch between xserver-xorg-input-evdev and xorg-server. A rebuild of the evdev input module fixes the issue. - [Stable Fix] - Same as development fix. + [Development Fix] + Rebuild will be pocket copied from Precise [Test Case] Plug in a headset and see if X crashes. [Regression Potential] Practically zero. Original bug report === On Precise, when I plug in the USB dongle that comes with a Logitech H800 headset, xorg segfaults. The following trace is captured in Xorg.log (see attachment XorgOldLog.txt) 45.488] (II) config/udev: Adding input device Logitech Logitech Wireless Headset (/dev/input/event7) [45.488] (**) Logitech Logitech Wireless Headset: Applying InputClass evdev keyboard catchall [45.488] (II) Using input driver 'evdev' for 'Logitech Logitech Wireless Headset' [45.488] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so [45.488] (**) Logitech Logitech Wireless Headset: always reports core events [45.488] (**) evdev: Logitech Logitech Wireless Headset: Device: /dev/input/event7 [45.488] (--) evdev: Logitech Logitech Wireless Headset: Vendor 0x46d Product 0xa29 [45.488] (--) evdev: Logitech Logitech Wireless Headset: Found absolute axes [45.488] (--) evdev: Logitech Logitech Wireless Headset: Found absolute multitouch axes [45.488] (--) evdev: Logitech Logitech Wireless Headset: Found keys [45.488] (II) evdev: Logitech Logitech Wireless Headset: Configuring as mouse [45.488] (II) evdev: Logitech Logitech Wireless Headset: Configuring as keyboard [45.488] (**) Option config_info udev:/sys/devices/pci:00/:00:1d.0/usb5/5-2/5-2:1.3/input/input7/event7 [45.488] (II) XINPUT: Adding extended input device Logitech Logitech Wireless Headset (type: KEYBOARD, id 9) [45.488] (**) Option xkb_rules evdev [45.488] (**) Option xkb_model pc105 [45.488] (**) Option xkb_layout fr [45.488] (**) Option xkb_variant oss [45.489] (II) evdev: Logitech Logitech Wireless Headset: initialized for absolute axes. [45.489] Backtrace: [45.489] 0: /usr/bin/X (xorg_backtrace+0x37) [0x983037] [45.489] 1: /usr/bin/X (0x7fb000+0x18bdba) [0x986dba] [45.489] 2: /lib/i386-linux-gnu/libpthread.so.0 (0x11b000+0xef30) [0x129f30] [45.489] 3: /lib/i386-linux-gnu/libc.so.6 (0x4fe000+0x1324ba) [0x6304ba] [45.489] 4: /usr/bin/X (XIChangeDeviceProperty+0x16c) [0x91b50c] [45.489] 5: /usr/lib/xorg/modules/input/evdev_drv.so (0x2b2000+0x634e) [0x2b834e] [45.489] 6: /usr/lib/xorg/modules/input/evdev_drv.so (0x2b2000+0x6595) [0x2b8595] [45.489] 7: /usr/bin/X (ActivateDevice+0x66) [0x8272d6] [45.489] 8: /usr/bin/X (0x7fb000+0x8cad5) [0x887ad5] [45.489] 9: /usr/bin/X (0x7fb000+0x9b012) [0x896012] [45.489] 10: /usr/bin/X (0x7fb000+0x9b883) [0x896883] [45.489] 11: /usr/bin/X (config_init+0x14) [0x8958e4] [45.489] 12: /usr/bin/X (InitInput+0xba) [0x875daa] [45.490] 13: /usr/bin/X (0x7fb000+0x2523e) [0x82023e] [45.490] 14: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x5174d3] [45.490] 15: /usr/bin/X (0x7fb000+0x255d9) [0x8205d9] [45.490] Segmentation fault at address 0x120 [45.490] Caught signal 11 (Segmentation fault). Server aborting ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.0-0ubuntu4 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Wed Apr 4 13:09:19 2012 DistUpgraded: 2009-11-14 19:02:58,254 DEBUG enabling apt cron job DistroCodename: precise DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu MachineType: ASUSTeK Computer Inc. U3SG ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-21-generic root=UUID=75f23f17-3ace-4485-af57-a7318eb6c2ff ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to precise on 2009-11-14 (871 days ago) dmi.bios.date: 01/28/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U3SG dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0
[Ubuntu-x-swat] [Bug 968845] Re: bcm5974 touchpad doesn't work after S3 on MacBookAir
Hi Seth, Luke, I have another fix for when a touch is active and the device is disabled. I have uploaded it to ppa:chasedouglas/jupiter. Please install it and retest to see if it fixes your issues. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/968845 Title: bcm5974 touchpad doesn't work after S3 on MacBookAir To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-input-synaptics/+bug/968845/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 973297] Re: Xorg recognizes Logitech Headset USB dongle as input device then segfaults in XIChangeDeviceProperty
Hi Dmitriy, Thanks for figuring that out! I can reproduce the crash here on my netbook. There is an ABI mismatch between xserver-xorg-input-evdev and xserver-xorg-core in the XIChangeDeviceProperty() function. The value parameter gets mangled between evdev and the server. It looks like this commit is related: http://cgit.freedesktop.org/xorg/xserver/commit/?id=ed8f3c4bd17bddf1369d050ea8e63b9451d887ce This was backported into the Precise xorg-server package in this commit: http://anonscm.debian.org/gitweb/?p=pkg-xorg/xserver/xorg- server.git;a=commitdiff;h=fe5444bfe3c7cc56cd8bddb32d2dc45b22431aea;hp=447156777040e0695391ecac709de3a857368a8d This was committed on January 10th and released in xorg-server 2:1.11.3-0ubuntu2 that same day. However, evdev was built on March 15th. The xserver-xorg-dev package used for the evdev build has an identical function signature to the current xorg-server package. However, when I do a rebuild of evdev against the current xorg-server, the result does not crash. The obvious fix is to upload a rebuild package to fix the ABI issue, but I have no idea what went wrong. ** Changed in: xorg-server (Ubuntu) Status: Incomplete = Invalid ** Changed in: xorg-server (Ubuntu Precise) Status: Incomplete = Triaged -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/973297 Title: Xorg recognizes Logitech Headset USB dongle as input device then segfaults in XIChangeDeviceProperty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/973297/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 968845] Re: bcm5974 touchpad doesn't work after S3 on MacBookAir
Hi Luke, Did you log out or restart after installing the updates? The updates do not take effect until the X server is restarted. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/968845 Title: bcm5974 touchpad doesn't work after S3 on MacBookAir To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-input-synaptics/+bug/968845/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 973297] Re: Xorg recognizes Logitech Headset USB dongle as input device then segfaults in XIChangeDeviceProperty
** Changed in: xorg-server (Ubuntu) Status: Confirmed = Incomplete ** Changed in: xorg-server (Ubuntu Precise) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/973297 Title: Xorg recognizes Logitech Headset USB dongle as input device then segfaults in XIChangeDeviceProperty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/973297/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 929065] Re: Drag and Drop with a touchscreen fails in Nautilus
Hi burli, Can you confirm which version of xorg-server you are running? Thanks! ** Changed in: xorg-server (Ubuntu) Status: Confirmed = Incomplete ** Changed in: xorg-server (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/929065 Title: Drag and Drop with a touchscreen fails in Nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/929065/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 968845] Re: bcm5974 touchpad doesn't work after S3 on MacBookAir
** Description changed: xorg-server SRU Justification = [Impact] When a laptop is suspended, X disables the input devices. If X believes the hardware has a button press when the device is disabled, it will not release the button on resume and device enabling. With tap to click turned out, the volatile mix of the touchpad and the LCD screen on lid closure can cause this problem on suspend/resume. [Development Fix] A one-line patch from upstream has been added to xorg-server 1.11.4-0ubuntu11. The patch can be seen in the SRU debdiff. It simply releases the buttons when an input device is disabled. [Stable Fix] The same one-line patch for the development fix has been made to xorg-server 1.11.4-0ubuntu10.2. Please see the attached xorg-server SRU debdiff. [Test Case] Close and open the lid to perform a suspend resume cycle on a MacBook Air. Repeat multiple times. Note that there will be issues until an SRU for xserver-xorg-input-synaptics is available too. [Regression Potential] Very minimal. The one-line change releases the buttons when an input device is disabled. It is a trivial fix. + + xserver-xorg-input-synaptics SRU Justification + == + [Impact] + When a laptop is suspended, X disables the input devices. The entire state of the device needs to be reset when the device is disabled so that it works properly when re-enabled. Without this fix, the trackpad may do odd things like behave as though there are active touches that no longer exist. This can manifest as scrolling with one finger, no cursor motion, and right clicking instead of left clicking. + + [Development Fix] + Upstream 1.6.0 has two patches that fix this specific issue, among other bug fixes. This has been uploaded to Quantal. + + [Stable Fix] + The Quantal 1.6.0 update has been uploaded for Precise and is identical to the Quantal package other than the Precise SRU version. The only changes from the previous package to the 1.6.0 package are various bug fixes. + + [Test Case] + Close and open the lid to perform a suspend resume cycle on a MacBook Air. Repeat multiple times. Ensure the trackpad continues to function properly.` + + [Regression Potential] + Minimal. The fixes for this patch are small and well-contained. The fixes for other issues in the upstream 1.6.0 release are also small and well-contained. Original Bug Report === I started seeing this immediately after installing updates that included xserver-xorg-input-synaptics from 1.5.99.901-0ubuntu2 to 1.5.99.902-0ubuntu1 and rebooting. When I initiate a suspend by closing the lid, after resuming the touchpad no longer works at all. I can see a stream of events by switching to a vt and running input events, and if I restart the display manager the touchpad starts working again. I do not see this issue if I initiate suspend from the menu, only when closing the lid. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-input-synaptics 1.5.99.902-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Thu Mar 29 23:01:23 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64+mac (20111208) MachineType: Apple Inc. MacBookAir4,1 ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=UUID=f4af0efe-df4b-4d74-8995-7081cf79889c ro SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/14/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B0E.1110141154 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C08A6BB70A942AC2 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C08A6BB70A942AC2 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B0E.1110141154:bd10/14/2011:svnAppleInc.:pnMacBookAir4,1:pvr1.0:rvnAppleInc.:rnMac-C08A6BB70A942AC2:rvrMacBookAir4,1:cvnAppleInc.:ct10:cvrMac-C08A6BB70A942AC2: dmi.product.name: MacBookAir4,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.7.2-0ubuntu4 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati
[Ubuntu-x-swat] [Bug 941953] Re: Xorg crashed with SIGSEGV in WriteToClient() with buf = 0x100000000 from ProcXIGetProperty()
I can't reproduce using a magic trackpad. Maybe the issue is a bad kernel driver for a different device? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/941953 Title: Xorg crashed with SIGSEGV in WriteToClient() with buf = 0x1 from ProcXIGetProperty() To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-input-synaptics/+bug/941953/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 968845] Re: bcm5974 touchpad doesn't work after S3 on MacBookAir
** Description changed: - I started seeing this immediately after installing updates that included - xserver-xorg-input-synaptics from 1.5.99.901-0ubuntu2 to - 1.5.99.902-0ubuntu1 and rebooting. + xorg-server SRU Justification + = + [Impact] + When a laptop is suspended, X disables the input devices. If X believes the hardware has a button press when the device is disabled, it will not release the button on resume and device enabling. With tap to click turned out, the volatile mix of the touchpad and the LCD screen on lid closure can cause this problem on suspend/resume. + + [Development Fix] + A one-line patch from upstream has been added to xorg-server 1.11.4-0ubuntu11. The patch can be seen in the SRU debdiff. It simply releases the buttons when an input device is disabled. + + [Stable Fix] + The same one-line patch for the development fix has been made to xorg-server 1.11.4-0ubuntu10.2. Please see the attached xorg-server SRU debdiff. + + [Test Case] + Close and open the lid to perform a suspend resume cycle on a MacBook Air. Repeat multiple times. Note that there will be issues until an SRU for xserver-xorg-input-synaptics is available too. + + [Regression Potential] + Very minimal. The one-line change releases the buttons when an input device is disabled. It is a trivial fix. + + Original Bug Report + === + I started seeing this immediately after installing updates that included xserver-xorg-input-synaptics from 1.5.99.901-0ubuntu2 to 1.5.99.902-0ubuntu1 and rebooting. When I initiate a suspend by closing the lid, after resuming the touchpad no longer works at all. I can see a stream of events by switching to a vt and running input events, and if I restart the display manager the touchpad starts working again. I do not see this issue if I initiate suspend from the menu, only when closing the lid. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-input-synaptics 1.5.99.902-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Thu Mar 29 23:01:23 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64+mac (20111208) MachineType: Apple Inc. MacBookAir4,1 ProcEnviron: - TERM=xterm - SHELL=/bin/bash - PATH=(custom, user) - LANG=en_US.UTF-8 + TERM=xterm + SHELL=/bin/bash + PATH=(custom, user) + LANG=en_US.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=UUID=f4af0efe-df4b-4d74-8995-7081cf79889c ro SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/14/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B0E.1110141154 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C08A6BB70A942AC2 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C08A6BB70A942AC2 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B0E.1110141154:bd10/14/2011:svnAppleInc.:pnMacBookAir4,1:pvr1.0:rvnAppleInc.:rnMac-C08A6BB70A942AC2:rvrMacBookAir4,1:cvnAppleInc.:ct10:cvrMac-C08A6BB70A942AC2: dmi.product.name: MacBookAir4,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.7.2-0ubuntu4 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 ** Attachment added: xorg-server SRU debdiff https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/968845/+attachment/3132422/+files/patch -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/968845 Title: bcm5974 touchpad doesn't work after S3 on MacBookAir To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-input-synaptics/+bug/968845/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 941953] Re: Xorg crashed with SIGSEGV in WriteToClient() with buf = 0x100000000 from ProcXIGetProperty()
There appears to be a bug where the number of touches goes negative. This leads to buffer overrun issues. ** Package changed: xorg-server (Ubuntu) = xserver-xorg-input-synaptics (Ubuntu) ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Status: Confirmed = Triaged ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Assignee: (unassigned) = Chase Douglas (chasedouglas) ** Also affects: xserver-xorg-input-synaptics (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: xserver-xorg-input-synaptics (Ubuntu Precise) Status: New = Triaged ** Changed in: xserver-xorg-input-synaptics (Ubuntu Precise) Importance: Undecided = High ** Changed in: xserver-xorg-input-synaptics (Ubuntu Precise) Assignee: (unassigned) = Chase Douglas (chasedouglas) ** Bug watch added: freedesktop.org Bugzilla #49439 https://bugs.freedesktop.org/show_bug.cgi?id=49439 ** Also affects: xserver-xorg-input-synaptics via https://bugs.freedesktop.org/show_bug.cgi?id=49439 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/941953 Title: Xorg crashed with SIGSEGV in WriteToClient() with buf = 0x1 from ProcXIGetProperty() To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-input-synaptics/+bug/941953/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 993561] Re: touch pad not working
Hi Steven, Ubuntu 10.10 is out of support as of the end of April. Please upgrade to a later release. I suggest Ubuntu 12.04 LTS. I am closing this bug as won't fix. Please reopen with a detailed bug description if you can reproduce it on a later Ubuntu release. Thanks! ** Changed in: utouch (Ubuntu) Status: New = Won't Fix ** Package changed: utouch (Ubuntu) = xserver-xorg-input-synaptics (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/993561 Title: touch pad not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/993561/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 968845] Re: bcm5974 touchpad doesn't work after S3 on MacBookAir
This bug was partially fixed in xserver-xorg-input-synaptics 1.5.99.902-0ubuntu5.1. Most suspend/resume cycles will complete successfully now. However, about 10-20% of the time the trackpad will stop working properly. There are two more patches for xserver-xorg- input-synaptics and one for xorg-server to fully resolve this issue. These are noted in comment #46. ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Status: Fix Released = In Progress ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: New = Triaged ** Changed in: xorg-server (Ubuntu Precise) Status: New = Triaged ** Changed in: xorg-server (Ubuntu) Importance: Undecided = Medium ** Changed in: xorg-server (Ubuntu Precise) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/968845 Title: bcm5974 touchpad doesn't work after S3 on MacBookAir To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-input-synaptics/+bug/968845/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 901630] Re: multitouch + qt doesn't work (eg fingerpaint demo) with wacom serial touchscreen
Hi bootchk, Do you have a touchscreen? If so, you want to be using the evdev driver isntead of wacom. If not, then you'll want to use the synaptics driver and open a different bug since this one is specific for touchscreens. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/901630 Title: multitouch + qt doesn't work (eg fingerpaint demo) with wacom serial touchscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/901630/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 901630] Re: multitouch + qt doesn't work (eg fingerpaint demo) with wacom serial touchscreen
On 04/25/2012 08:03 AM, bootchk wrote: Chase wrote You have to put five or more fingers down on a trackpad to start sending events that aren't caught by Unity or X synaptics. My understanding now: Unity is a window manager (more or less.) It is also in the so-called stack that processes touch events. It does gesture recognition and hides touch events from an application (possibly converting sequences of touch events, i.e. gestures, to other event types) unless five touches are used. Is there any way to disable unity gesture recognition (so that all touch events go to the application), similarly to the way you can disable gesture recognition in the synaptics Xorg input driver? No. The Unity gesture specification doesn't allow for gesture configuration, and that's what we are implementing. If you want to influence this decision, I suggest sending a message to the unity-dev mailing list. The stack: kernel device driver (e.g. wacom) Xorg input driver (e.g. synaptics) window manager (e.g. unity) GUI toolkit (e.g. Qt) application Shouldn't there be a set of protocols for querying and disabling gesture recognition throughout the entire stack? An API in the GUI TK that an app uses to configure touch? I suppose that is what you architecting now. I understand it is not easy to do, in terms of coordinating all the software pieces and also in terms of providing a consistent user interface across platforms. It's simply a matter of what gestures Unity subscribes to. It could be configurable through gnome-control-center, for example. Some Unity options are already provided there. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/901630 Title: multitouch + qt doesn't work (eg fingerpaint demo) with wacom serial touchscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/901630/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 966619] Re: 3 Finger Touch and gestures no longer working
Hi Rishi, You probably have a touchpad that tells us of only two touch locations, but also tells us how many total touches are on the trackpad. When we moved to the new uTouch architecture in Precise, we lost the ability to support these types of devices. I am modifying the state of this bug to become a task to handle two- touch multitouch trackpads. ** Package changed: unity (Ubuntu) = xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Importance: Low = Wishlist ** Changed in: xorg-server (Ubuntu) Assignee: Chase Douglas (chasedouglas) = (unassigned) ** Summary changed: - 3 Finger Touch and gestures no longer working + Provide emulated three-touch gesture support for two-touch trackpads ** Also affects: utouch-frame (Ubuntu) Importance: Undecided Status: New ** Also affects: utouch-grail (Ubuntu) Importance: Undecided Status: New ** Also affects: utouch-grail Importance: Undecided Status: New ** Also affects: utouch-frame Importance: Undecided Status: New ** Changed in: utouch-frame Importance: Undecided = Wishlist ** Changed in: utouch-grail Importance: Undecided = Wishlist ** Changed in: utouch-frame (Ubuntu) Importance: Undecided = Wishlist ** Changed in: utouch-grail (Ubuntu) Importance: Undecided = Wishlist ** Changed in: utouch-frame Status: New = Triaged ** Changed in: utouch-grail Status: New = Triaged ** Changed in: utouch-frame (Ubuntu) Status: New = Triaged ** Changed in: utouch-grail (Ubuntu) Status: New = Triaged ** Changed in: xorg-server (Ubuntu) Status: New = Triaged ** Description changed: - 3 Finger touch support worked out of the box on my Dell XPS L501x in Ubunt 11.10. - This is no longer the case in 12.04. + Two-touch multitouch trackpads usually tell how many total touches are + on the device. If the trackpad reports three total touches, we can + emulate three touch gestures by following the movements of the two + reported touches. This requires the X server sending the details on the + number of touches, and the uTouch stack interpreting those details. + + Original Bug Report + === + 3 Finger touch support worked out of the box on my Dell XPS L501x in Ubunt 11.10. + This is no longer the case in 12.04. Symclient -m 100 reports all 3 fingers detected. Even the synaptiks app reports 3 finger touch support. It definitely worked fine in 11.10. Geisview reports device touches: 2 Any suggestions? I know the hardware supports it, because it worked before. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/966619 Title: Provide emulated three-touch gesture support for two-touch trackpads To manage notifications about this bug go to: https://bugs.launchpad.net/utouch-frame/+bug/966619/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 948587] Re: hid-wiimote driver causes Xorg crash in GetPointerEvents
** Changed in: xorg-server (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/948587 Title: hid-wiimote driver causes Xorg crash in GetPointerEvents To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/948587/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 901630] Re: multitouch + qt doesn't work (eg fingerpaint demo) with wacom serial touchscreen
Hi bootchk, Multitouch is supported in Qt in Ubuntu. We added support for it in Ubuntu 11.04 and have maintained it since then. We haven't had a chance to merge it upstream yet. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/901630 Title: multitouch + qt doesn't work (eg fingerpaint demo) with wacom serial touchscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/901630/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 968845] Re: bcm5974 touchpad doesn't work after S3 on MacBookAir
Hi Daniel, After you upgraded, did you log out and back in, or restart your computer? The changes would not take effect until you restarted the X server. That would explain why it didn't fix things at first, and now it is fixed. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/968845 Title: bcm5974 touchpad doesn't work after S3 on MacBookAir To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/968845/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 901630] Re: multitouch + qt doesn't work (eg fingerpaint demo) with wacom serial touchscreen
On 04/24/2012 04:35 PM, bootchk wrote: Thanks. How I interpret your last comment is: it is in Ubuntu but not upstream to Qt (whoever that is now, Nokia or other.) As long as I use Ubuntu's version of Qt (whether the source or libraries) it should work. Correct. Also, referring to: https://wiki.ubuntu.com/Multitouch , specifically where it says 2 finger gestures require extra setup. I interpret that to mean: without the setup, the synaptics driver (which is inappropriately named, is really THE driver for most touch HID's, not just those of the Synaptics brand) will hide all one finger and two finger events from further up the stack, i.e. from a Qt application? Possibly that is the problem with my testing. It could be. And then three and four finger interactions are grabbed by Unity. You have to put five or more fingers down on a trackpad to start sending events that aren't caught by Unity or X synaptics. The whole business of the stack confuses me. My understanding is a driver can translate certain sequences of touch events into single mouse events, i.e. recognize multi-finger gestures, in an attempt to be friendly to an app. For example, two finger tap in a certain corner translates to something, as you can see in the System Settings panel for a touchpad. For example, the way you must write an app to be pen-friendly is to rely on the translated mouse events instead of raw pen events. How does an application control what the driver does, if the application wants raw touch events to do its own gesture recognition? E.g. using Qt custom QGestureRecognizer. Does Qt have any way of knowing that certain friendly mouse events were in fact a sequence of touch events translated by a driver? (Not that it needs to, what could Qt or an app do differently if it knew, besides tell the user that the driver might be improperly setup for the gestures that Qt or the app was ready to recognize.) You're getting at the fundamental problem of the traditional touchpad gestures being interpreted in the X server. It worked reasonably well to this point, but is fundamentally broken now. We need to rework how touchpad gestures are recognized. They should be moved into the toolkits. However, that's a large amount of work. We are looking into our options. Does Qt QPanGesture require a certain number of fingers, or even require touch at all? For example, would Qt recognize a pan consisting of mouse events that were in fact translated from touch events by a touchpad driver? The Qt gestures only work with touch events, as far as I know. They will not work with mouse events. If there is a better forum for this discussion, please let me know. Feel free to ask questions and participate in discussions on the multi-touch-dev mailing list. You can subscribe on the project's page: http://launchpad.net/~multi-touch-dev -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/901630 Title: multitouch + qt doesn't work (eg fingerpaint demo) with wacom serial touchscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/901630/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 968845] Re: bcm5974 touchpad doesn't work after S3 on MacBookAir
For those of us who hit this issue and are proficient programmers (sarvatt, sforshee, laney, hint hint :), I suggest adding some debug statements inside the src/eventcomm.c touch handling functions to see exactly what is going on. The patch that RAOF added for this bug resets the touch state when the device is re-enabled, which I think happens on resume, so something is likely going wrong after that. Logging touch count changes would be a good first start, since the touch count determines whether the left or right clicks are emitted, and whether the cursor is moved or two-touch scrolling occurs. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/968845 Title: bcm5974 touchpad doesn't work after S3 on MacBookAir To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/968845/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 974887] Re: unity 3d touch stops registering clicks
xorg-server has been accepted into precise-proposed. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/974887 Title: unity 3d touch stops registering clicks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/974887/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 747835] Re: Add support for independent devices
** Summary changed: - Three Finger touch does not work on the Magic Mouse + Add support for independent devices ** No longer affects: unity ** No longer affects: unity (Ubuntu) ** Project changed: utouch = utouch-frame ** Also affects: utouch-grail Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Also affects: utouch-frame (Ubuntu) Importance: Undecided Status: New ** Also affects: utouch-geis (Ubuntu) Importance: Undecided Status: New ** Changed in: utouch-grail Status: New = Triaged ** Changed in: utouch-frame (Ubuntu) Status: New = Triaged ** Changed in: utouch-geis (Ubuntu) Status: New = Triaged ** Changed in: xorg-server (Ubuntu) Status: New = Triaged ** Changed in: utouch-grail Importance: Undecided = Wishlist ** Changed in: utouch-frame (Ubuntu) Importance: Undecided = Wishlist ** Changed in: xorg-server (Ubuntu) Importance: Undecided = Wishlist ** Changed in: utouch-geis (Ubuntu) Importance: Undecided = Wishlist -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/747835 Title: Add support for independent devices To manage notifications about this bug go to: https://bugs.launchpad.net/utouch-frame/+bug/747835/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 973297] Re: Xorg recognizes Logitech Headset USB dongle as input device then segfaults in XIChangeDeviceProperty
Hi Jean-Baptiste, You need to follow the instructions here to be able to install xserver- xorg-input-evdev-dbgsym: https://wiki.ubuntu.com/DebuggingProgramCrash. Alternatively, you could install it manually by downloading http://ddebs.ubuntu.com/pool/main/x/xserver-xorg-input-evdev/xserver- xorg-input-evdev-dbgsym_2.7.0-0ubuntu1_i386.ddeb. Please try again after installing the debug package. Thanks! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/973297 Title: Xorg recognizes Logitech Headset USB dongle as input device then segfaults in XIChangeDeviceProperty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/973297/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 974887] Re: unity 3d touch stops registering clicks
DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: Acer Aspire 1825PTZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-22-generic root=UUID=3edf82f9-f9ff-489c-8b24-2ffb824a9cd1 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to precise on 2012-03-11 (25 days ago) dmi.bios.date: 04/23/2010 dmi.bios.vendor: INSYDE dmi.bios.version: V1.3127 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM12-MS-CAP dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrV1.3127:bd04/23/2010:svnAcer:pnAspire1825PTZ:pvrV1.3127:rvnAcer:rnJM12-MS-CAP:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire 1825PTZ dmi.product.version: V1.3127 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.7.4-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 ** Also affects: xorg-server (Ubuntu Precise) Importance: Medium Assignee: Chase Douglas (chasedouglas) Status: In Progress ** Changed in: xorg-server (Ubuntu Precise) Importance: Medium = High ** Description changed: SRU Criteria [Impact] Touchscreen input handling is broken in many ways in the Precise X server. The issues include crashes, events sent to the wrong window, broken grabs, memory leaks, and Compiz and toolkit pop-up menu breakage. [Upstream Fixes] http://cgit.freedesktop.org/~cndougla/xserver/log/?h=input-fixes All commits were developed specifically for this bug. I just kept unraveling issues until things worked properly on my touchscreen. A high level overview of the impact of the fixes: * Crash or events sent to the wrong windows due to inappropriate casting and memory accesses: - - Check core event mask properly for pointer emulated touch events - - Only set XI2 mask if pointer emulation is for XI2 client - - Check other clients' core masks properly when adding touch listener + - Check core event mask properly for pointer emulated touch events + - Only set XI2 mask if pointer emulation is for XI2 client + - Check other clients' core masks properly when adding touch listener * Non-functional changes required for subsequent fixes: - - Split out helper function TouchListenerAcceptReject() - - Rename TouchEnsureSprite to TouchBuildSprite and event type checks + - Split out helper function TouchListenerAcceptReject() + - Rename TouchEnsureSprite to TouchBuildSprite and event type checks * Fixes for internal touch and pointer records remaining in an open state, leading to memory leaks and potentially input locking up: - - Accept touch sequence for pointer listener after second event delivery - - When deactivating an explicit pointer grab, reject all grabs on touches - - Ensure touch is ended when last listener is rejected + - Accept touch sequence for pointer listener after second event delivery + - When deactivating an explicit pointer grab, reject all grabs on touches + - Ensure touch is ended when last listener is rejected * Fixes for event and server time issues, which lead to grab and ungrab requests being rejected or unhandled: - - Fix copy/paste error from before git history in UpdateCurrentTimeIf() - - Update currentTime in dispatch loop - - Replay original touch begin event instead of generated begin event + - Fix copy/paste error from before git history in UpdateCurrentTimeIf() + - Update currentTime in dispatch loop + - Replay original touch begin event instead of generated begin event * Don't send end event to accepting client if touch hasn't physically ended: - - On touch accept, only process end event for owner if it has seen the end + - On touch accept, only process end event for owner if it has seen the end * Don't prematurely end touches and deactivate implicit grabs if a touch end event is emitted in response to something other than the touch physically ending: - - End a pointer emulated touch event only on a real end event - - Don't deactivate implicit pointer grab on fake touch end event + - End a pointer emulated touch event only on a real end event
[Ubuntu-x-swat] [Bug 974887] Re: unity 3d touch stops registering clicks
** Description changed: SRU Criteria [Impact] Touchscreen input handling is broken in many ways in the Precise X server. The issues include crashes, events sent to the wrong window, broken grabs, memory leaks, and Compiz and toolkit pop-up menu breakage. [Upstream Fixes] http://cgit.freedesktop.org/~cndougla/xserver/log/?h=input-fixes All commits were developed specifically for this bug. I just kept - unraveling issues until things worked properly on my touchscreen. These - patches have been reviewed by Peter Hutterer, the upstream X input - subsystem maintainer, and Bryce Harrington, one of the Ubuntu X team - members. A high level overview of the impact of the fixes: + unraveling issues until things worked properly on my touchscreen. A high + level overview of the impact of the fixes: * Crash or events sent to the wrong windows due to inappropriate casting and memory accesses: - Check core event mask properly for pointer emulated touch events - Only set XI2 mask if pointer emulation is for XI2 client - Check other clients' core masks properly when adding touch listener * Non-functional changes required for subsequent fixes: - Split out helper function TouchListenerAcceptReject() - Rename TouchEnsureSprite to TouchBuildSprite and event type checks * Fixes for internal touch and pointer records remaining in an open state, leading to memory leaks and potentially input locking up: - Accept touch sequence for pointer listener after second event delivery - When deactivating an explicit pointer grab, reject all grabs on touches - Ensure touch is ended when last listener is rejected * Fixes for event and server time issues, which lead to grab and ungrab requests being rejected or unhandled: - Fix copy/paste error from before git history in UpdateCurrentTimeIf() - Update currentTime in dispatch loop - Replay original touch begin event instead of generated begin event * Don't send end event to accepting client if touch hasn't physically ended: - On touch accept, only process end event for owner if it has seen the end * Don't prematurely end touches and deactivate implicit grabs if a touch end event is emitted in response to something other than the touch physically ending: - End a pointer emulated touch event only on a real end event - Don't deactivate implicit pointer grab on fake touch end event * Fix toolkit pop-up menus so when you touch the menu, it opens, and then you drag to select an item before lifting the menu will receive the events: - When activating an explicit grab, update owning listener * Fix dragging a Compiz window by touching the title bar using a touchscreen: - Create a new dix touch record for an emulated touch with no listeners - Update device state including when touch record does not exist [Development Fix] The Q series is not open yet, so there is no development fix. [Stable Fix] The upstream fixes have been squashed and rebased into one patch for the Precise xorg-server. The patch has been attached. The touch code has been completely rewritten from the prototype implementation in previous Ubuntu releases, so these changes have not been nominated for them. + + [Test Cases] + * Attempt to interact with a GTK menu on a touchscreen by touching to open the menu and dragging to select items without lifting the touch in between. The items should highlight, and the selected item should activate. + * Attempt to move a window in Unity 3D by dragging the title bar with a touchscreen touch. + * Interact with various windows in Unity to raise them. This exercises grabbing code paths. Ensure all input devices continue to function properly, no crashes result, and events appear to go to the appropriate windows. [Regression Potential] Many patches only affect touch pointer emulation, which only affects touchscreens. The code paths modified should have no regression potential for other usages. Some of the other patches affect touch handling in general. These could impact gestures for trackpads, but traditional trackpad pointing and clicking does not go through these code paths. The server time fixes that are not touch-specific are small and merely keep the server time more up to date than it currently is. There could be a regression potential here for input device grabbing, but it is unlikely. Original Bug Report === Hi, similar to #949791 ... that bug made things better (i can now move windows using the touch screen) but it still often stops to react to any clicks when using touch. I just updated. In unity 3d (not in unity 2d nor in gnome shell) if i touch the top bar without any program running it most of the time stops to react to any clicks (both touch and clicks of the touch pad buttons). I cannot reproduce it always with the first touch but usually latest with 2 or 3. i
[Ubuntu-x-swat] [Bug 930936] Re: Xorg crashes after connect bluetooth keyboard
It looks like this wasn't actually enabled in the 1.11.4-0ubuntu8 package: http://anonscm.debian.org/gitweb/?p=pkg-xorg/xserver/xorg- server.git;a=commitdiff;h=d8e24bf6634b0ef80a21ac1d1b13412d88aa7800;hp=3a70935e497c908419a2704e699e615d148718d3 This has been fixed in this packaging commit, and will be applied for 1.11.4-0ubuntu11: http://anonscm.debian.org/gitweb/?p=pkg-xorg/xserver/xorg- server.git;a=commitdiff;h=5042d16f315953b76dc59a6d8063638a42f23b18;hp=362e84eae058b86a7a67b8993d0a1a2b57fac9a1 ** Changed in: xorg-server (Ubuntu Precise) Status: Fix Released = Fix Committed ** Description changed: + SRU Criteria + + [Impact] + The X server may crash after connecting a bluetooth keyboard. + + [Development Fix] + The Q series is not open for development yet. + + [Stable Fix] + Please see the attached patch midispcur.c.patch. + + [Test Case] + Connect a bluetooth keyboard and use it for five minutes. Check if X server has crashed. + + [Regression Potential] + Low. The patch merely short circuits code that may dereference a NULL pointer. It is possible that this causes a further issue, but such an issue is likely to be at worst just as bad as without this fix. + + Original Bug Report + === X crashes after connect bluetooth keyboard. With bluetooth mouse everything ok, crash only when i connect keyboard. After connecting the keyboard works and i can use it. Failure occurs in the interval between 30 seconds and 5 minutes after connecting. It does not depend on whether I'm typing on a keyboard or not. On Ubuntu Lucid same error ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xserver-xorg 1:7.6+7ubuntu7.1 ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13 Uname: Linux 3.0.0-15-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Sun Feb 12 16:08:39 2012 InstallationMedia: Ubuntu 11.10 Oneiric - Build i386 LIVE Binary 20120208-10:12 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/930936 Title: Xorg crashes after connect bluetooth keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/930936/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 974887] Re: unity 3d touch stops registering clicks
** Changed in: xorg-server (Ubuntu Precise) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/974887 Title: unity 3d touch stops registering clicks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/974887/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 968845] Re: bcm5974 touchpad doesn't work after S3 on MacBookAir
The root cause is the hardware itself. The work around of adding a SUSPEND_MODULES config file to /etc/pm/config.d should fix the issue for broken input after resume. The next question is: what package should this go into? I would suggest pm-utils since it already has video quirks. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/968845 Title: bcm5974 touchpad doesn't work after S3 on MacBookAir To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/968845/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 973297] Re: Xorg recognizes Logitech Headset USB dongle as input device then segfaults in XIChangeDeviceProperty
I can't reproduce the issue with the evemu device prop file. Let's try traditional debugging approaches. Please install xserver-xorg-input- evdev-dbgsym from the ddebs archive. Then start X, attach to it with gdb, plug in your headset, and when it crashes issue bt full and attach the output here. Thanks! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/973297 Title: Xorg recognizes Logitech Headset USB dongle as input device then segfaults in XIChangeDeviceProperty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/973297/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 974887] Re: unity 3d touch stops registering clicks
I have found the causes of both Henri's and mweyen's issues, along with multiple other bug fixes along the way. They have all be proposed upstream on the xorg-devel mailing list and uploaded to the jupiter ppa as 1.11.4-0ubuntu11~jupter7. Please retest. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/974887 Title: unity 3d touch stops registering clicks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/974887/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 968845] Re: bcm5974 touchpad doesn't work after S3 on MacBookAir
Hi Gorka, The cursor moving while the trackpad button is pressed is expected behavior. It allows for operations like click + drag. Thanks! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/968845 Title: bcm5974 touchpad doesn't work after S3 on MacBookAir To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/968845/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 973297] Re: Xorg recognizes Logitech Headset USB dongle as input device then segfaults in XIChangeDeviceProperty
I think this patch may fix things: http://lists.x.org/archives/xorg-devel/2012-March/030178.html -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/973297 Title: Xorg recognizes Logitech Headset USB dongle as input device then segfaults in XIChangeDeviceProperty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/973297/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 973297] Re: Xorg recognizes Logitech Headset USB dongle as input device then segfaults in XIChangeDeviceProperty
Just to be sure, please capture an evemu device property file. Plug in the device. Then run: $ sudo evtest Determine which /dev/input/event* node pertains to your headset. Then run: $ sudo evemu-describe [/dev/input/event* node] device.prop Attach device.prop here. Then anyone else can load the device virtually to reproduce. ** Changed in: xorg-server (Ubuntu) Assignee: (unassigned) = Chase Douglas (chasedouglas) ** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Precise) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/973297 Title: Xorg recognizes Logitech Headset USB dongle as input device then segfaults in XIChangeDeviceProperty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/973297/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 974887] Re: unity 3d touch stops registering clicks
Hi Henri, Your backtrace looks like a general corruption of some sort. We have been seeing these in the precise X server, but we have not been able to track down the issue. If you can find a way to reproduce the issue please let us know. THanks! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/974887 Title: unity 3d touch stops registering clicks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/974887/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 974887] Re: unity 3d touch stops registering clicks
Hi mweyen, I believe the issue you are seeing is a bug in gtk. It is using GTK 3, which now has some touch support. I have tracked the X event handling through the X server and found that it is sending events correctly. Please file a separate bug for this issue against gtk+3.0. Please confirm that there are no other issues with the jupiter6 X server. I would like to begin preparing an SRU for the fixes for this bug. Thanks! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/974887 Title: unity 3d touch stops registering clicks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/974887/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 974887] Re: unity 3d touch stops registering clicks
Hi mweyen, Good point about reporting a bug against a PPA. Lets wait until this bug is fixed at least in precise-proposed. Thanks! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/974887 Title: unity 3d touch stops registering clicks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/974887/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 943880] Re: Xorg crashed with SIGABRT in __libc_message() from malloc_printerr() via XIDestroyDeviceProperty
I just figure out today how to get what I believe is a full unity session up and running in a valgrind X: 1. Log out, we're going to stop the current X session. 2. Switch to a VT (ctrl+alt+fn2) 3. Log in 4. $ sudo stop lightdm 5. $ sudo valgrind Xorg :0 21 | tee /tmp/log 6. Switch to another VT (ctrl+alt+fn3) and login (or use a different screen window if you are running screen) 7. $ DISPLAY=:0 dbus-launch unity Make sure there are no user dbus daemons running before running dbus- launch. That seemed to mess things up. Also, the desktop is going to run *REALLY* *REALLY* slow and might take multiple minutes just to start. It may also have all kinds of visual artifacts. Hopefully you can get around them to reproduce the issue. Once you have, attach /tmp/log here. Thanks! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/943880 Title: Xorg crashed with SIGABRT in __libc_message() from malloc_printerr() via XIDestroyDeviceProperty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/943880/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 980041] [NEW] Button mask and labels are reported wrong, array offset of 1 element
Public bug reported: libXi transforms the XI wire protocol data into client library structures. A recent change ensured that the client structures were formatted properly so doubles were aligned to 8 bytes. However, this change introduced an off-by-one bug when copying button state and labels. The fix is here: http://cgit.freedesktop.org/xorg/lib/libXi/commit/?id=8436c920953f288aea2d6d5f370f8eaaaef82d97 Without this fix, xinput list device id|device name is broken. It fails with an error about a bad atom passed to XGetAtomName because the last button label returned from XIQueryDevice() is invalid. ** Affects: libxi (Ubuntu) Importance: Medium Assignee: Chase Douglas (chasedouglas) Status: In Progress -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libxi in Ubuntu. https://bugs.launchpad.net/bugs/980041 Title: Button mask and labels are reported wrong, array offset of 1 element To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxi/+bug/980041/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 980041] Re: Button mask and labels are reported wrong, array offset of 1 element
** Changed in: libxi (Ubuntu) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libxi in Ubuntu. https://bugs.launchpad.net/bugs/980041 Title: Button mask and labels are reported wrong, array offset of 1 element To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxi/+bug/980041/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 980041] Re: Button mask and labels are reported wrong, array offset of 1 element
** Tags added: precise -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libxi in Ubuntu. https://bugs.launchpad.net/bugs/980041 Title: Button mask and labels are reported wrong, array offset of 1 element To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxi/+bug/980041/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 974887] Re: unity 3d touch stops registering clicks
** Package changed: unity (Ubuntu) = xorg-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/974887 Title: unity 3d touch stops registering clicks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/974887/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 974017] Re: Crash when touching Apple trackpad with 11 fingers
** Summary changed: - Crash when touching trackpad with 10 fingers + Crash when touching Apple trackpad with 11 fingers ** Description changed: - Using an Apple Magic Trackpad, pair it to the system and put down 10 + Using an Apple Magic Trackpad, pair it to the system and put down 11 fingers. Unity-2D will freeze immediately and after a while X gets restarted. Running newest Precise with uTouch daily build PPA. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity-2d 5.8.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Thu Apr 5 10:38:34 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120327.1) PackageArchitecture: all ProcEnviron: - LANGUAGE=en_US:en - TERM=xterm - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/zsh + LANGUAGE=en_US:en + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/zsh SourcePackage: unity-2d UpgradeStatus: No upgrade log present (probably fresh install) ** No longer affects: unity-2d (Ubuntu) ** No longer affects: unity (Ubuntu) ** Package changed: xorg-server (Ubuntu) = xserver-xorg-input-synaptics (Ubuntu) ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Status: Confirmed = In Progress ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Assignee: (unassigned) = Chase Douglas (chasedouglas) ** Description changed: - Using an Apple Magic Trackpad, pair it to the system and put down 11 - fingers. Unity-2D will freeze immediately and after a while X gets - restarted. + The default number of touch records allocated in the synaptics driver is + 10. The Apple multitouch trackpads support at least 11, which can occur + spuriously with 10 fingers on the device. The synaptics driver does not + do proper bounds checking on the touch record array, so when the 11th + touch occurs the X server crashes. + + Original bug report + === + Using an Apple Magic Trackpad, pair it to the system and put down 11 fingers. Unity-2D will freeze immediately and after a while X gets restarted. Running newest Precise with uTouch daily build PPA. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity-2d 5.8.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Thu Apr 5 10:38:34 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120327.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: unity-2d UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/974017 Title: Crash when touching Apple trackpad with 11 fingers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/974017/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 974017] Re: Crash when touching Apple trackpad with 11 fingers
** Patch added: Fix for out of bounds touch record access https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/974017/+attachment/3035860/+files/0001-Fix-crash-on-Apple-trackpads-when-touching-with-more.patch -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/974017 Title: Crash when touching Apple trackpad with 11 fingers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/974017/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 974017] Re: Crash when touching Apple trackpad with 11 fingers
To expand on my previous bug comment, I can reproduce the issue now that I know to try with 10 fingers and a nose instead of merely tapping and moving quickly with 10 fingers trying to generate a spurious 11th touch. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/974017 Title: Crash when touching Apple trackpad with 11 fingers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/974017/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 975356] Re: Logging from signal context is unsafe
This new version of the patch fixes issues in the first version and adds many more logging paths that needed fixing. The cause of a bug that was thought to be fixed by this patch has been found. As such, the only known effect of this patch is to not crash valgrind when attempting to log in a signal handler. Since this is a large patch to be adding this late in the cycle, I am marking this bug as won't fix for precise. We can add it in Q. ** Patch added: Proposed fix for signal-unsafe logging v2 https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/975356/+attachment/3036000/+files/228_sigsafe_logging.patch ** Also affects: xorg-server (Ubuntu Precise) Importance: Medium Assignee: Chase Douglas (chasedouglas) Status: In Progress ** Also affects: xorg-server (Ubuntu Q-series) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu Precise) Status: In Progress = Won't Fix ** Changed in: xorg-server (Ubuntu Q-series) Status: New = Triaged ** Changed in: xorg-server (Ubuntu Q-series) Importance: Undecided = Medium ** Changed in: xorg-server (Ubuntu Q-series) Assignee: (unassigned) = Chase Douglas (chasedouglas) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/975356 Title: Logging from signal context is unsafe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/975356/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 975356] [NEW] Logging from signal context is unsafe
Public bug reported: The X internal logging functions use signal-unsafe functions. However, the server is logging messages while in signal context. This can create memory and locking corruption. ** Affects: xorg-server (Ubuntu) Importance: Medium Assignee: Chase Douglas (chasedouglas) Status: In Progress -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/975356 Title: Logging from signal context is unsafe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/975356/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 975356] Re: Logging from signal context is unsafe
The patch is derived from the patch series I submitted upstream for this issue: http://lists.x.org/archives/xorg-devel/2012-April/030285.html ** Attachment added: Proposed fix for signal-unsafe logging https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/975356/+attachment/3017803/+files/patch -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/975356 Title: Logging from signal context is unsafe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/975356/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 975356] Re: Logging from signal context is unsafe
The patch has been refreshed with a fix for a test case. It has been uploaded to ppa:chasedouglas/jupiter for testing. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/975356 Title: Logging from signal context is unsafe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/975356/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 972727] Re: Synaptics Clickpad functionalities incomplete: Right button area, two-tap disabling
Hi Mason, See Robert's comment above on how to enable it by default. I recognize that it's not as easy as providing an option in gnome-control-center, but for those who really want it it isn't too difficult either. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/972727 Title: Synaptics Clickpad functionalities incomplete: Right button area, two- tap disabling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/972727/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 582809] Re: Synaptics Clickpad touchpad buttons are not working
This should all be fixed. The only remaining issue is that the right button area is not handled as a right click by default. The support for it came too late in the cycle to enable it by default. You can follow that issue in bug 972727. ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/582809 Title: Synaptics Clickpad touchpad buttons are not working To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/582809/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 582809] Re: Synaptics Clickpad touchpad buttons are not working
I am declining any work on Lucid because the features necessary in the kernel and the X.org stack are not available in that release. It is not feasible to backport fixes to it. ** Changed in: xserver-xorg-input-synaptics (Ubuntu Maverick) Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/582809 Title: Synaptics Clickpad touchpad buttons are not working To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/582809/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 949791] Re: Touchscreen does not work with unity-3d
mweyen, I forgot to add, please assign me when you've created the new bug. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/949791 Title: Touchscreen does not work with unity-3d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/949791/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 949791] Re: Touchscreen does not work with unity-3d
Hi mweyen, Please file a new bug report for the remaining issues you see. Thanks! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/949791 Title: Touchscreen does not work with unity-3d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/949791/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 968845] Re: bcm5974 touchpad doesn't work after S3
I don't think asking xf86-input-synaptics to listen to unrelated events is a good idea. However, there is functionality already present in synaptics that we may be able to use: the Synaptics Off option. Syndaemon already uses this to disable the trackpad when the user is typing on the keyboard. We could add functionality to syndaemon to listen for lid closure as well. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/968845 Title: bcm5974 touchpad doesn't work after S3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/968845/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 949791] Re: Touchscreen does not work with unity-3d
This is caused by bad input event mask checking and handling in the X server for touchscreen pointer emulation. The following patches fix the issue: http://lists.x.org/archives/xorg-devel/2012-April/030265.html http://lists.x.org/archives/xorg-devel/2012-April/030267.html http://lists.x.org/archives/xorg-devel/2012-April/030266.html ** Package changed: unity (Ubuntu) = xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Milestone: None = ubuntu-12.04 ** Changed in: xorg-server (Ubuntu) Status: Triaged = In Progress ** Changed in: xorg-server (Ubuntu) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/949791 Title: Touchscreen does not work with unity-3d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/949791/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 949791] Re: Touchscreen does not work with unity-3d
Some more info on what was going on: Nautilus, the file manager, is in charge of the desktop. This is how files on your desktop are managed. When it sees button press event, it grabs the device. When the button release event is seen, it ungrabs the device. GTK is only selecting for events on master devices, but if it sees an event on a slave device it will interpret the event as though it came from a master device. The bugs in the X server were generating both master and slave button press events. Slave and master events are delivered independently. The master button presses were being sent correctly to other windows that the user touched. The slave button presses were being sent only to Nautilus due to the X bug. This was causing nautilus to grab the master device, so all further events were being directed to it instead of to other windows. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/949791 Title: Touchscreen does not work with unity-3d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/949791/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 973783] [NEW] Two touch tap defaults to middle button instead of right button click
Public bug reported: This usually isn't seen because gnome-settings-daemon overwrites the setting once logged in. However, if g-s-d isn't used or isn't running, the user will be left with the wrong setting. This is due to a bad change in distro patch 104_always_enable_tapping.patch: -/* Enable tap if we don't have a phys left button */ -tapButton1 = priv-has_left ? 0 : 1; -tapButton2 = priv-has_left ? 0 : 3; -tapButton3 = priv-has_left ? 0 : 2; +/* Enable tap */ +tapButton1 = 1; +tapButton2 = 2; +tapButton3 = 3; ** Affects: xserver-xorg-input-synaptics (Ubuntu) Importance: Low Assignee: Chase Douglas (chasedouglas) Status: In Progress -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/973783 Title: Two touch tap defaults to middle button instead of right button click To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/973783/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 972727] Re: Synaptics Clickpad functionalities incomplete: Right button area, two-tap disabling
I do plan to enable it in 12.10. I suggest following Robert's approach for 12.04. ** Also affects: xserver-xorg-input-synaptics (Ubuntu Precise) Importance: Wishlist Status: Triaged ** Also affects: xserver-xorg-input-synaptics (Ubuntu Q-series) Importance: Undecided Status: New ** Changed in: xserver-xorg-input-synaptics (Ubuntu Precise) Status: Triaged = Won't Fix ** Changed in: xserver-xorg-input-synaptics (Ubuntu Q-series) Importance: Undecided = Wishlist ** Changed in: xserver-xorg-input-synaptics (Ubuntu Q-series) Status: New = Triaged ** Changed in: xserver-xorg-input-synaptics (Ubuntu Q-series) Assignee: (unassigned) = Chase Douglas (chasedouglas) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/972727 Title: Synaptics Clickpad functionalities incomplete: Right button area, two- tap disabling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/972727/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 972125] Re: Right and middle mouse button do not work on clickpad
*** This bug is a duplicate of bug 972727 *** https://bugs.launchpad.net/bugs/972727 ** This bug has been marked a duplicate of bug 972727 Synaptics Clickpad functionalities incomplete: Right button area, two-tap disabling -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/972125 Title: Right and middle mouse button do not work on clickpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/972125/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 972727] Re: Synaptics Clickpad functionalities incomplete: Right button area, two-tap disabling
Hi Mason, While I understand your sentiment, clickpad support is fully available in 12.04. The right button area is not enabled by default, but it can be easily enabled by users who want it. There's a lot to clickpad functionality beyond just emitting the correct button click when tapping or clicking in specific areas. Two touch click and drag is a major piece of the puzzle, and that is enabled by default. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/972727 Title: Synaptics Clickpad functionalities incomplete: Right button area, two- tap disabling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/972727/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 968845] Re: bcm5974 touchpad doesn't work after S3 on MacBookAir4, 1
This is something that requires some physical testing to ensure it gets done right. Unfortunately, my Macbook 5,1 laptop won't resume from suspend, so I can't really develop a fix for this. I'm unassigning myself. A workaround is to unload and reload the bcm5974 kernel module: $ sudo rmmod bcm5974 $ sudo modprobe bcm5974 This will reset the state of synaptics. ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Assignee: Chase Douglas (chasedouglas) = (unassigned) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/968845 Title: bcm5974 touchpad doesn't work after S3 on MacBookAir4,1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/968845/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 969495] Re: evdev stopped remapping events
Hi Pieter, For Ubuntu, you need to branch the package: $ bzr branch lp:ubuntu/xserver-xorg-input-evdev Then add the patch that adds the remap functionality inside debian/patches/ As for upstream, please provide the patch in the bug report. It is more likely to be reviewed if a patch is readily available. Also, if you are comfortable sending to a mailing list, the preferred mechanism for X development is to send patches for review to xorg-de...@lists.x.org. Thanks! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/969495 Title: evdev stopped remapping events To manage notifications about this bug go to: https://bugs.launchpad.net/evdev/+bug/969495/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 972985] [NEW] XQueryPointer does not return button 1 set when touch on touchscreen is active
Public bug reported: This causes compiz to not see the touch event as a mouse button event, and since compiz is not touch-aware it disregards the event entirely. This may also be causing compiz to not call XAllowEvents on grabbed button events, which causes all further pointer interaction from any device to be broken. ** Affects: xorg-server (Ubuntu) Importance: High Assignee: Chase Douglas (chasedouglas) Status: In Progress -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/972985 Title: XQueryPointer does not return button 1 set when touch on touchscreen is active To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/972985/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 971783] [NEW] 3 touch taps and clicks are broken
Public bug reported: xserver-xorg-input-synaptics 1.5.99.902-0ubuntu1 caused a regression in functionality. Three touch taps and click actions, which may be set using synclient TapButton3=2 and synclient ClickFinger3=2, no longer function correctly on many touchpads. Some devices report a higher touch count than the number of touches they can provide data for. For example, many Synaptics touchpads can report up to five touches, but only provide data for two of them. We need to be able to report the correct number of touches for these devices when there are three touches. Using the maximum of the reported touch count and the number of touches provided ensures the count is accurate for all device types. ** Affects: xserver-xorg-input-synaptics (Ubuntu) Importance: Low Assignee: Chase Douglas (chasedouglas) Status: In Progress -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/971783 Title: 3 touch taps and clicks are broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/971783/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 754000] Re: Running Unity disables Xorg's 3-finger click support (middle click)
Rather than reuse this bug for a new issue, I've decided to create a new bug and revert this to Won't Fix. Please see bug 971783 for more details. Thanks! ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Status: Confirmed = Won't Fix ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Assignee: Chase Douglas (chasedouglas) = (unassigned) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/754000 Title: Running Unity disables Xorg's 3-finger click support (middle click) To manage notifications about this bug go to: https://bugs.launchpad.net/mactel-support/+bug/754000/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
