Bug 588045 - Synaptics appletouch driver fails to load
Summary: Synaptics appletouch driver fails to load
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-synaptics
Version: 12
Hardware: powerpc
OS: Linux
low
medium
Target Milestone: ---
Assignee: Peter Hutterer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-02 11:28 UTC by Peter Lemenkov
Modified: 2010-05-02 12:16 UTC (History)
2 users (show)

Fixed In Version: kernel-2.6.32.12-114.fc12.ppc
Clone Of:
Environment:
Last Closed: 2010-05-02 12:16:23 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Xorg log (38.13 KB, text/plain)
2010-05-02 11:28 UTC, Peter Lemenkov 		no flags Details
lshal output (92.27 KB, text/plain)
2010-05-02 11:30 UTC, Peter Lemenkov 		no flags Details
Contents of /dev/input directory (721 bytes, text/plain)
2010-05-02 11:38 UTC, Peter Lemenkov 		no flags Details
Contents of /proc/bus/input/devices (1.29 KB, text/plain)
2010-05-02 11:41 UTC, Peter Lemenkov 		no flags Details
View All

Description Peter Lemenkov 2010-05-02 11:28:38 UTC 
Created attachment 410783 [details]
Xorg log

I just rebooted to Fedora at my Powerbook G4 and become very dissapointed bdue to non-working Synaptics driver.

I updated to the latest driver from updates-testing, at once, but noting changed - appletouch doesnt' work anymore for me (and yes, it does work in Mac OS X).
Comment 1 Peter Lemenkov 2010-05-02 11:30:04 UTC 
Created attachment 410784 [details]
lshal output
Comment 2 Peter Lemenkov 2010-05-02 11:38:35 UTC 
Created attachment 410788 [details]
Contents of /dev/input directory
Comment 3 Peter Lemenkov 2010-05-02 11:41:11 UTC 
Created attachment 410789 [details]
Contents of /proc/bus/input/devices
Comment 4 Peter Lemenkov 2010-05-02 12:16:23 UTC 
Peter, sorry for noise - I just upgraded up to latest kernel (kernel-2.6.32.12-114.fc12.ppc) and udev (udev-145-21.fc12.ppc) and this pgoblem was gone.

Not sure, what update exactly solved this issue, so I'm guessing that something was changed in kernel.
Note You need to log in before you can comment on or make changes to this bug.