Frank McCormick wrote: > localepurge: checking for existence of > /var/cache/localepurge/localelist... localepurge: > checking system for new locale ... > Segmentation fault E: Problem executing scripts DPkg::Post-Invoke > 'if [ -x /usr/sbin/localepurge ] && [ $(ps w -p $PPID | egrep -c > '(remove|purge)') != 1 ]; then /usr/sbin/localepurge; else exit 0; > fi' E: Sub-process returned an error code debian: > /home/frank# > Any ideas or should I just wait until it sorts itself out ?
A segmentation fault in a program you are writing is probably a bug in
your program. A segmentation fault in a program that everyone runs
okay but you is probably not a software bug. Instead it must be
hardware.
I suspect bad ram or a flakey socket connection. Bad ram is a likely
suspect but it could be a problem SATA cable or other. Think hardware
problem. But probably just a component. I have had both ram problems
and disk cable problems produce these types of issues.
I would start by checking the disk drive for errors. Run a SMART
drive selftest. These exact commands are not important but just to
show you the general idea.
smartctl -l error /dev/sda
smartctl -t short /dev/sda &&
sleep 120 &&
smartctl -l selftest /dev/sda
I would carefully (beware and avoid the ESD zap) unsocket the ram and
resocket it. I would carefully unplug and reattach every SATA cable.
Hopefully that will sort things out. If not run memtest. If no
answer there I would bisect the problem by splitting the ram or
swapping cpus with another. I usually debug these things by swapping
components until I can isolate the problem to something specific.
Alternatively it is possible that some attacker is wedging into your
system and the files are compromised. I doubt that is the problem but
I feel compelled to cover the base by mentioning it.
Good luck!
Bob
signature.asc
Description: Digital signature
