Hide Forgot
Description of problem: Until I don't press the "Disable touchpad" key everything is ok, When I press it, touchpad is disabled correctly but I can't re-enable it by pressing the key again, and it remains disabled until logout. In login screen there is a reverse situation. Pressing the key shows a disabled touchpad on screen but it's enabled and doesn't get disabled. *I'm not sure about the selected component(xorg-x11)
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach * your X server config file (/etc/X11/xorg.conf, if available), * X server log file (/var/log/Xorg.*.log*; check with grep Backtrace /var/log/Xorg* which logs might be the most interesting ones, send us at least Xorg.0.log), * output of the evtest command against /dev/input/event* file (which exactly file is appropriate for your touchpad could be find in /var/log/Xorg.0.log), and * system log (/var/log/messages) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Created attachment 527023 [details] Xorg.0.log
Created attachment 527025 [details] evtest output
Created attachment 527026 [details] /var/log/messages
Is the main problem that the touchpad cannot be reenabled (to fix the Summary of this bug; after the reading the current one my answer was "And so what's wrong?")?
Yes. the main problem is, touchpad cannot be re-enabled. I can't scroll or click on anything.
gsettings get org.gnome.settings-daemon.peripherals.touchpad touchpad-enabled what does that show when you toggle enabled/disabled? Can you reproduce this in a plain X session? some touchpads disable in hardware and if gnome gets out of sync, you always have something disabling the touchpad when the other part enables it.
gsettings get org.gnome.settings-daemon.peripherals.touchpad touchpad-enabled return expected values, False when disabled and true when enabled I don't know how to reproduce it in a plain X session
yum install xterm init 3 xinit -- fires up a plain x session with xterm. then try the touchpad disable key
In plain x session, like login screen the key doesn't work. After pressing the key, touchpad is enabled and doesn't get disabled.
Please post the output of xinput list-props "SynPS/2 Synaptics TouchPad" when the touchpad should be enabled (but is disabled) and when it is disabled (but should be enabled). Plus please double-check again what the gsettings shows in each case and add that info to the xinput list-props output (in the bugzilla comment) Does evtest show any output when the touchpad is disabled? Does triggering the gsettings key manually have any effect? gsettings set org.gnome.settings-daemon.peripherals.touchpad touchpad-enabled true (or false to disable)
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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" (top right of this page) 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