症状是 touchpad 可以识别,按笔记本上的启用/禁止触摸板键,屏幕上也有正确提示,但是触摸板就是不能工作。
一个可能的原因就是在windows里面禁用了,重启进ubuntu以后就出这个问题。
另外发现在禁用的情况下,按住笔记本上那个键(我这里是Fn+F7)就可以用,松开就不行。
在网上搜到的gconf的键值,观察了一下,只有按住的时候是enabled,否则是disabled了。
临时解决方案是:
gconftool-2 -t bool -s /desktop/gnome/peripherals/touchpad/touchpad_enabled "True"
运行以后笔记本上的启用/禁止键也能正常工作了。
这个估计是Xorg或者GNOME的bug。
The symptom is that although my touchpad is recognized, and when I press the enable/disable key on my keyboard, there's right notification on the screen, but my touchpad just is not working.
One possible reason is that I've disabled it in Windows, then I restarted my machine and entered Ubuntu.
Another thing I found is that only when holding the enable/disable key can I use the touchpad.
I found the corresponding key in gconf, and indeed I observed that the key is enabled only when the enable/disable key is being held.
A workaround is to run the following command.
gconftool-2 -t bool -s /desktop/gnome/peripherals/touchpad/touchpad_enabled "True"
After that the enable/disable key works well.
This must be a bug in Xorg or GNOME.
一个可能的原因就是在windows里面禁用了,重启进ubuntu以后就出这个问题。
另外发现在禁用的情况下,按住笔记本上那个键(我这里是Fn+F7)就可以用,松开就不行。
在网上搜到的gconf的键值,观察了一下,只有按住的时候是enabled,否则是disabled了。
临时解决方案是:
gconftool-2 -t bool -s /desktop/gnome/peripherals/touchpad/touchpad_enabled "True"
运行以后笔记本上的启用/禁止键也能正常工作了。
这个估计是Xorg或者GNOME的bug。
The symptom is that although my touchpad is recognized, and when I press the enable/disable key on my keyboard, there's right notification on the screen, but my touchpad just is not working.
One possible reason is that I've disabled it in Windows, then I restarted my machine and entered Ubuntu.
Another thing I found is that only when holding the enable/disable key can I use the touchpad.
I found the corresponding key in gconf, and indeed I observed that the key is enabled only when the enable/disable key is being held.
A workaround is to run the following command.
gconftool-2 -t bool -s /desktop/gnome/peripherals/touchpad/touchpad_enabled "True"
After that the enable/disable key works well.
This must be a bug in Xorg or GNOME.
Comments