UBUNTU更新源出现错误解决方法小结
<p>在Ubuntu更新中,谁没有碰见个错误?在Ubuntu和其它基于Ubuntu的Linux发行版中,更新错误是一个共性的错误,也经常发生。这些错误出现的原因多种多样,修复起来也很简单。在本文中,我们将见到Ubuntu中各种类型频繁发生的更新错误以及它们的修复方法。<br /> </p>
<p>合并列表问题<br />
当你在终端中运行更新命令时,你可能会碰到这个错误“<a rel="external nofollow" target="_blank" href="http://itsfoss.com/how-to-fix-problem-with-mergelist/">合并列表错误</a>”,就像下面这样:</p>
<blockquote>
<p>E:Encountered a section with no Package: header,<br />
E:Problem with MergeList /var/lib/apt/lists/archive.ubuntu.comubuntudistspreciseuniversebinary-i386Packages,<br />
E:The package lists or status file could not be parsed or opened.’</p>
</blockquote>
<p>可以使用以下命令来修复该错误:</p>
<blockquote>
<p>sudo rm -r /var/lib/apt/lists/*<br />
sudo apt-get clean && sudo apt-get update<br />
</p>
</blockquote>
<p><strong>下载仓库信息失败 -1</strong><br />
实际上,有两种类型的<a rel="external nofollow" target="_blank" href="http://itsfoss.com/solve-ubuntu-error-failed-to-download-repository-information-check-your-internet-connection/">下载仓库信息失败错误</a>。如果你的错误是这样的:</p>
<blockquote>
<p>W:Failed to fetch bzip2:/var/lib/apt/lists/partial/in.archive.ubuntu.comubuntudistsoneiricrestrictedbinary-i386Packages Hash Sum mismatch,<br />
W:Failed to fetch bzip2:/var/lib/apt/lists/partial/in.archive.ubuntu.comubuntudistsoneiricmultiversebinary-i386Packages Hash Sum mismatch,<br />
E:Some index files failed to download. They have been ignored, or old ones used instead</p>
</blockquote>
<p>那么,你可以用以下命令修复:</p>
<blockquote>
<p>sudo rm -rf /var/lib/apt/lists/*<br />
sudo apt-get update</p>
</blockquote>
<p><strong>下载仓库信息失败 -2</strong><br />
下载仓库信息失败的另外一种类型是由于PPA过时导致的。通常,当你运行更新管理器,并看到这样的错误时:</p>
<p><img alt="" src="https://img.jbzj.com/file_images/article/202002/20200215180035.png" /></p>
<p>你可以运行sudo apt-get update来查看哪个PPA更新失败,你可以把它从源列表中删除。你可以按照这个截图指南来<a href="http://itsfoss.com/failed-to-download-repository-information-ubuntu-13-04/">修复下载仓库信息失败错误</a>。</p>
<p><strong>下载包文件失败错误</strong></p>
<p>一个类似的错误是<a href="http://itsfoss.com/fix-failed-download-package-files-error-ubuntu/">下载包文件失败错误</a>,像这样:</p>
<p><img alt="" src="https://img.jbzj.com/file_images/article/202002/20200215180036.jpg" /></p>
<p> 该错误很容易修复,只需修改软件源为主服务器即可。转到“软件和更新”,在那里你可以修改下载服务器为主服务器:</p>
<p> <img alt="" src="https://img.jbzj.com/file_images/article/202002/20200215180037.jpg" /></p>
<p><strong> 部分更新错误</strong></p>
<p>在终端中运行更新会出现<a href="http://itsfoss.com/fix-partial-upgrade-error-elementary-os-luna-quick-tip/">部分更新错误</a>:</p>
<blockquote>
<p>Not all updates can be installed</p>
<p>Run a partial upgrade, to install as many updates as possible</p>
</blockquote>
<p>在终端中运行以下命令来修复该错误:</p>
<ol>
<li>sudo apt-get install -f</li>
</ol>
<p><strong>加载共享库时发生错误</strong></p>
<p>该错误更多是安装错误,而不是更新错误。如果尝试从源码安装程序,你可能会碰到这个错误:</p>
<blockquote>
<p>error while loading shared libraries:</p>
<p>cannot open shared object file: No such file or directory</p>
</blockquote>
<p>该错误可以通过在终端中运行以下命令来修复:</p>
<ol>
<li>sudo /sbin/ldconfig -v</li>
</ol>
<p>你可以在这里查找到更多详细内容<a href="http://itsfoss.com/solve-open-shared-object-file-quick-tip/">加载共享库时发生错误</a>。</p>
<p><strong> 无法获取锁 /var/cache/apt/archives/lock</strong></p>
<p>在另一个程序在使用APT时,会发生该错误。假定你正在Ubuntu软件中心安装某个东西,然后你又试着在终端中运行apt。</p>
<blockquote>
<p>E: Could not get lock /var/cache/apt/archives/lock – open (11: Resource temporarily unavailable)</p>
<p>E: Unable to lock directory /var/cache/apt/archives/</p>
</blockquote>
<p>通常,只要你把所有其它使用apt的程序关了,这个问题就会好的。但是,如果问题持续,可以使用以下命令:</p>
<ol>
<li>sudo rm /var/lib/apt/lists/lock</li>
</ol>
<p>如果上面的命令不起作用,可以试试这个命令:</p>
<ol>
<li>sudo killall apt-get</li>
</ol>
<p>关于该错误的更多信息,可以在这里找到。</p>
<p><strong> GPG错误: 下列签名无法验证</strong></p>
<p>在添加一个PPA时,可能会导致以下错误GPG错误: 下列签名无法验证,这通常发生在终端中运行更新时:</p>
<blockquote>
<p>W: GPG error: http://repo.mate-desktop.org saucy InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 68980A0EA10B4DE8</p>
</blockquote>
<p>我们所要做的,就是获取系统中的这个公钥,从信息中获取密钥号。在上述信息中,密钥号为68980A0EA10B4DE8。该密钥可通过以下方式使用:</p>
<ol>
<li>sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 68980A0EA10B4DE8</li>
</ol>
<p>在添加密钥后,再次运行更新就没有问题了。</p>
<p><strong> BADSIG错误</strong></p>
<p>另外一个与签名相关的Ubuntu更新错误是BADSIG错误,它看起来像这样:</p>
<blockquote>
<p>W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://extras.ubuntu.com precise Release: The following signatures were invalid: BADSIG 16126D3A3E5C1192 Ubuntu Extras Archive Automatic Signing Key</p>
<p>W: GPG error: http://ppa.launchpad.net precise Release:</p>
<p>The following signatures were invalid: BADSIG 4C1CBC1B69B0E2F4 Launchpad PPA for Jonathan French W: Failed to fetch http://extras.ubuntu.com/ubuntu/dists/precise/Release</p>
</blockquote>
<p>要修复该BADSIG错误,请在终端中使用以下命令:</p>
<blockquote>
<p>sudo apt-get clean<br />
cd /var/lib/apt<br />
sudo mv lists oldlist<br />
sudo mkdir -p lists/partial<br />
sudo apt-get clean<br />
sudo apt-get update</p>
</blockquote>
<p>本文汇集了你可能会碰到的Ubuntu更新错误,我希望这会对你处理这些错误有所帮助。你在Ubuntu中是否也碰到过其它更新错误呢?请在下面的评论中告诉我,我会试着写个快速指南。</p>
<p><strong>下面是其他网友的补充</strong></p>
<p>更新源出现问题</p>
<blockquote>
<p>E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then appstreamcli refresh > /dev/null; fi'<br />
E: Sub-process returned an error code</p>
</blockquote>
<p>解决办法</p>
<blockquote>
<p>sudo pkill -KILL appstreamcli</p>
</blockquote>
<p>wget -P /tmp https://launchpad.net/ubuntu/+archive/primary/+files/appstream_0.9.4-1ubuntu1_amd64.deb https://launchpad.net/ubuntu/+archive/primary/+files/libappstream3_0.9.4-1ubuntu1_amd64.deb</p>
<p>sudo dpkg -i /tmp/appstream_0.9.4-1ubuntu1_amd64.deb /tmp/libappstream3_0.9.4-1ubuntu1_amd64.deb</p>
<p>然后在次更新 就ok</p>
<p><strong>E: GPG 错误:http://mirrors.163.com precise Release: 下列签名无效: NODATA 1 NODATA 2</strong></p>
<p>出现这个错误表示没有连上网,检查一下网络状态。<br />
</p>
<p>在添加源,然后在更新源时中途中断了更新,只要再安装软件或者再去更新的时候就会出来的错误提示。</p>
<p><strong>E: 无法获得锁 /var/lib/apt/lists/lock - open (11: 资源暂时不可用) E: 无法对目录 /var/lib/apt/lists/ 加锁</strong></p>
<p>输入指令:sudo rm /var/lib/apt/lists/lock</p>
頁:
[1]