Red Hat Bugzilla – Bug 968314
after upgrade with fedup from F17 to F18 touchpad stops working
Last modified: 2016-01-04 00:10:26 EST
(Maybe this bug belongs to component fedup)
Description of problem:
After upgrade with fedup from F17 to F18 touchpad stops working.
Version-Release number of selected component (if applicable):
fedup last version in F17
May 29 13:22:15 Erased: xorg-x11-drv-synaptics-1.6.3-4.fc17.x86_64
May 29 13:23:47 Installed: xorg-x11-drv-synaptics-1.6.3-3.fc18.x86_64
I only did the process once, but it was reported in different hardware by another user.
Steps to Reproduce:
1. Upgrade F17 with fedup to F18.
2. Check the xorg-x11-drv-synaptics package release.
3. Check that the touchpad is dead.
Touchpad not working.
I fixed the issue removing the F17 package, and installing the F18 one. After a reboot touchpad went back to normal.
# yum remove xorg-x11-drv-synaptics
# yum install xorg-x11-drv-synaptics
Had the identical experience. Fixed with 'yum distro-sync xorg-x11-drv-synaptics.' After Xorg logout, touchpad detected and working correctly.
xorg-x11-drv-synaptics-1.6.4-2.fc18 has been submitted as an update for Fedora 18.
The problem *WAS NOT* with the package itself. Removing the F17 package and installing the F18 one does fix this issue. Or, simply running "yum dist-sync".
I opened this bug because I think fedup should do this "out-of-the-box". It's a standard package.
the upgrade path was broken, with the F17 package > the F18 package. This is why you had to distro-sync. as I wrote in the udpate, the new package doesn't have any code changes, it merely updates the package version.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing xorg-x11-drv-synaptics-1.6.4-2.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
xorg-x11-drv-synaptics-1.6.4-2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.