Comment 4 for bug 49442

Yes, this problem is still there. It's tricky since it only occurs on one machine (all other Dapper machines work fine, but they have different hardware too, so it may be a driver issue somewhere which triggers a bug in gpm). In any case, I'm attaching a gpm log file in case that helps the debugging process. It contains some **WARNING** lines which perhaps help to pin down what's going on. I can't see anything very useful in the daemon.log (with hald output), but I'll attach that too.