brichert
January 27th, 2014, 06:50 PM
Howdy all. I'm running 12.04 on a Dell Optiplex 7010, dual booting, and having two problems, one major and one minor. I've been hashing through the major networking problem in another thread http://ubuntuforums.org/showthread.php?t=2183423 (http:// http://ubuntuforums.org/showthread.php?t=2183423), and if anyone has any advice there I would really appreciate it (for a bit I've been having a conversation with myself there).
In any event, I also have the GPG errors. When I run update-manager and try to install updates I get the usual : this would require installation of untrusted packages. After looking around on the forums, I did the following:
sudo apt-get clean
sudo rm -r /var/lib/apt/lists/*
sudo touch /var/lib/apt/lists/lock
sudo mkdir /var/lib/apt/lists/partial
sudo apt-get clean
sudo apt-get update
which works like a charm (though I confess to not being totally sure what it is doing ... presumably removing the authentication keys, but what does the time stamp have to do with it?). In any event, after running this, update-manager works with no problem. The trouble is, a day or so goes by, and I try to run update-manager again, and get the error back again! The same fix still works, but there must be something deeper going on here. Any ideas? Thanks.
In any event, I also have the GPG errors. When I run update-manager and try to install updates I get the usual : this would require installation of untrusted packages. After looking around on the forums, I did the following:
sudo apt-get clean
sudo rm -r /var/lib/apt/lists/*
sudo touch /var/lib/apt/lists/lock
sudo mkdir /var/lib/apt/lists/partial
sudo apt-get clean
sudo apt-get update
which works like a charm (though I confess to not being totally sure what it is doing ... presumably removing the authentication keys, but what does the time stamp have to do with it?). In any event, after running this, update-manager works with no problem. The trouble is, a day or so goes by, and I try to run update-manager again, and get the error back again! The same fix still works, but there must be something deeper going on here. Any ideas? Thanks.