As I said, the synaptics driver is not being used.
c...@inspiron:~$ grep -i synaptics /var/log/Xorg.0.log
(II) LoadModule: synaptics
(II) Loading /usr/lib/xorg/modules/input//synaptics_drv.so
(II) Module synaptics: vendor=X.Org Foundation
(II) Synaptics touchpad driver version 1.1.0
Note:
Hmm, now I'm not so certain. Although there is no output indicating that
the synaptics driver is being used (as opposed to merely being loaded),
it seems the driver is in use.
I tried to manually enable tap-to-click via synclient TapButton1=1 -
and it worked. I also tried to remove the
@Conn,
If this is the case.. grab my custom fdi file from the previous post and follow
the instructions, if everything works as it should you should have tap-clicking
and vertical scrolling re-enabled, I also left the 2 finger scrolling active in
case anyone wanted both but you can easily
I would presume then that the bug is in the options being applied then,
in this case I think that Fedora is either using a newer version or a
patch as they have more options and it actually workes. Now that the
touchpad settings dialogue has gone upstream (from the Ubuntu patch), I
presume we just
See /usr/share/doc/xserver-xorg-input-synaptics/NEWS.Debian.gz for
solution.
Don't know why gnome-mouse-properties doesn't set the TapButtons ... I
guess it needs to catch up with Xorg changes.
--
[Karmic] Touchpad not recognised correctly, synaptics driver not in use
To: Andreas Henriksson
Unfortunately in my case (and probably others), the synaptics driver
doesn't actually seem to be loading. Typing the options listed in that
news file doesn't seem to effect the mouse at all.
--
[Karmic] Touchpad not recognised correctly, synaptics driver not in use
SRElysian:
The synaptics driver loads here. Could you please provide your
Xorg.0.log or atleast the output of grep -c Synaptics
/var/log/Xorg.0.log ?
Could you please also provide the output of lshal or atleast the output
of lshal | grep -c input.touchpad to see if the HAL finds your
touchpad at
$ grep -c Synaptics /var/log/Xorg.0.log
15
$ lshal | grep -c input.touchpad
1
This is rather odd.. it seems to actually find my touchpad (which is
good in some respects)..
$ cat /var/log/Xorg.0.log | grep Synaptics
(II) config/hal: Adding input device SynPS/2 Synaptics TouchPad
(II) Synaptics
... however, as I stated previously.. using those options found in the
news file didn't allow touch clicking, and my scroll is broken too
(there's a designated area on the right of the touchpad for it). It
seems to me, that while it is detecting it, it's not applying the proper
driver for it.
There is no reason to be rude here. I was not vague at all, i merely
made the assumption that you read the file you suggested other people
read in regards to re-enabling tap-clicking, which I stated did not work
for me.
No, I was not aware that it defaults to mac touchpad behavior, but
Tap to click is an essential feature to enable by default. From
experience it was incessantly annoying when disabled by default in
fedora. Quite a lot of newer laptops (including my eeePc) depend on it
as the either have harder to click physical buttons or some have none at
all. Fedora seems to
SRElysian: I'm sorry if I offended you. It was not my intention. I only
wanted to give helpful suggestions. Also, none of my laptops have the
(visual indication of) touchpad scrollbars. Doesn't really matter either
way. No one configuration is going to suit everybody. Your fdi file is
the perfect
Right, would most people agree that brainstorm is the right place or IRC
or the forums? Apple only have to support their own products which are
designed to work without tap to click. If you have every used eeePc's or
some new smaller laptops the physical buttons are nearly unclickable so
it is
People,
You're hijacking my bug report. If you read my Xorg.0.log you'll see
that the Synaptics driver isn't being loaded at all - this is my issue,
not tap-to-click being disabled by default.
Although I also prefer tap-to-click to be enabled by default, this is
not the problem. The problem is
@Conn
You are completely right - as I said before this issue is about the inability
for the options to be correctly applied and not about the default options. I
have created a new bug report here:
https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/384641
and will
Acer Aspire 3050
4GB RAM DDR2
1.8Ghz Mobile AMD Sempron 64bit
Synaptics Touchpad
Same here, drivers not working and lost touchpad features.
Im running karmic alpha1 64bit
--
[Karmic] Touchpad not recognised correctly, synaptics driver not in use
https://bugs.launchpad.net/bugs/380126
You
This regression is probably caused by the switch to udev. Is anyone with
a Synaptics touchpad not experiencing it?
--
[Karmic] Touchpad not recognised correctly, synaptics driver not in use
https://bugs.launchpad.net/bugs/380126
You received this bug notification because you are a member of
As a workaround, if I use my index and middle finger at the same time,
it works :)
--
[Karmic] Touchpad not recognised correctly, synaptics driver not in use
https://bugs.launchpad.net/bugs/380126
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
I meant vertical scrolling works.
--
[Karmic] Touchpad not recognised correctly, synaptics driver not in use
https://bugs.launchpad.net/bugs/380126
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in ubuntu.
Can confirm same issue on the HP Pavilion dv9610us. No tap-click, no
scroll:
~$ cat /var/log/Xorg.0.log | grep -i mouse
(==) NVIDIA(0): Silken mouse enabled
(II) config/hal: Adding input device Macintosh mouse button emulation
(**) Macintosh mouse button emulation: always reports core events
(**)
Confirmed with Xorg.0.log showing same details. HP Mininote 2133.
2.6.30-6-generic kernel.
gsynaptics allows enabling of tap to click, but horizontal or vertical
scrolling no longer work.
--
[Karmic] Touchpad not recognised correctly, synaptics driver not in use
101 - 121 of 121 matches
Mail list logo
