David Wright <deb...@lionunicorn.co.uk> writes:
> and see if the packages being installed around that time give you any > clue as to why it might have been changed (by the sysadmin). The clues > might be indirect, like, say, installing a package that lacked enough > functionality to do a particular task, which caused you to take some > action of other. > Looking at the dates it seems the culprit may have been linphone, which didn't show up in aptitude search '?narrow(?installed,!?origin(Debian))' Linphone fell over with a segmentation fault, so I will remove it anyway.
