f14 and xfce 4.8

David A. De Graaf dad at datix.us
Wed Apr 13 18:10:42 UTC 2011

On Sat, Mar 26, 2011 at 09:18:41AM +0200, Gilboa Davara wrote:
> On Mon, 2011-03-21 at 22:41 +0530, Rahul Sundaram wrote:
> > On 03/21/2011 10:21 PM, Genes MailLists wrote:
> > > Following Alan's suggestion to consider xfce as an alternative to gnome
> > > shell - I see the f14 version is 4.6.2 and the current (as of january
> > > 2011) is 4.8
> > >
> > > Is there a chance 4.8 could be packaged for f14 ?
> > >
> > > thanks!
> > http://repos.fedorapeople.org/repos/cwickert/xfce-4.8/
> > 
> > Rahul
> Working great.
> Thanks!
> - Gilboa

I've replaced xfce4.6 with xfce-4.8 from the fedora-xfce-4.8 repo and
it is lovely, except for one thing.

On my two laptops, tapping the touchpad no longer works, nor does
horizontal scrolling.

Previously, in F13 and F14 until now, it was necessary to augment
/etc/X11/xorg.conf to specify the synaptics driver and options for it.
This file no longer produces the desired behaviour.  
The synclient command displays the state of the synaptics driver options
and there are many changes from F13, most importantly:
    <     HorizEdgeScroll         = 1
    >     HorizEdgeScroll         = 0

    <     TapButton1              = 1
    >     TapButton1              = 0

I note that a script, /usr/local/bin/touchpadfix:
    /usr/bin/synclient TapButton1=1
    /usr/bin/synclient HorizEdgeScroll=1
can work around this problem, but
a)  it's a kluge
b)  I can't find a way to automatically run it.  Executing it from
Application | Preferences | SessionandStartup doesn't work.

Does anyone know how to restore normal behaviour, and to initialize
properly these critical synaptics options?

Does anyone know why this changed?

Needless to say, loss of this basic functionality is deeply annoying.

I dredged up a prospective solution from google.
Someone said to add a file, /etc/X11/xorg.conf.d/10-synaptics.conf:

Section "InputClass"
      Identifier "touchpad catchall"
      Driver "synaptics"
      MatchIsTouchpad "on"
      MatchDevicePath "/dev/input/event*"
            Option "TapButton1" "1"
            Option "HorizEdgeScroll" "1"

It didn't work.  Can't pretend to understand why it would or wouldn't.

        David A. De Graaf    DATIX, Inc.    Hendersonville, NC
        dad at datix.us         www.datix.us

A: Because people read from top to bottom
Q: Why is top posting bad?

More information about the users mailing list