The driver itself works now, but it's not configured properly due to
incoming input-hotplug support. (bug #173411)
Anyway, closing this one.
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: In Progress = Fix Released
--
[hardy] synaptics driver broken w/ latest xserver
Here's the solution.
It works perfectly for me with zero ill effects. I based it off the
xorg.conf a Gutsy Live CD session creates.
SHMConfig is included.
** Attachment added: xorg.conf
http://launchpadlibrarian.net/10911523/xorg.conf
--
[hardy] synaptics driver broken w/ latest xserver
Also, restarting X after making these changes is not enough. You have to
restart the system.
--
[hardy] synaptics driver broken w/ latest xserver
https://bugs.launchpad.net/bugs/161014
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Well... for me, package posted by Cedric Schieli on 2007-11-11 solved
the problem. Few days later, the package appeared in gutsy repos, so the
trackpad is working seamlessly since then.
Shortly: everything is working for me since 2007-11-11 with _no_
xorg.conf changes whatsoever :)
--
[hardy]
Neither the PPA nor repo version solved the problem for me. Trust me, I
went through dozens of X reconfigurations to test every variable. Only
when coupled with a modified xorg.conf can I say that my problems were
resolved.
Can you post some steps that may aid me in reproducing your results?
--
I have a standard PS/2 Synaptics touchpad in ASUS A3L notebook. Detected
on boot as:
Synaptics Touchpad, model: 1, fw: 5.9, id: 0x926eb1, caps: 0xa0471b/0x0
input: SynPS/2 Synaptics TouchPad as /class/input/input3
Using stock Gutsy packages (all updated to current version), with a
default entry
Wait. I'm confused now...
This is a Hardy Heron (Ubuntu 8.04) problem. Not a Gutsy problem. How
are you running Xorg 7.3 (X11 1.4) on Gutsy?
--
[hardy] synaptics driver broken w/ latest xserver
https://bugs.launchpad.net/bugs/161014
You received this bug notification because you are a member of
Well, yes, You were right - I meant Hardy, but wrote Gutsy.
Actually, running Xorg 1.4 on Gutsy is possible, by changing sources.list and
upgrading Xorg with its dependencies - but that's not the case.
Anyway, is there anybody still having problem with Synaptics driver?
(not me :)
--
[hardy]
Isn't this a duplicate of Bug #173411?
--
[hardy] synaptics driver broken w/ latest xserver
https://bugs.launchpad.net/bugs/161014
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I'm using xserver-xorg-input-synaptics 0.14.7~git20070706 and I found a
crude work around that lets me control the touchpad using GSynaptics.
My working xorg.conf is attached.
** Attachment added: xorg.conf
http://launchpadlibrarian.net/10850655/xorg.conf
--
[hardy] synaptics driver broken
Does anyone know when the corrected package will appear in repo's?
--
[hardy] synaptics driver broken w/ latest xserver
https://bugs.launchpad.net/bugs/161014
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
As an interim solution, I've uploaded working package (pulled from
debian unstable) in my ppa :
deb http://ppa.launchpad.net/cschieli/ubuntu hardy main
--
[hardy] synaptics driver broken w/ latest xserver
https://bugs.launchpad.net/bugs/161014
You received this bug notification because you are
The reason why this went unnoticed was that the source tarballs have
different names in Debian/Ubuntu (xfree86-driver-synaptics in Debian,
renamed to xserver-xorg-input-synaptics in Ubuntu over two years ago).
I'll do a fakesync/merge for now, and have asked the Debian maintainer
to consider
confirming
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Importance: Undecided = Medium
Status: New = Triaged
--
[hardy] synaptics driver broken w/ latest xserver
https://bugs.launchpad.net/bugs/161014
You received this bug notification because you are a member of Ubuntu
Bugs,
14 matches
Mail list logo
