Bug 963888 - xorg-x11-drv-synaptics-1.6.3-3.fc17 crashes X-server when pushing left touchpad button
Summary: xorg-x11-drv-synaptics-1.6.3-3.fc17 crashes X-server when pushing left touchp...
Keywords:
Status: CLOSED DUPLICATE of bug 962721
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-synaptics
Version: 17
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Hutterer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-16 17:51 UTC by inte
Modified: 2013-05-16 18:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-16 18:59:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description inte 2013-05-16 17:51:35 UTC
Description of problem:
Installing xorg-x11-drv-synaptics-1.6.3-3.fc17.x86_64.rpm through fc17 updates leads to X crashing when pushing the left touchpad (hard)button on my HP Pavillion dv5.
As a workaround, the bug can currently be fixes by reverting to the previous release of the package (org-x11-drv-synaptics-1.6.0-1.fc17.x86_64.rpm).

Version-Release number of selected component (if applicable):
xorg-x11-drv-synaptics-1.6.3-3.fc17.x86_64.rpm

How reproducible:
Click the left touchpad button (lower left corner)

Steps to Reproduce:
1.Let yum update your fc17 release to current (xorg-x11-drv-synaptics-1.6.3-3.fc17.x86_64.rpm).
2.Restart X (e.g. logging out).
3.Push the left touchpad button.
  
Actual results:
X crashes

Expected results:
X does not crash

Additional info:
Can currently be fixed by reverting to the previous release of the package (org-x11-drv-synaptics-1.6.0-1.fc17.x86_64.rpm).

Comment 1 inte 2013-05-16 18:59:27 UTC
Just found this bug to have been reported already.
However, the possibly fixed release org-x11-drv-synaptics-1.6.3-4.fc17.x86_64.rpm is not applicable through my update mirror yet :(

*** This bug has been marked as a duplicate of bug 962721 ***


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