I had some feedback from at least two readers who could not enable SHMConfig, and when they tried to use gsynaptics or syndaemon, they were met with the error “You have to set ‘SHMConfig’ ‘true’ in xorg.conf or XF86Config“. The instructions provided in the post to enable SHMConfig using the /etc/hal/fdi/policy/shmconfig.fdi method did not appear to be working.
After a lot of troubleshooting work with Travis, we were able to determine why this was occuring, and how to resolve it.
Firstly, and briefly, the why. The HAL daemon (hald) keeps a cache in /var/cache/hald/fdi-cache. For some reason, hald was using this cache file, and not picking up the newly created shmconfig.fdi file.
Now the important part – how to resolve it! This is easy, you just need to remove the cache:
sudo rm /var/cache/hald/fdi-cache
Provided you have created the shmconfig.fdi file as described in the gsynaptics post, reboot your machine, and you should be able to load gsynaptics and setup syndaemon without being told SHMConfig needs to be set to true. The fdi-cache file will be recreated when you reboot, and you shouldn’t have any more problems.
A big thanks to Travis for helping to troubleshoot this one!