Hide Forgot
Created attachment 528194 [details] dmesg.txt Description of problem: Sometimes the trackpoint does not work at all on my x121e, including left, right, middle button. It does not work right from boot up. However the Touchpad is fully operational. Not sure if this is a kernel or xorg issue. Feel free to reassign if necessary. Version-Release number of selected component (if applicable): kernel-3.1.0-0.rc9.git0.0.fc16.x86_64 How reproducible: happens in 1 of 20 boots
(In reply to comment #1) > Created attachment 528194 [details] > dmesg.txt > Is that from the kernel when it's working or is that from when it fails? Whichever one it is, please post the other one (and say which one it is.)
That's the dmesg from the non-working trackpoint. Going to follow up with a working dmesg as requested.
Created attachment 528732 [details] dmesg-working-trackpoint.txt dmesg after boot when trackpoint works
[mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update.
Retested with kernel-3.3.4-3 and the problem still exists.
Confirmed on the x121e's less expensive cousin, the x130e. It can be a little infuriating. I too have noticed this for a while both Fedora 16 and Fedora 17, but turned a blind eye to it for some time. Lenovos are usually fully supported by the kernel, this must have been a recent update on their part. I am now posting a piped dmesg from a boot where the pointer device did not work and one from where it did.
Created attachment 588634 [details] dmesg output (failed) As perviously mentioned on this thread. The pointer does not work from boot on.
Created attachment 588636 [details] dmesg output (successful)
Also, I am sorry to have forgetten this, I am using kernel 3.3.7-1.
Is this still being seen with the 3.4 or 3.5 kernel updates?
yes, still present with 3.4.9-2.fc16
3.5.4-1.fc17.x86_64 same story, with the x130e (same line, though).
# Mass update to all open bugs. Kernel 3.6.2-1.fc16 has just been pushed to updates. This update is a significant rebase from the previous version. Please retest with this kernel, and let us know if your problem has been fixed. In the event that you have upgraded to a newer release and the bug you reported is still present, please change the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. If you are not the original bug reporter and you still experience this bug, please file a new report, as it is possible that you may be seeing a different problem. (Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).
The same problem appears with 3.6.3-1.fc17.x86_64 on ThinkPad X230.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I have a Thinkpad X230 on F18, and this issue occurs regularly. I have a working trackpoint about 2/3 of the time after boot. The trackpad always works. Workaround is to reboot until the trackpoint works. I did not see this issue on F17. I will attach dmesg and xorg.0.log for each state.
Created attachment 689308 [details] F18 dmesg, working trackpoint
Created attachment 689309 [details] F18 dmesg, broken trackpoint
Created attachment 689310 [details] F18 Xorg.0.log, working trackpoint
Created attachment 689312 [details] F18 Xorg.0.log, broken trackpoint
I have the same issue with F17/F18 on my X230. Workaround: disable the trackpad in BIOS. Bug report for F18: https://bugzilla.redhat.com/show_bug.cgi?id=872925
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.