kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

luckymurari, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal
(Applications->Accessories->Terminal), as it will automatically gather
and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results. Thank you for your
understanding.

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
       Status: In Progress => Incomplete

** Changed in: linux (Ubuntu)
     Assignee: Brad Figg (brad-figg) => (unassigned)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/791833

Title:
  Dell ST2220T Monitor responds to touch only on warm boot from windows

Status in OEM Priority Project:
  Invalid
Status in OEM Priority Project oneiric series:
  Invalid
Status in “linux” package in Ubuntu:
  Incomplete
Status in “linux” source package in Oneiric:
  Invalid
Status in “linux” package in Fedora:
  Unknown

Bug description:
  Dell ST2220T Monitors have been purchased. On first install, the
  touchscreen worked pretty well. But it started to behave weird after
  restarts. The behaviour is as follows:

  On cold boot touch never works. But once going to Windows 7 and coming
  back after a warm boot, the touch works perfectly. From now, it works
  until there are no cold boots. Once cold boot happens into Ubuntu,
  touch stops working. This behaviour has been consistent. I tried to
  put usbhid.quirks with <vendorid> : <productid>: 0x40 as  mentioned
  here http://ubuntuforums.org/showthread.php?p=10287057#post10287057
  but it did not work.

  This is on Ubuntu Natty.

  A patch from Red Hat bugzilla:
  https://bugzilla.redhat.com/show_bug.cgi?id=703118   seems to help the
  issue significantly, but, a few touch features (such as "click") seem
  to still need some work.  The patch doesn't seem to be upstream yet in
  the mainline kernel.


  
  SRU Request:

  Impact:

  Customer currently has 150 of these monitors with plans to expand to 1,500 next year and 10,000 in the year after that. Getting these devices to
  work with ubuntu will help out a lot with cost reduction for the customer.

  Patch:

  See bugzilla reference above.

  Steps to reproduce:

  1) Install 11.04 (In this case the system was dual-booted with Windows 7)
  2) Without the patch, the touchscreen only seems to work if the machine is warm-rebooted from Windows. The touch features don't work at all if the system is cold-booted into Ubuntu.
  3) With the patch, the touchscreen appears to work with cold boots and warm reboots, but, 'click' features on the touchscreen still need to be applied.

  TEST CASE:

  Apply the patch to the kernel, then test the touchscreen after warm
  reboots and cold boots to ensure that the touchscreen is fully
  functional.  Customer has agreed to assist with testing, etc.

  Regression Potential:

  Unknown at this time.  Patch appears to be pretty trivial and isolated
  so regression potential seems to be pretty low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/791833/+subscriptions