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 »

Exploring Immutable Distros and Declarative Management

My current server setup, based on Debian Stable and Docker, has served me reliably for years. It's stable, familiar, and gets the job done. However, an intriguing article I revisited recently about Fedora CoreOS, rpm-ostree, and OSTree native containers sparked my curiosity and sent me down a rabbit hole exploring alternative approaches to system management. Could there be a better way? Core Goals & Requirements Before diving into new technologies, I wanted to define what "better" means for my use case: The base operating system must update automatically and reliably. Hosted services (applications) should be updatable either automatically or manually, depending on the service. Configuration and data files need to be easy to modify, and crucially, automatically tracked and backed up. Current Setup: Debian Stable + Docker My current infrastructure consists of several servers, all running Debian Stable. System Updates are andled automatically via unattended-upgrades. Se...
Post a Comment
Read More »

mkosi: First Impressions

I stumbled upon the Gentoo wiki page for systemd-nspawn , which in turn led me to nspawn.org , mkosi , and later systemd-sysupdate . mkosi quickly caught my eye because it's almost exactly what I wanted to build myself, as mentioned in a previous post . So, I decided to spend my "sysadmin fun quota" on it. Overview mkosi is similar to docker build or podman build , but it's designed for creating full OS images. It focuses on development and testing. For example, much like nix-shell , mkosi can quickly launch a sandboxed shell with a specific distribution and selected packages installed. The systemd project itself uses mkosi for testing across different distros. The re-introduction article  is a great read. Speed Note that this is by no means a rigid benchmark. My setup is an SSD with LUKS and an ext4 filesystem (without reflink support). Building Container Images mkosi is pretty fast. A simple mkosi command creates a fresh Debian image. I used the --incrementa...
Post a Comment
Read More »