Ubuntu 20.04下无法通过图形化方式使用.deb文件升级软件包的解决方案咨询
Hey there, I totally get your frustration—having the default graphical package managers fail to recognize .deb upgrades when the command line works flawlessly is such a headache. Let’s walk through your options, starting with default tools you can use without adding third-party software:
Try GDebi (it might already be installed)
GDebi is a lightweight, dedicated tool for handling .deb files, and it’s often pre-installed on Ubuntu 20.04. Unlike the confusing dual-purpose software center, GDebi automatically detects if you’re upgrading an existing package and gives you the proper upgrade option. Just right-click your .deb file, select "Open With," and pick GDebi Package Installer. If it’s missing, runsudo apt install gdebiin the terminal to set it up—it’s way more reliable for local .deb packages than the default manager.Work around with Software Updater
If you prefer sticking to something familiar, you can manually place your .deb file into the/var/cache/apt/archives/directory, then open Software Updater. It’ll scan local cached packages and prompt you to upgrade the existing one. This is a bit roundabout, but it works if you want to avoid new tools.
If those default options don’t fit your workflow, third-party package managers are solid alternatives:
Synaptic Package Manager
This is a classic, full-featured graphical manager that behaves a lot like the old software manager you’re used to. It handles local .deb upgrades seamlessly. Install it withsudo apt install synaptic, then open it, go to the "File" menu, select "Install Package," and load your .deb file—it’ll automatically detect and perform the upgrade.QAPT Package Installer
Originally designed for KDE environments, this works great on GNOME too. It has a clean, straightforward interface for installing/upgrading .deb packages. Grab it withsudo apt install qapt-deb-installer.
Quick note on why this happens: The default Ubuntu Software app in 20.04 (which handles both snaps and deb packages) has known bugs when dealing with local .deb upgrades. A lot of users have hit this issue, so using a tool built specifically for .deb files is the most reliable fix.
备注:内容来源于stack exchange,提问作者AntiMatterDynamite

