Bug 215775 - ksynaptics spuriously overrides synaptics settings from xorg.conf
Summary: ksynaptics spuriously overrides synaptics settings from xorg.conf
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: ksynaptics
Version: 6
Hardware: powerpc
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Orion Poplawski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: bzcl34nup
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-11-15 17:56 UTC by Klaus-Peter Schrage
Modified: 2008-05-06 16:50 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-05-06 16:50:11 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Klaus-Peter Schrage 2006-11-15 17:56:40 UTC
Description of problem:
The synaptics driver on my ibook G4 works nicely after changing the 'edge'
settings in xorg.conf to some decent values:
        Option        "LeftEdge"      "20"
        Option        "RightEdge"     "960"
        Option        "TopEdge"       "20"
        Option        "BottomEdge"    "337"
These are the values that the driver uses when the X server is started,
according to Xorg.0.log. But when KDE is up and ksynaptics gets loaded, these
values are overridden with defaults that render the Apple touchpad unusable.
Output from synclient -l:
    LeftEdge             = 1700
    RightEdge            = 5300
    TopEdge              = 1700
    BottomEdge           = 4200
Disabling ksynaptics and restarting X cures the problem. 
BTW, other settings in xorg.conf, e. g. 'MinSpeed', are not overridden.

Version-Release number of selected component (if applicable):
0.3.1-3.fc6

How reproducible:
Always

Steps to Reproduce:
1. Install ksynaptics from fedora extras
2. Restart X or enable touchpad in control center
3.
  
Actual results:
Apple touchpad gets unausable

Expected results:


Additional info:

Comment 1 Bug Zapper 2008-04-04 04:42:29 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
http://fedoraproject.org/wiki/LifeCycle/EOL

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers

Comment 2 Bug Zapper 2008-05-06 16:50:09 UTC
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.