From: Matteo Riva on 20 Nov 2009 15:10 After the full-upgrade of my testing system (with kernel 2.6.30) I can't do anything about my touchpad anymore, with the main problem being that I can't disable it. Neither synclient nor xinput have any effect on it, and if I try gsynaptics-init I get GSynaptics couldn't initialize. You have to set 'SHMConfig' 'true' in xorg.conf or XFree86.conf to use GSynaptics relevant part of xorg.conf: Section "InputDevice" Identifier "Synaptics Touchpad" Driver "synaptics" Option "SendCoreEvents" "true" Option "Device" "/dev/psaux" Option "Protocol" "auto-dev" Option "HorizScrollDelta" "0" Option "SHMConfig" "true" EndSection Any suggestion on how to turn that thing off again? Thanks -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Cameron Hutchison on 20 Nov 2009 17:30 Matteo Riva <muradin(a)gmail.com> writes: >After the full-upgrade of my testing system (with kernel 2.6.30) I >can't do anything about my touchpad anymore, with the main problem >being that I can't disable it. >Neither synclient nor xinput have any effect on it, [...] >From /usr/share/doc/xserver-xorg-input-synaptics/NEWS.Debian.gz: * All the shared memory code has been removed from synclient and syndaemon. The SHMConfig option is still available but the only use is for monitoring the hardware state data. If you have any script that changes the synaptics driver configuration make sure that you don't use the -s option to synclient. Or even better, configure the driver via hal. > Option "SHMConfig" "true" That looks like the problem. -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Mr. Wang Long on 20 Nov 2009 21:30 On Sat, Nov 21, 2009 at 06:22, Cameron Hutchison <lists(a)xdna.net> wrote: > Matteo Riva <muradin(a)gmail.com> writes: > >>After the full-upgrade of my testing system (with kernel 2.6.30) I >>can't do anything about my touchpad anymore, with the main problem >>being that I can't disable it. > >>Neither synclient nor xinput have any effect on it, [...] > > >From /usr/share/doc/xserver-xorg-input-synaptics/NEWS.Debian.gz: > >  * All the shared memory code has been removed from synclient and syndaemon. >   The SHMConfig option is still available but the only use is for monitoring >   the hardware state data. >   If you have any script that changes the synaptics driver configuration >   make sure that you don't use the -s option to synclient. Or even better, >   configure the driver via hal. > >>    Option    "SHMConfig" "true" > > That looks like the problem. > > I got a similar problem. I had configured the driver via hal, and if I login to KDE4, every feature I want was enabled. But for Gnome, I had to run this command every time after started up or resumed from sleep: /usr/bin/synclient TapButton1=1 HorizEdgeScroll=1 It seemd something in gnome disabled those options. Is there anything I can do to workaround or at least to monitor and find out the one in gnome who disabled the options? These are my configuration files: =========== /etc/hal/fdi/policy/x11-synaptics.fd: ============== <?xml version="1.0" encoding="ISO-8859-1"?> <deviceinfo version="0.2"> <device> <match key="info.capabilities" contains="input.touchpad"> <merge key="input.x11_driver" type="string">synaptics</merge> <merge key="input.x11_options.TouchpadOff" type="string">0</merge> <merge key="input.x11_options.HorizEdgeScroll" type="string">1</merge> <merge key="input.x11_options.LockedDrags" type="string">1</merge> <merge key="input.x11_options.FastTaps" type="string">1</merge> <merge key="input.x11_options.TapButton1" type="string">1</merge> <merge key="input.x11_options.LBCornerButton" type="string">2</merge> <merge key="input.x11_options.RBCornerButton" type="string">3</merge> </match> </device> </deviceinfo> =========== This is all I have in /etc/X11/xorg.conf: =============== # xorg.conf (X.Org X Window System server configuration file) Section "Device" Identifier "Configured Video Device" Driver "nvidia" VendorName "NVIDIA Corporation" EndSection --- Thanks & Regards, Wang Long -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Matteo Riva on 21 Nov 2009 06:30 I don't understand, yesterday I managed to switch it on and off by inserting and removing the `psmouse` module via modprobe, today it just doesn't get back on -- I haven't change anything else in my configuration. Also about the quoted changelog, I wasn't using `synclient` with the `-s` switch. -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
|
Pages: 1 Prev: Trouble getting Linksys WUSB54GC v. 3 to work in Lenny Next: Bluetooth on testing |