Quote:
|
Originally Posted by deadeyes
try:
sudo apt-get update
sudo apt-get dist-upgrade
Or/also uninstall the program that started this pain in the ...
|
I wouldn't go there..un/reinstalling the program won't probably help, because (as far as I can tell from my experience) it's not caused by the program itself that doesn't start, but rather something else (like some pointed out, files under the configuration directories may affect it). Also running dist-upgrade just might do something you don't want, making the system less usable; I've had it when I was first introduced to that command, and didn't like it. And what it does is simply upgrade software, which probably doesn't work like I already pointed out.
The usual method to begin with is to remove/rename certain configuration files under the home directory. If you open your file manager (Nautilus on Gnome, Konqueror on KDE, ...) and head to your home directory, then set the file manager to show "hidden" files also (all those files and directories that begin with '.'; in Gnome/Nautilus the shortcut key is CTRL+H to display these.), you'll usually see quite a few directories. For example .config, .gconf, .gconfd, .gnome, .gnome2, ... and so on (for KDE .kde and such). They include a lot of information that is specific to your user account, like your current theme settings (at least in Gnome) and such. Note that when a user account is created, its homedir is usually either empty or then an admin has set some files that are to be copied to the directory when it's created. Either way those hidden directories don't exist always, they're created when missing - and that means you can "reset" some configurations by removing the relevant files/directories. Removing them all usually results in your desktop going back to the "factory settings", but right now you're interested in locating the specific file that may be causing this trouble - and removing it (or fixing it, but if you don't know how, it's easier to remove). Next time it's needed, it's re-created, and the problem should be solved.
So, start looking at those dot-directories. And don't remove them right away - rather, if you think you've found what you're looking for, rename the directory first (for example add a _backup to the end of the filename) because it has the same effect. If it was what you wanted, remove the renamed file - or if not, move it back to it's original name (overwriting a possible newly created file/dir), and you're set. It might take some time to find out the offending file/files, but it might be worth it too..
Actually the easiest way (that I didn't mention first, because it would have been too easy, right?
) to test this method is to simply create a new user - log in as that user, then try to run the apps that don't run fine with the other user. If it works, it's about those config files - and if it doesn't, there's presumably something bigger (read: system-wide) wrong, and it's useless to play around with your own config files. So add a new user (there are graphical user interfaces to do that, if you're not familiar with useradd) and once you've tested, remove it (with the same tool, or userdel).
As a last thing I must say it might be that the problem just doesn't get solved in a decent amount of time. I've faced that too. Then the easiest solution is to take backups of anything important and do a clean reinstallation - nowadays it doesn't take much, with Ubuntu you can get to 15 or 20 minutes. And if you have a separate /home you can make this even easier because taking backups isn't absolutely necessary (though it is recommended).
