If the touchpad works after logging out then the driver seems to be
working fine. Moving to xserver-xorg-input-synaptics.
** Package changed: linux (Ubuntu) => xserver-xorg-input-synaptics
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
The latest precise-propsed packages are an improvement. I'm no longer
seeing single clicks behaving like double-clicks after initiating S3 by
closing the lid. I am however seeing the following behavior: If I
depress the clickpad with one finger and tap a second finger at other
various locations on
Chase: I no longer see the double clicks when using tap-to-click, but I
can still reproduce the pointer jumps as described in comment #59.
--
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/9688
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
Verified that i915_bpo.ko in 4.4.0-34.53 reflects the PCI id changes
from the patches.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bu
Public bug reported:
Since upgrading to yakkety on this machine I see frequent instances of
the screen "scrambling," for lack of a better work. What I mean is that
for a split second things appear at the wrong location on the screeen,
as though the video has lost sync temporarily. Then it returns
I just had one of these which lasted for about 30 seconds and got a
picture, which I am attaching. This is different than what I perceive
from the momentary corruption, but those are so quick that it's hard to
be sure of what I'm seeing.
** Attachment added: "IMG_20160919_094055.jpg"
https://b
Also should have mentioned that the pic in comment #2 came when my
browser popped up a dialog to select a file.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1625154
Title:
Things I've tested which haven't made a difference:
* Copy /usr/share/doc/xserver-xorg-video-intel/xorg.conf to
/etc/X11/xorg.conf
* Running with the drm-intel-next kernel
Also verified that xenial still doesn't exhibit any issues by booting a
live image, so it isn't an hw issue.
--
You receiv
Well, I upgraded yesterday and haven't seen this since. Hopefully it's
fixed for good. Closing the bug for now.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserve
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-ppa/artful/amd64/n/nvidia-graphics-drivers-304/20170517_172947_fd0b4@/log.gz
i386:
https://objectstorage.prods
** Attachment added: "make.log"
https://bugs.launchpad.net/bugs/1691839/+attachment/4879183/+files/make.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1691839
Title:
I updated the package with fixes for 4.11:
http://people.canonical.com/~sforshee/nvidia-updates/nvidia-graphics-
drivers-304/
Test builds are available in the c-k-t/unstable ppa. 4.11 kernel builds
are available in the c-k-t ppa.
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Importance:
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/amd64/n/nvidia-graphics-drivers-304/20170627_064326_be787@/log.gz
i386:
https://objectstorage.
** Attachment added: "make.log"
https://bugs.launchpad.net/bugs/1700798/+attachment/4904203/+files/make.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1700798
Title:
Attaching patch which fixes the build for 4.12. Could use some testing
with actual hardware.
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Importance: Undecided => High
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Status: New => Triaged
** Changed in: nvidia-graphics-drive
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-bootstrap/artful/amd64/n/nvidia-graphics-drivers-304/20170725_185807_97a42@/log.gz
i386:
https://objectstorage
** Attachment added: "make.log"
https://bugs.launchpad.net/bugs/1706431/+attachment/4921172/+files/make.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1706431
Title:
Public bug reported:
Testing failed on:
i386:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/i386/n/nvidia-graphics-drivers-304/20170808_035826_7c51b@/log.gz
** Affects: nvidia-graphics-driver
** Attachment added: "make.log"
https://bugs.launchpad.net/bugs/1709317/+attachment/4928827/+files/make.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1709317
Title:
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Importance: Undecided => High
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Status: New => In Progress
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
You
I had a mistaken impression when I wrote the original 4.12 support
patch, it's the number of page table levels supported by the kernel
which matters and not the number of page table levels the arch actually
uses. Seems I also forgot to test on i386, oops.
Attaching an updated support patch for 4.1
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1709317
Title:
nvidia-graphic
** Attachment added: "make.log"
https://bugs.launchpad.net/bugs/1724871/+attachment/4976107/+files/make.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1724871
Title:
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-304/20171018_120651_877e3@/log.gz
i386:
https://objectstorage.prodstack4-5.canonical.com/v1/A
** Attachment added: "make.log"
https://bugs.launchpad.net/bugs/1727015/+attachment/4992445/+files/make.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1727015
Title:
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/amd64/n/nvidia-graphics-drivers-304/20171024_133147_bfe9f@/log.gz
i386:
https://objectstorage.
** Tags removed: kernel-adt-failure
** Tags added: kernel-adt-failure-hwe-edge-4.11
** Tags removed: kernel-adt-failure-hwe-edge-4.11
** Tags added: kernel-adt-failure-hwe-edge-4.13
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics
Attaching fix.
** Patch added: "nvidia-graphics-drivers-304_304.137-0ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1727015/+attachment/5006030/+files/nvidia-graphics-drivers-304_304.137-0ubuntu2.debdiff
** Changed in: nvidia-graphics-drivers-304 (
** Attachment added: "make.log"
https://bugs.launchpad.net/bugs/1737750/+attachment/5021698/+files/make.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1737750
Title:
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/n/nvidia-graphics-drivers-304/20171212_030744_5105c@/log.gz
i386:
https://objectstorage
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Importance: Undecided => Medium
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Status: New => In Progress
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Assignee: (unassigned) => Seth Forshee (sforshee)
** Pa
Note that I've compile tested the attached fix but don't have hardware
to do run-time testing.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1737750
Title:
nvidia-graphic
** Attachment added: "make.log"
https://bugs.launchpad.net/bugs/1747009/+attachment/5047629/+files/make.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1747009
Title:
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/n/nvidia-graphics-drivers-304/20180201_135601_91de8@/log.gz
i386:
https://objectstorage
*** This bug is a duplicate of bug 1737750 ***
https://bugs.launchpad.net/bugs/1737750
** This bug has been marked a duplicate of bug 1737750
nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux
4.15.0-1.2
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1737750 ***
https://bugs.launchpad.net/bugs/1737750
** This bug has been marked a duplicate of bug 1737750
nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux
4.15.0-1.2
--
You received this bug notification because you are a member
It's been suggested that this driver should be removed as it's not
longer maintained (bug 1748000), so I'm not sure what the fate of this
patch will be.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https:
My bug was duped to this one. After dist-upgrading 18.04 yesterday I
consistently get a crash logging into any gnome sessions, only the unity
session doesn't crash on me.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
http
I provided a patch months ago on bug 1737750 if we want to fix it.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1748000
Title:
Remove from the archive: this legacy drive
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1789924
Title:
Missing Intel GPU pci-id's
To manage notifications about th
Thanks for checking, Martin. I was afraid that might happen with this
bug. Can you also try the other builds before 006 that reported as good
(001, 004, 005) and see if any of those fail?
It's best if we can get as many testers as possible for each build. It's
pretty clear when we get a bad result
Based on Christian's feedback the problem appears to be in the
proprietary nvidia drivers, so I'm closing the linux task as invalid.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
anged in: linux (Ubuntu)
Assignee: Maria Sophie (thomas-garcia789) => Seth Forshee (sforshee)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/681904
Title:
[arrandale] S
Julien, thanks for the dkms package.
On Sun, Aug 14, 2011 at 05:43:39PM -, Jeanfrancoissven wrote:
> Can anyone explain me how to use the patch from comment 59?
> I don't understand all the steps that I must follow...
> I have a dell Vostro 3750, kernel 2.6.38-11
Please don't test the patch f
On Mon, Aug 15, 2011 at 01:42:24PM -, Patrick Pfeifer wrote:
> Observations: - 3-finger middle tap used to work with patch from #59,
> doesn't any more, but worked only 90% anyway
Yep, this is a side-effect of using the "real" multitouch protocol. This
is a class of device that is called semi-
I'm trying to construct a list of good and bad commits to use for
starting a new bisection run. Please take note that it only takes a
single occurrence of the evergreen_cp_resume oops to qualify a commit as
bad, so there's no need to continue testing once you've seen that oops.
I do agree that the
Oops, just noticed that I included 005 in the bad and inconclusive
lists. I meant for it to be only in the inconclusive list.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/727620
I've put up a new build (bisect012) at:
http://people.canonical.com/~sforshee/lp727620/bisect/
Here's the bisect log I used to re-seed the bisection.
# bad: [55922c9d1b84b89cb946c777fddccb3247e7df2c] Linux 3.0-rc1
# good: [61c4f2c81c61f73549928dfd9f3e8f26aa36a8cf] Linux 2.6.39
git bisect start '
bisect013 is now available.
http://people.canonical.com/~sforshee/lp727620/bisect/
# bad: [fcfc768806f2ed8ad56d9fd3f0c6af1cdb5e10e2] drm/nva3: support for memory
timing map table
git bisect bad fcfc768806f2ed8ad56d9fd3f0c6af1cdb5e10e2
Now testing commit 2703c21a82301f5c31ba5679e2d56422bd4cd404.
bisect014 is now available.
http://people.canonical.com/~sforshee/lp727620/bisect/
# bad: [2703c21a82301f5c31ba5679e2d56422bd4cd404] drm/nv50/gr: move to exec
engine interfaces
git bisect bad 2703c21a82301f5c31ba5679e2d56422bd4cd404
Now testing commit 000703f44c77b152cd966eaf06f4ab043274ff46.
I've posted an update to the driver, this time just as a dkms package.
It's avaiable at
http://people.canonical.com/~sforshee/lp681904/psmouse-elantech-
dkms/v0.1/psmouse-elantech-dkms_0.1_all.deb
Please test and let me know how it works. Thanks!
--
You received this bug notification because yo
himegoto: First, please run 'sudo modprobe psmouse' (which I'm expecting
will fail), then 'dmesg > dmesg-psmouse-elantech-dkms.txt'. Please
provide the output from modprobe and the dmesg-psmouse-elantech-dkms.txt
file here. After that you can remove the package by running 'sudo dpkg
-r psmouse-elan
bisect015 is now available.
http://people.canonical.com/~sforshee/lp727620/bisect/
# bad: [000703f44c77b152cd966eaf06f4ab043274ff46] mxm/wmi: add MXMX interface
entry point.
git bisect bad 000703f44c77b152cd966eaf06f4ab043274ff46
Now testing commit 63f7d9828bf55cc8ee6f460830c5285fe06bef3e.
--
bisect016 is now available.
http://people.canonical.com/~sforshee/lp727620/bisect/
# good: [63f7d9828bf55cc8ee6f460830c5285fe06bef3e] drm/radeon/kms: add support
for thermal chips on combios asics
git bisect good 63f7d9828bf55cc8ee6f460830c5285fe06bef3e
Now testing commit 99b38b4acc0d7dbbab4432
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/681904
Title:
[arrandale] Samsung
QX310/QX410/QX510/SF
bisect017 is now available.
http://people.canonical.com/~sforshee/lp727620/bisect/
# good: [99b38b4acc0d7dbbab443273577cff60080fcfad] platform/x86: add MXM WMI
driver.
git bisect good 99b38b4acc0d7dbbab443273577cff60080fcfad
Now testing commit 3448a19da479b6bd1e28e2a2be9fa16c6a6feb39.
--
You
bisect018 is now available. This should be the last bisect build, then
we'll need to apply the commit identified as fixing the issue onto natty
and see if that fixes the problem there.
http://people.canonical.com/~sforshee/lp727620/bisect/
# bad: [3448a19da479b6bd1e28e2a2be9fa16c6a6feb39] vgaarb:
** Changed in: linux (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-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/681904
Title:
[arrandale] Samsung
QX310/QX4
The bisect identified this as the commit that fixes the problem:
3448a19 vgaarb: use bridges to control VGA routing where possible.
A natty build with this patch applied is available at the link below.
Please test to see whether or not the bug is reproducible in this build.
Thanks!
http://people
I've been looking at the patch we identified as fixing the problem, but
I can't work out any causal relationship between what it does and the
GPU being on when nouveau probes. I've inquired about it on the upstream
bugzilla to see if I'm missing something. But I'm beginning to suspect
that the patc
I've been working on changes aimed at providing proper support for these
touchpads. I've posted a dkms package with my changes for testing, and
I'd appreciate it if you all could test and provide your feedback. The
package is available at:
http://people.canonical.com/~sforshee/alps-touchpad/psmous
On Thu, Sep 01, 2011 at 09:09:30PM -, Nate Carlson wrote:
> @Seth E6520.. seems to work fairly well so far, only thing I'm noticing
> is that it seems to be much more sensitive - IE, if I am holding my
> finger "still" on the touchpad, the pointer twitches around, which it
> didn't with the psm
Thanks to everyone who has tested the patch! One note -- when you include the
dmesg output please don't just grep for alps, as some of the messages of
interest don't contain that string.
A few of things are becoming clear. First, there are at least a couple of
different versions of the touchpads t
AceLan: The problem right now is that I suspect that the patch doesn't
actually do anything to directly fix the problem. I.e., that the patch
fixes this oops is just a side-effect of burning more time before the
driver tries to access the hardware or something like that. I'm not sure
though so I'd
I've posted a new version of alps-reg-dump that should get it working
with more touchpads. If the previous version didn't work for you, please
give this one a try and email me your output (seth dot forshee at
canonical dot com).
Executable:
http://people.canonical.com/~sforshee/alps-touchpad/al
Bob: It will finish, it just takes a while to complete. Yours wasn't
even halfway done :)
You want to capture the output to a file, i.e. 'alps-reg-dump > reg-
dump.txt'. If you let it run to completion it will restore your touchpad
functionality, but if you interrupt it your touchpad will fail to
Hemanti: I think the driver failed for you because your machine doesn't
have a trackstick. From there your touchpad was probably left in a bad
state. I think I have both of these fixed for the next update, but it's
strange that shutdown doesn't clear up the symptoms. Have you tried
turning off the
On Thu, Sep 15, 2011 at 06:07:14PM -, Hemanti wrote:
> $ sudo ./alps-reg-dump
> Error: Could not locate serio mouse
That's odd -- what output do you get from the following:
for f in /sys/bus/serio/devices/serio*/description; do
echo -n "${f}: "
cat $f
done
> $ sudo input-events 1
I've uploaded a new version of the driver, available at:
http://people.canonical.com/~sforshee/alps-touchpad/psmouse-alps-0.2
/psmouse-alps-dkms_0.2_all.deb
(Max: you can find patches in the same directory as the deb package,
which is true for the previous version as well.)
What's new in this
On Thu, Sep 15, 2011 at 08:08:44PM -, bishoptf wrote:
> Seth I've been holding out trying the driver since I read that you were
> coming out with a newer one, I have a Acer Timelinex 1830T series, I see you
> also have an acer, do you think this new version is the one to try with us
> that do n
Hemanti: Please send me the output of the dmesg command when the
touchpad isn't working for you.
George: In the current verions there's no multitouch for v3 or v4.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in U
aa-hcl: Thanks for testing. I'm glad the driver is working for you.
> If choosing two-finger scrolling then the scrolling does not work at
> all.
Yes, that's because of the missing multitouch support that I mentioned.
I'm working on that now.
> I also compared the touchpad and stick performance
On Sat, Sep 17, 2011 at 10:49:24AM -, Francisco Cribari wrote:
> The driver works fine on my DELL Latitude E6510. Will it be in Ubuntu
> 11.10?
11.10 is already at feature freeze, meaning only bug fixes from now
until release. The dkms package should continue working just fine though
until the
On Sat, Sep 17, 2011 at 04:10:03PM -, César Izurieta wrote:
> Hi Seth, thanks a lot for the patches. On my computer (Dell Inspiron
> N5110, opensuse 11.4 kernel 3.0.4, just touchpad, no trackstick) it's
> working well. Just 3 problems:
>
> 1. When leaving my finger over the touchpad without mo
On Mon, Sep 19, 2011 at 10:04:18AM -, rjmackay wrote:
> Is it useful to send you dmesg output and reg-dump output too?
dmesg isn't necessary, but the alps-reg-dump output along with the
maximum ABS_X and ABS_Y values would be helpful. Thanks!
--
You received this bug notification because you
On Tue, Sep 20, 2011 at 08:54:40PM -, Hemanti wrote:
> Hi Seth,
>
> I'm quite happy with your driver. As long as it works, all is wonderful.
> Unfortunately, however, at times it won't work after a reboot (touchpad
> not recognized --> no reaction of mouse cursor). The only thing that
> helps
Version 0.3 of the psmouse-alps-dkms package is now available at:
http://people.canonical.com/~sforshee/alps-touchpad/psmouse-alps-0.3
/psmouse-alps-dkms_0.3_all.deb
Changes since v2:
* Improved cleanup after trackstick initialization errors
* Driver should still load if trackstick initializa
César, Hemanti: I've uploaded a 0.4 package for both of you to test. In
only adds two things -- some debug output and a reset prior to
initialization.
http://people.canonical.com/~sforshee/alps-touchpad/psmouse-alps-0.4
/psmouse-alps-dkms_0.4_all.deb
César, what I need from you is for you to open
On Thu, Sep 22, 2011 at 07:57:42PM -, David Cramer wrote:
> Hi Seth,
>
> I'll be very happy to have multi-touch. Thank you for working on this.
Note that "multi-touch" for this device is basically going to be
two-fingered scrolling. The data isn't good enough to do much more with
it.
> For m
On Thu, Sep 22, 2011 at 08:30:45PM -, César Izurieta wrote:
> Seth, I've attached dmesg-stray-click.txt after following your
> instructions. Two middle clicks where fired during the test. I used two
> fingers and made an horizontal scroll for about one second.
What I see in the logs indicates
On Thu, Sep 22, 2011 at 09:46:22PM -, Hemanti wrote:
> Thanks Seth, it works now. :-) I just had to install the new version in
> all my Ubuntu systems (Natty and Oneiric) and rebooting now works fine
> under all circumstances (at least those I have tested).
Great! I plan to get out a new relea
César: It appears your hardware is sending different data. I put up a
new version for you that will dump the raw packets so I can take a look
at it. Please install the package at the link below, then do the
following.
Open two terminal windows. In the first, run 'sudo modprobe -r psmouse'
followed
A new version of the psmouse-dkms package is available at:
http://people.canonical.com/~sforshee/alps-touchpad/psmouse-alps-0.6
/psmouse-alps-dkms_0.6_all.deb
Changes since version 0.3 (since the intermediate builds were just for
collecting debug information):
* Add a reset of the touchpad prior
On Sat, Sep 24, 2011 at 03:34:08PM -, David Cramer wrote:
> Update: when I log in using KDE, the touchpad continues to work and
> two-finger scrolling works. If I log in using Gnome, however, even in
> Safe Mode or with "No Effects", the touchpad to stop working.
>
> Any idea what in Gnome cou
On Sat, Sep 24, 2011 at 01:36:48PM -, mio75 wrote:
> I wanted to try the 0.6 .deb, but got the error message described in
> #385 upon installation with dpkg -i.
mio75: I take it you are running something earlier than natty? Others
have reported such failures. The package is based off of a 3.0
On Sat, Sep 24, 2011 at 07:07:23PM -, Marja Erwin wrote:
> I was unable to install the package on Ubuntu 11.04.
Marja: Could you please provide more information about what went wrong?
Error messages and log files would be helpful. Thanks!
--
You received this bug notification because you are
On Sun, Sep 25, 2011 at 12:40:52AM -, masjan wrote:
> I have Dell N5110 (Dell Inspiron 15R) and unfortunately your driver doesn't
> work for me :(
> Ubuntu 11.04 amd64
>
> After installing 0.6 version
> sudo rmmod psmouse
> sudo modprobe psmouse
> dmesg:
> [ 3709.329414] alps.c: E6 report: 00
On Sat, Sep 24, 2011 at 04:14:00PM -, pitboss wrote:
> Ubuntu 11.04 on Latitude e6410. After I upgraded to 0.6 version, two
> finger scrolling stopped working. It's enabled from the settings but it
> doesn't work. Everything else seems to work fine.
pitboss: Please do the following. Switch to
David: Thanks for testing! Almost everything you've mentioned is a
desktop issue more than a driver issue. The driver mostly just passes
the raw data from the touchpad up to the desktop, and the desktop
translates this data into motion or scrolling or tapping. Specifically,
I think most of the thin
Speaking to the jitter, I haven't looked into it but a couple of
possiblities come to mind. First, the new driver changes the way the
data is reported, and perhaps the data is higher resolution and more
sensitive. It was also using different code on the X server side of
things, so something in ther
I've posted a new version with just a few changes for debugging problems
that have been reported, available at:
http://people.canonical.com/~sforshee/alps-touchpad/psmouse-alps-0.7
/psmouse-alps-dkms_0.7_all.deb
Anyone whose machine has a trackstick, please check that the mouse
buttons just below
On Mon, Sep 26, 2011 at 10:10:02PM -, David Cramer wrote:
> On my E6510, the trackstick buttons do work with 0.6. Am I understanding
> correctly that you want us to confirm that they still work with 0.7?
Yes. 0.7 changes the way the trackstick buttons are handled in a way
that should fix the i
On Tue, Sep 27, 2011 at 08:29:29PM -, jcat wrote:
> Hi Seth,
>
>
> You patch doesn't work for my new Dell Laptop, it's an XPS 15z.
>
> When I load the dell i8k module, it reports this info about the model.
>
> [ 297.412044] i8k: vendor=Dell Inc. , model=Dell System XPS
> 15Z, versi
On Tue, Sep 27, 2011 at 08:52:23PM -, cement_head wrote:
> @Seth Forshee
>
> What's the likelihood of getting this deb rolled (backported/PPA'd)
> against Lucid / Maverick?
I'm focused on getting these driver updates ready in time for the next
Ubuntu release, and
I may have found a way to detect where to look for the trackstick
buttons. I've uploaded a new driver to:
http://people.canonical.com/~sforshee/alps-touchpad/psmouse-alps-0.8
/psmouse-alps-dkms_0.8_all.deb
Please, *everyone* with a trackstick test this new version and let me
know if you see any i
On Thu, Sep 29, 2011 at 09:25:42AM -, fritz276 wrote:
> Trackstick buttons do not work with 0.8 - Toshiba R840-116
>
> They did work with 0.2, eventhough that version did not work perfect for
> me, somehow, it had glitches when I accidently touched the trackstick
> while typing (I dont know if
Thanks everyone for testing! Here's another new version to address
fritz276's issue. Again, everyone with tracksticks is encouraged to test
and make sure all buttons continue to function.
http://people.canonical.com/~sforshee/alps-touchpad/psmouse-alps-0.9
/psmouse-alps-dkms_0.9_all.deb
--
You r
On Fri, Sep 30, 2011 at 02:06:03AM -, Andrew Skalski wrote:
> Hi Seth,
>
> Thanks for your work on this. I'm trying out 0.9 right now, and ran
> into a problem (Dell Precision M4600). It was working fine for about 40
> minutes, until the driver (apparently) lost synchronization with the
> ev
This doesn't sound like a kernel issue. Moving to xserver-xorg-input-
synaptics. I'm not sure that's where the problem resides, but it should
be a step in the right direction at least.
** Package changed: linux (Ubuntu) => xserver-xorg-input-synaptics
(Ubuntu)
--
You received this bug notificati
1 - 100 of 264 matches
Mail list logo
