Maybe you've corrupted things with fsck after forcing a shutdown? Make a new user and try that profile out, that's what I've done - essentially I've cleaned out old .* config files in my home directory. The gist of it, is that killing the power and forcing an fsck check always has the potential to corrupt data. I have found on my desktop that means my .* config files in my home directory are unreadable. OpenBSD will then attempt to repair these files it seems, which takes forever. I have a sneaking suspicion that if you waited long enough things would mostly get repaired, but frankly OpenBSD is not intended to run as a desktop and you've said this has been a problem for a while. Also, is this the machine where 'apm -z' is not working?
Last edited by vanGrimoire; 7th June 2013 at 03:49 AM.
|