I have the same problems as described in this bug. Every time I print
something cupsd crashes with core dump and cups-browsed also crashes. My
printer is a Samsung CLX 6260 Series. I can successfully print one job,
then get the crash, then have to wait some minutes before the services
are up
The best would be to add it to the settings, make the behaviour optional
(like the hiding of the launcher in Unity 7), forgot to add that to my
post.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Opening the app switcher has become extremely laggy on mx4.
When opening it there's always (since ota-14) a great lagg, it happens
every time, which was not the case before the update. The scrolling is
also a bit laggy but at least for me the worst part is when I swipe it
open. Happens 100% of
Why would it have a edge trigger? For desktop usage there's Alt + Tab.
When there's no keyboard, swipe (touch screen) or use the launcher
(touch or mouse).
I have only tried desktop mode a few times with mouse and keyboard but
this was a problem.
--
You received this bug notification because
My experience with my mx4 is that most of the time the hotspot works
after a couple of attempts (almost always fails on first attempt) but
the last months it rarely show any indicator. It also, as stated earlier
by others in this thread, often stays active after turned off.
For me, the hotspot
The browser app will never be good in my opinion without an adblocker.
Host blocking works well on Ubuntu Touch, no need to make / writable
more than temporarily. It isn't enough however. Some web sites deliver
the ads themselves through their site and for those sites host blocking
doesn't work.
This bug has become a big problem for me.
The home button also serves to wake the phone up and show the lock screen.
I prefer to have the notification drawer available when the device is locked
but due to this bug the phone wakes up in my pocket.
Then some of the following things randomly
Matthew, ok I didn't know it was a bug.
I added myself as affected for that bug though I still think it may be
something that needs to be added. At least an indicator, I have no idea how
many different sound groups we have (or what they're called).
--
You received this bug notification
I would even say that the edge width needs to be configurable by the
user.
Personally I use a cover for my Meizu mx4 and the edges of the cover
gets in the way when i swipe.
It especially affects the gesture for the launcher and for swiping to
the home screen, which I perform successfully about
I never start listen to music with headphones on my ears because the
phone almost always chose maximum volume and the output will be max for
a moment, even with the warning dialog showing on screen, before
automatically lowering it slightly.
I don't dare using headphones until I have checked the
This hardware should be supported out-of-the-box in natty. Davide, if
you have the opportunity, it would be great with a confirmation. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/654507
Benjamin, on what device are you experiencing the inverted axes?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/549447
Title:
eGalax touchscreen configured as tablet
--
ubuntu-bugs mailing list
This request was actually never merged and uploaded, and was never part
of the critical set of changes needed for unity. We are retracting this
request, retargeting for oneiric instead. Thanks.
** Changed in: utouch-frame
Status: Fix Released = Invalid
** Changed in: utouch-frame
Something else seems to be wrong here. I have never seen the package
problem before, and it works fine in this end. Fully updated natty. I
just do
sudo apt-get install hid-ntrig-dkms
reboot
to install, and
sudo apt-get purge hid-ntrig-dkms
reboot
to uninstall.
--
You received this bug
The compiz plugin is not used (yet), so this problem should most likely
be filed against unity itself. Please also note the date of the latest
update, since the problem might already be fixed.
** Changed in: utouch-compiz (Ubuntu)
Status: New = Invalid
--
You received this bug
The latest ntrig driver is 1.1.4, so perhaps you like to try again with a fully
updated system.
Also, the hid-dkms package was updated for other reasons, so please try the new
attached version. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: hid-dkms for testing hid limits
https://bugs.launchpad.net/ubuntu/+source/utouch/+bug/724831/+attachment/2014949/+files/hid-dkms_1.1.2%7Etest2_all.deb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The hid-ntrig-dkms-1.1.3 version had mismatching package and
installation version, very confusing. I have uploaded 1.1.5 to fix that.
All current package do however compile and run as expected, so previous
comments still apply. Thanks!
--
You received this bug notification because you are a
To clarify, the mentioned bug is about the synaptics kernel driver,
which lives in the psmouse kernel module. This bug is about the ALPS
kernel driver, which lives in the same kernel module.
Unfortunately, the ALPS touchpads do not have MT support in the kernel -
yet.
** Changed in: utouch
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/643212
Title:
ntrig touchscreen no longer works
--
ubuntu-bugs mailing list
This should work fine in natty, or in maverick using the utouch ppa dkms
packages. If someone still has problems, please do tell.
** Changed in: utouch
Status: New = Fix Committed
** Changed in: utouch
Importance: Undecided = Medium
--
You received this bug notification because you
** Changed in: utouch
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/620609
Title:
add touch support for ACER 1820PTZ [MosArt RMTP-MA957]
--
ubuntu-bugs
** Changed in: utouch-grail (Ubuntu)
Assignee: Henrik Rydberg (rydberg) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/742582
Title:
Add touch gesture events
--
ubuntu-bugs
Regarding the timing of these changes, I believe we are all aware they
are late indeed. The reason we still propose them is probably also clear
to everyone.
Regarding the nature of the changes, the impact on existing setups is
much smaller than what it may seem like. It is not exactly zero, but
This bug, as stated in the title, has been fixed upstream (2.6.38), and
has been released in natty. There is also a package linked in this bug,
confirmed by a large number of users, to work on maverick. Therefore, I
am marking this bug as fixed.
Please people, if you still experience problems
** Branch linked: lp:~utouch-team/utouch-grail/trunk.endfix2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/744391
Title:
sometimes gestures stick around uncompleted
--
ubuntu-bugs mailing list
Great wiki, Chase.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/742567
Title:
multitouch events do not respect swap/invert axes properties
--
ubuntu-bugs mailing list
** Changed in: utouch-grail
Importance: Medium = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/744391
Title:
sometimes gestures stick around uncompleted
--
ubuntu-bugs mailing list
Why is this important if semi-mt devices are not even supported yet?
I suggest we let this one stay in trunk together with all the other
major but less critical changes, as we discussed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thank you very much for this information. It seems your device hits a
limitation in the hid parser. The attached package changes that
limitation, but might have other side effects. Once again, the debug
output will be most valuable. Thanks!
--
You received this bug notification because you are a
** Attachment added: hid parser test limits
https://bugs.launchpad.net/ubuntu/+source/utouch/+bug/724831/+attachment/1939478/+files/hid-dkms_1.1.2%7Etest1_all.deb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Interesting. This will turn on more information:
echo 1 | sudo tee /sys/module/hid/parameters/debug
(a zero will turn debug output off)
In addition, since it seems to be a parsing error, having the full
description of the device would be useful. Please download this script,
for instance like
The evdev protocol only sends changes, so this is perfectly normal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/736500
Title:
very jumpy cursor with wacom-dkms
--
ubuntu-bugs mailing list
The name is Henrik.
The fact that the problem does not show up in the a different desktop
setting means the problem seems to be related to something else,
possibly simpler to fix. That is good news. I would recommend trying the
next level now, X. Try logging into a safe mode session and see if
The recording does not seem to exhibit the irregularities you mentioned.
Perhaps it did not occur during this particular recording?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/736500
Title:
very
Hi again, does this version work better? Thanks for testing!
** Attachment added: for testing 0008
https://bugs.launchpad.net/ubuntu/+source/utouch/+bug/724831/+attachment/1929387/+files/hid-ntrig-dkms_1.1.3%7Etest5_all.deb
--
You received this bug notification because you are a member of
My bad, I assumed this would be for natty now. Backporting to maverick
will probably happen at some point, but it would be even better to get a
confirmation that this works in natty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The wacom-pen2.record file seems fine here, and looking through the
file, there is nothing special happening with the y axis (grep for 0003
0001 in the file). In other words, this might still be due to some
other fu in your system.
--
You received this bug notification because you are a member
** Attachment added: debdiff
https://bugs.launchpad.net/utouch-frame/+bug/735672/+attachment/1910879/+files/debdiff.txt
** Branch linked: lp:utouch-frame
** Branch linked: lp:ubuntu/utouch-frame
** Also affects: utouch-frame (Ubuntu)
Importance: Undecided
Status: New
** Changed
** Also affects: utouch-evemu (Ubuntu)
Importance: Undecided
Status: New
** Changed in: utouch-evemu
Status: New = Fix Committed
** Changed in: utouch-evemu
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Here is an updated package, with support for all Bamboos, and more.
Should run on all architectures, and on both maverick and natty. Please
install and test and report successes or failures here. Thanks!
** Attachment added: wacom-dkms-1.0.6 test driver
Old bug so hard to tell what you fine people are running now, but there
are two things that might be possible off-hand:
1. Install the linux-backports-modules-input package (in ubuntu
backports repo).
2. Install the hid-wacom-dkms package (utouch ppa)
The first approach should be valid for
It seems the project is there, the package is built, but there is no
package in the repo. According to didrocks, a binary new seems needed.
** Changed in: mtview (Ubuntu)
Status: Fix Released = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Bug number added to the changelog and pushed to the packaging branch.
** Also affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/702630
Title:
Moved the packaging branch to the utouch-packaging team,
https://code.launchpad.net/~utouch-packaging/mtview/ubuntu
to simplify future modifications. Also added a Vcs-Bzr tag. Thanks
didrocks!
** Branch linked: lp:~utouch-packaging/mtview/ubuntu
** Branch unlinked:
Public bug reported:
Binary package hint: xserver-xorg-input-evdev
This problem is shared between evdev and synaptics, is part of the
gesture patch, and has an easy fix. Under some circumstances, the
gestures can end up at the wrong window, because the gesture mask is not
always cleared for a
Boyle, here is a first attempt at support for your device. Please
install the package and report the output of dmesg | grep -i ntrig.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/724831
Title:
** Attachment added: test support for 0x0008 (test1)
https://bugs.launchpad.net/ubuntu/+source/utouch/+bug/724831/+attachment/1876903/+files/hid-ntrig-dkms_1.1.3%7Etest1_all.deb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here is a possible fix for the problem, for someone with 64bit. The
package contains a tiny patch which makes utouch not interfere with
traditional semi-mt touchpads. Please report back here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: possible bugfix
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/724051/+attachment/1868874/+files/libutouch-frame1_1.1.0-0ubuntu2%7Etest1_amd64.deb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I verified that the fix in the debian package resolves the issue, so
Bilal, if it does for you too, a new package will be on its way shortly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/724051
** Branch linked: lp:~utouch-team/utouch-frame/trunk.v1.1.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/724051
Title:
upgrade to 1.3.99+git20110116.0e27ce3a-0ubuntu4 breaks touchpad
--
** Changed in: utouch-frame (Ubuntu)
Assignee: Henrik Rydberg (rydberg) = (unassigned)
** Changed in: utouch-frame (Ubuntu)
Status: In Progress = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
** Description changed:
utouch-frame has preliminary support for multi-finger, non-mt trackpads.
However, it appears the support is broken. The result is a trackpad that
fails to move the cursor. We will disable this support for now. This
- removes gesture functionality from these
Works for me too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/724342
Title:
pointer mode not available with ntrig touchscreen
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
The problems you see are due to abi problems with other upgrades, and
are not related to this package. You can use sudo apt-get install
libutouch-frame1 to upgrade only the package for the bugfix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Please upload utouch-frame 1.1.0 to Ubuntu. The changes are binary
compatible with 1.0.* and includes API additions only. Old programs will
run and compile fine against this new package.
The new package can be found at https://code.launchpad.net/~utouch-
The new utouch-evemu and utouch-frame packages, respectively. There are
new-package bugs present for those as well, but because they are new,
they are against the packages themselves:
https://bugs.launchpad.net/utouch-evemu/+bug/702597
https://bugs.launchpad.net/utouch-frame/+bug/702623
--
You
The rest of the utouch effort during natty will depend on mtdev-1.1.0
and any eventual fixes being available as soon as possible, so I
recommend against round-trip delays. Debian only recently caught up
with ubuntu regarding mtdev, so there is no inherent reason for this
package to be synced from
Public bug reported:
Please upload mtdev 1.1.0 to Ubuntu. The changes are binary compatible
with 1.0.11 and includes an optional stable API. Old programs will run
and compile fine against this new package, and new programs will run
fine against the old package.
The new package can be found at
This package has the following new package dependencies:
libmtdev-dev (= 1.1),
libutouch-evemu-dev (= 1.0),
libutouch-frame-dev (= 1.0)
** Branch linked: lp:ubuntu/utouch-grail
** Branch linked: lp:~utouch-team/utouch-grail/packaging
--
You
Public bug reported:
Please upload utouch-grail 1.0.18 to Ubuntu. The changes are binary
compatible with 1.0.18 and includes an optional stable API. Old programs
will run and compile fine against this new package.
The new package can be found at https://code.launchpad.net/~utouch-team
The patches are now in 2.6.38 mainline, and will appear in natty when
-rc1 has been merged.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/308191
Title:
Multitouch support not available for
Fully updated natty confirmed to be working for a BCM43224 802.11a/b/g/n
(rev 01). Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/700176
Title:
bcmwl bcmwl-kernel-source
Glad it works, and thanks for all the reports! There is a path for
clickpads now, although it may be a while before it materializes. It
should be a different bug, anyways, as this bug should soon be marked
fixed. Happy new year!
--
You received this bug notification because you are a member of
@anton: the click pad issue is a separate problem, which is also being
worked on.
The attached package is for maverick only, and is similar to the final
final upstream version. Should appear in natty in the beginning of the
new year. Thanks to everyone reporting!
--
You received this bug
** Attachment added: synaptics-dkms_1.1.1_all.deb
https://bugs.launchpad.net/utouch/+bug/308191/+attachment/1771346/+files/synaptics-dkms_1.1.1_all.deb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here is a second version, still for maverick (2.6.35), but with both
three-finger support and MT support. This package is very close to the
final upstream version. Release in natty will follow on positive test
results. Enjoy!
--
You received this bug notification because you are a member of
** Attachment added: synaptics-dkms_1.1.0_all.deb
https://bugs.launchpad.net/utouch/+bug/308191/+attachment/1765202/+files/synaptics-dkms_1.1.0_all.deb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Gustavo, thank you very much for this! Looks very sane. We will continue
to process this to see what can be done for Maverick. As you are
probably aware, this problem will go away automatically in Natty. Thanks
again, very nice.
--
You received this bug notification because you are a member of
I had a similiar problem and I solved it with:
[srydb...@zeus ~]$ echo $SSH_AUTH_SOCK
/tmp/keyring-KXX3Aw/ssh
[srydb...@zeus tmp]$ sudo rm -rf keyring-KXX3Aw/
Maybe the keys are cached there?
--
ssh Agent admitted failure to sign using the key on big endian machines
I had a similiar problem and I solved it with:
[srydb...@zeus ~]$ echo $SSH_AUTH_SOCK
/tmp/keyring-KXX3Aw/ssh
[srydb...@zeus tmp]$ sudo rm -rf keyring-KXX3Aw/
Maybe the keys are cached there?
--
ssh Agent admitted failure to sign using the key on big endian machines
Thanks for looking into this. A natty branch has been linked here, and a
merge request into packaging is pending. Is the change satisfactory?
(https://code.launchpad.net/~utouch-team/utouch-grail/packaging.natty)
** Branch linked: lp:~utouch-team/utouch-grail/packaging.natty
--
Tap is
** Branch unlinked: lp:~utouch-team/utouch-grail/packaging.natty
** Branch unlinked: lp:~utouch-team/utouch-grail/packaging.maverick
--
Tap is sometimes not registered on touchscreens
https://bugs.launchpad.net/bugs/667802
You received this bug notification because you are a member of Ubuntu
Didier, may we ask for your kind sponsoring once again?
--
Tap is sometimes not registered on touchscreens
https://bugs.launchpad.net/bugs/667802
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Version 1.0.16-0ubuntu1 seems to behave as expected.
--
Tap is sometimes not registered on touchscreens
https://bugs.launchpad.net/bugs/667802
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
@baptist: The process of adding this functionality to future releases of
ubuntu and mainline is ongoing, and has been for some time. The utouch
package is based on the upcoming mainline solution.
@tob: The kernel will provide MT data, and Clickpads and Macbook
integrated trackpads will be served
What is missing from all synaptics drivers is support for three
individual fingers, i.e., real multitouch support. However, most
firmwares are capable of detecting three objects on the pad, so there is
still hope that this information can be enabled.
--
Multitouch support not available for
With the hid-quanta-dkms from ppa:utouch-team/utouch, perhaps the
remains of this bug is a duplicate of
https://bugs.launchpad.net/ubuntu/+source/utouch-grail/+bug/667802
Regarding mtview, perhaps someone with a 32-bit machine handy can
compile and post a binary here.
--
Pressing buttons on
There is a hid-mosart-dkms package in ppa:utouch-team/utouch, it would
be great to hear if that works or not.
** Changed in: utouch
Status: New = Fix Committed
** Changed in: utouch
Status: Fix Committed = In Progress
--
add touch support for ACER 1820PTZ [MosArt RMTP-MA957]
Please try the wacom-dkms package in ppa:utouch-team/utouch to see if
that fixes the problem.
** Changed in: utouch
Status: New = In Progress
--
Wacom Bamboo Fun (056a:00d3 Wacom Co., Ltd): Pen Touch don't work in any way
(touch or pencil)
https://bugs.launchpad.net/bugs/616891
You
For maverick users: the attached dkms package should provide multitouch
support for a family of synaptics touchpads. Install and reboot. Please
report both success and failure here. Thanks!
--
Multitouch support not available for Synaptics touchpads v7.2
https://bugs.launchpad.net/bugs/308191
** Attachment added: synaptics dkms with mt support
https://bugs.launchpad.net/utouch/+bug/308191/+attachment/1735234/+files/synaptics-dkms_1.0.0_all.deb
** Changed in: utouch
Status: New = In Progress
** Changed in: utouch
Assignee: (unassigned) = Henrik Rydberg (rydberg
Glad it works. :-)
Credit for finding out the hardware protocol goes to Takashi Iwai. Chase
Douglas put the pieces together and sent the first batch upstream. Chris
Bagwell did further improvements and cleanup.
I have uploaded the package to the ppa:utouch-team/utouch, it should be
available
Hi Didier,
Hey Henrik, just to confirm from lp:~utouch-team/utouch-
grail/packaging
branch, I get this:
This is the packaging branch we use for natty.
dpkg-source: info: construction de utouch-grail à partir de
./utouch-grail_1.0.16.orig.tar.gz
patching file src/grail-api.c
Reversed
ok, but your branch contains the patches where it shouldn't:
http://bazaar.launchpad.net/~utouch-team/utouch-
grail/packaging/files/head:/debian/patches/
Oh! Thanks for the fix, pulled and tested.
--
Tap is sometimes not registered on touchscreens
https://bugs.launchpad.net/bugs/667802
You
Great - I have pushed the package to ppa:utouch-team/utouch. Thanks!
--
ntrig touchscreen no longer works
https://bugs.launchpad.net/bugs/643212
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Jayhawk, thank you very much for the patch.
Does this package work for you? If not, please provide the output of
dmesg | grep ntrig. Thanks!
** Attachment added: single touch firmware, test1
** Changed in: utouch-grail
Status: Fix Committed = Fix Released
--
Tap is sometimes not registered on touchscreens
https://bugs.launchpad.net/bugs/667802
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Also affects: utouch-grail (Ubuntu)
Importance: Undecided
Status: New
** Changed in: utouch-grail
Status: New = Fix Committed
--
Tap is sometimes not registered on touchscreens
https://bugs.launchpad.net/bugs/667802
You received this bug notification because you are a member
** Branch linked: lp:~utouch-team/utouch-grail/packaging.maverick
** Branch unlinked: lp:~utouch-team/utouch-grail/packaging.quilt
--
Tap is sometimes not registered on touchscreens
https://bugs.launchpad.net/bugs/667802
You received this bug notification because you are a member of Ubuntu
On 11/02/2010 06:51 PM, dimos wrote:
hmmm...well it didn't work for with my hardware for some reason. I'll
post all that I know about my system and maybe someone will spot out the
problem...the following was all I could gather from the original WeTab
Os that came preinstalled:
[...]
Bus
On 11/02/2010 09:42 PM, dimos wrote:
Hi Henrik,
I actually installed the utouch package you mentioned above on to a clean
install of Maverick
but still got the same behaviour: I press on the screen and the cursor just
jumps to the top left corner. The log shows that the eGalax device is
** Also affects: utouch
Importance: Undecided
Status: New
--
[0eef:0001] eGalax touch screen recognized but not working properly
https://bugs.launchpad.net/bugs/512188
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Also affects: utouch
Importance: Undecided
Status: New
--
Multitouch support not available for Synaptics touchpads v7.2
https://bugs.launchpad.net/bugs/308191
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Also affects: utouch
Importance: Undecided
Status: New
--
wacom bamboo pen touch not working in karmic
https://bugs.launchpad.net/bugs/477105
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Also affects: utouch
Importance: Undecided
Status: New
--
eGalax touchscreen configured as tablet
https://bugs.launchpad.net/bugs/549447
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Also affects: utouch
Importance: Undecided
Status: New
--
Wacom Bamboo Fun (056a:00d3 Wacom Co., Ltd): Pen Touch don't work in any way
(touch or pencil)
https://bugs.launchpad.net/bugs/616891
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Actually, it seems people are talking about different problems in this
thread. First of all, if a single finger is put down to move some time
before a second finger, the single-finger move is intentional so we end
up in a grey zone where latency and finger grouping have to be balanced.
In
Tested on three normal MT touchpads and two touchscreens without
regressions.
--
One Finger tap as mouse click is confusing
https://bugs.launchpad.net/bugs/647761
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
1 - 100 of 300 matches
Mail list logo
