Generally, you can trust apt-gets autoremove. However, having a quick look at what is going to be removed is a recommendable attitude.In this case it looks quite plausible.
I think someone already reported this somewhere on this forum, but i can't find it.Apt-get autoremove doesn't autoremove anything anymore. Is this a bug or a new feature? :/And did anyone solve this already?
I have uninstalled my distro's (Debian Wheezy) package of torchat, and use a newer version I've built myself. Since removing the package apt-get wants me to autoremove something which the software I've built still depends on.
Hey, all. I am running 64-bit Precise Pangolin/Unity, and earlier today I used the "autoremove" command to clean things up a bit. Turns out I should not have done that. Apparently, autoremove occasionally removes a bit too much, and I think that happened in my case today. Upon rebooting, compiz failed to launch, as did unity.
I know I have some packages ready to be removed if I run apt-get autoremove, but I just want to know which are them, without removing them. I'm afraid that running the above command will remove them, without promting me yes/no ... How can I know them without removing them, or how to exec the above command forcing the prompt to pop out? .. so I can press "no" :)
i got some borkage with latest update, dist-upgrade, autoremove.Noticed notification area in tint2 wasn't displaying nm-applet or volume icon.Manually reinstalling (via synaptic) the following items restored things back to normalmenu-xdgpython-xdgxdg-user-dirsunsure if anything else is broken - will keep an eye out.items for autoremove were the followinggurtid@cbwaldorf64:~$ sudo apt-get auto