Skip to main content

不能启用触摸板的临时办法 | A workaround of enabling touchpad

症状是 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.
Labels:

Comments

Post a Comment

Popular posts from this blog

A Rocky Migration: Moving from docker-compose to Podman and gVisor

I've been running a few containers for several years. They were all running under rootless Docker with a single user. Initially, I planned to  migrate the containers to VMs , but I couldn't get a stable workflow after about two months of effort. Later,  gVisor caught my attention , and I decided to migrate to Podman with gVisor instead. The new plan is to run each container with  --userns=auto  and use Quadlet for systemd integration. This approach provides better isolation and makes writing firewall rules easier. I'm now close to migrating all my containers. Here are a couple of rough edges I'd like to share. Network Layout I compared  various networking options  and spent a few hours trying the one-interface-per-group approach before giving up. I settled on a single macvlan network and decided to use static IP addresses for my containers. To prevent a randomly assigned IP address from conflicting with a predefined one, I allocated a large IP range for my ...
Post a Comment
Read More »

GameConqueror 0.09 -- Linux Game Hacking Tool

If you are a game hacker If you've been looking for a `CheatEngine for Linux` Then you can't miss this. ============================================== GameConqueror is a game hacking tool for linux, it's written in PyGTK and uses scanmem as its backend. It's supposed to be with most useful features of CheatEngine for Linux. Currently, I've implemented almost everything about scanning, involving variant data types and scan types: Data Types: int{8/16/32/64}, float{32/64}, unknown type(int or float) and unknown width(will try each of them), byte array and string Scan Types: equal, greater, less, changed, unchanged, increased(by), decreased(by) This should be enough for most cases, so I decided to release it at the current status. ============================================= Here's how you can get it PPA (for Ubuntu users) https://launchpad.net/~coolwanglu/+archive/scanmem (I've not test it in 32bit environments or Jaunty, do please inform me if it doe...
Post a Comment
Read More »

Fix Google Security Code

Google Security Code (http://g.co/sc) is one type of 2-step verification. This is particularly useful when security keys and passkeys are not available. I have been using it in my LXC containers, until today I found out that it stopped working. It just kept saying "The code is invalid". It is easy to rule out some factors: The code works on other browsers on my laptop. The code works on other devices that are directly connected to the router. So it appears that Google also checks IP addresses besides the security code. Recently I have IPv6 enabled, so most devices that are directly connected to the router have both IPv4 and IPv6 addresses. But  I only enabled IPv4 for my LXC containers. So I guess when a code is generated by device A and used by device B, Google should be able to check that device A and device B are closely located. But in my case, IPv6 address appears on device A but not on device B, which may look suspicious. To fix the problem, I just needed to disable IPv...
Post a Comment
Read More »