Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

This site requires JavaScript to be enabled to function correctly, please enable it.

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.0.4-1.3.1 Firefox/1.0.4
Description of problem:
When booting the computer, the Synaptics touchpad is sometimes not detected. As a consequence, X does not start because of a missing core pointer. After a few reboots, the touchpad is suddenly detected and works fine. Often it also works immediately at the first attempt. It looks like it's some kind of race condition.
After having updated to synaptics-0.14.2-1, the synaptics detection seems to be much more reliable, but it still fails sometimes.
Also, rhgb will never detect the touchpad, so it is always a textual boot.
Version-Release number of selected component (if applicable):
How reproducible:
Sometimes
Steps to Reproduce:
1. Install FC4
2. Manually add synaptics configuration to xorg.conf
3. (update to synaptics-0.14.2-1)
4. Boot the computer several times
Actual Results: Often it works fine (rhgb will never work though). Sometimes the touchpad is not detected, and then X fails because the core pointer is missing.
Expected Results: Synaptics is detected every time, so X will always start. (It would be fine if it is even detected before rhgb starts.)
Additional info:
The relevant part of my xorg.conf is:
Section "InputDevice"
Identifier "Mouse0"
Driver "synaptics"
Option "Protocol" "auto-dev"
Option "Device" "/dev/psaux"
Option "LeftEdge" "1700"
Option "RightEdge" "5300"
Option "TopEdge" "1700"
Option "BottomEdge" "4200"
Option "FingerLow" "25"
Option "Fingertop" "30"
Option "MaxTapTime" "180"
Option "MAxTapMove" "220"
Option "VertScrollDelta" "100"
Option "MinSpeed" "0.06"
Option "MaxSpeed" "0.12"
Option "AceelFactor" "0.0010"
Option "SHMConfig" "on"
Option "RTCornerButton" "2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "yes"
EndSection
When synaptics is not detected, it is also not mentioned at all in dmesg. If it was detected, dmesg says:
synaptics reset failed
Synaptics Touchpad, model: 1
Firmware: 5.9
Sensor: 18
new absolute packet format
Touchpad has extended capability bits
-> 4 multi-buttons, i.e. besides standard buttons
-> multifinger detection
-> palm detection
input: SynPS/2 Synaptics TouchPad on isa0060/serio4

[This comment has been added as a mass update for all FC4 kernel bugs.
If you have migrated this bug from an FC3 bug today, ignore this comment.]
Please retest your problem with todays 2.6.12-1.1398_FC4 update.
If your problem involved being unable to boot, or some hardware not being
detected correctly, please make sure your /etc/modprobe.conf is correct *BEFORE*
installing any kernel updates.
If in doubt, you can recreate this file using..
mv /etc/sysconfig/hwconf /etc/sysconfig/hwconf.bak
mv /etc/modprobe.conf /etc/modprobe.conf.bak
kudzu
Thank you.

Mass update to all FC4 bugs:
An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream
kernel (2.6.13.2). As there were ~3500 changes upstream between this and the
previous kernel, it's possible your bug has been fixed already.
Please retest with this update, and update this bug if necessary.
Thanks.

This is a mass-update to all currently open kernel bugs.
A new kernel update has been released (Version: 2.6.15-1.1830_FC4)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO_REPORTER state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
Thank you.