3

I want to remove update-notifier, but when I try (aptitude remove update-notifier) it wants to remove the ubuntu-desktop package. Which seems ok, but then when I try that it asks me to remove several libreoffice packages, which I don't want.

How do I just remove some packages depended on by ubuntu-desktop, or remove it entirely but keep everything else?

  • You cannot. What do you have against update-notifier? If you want to use another desktop package you may be better served by installing a different flavor of Ubuntu. – AlexP Feb 17 '17 at 7:11
  • If you do apt-get remove update-notifier ubuntu-desktop, what happens? – muru Feb 17 '17 at 8:43
  • Similar: askubuntu.com/questions/126390/… – Melebius Apr 13 '17 at 12:11
2

There is a way to do this. Aptitude is only a layer abstraction on top of dpkg that makes it more user-friendly, or easier to use, or safer, or less powerful, or patronizingly child-proofed depending on your relationship with your system and your outlook on life.

By definition, when you remove a package that is a (in this case a completely arbitrary) dependency, you are going to 'break the package' that depends on it. More often than you would think, this doesn't actually impair the functionality of the broken package perceptibly. Just always know that you can press CTRL+ALT+F1 or CTRL+ALT+F2 F3, F4, etc. once the OS is loaded and get a terminal to fix whatever you need to. Though you very well may have to be able to configure networking from the command line in that case... Anyways, If anyone tells you that "you can't", take it with a grain of salt. Because "you can".

Check that you got the right package name ~$ dpkg --list | grep "update-"

You should get some output like this with version numbers and some other info:

ii python3-update-manager ii update-inetd ii update-manager ii update-manager-core ii update-notifier ii update-notifier-common

Cool. Now you can see that update-notifier has another library associated with it update-notifier-common. Let's remove these unnecessary packages. (Because seriously, let's face it, that ubuntu makes the entire gnome setup dependent on a GUI interface to an abstraction-layer of the Debian package manager is ridiculous.)

~# sudo dpkg -r --force-depends update-notifier

The -r flag is short --remove and --force-depends removes the package even though it breaks a dependency.

Or if you hate the thought of a bunch of configuration files for packages that you don't have on your computer laying around:

~# sudo dpkg -P --force-depends update-notifier

The -P flag is Purge.

I usually restart at this point and check to make sure nothing I care about is broken. If it's all good, repeat the process for update-notifier-common, and check again. You would be amazed at how much you can break and still have a fully functioning workstation.

And there you go. It's gone.

In fact, instead of update-notifier you should just install unattended-upgrades then run dpkg-reconfigure -plow unattended-upgrades to automatically update unattended upgrades, and get the vital security updates without thinking about it ever again.

To reiterate: if this does break something you can't live without, you can always get to a terminal via CTRL+ALT+F1 when the OS loads and reinstall the package. But seriously, if it's not a production system at work. Break it, and fix it, and break it again. Not only is it more fun, but you learn more faster. When you've messed around with packages enough to feel comfortable, I recommend moving on to kernel modules. Seriously, I'm not joking. You will learn so much.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.