Hi Cindy, > Hi, Hans.. Have you tried renaming cached-utf8.tmp to move it out of > the way to see if the system creates a new one? I rename the "." to > "DOT" when I do that. Other times I'll move my problem files to a > completely new, relatively "safe" directory, e.g. ~/Documents. Yes, removed - no success.
> > The problem with changing that name is it might make the keyboard > instantly useless. If you have the option to do so, maybe playing in > either chroot or a virtual machine is best just in case that file does > a lot despite its harmless looking "tmp" name there. > > My setup doesn't have that cached-utf8.tmp file. Does it contain > anything that would be worth sharing in your thread here? > No it doesn't. > If this was happening to me, I'd go the full reboot after the file > name change just to be confident the kernel was basically in full > control. > > Hoping there's an easy solve. You all have already touched on my > favorites, those two "dpkg-reconfigure" ones. > > Cindy :) Best Hans