autoremove removes packages that are no longer used and should not affect anything.
However, if you have messed with your system (eg manually copied some software or edited a configuration you should not have touched) then autoremove may remove things the system now needs to boot.
How do I know this? Because I once did exactly that (to be fair, apt-get told me this could happen and asked for a second confirmation)
I know what it should do, and I use it regularly.
That one time, it triggered or caused Xenial to stop working correctly.
> Kind if off-topic, but I have to ask. Why do you use autoremove regularly? The amount of storage that is wasted it negligible so I barely bother with it
I have lots of VMs that I update pretty regularly for clients. Many time I just chain the command after apt-get upgrade.
> I know what it should do, and I use it regularly.
Kind if off-topic, but I have to ask. Why do you use autoremove regularly? The amount of storage that is wasted it negligible so I barely bother with it, even inside vms and containers which often have tiny filesystems.
Do you have similar issues when using Linux for servers?
There are many packages and apps out there that get released but are far from stable, and no easy way for non-devs (as in Linux devs) to opt out of unstable software.
I'm not your average MacBook user, either. I use Linux on the server on a daily basis.
If I waste 2 hours because of something like this--which doesn't involve experimenting with config files or deleting random files, but just doing regular maintainance--it's a big deal for me and my clients.