Ubuntu 8.10 wacom 绘图板驱动问题

我的绘图板在Linux认成Waltop的板子，一直以来用wacom的驱动跑得好好的。

但是前一阵子更新系统以后就出了问题，现象是移动没问题，但是一点击就没有反应了，得把笔尖离开板子几秒再靠近才行。或者如果一开始迅速把笔尖点在板子上移动也能响应，但是抬起就不行了。

中间折腾了很长时间，一开始以为电池没电了，后来发现Windows下好好的。后来开始到处搜，xorg.conf自然是改了无数次，另外还改了udev, hal。到最后这几个东西弄得差不多都明白了，绘图板还是不干活。

后来，终于在Ubuntu官方帮助里看到了如下文字：

Users might also be affected by a bug in the 8.1.4 version of the wacom drivers that comes with Ubuntu 8.10, where the input freeze when the pen touches the tablet. If that is the case for you, you can install updated drivers :

于是“一声叹息”。。。

后来想编译份最新的linuxwacom，但是又有别的问题，总报usbParse: Exceeded channel count; ignoring the events.搜了一下，似乎也是很新的问题，开发者还在解决中。

于是下了那个帮助里给的两个deb并安装，似乎第一次没有成功，也可能是没有重启的缘故。但是第二次就好了。

总算是好了。

Comments

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...

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 ...

Determine Perspective Lines With Off-page Vanishing Point

In perspective drawing, a vanishing point represents a group of parallel lines, in other words, a direction. For any point on the paper, if we want a line towards the same direction (in the 3d space), we simply draw a line through it and the vanishing point. But sometimes the vanishing point is too far away, such that it is outside the paper/canvas. In this example, we have a point P and two perspective lines L1 and L2. The vanishing point VP is naturally the intersection of L1 and L2. The task is to draw a line through P and VP, without having VP on the paper. I am aware of a few traditional solutions: 1. Use extra pieces of paper such that we can extend L1 and L2 until we see VP. 2. Draw everything in a smaller scale, such that we can see both P and VP on the paper. Draw the line and scale everything back. 3. Draw a perspective grid using the Brewer Method. #1 and #2 might be quite practical. #3 may not guarantee a solution, unless we can measure distances/p...

WangLu's Notes

Search This Blog