Kernels galore and no NVIDIA driver in sight

[Keith]

On 12/25/2024 5:36 PM, Little Girl wrote:
> Hey there,
> 
> Keith via ubuntu-users wrote:
>> Little Girl wrote:
>   
>> These are packages that were removed either directly by you, or by
>> the removal of one or more of their dependencies leaving their
>> config files on the system. Dpkg will allow you see the files left
>> over.
>>
>> $ dpkg -L steam:i386
>>
>> Assuming you don't need them anymore then there's no harm in
>> removing them.
> 
> I'm not sure. I'm a bit worried about my sound from the output
> I got below after running the command on each of the questionable
> files. If all of this looks fine to you, I'll go for it:
> 
> $ dpkg -L libasound2-plugins:i386
> /etc
> /etc/alsa
> /etc/alsa/conf.d
> 
> $ dpkg -L libpulse0:i386
> /etc
> /etc/pulse
> 
> $ dpkg -L libglib2.0-0:i386
> Package 'libglib2.0-0:i386' does not contain any files (!)
> 
> $ dpkg -L libkf5akonadicontact-data
> Package 'libkf5akonadicontact-data' does not contain any files (!)
> 
> $ dpkg -L libkf5calendarcore5abi2
> Package 'libkf5calendarcore5abi2:amd64' does not contain any files (!)
> 
> $ dpkg -L libkf5grantleetheme5
> Package 'libkf5grantleetheme5' does not contain any files (!)
> 
> $ dpkg -L steam:i386
> Package 'steam:i386' does not contain any files (!)

There are little to no files on your system associated with those 
packages. They've been removed when the packages were uninstalled. But 
if you are unsure and want to keep the packages' remnant entries in the 
package database that's your prerogative.

> 
>>> 1. Fetch updates: sudo apt update && sudo apt full-upgrade && snap
>>> refresh
>>
>> Have created a login for snapd? If you haven't, then the "snap
>> refresh" command will fail because it needs sudo to upgrade any
>> snaps.
> 
> Actually, if you run it without sudo, it pops up a little window for
> you to put your password into.

Well, yes, but it kinda defeats the whole point of chaining those 
commands together. But as you say its just a minor annoyance.

> 
>> Alternatively the following will do what you want with one
>> invocation of sudo.
>>
>> $ sudo bash -c 'apt update && apt full-upgrade && snap refresh'
> 
> I suppose that might be better since my current version has me
> signing in twice, although it's just a minor annoyance.
> 
>>> 2. Reboot if prompted.
>>> 3. Tidy up: sudo apt autoremove --purge && sudo apt clean
>>>
>>> Does that seem like a solid future routine?
>>>
>> Yeah if it works for you. I prefer letting the system as its set up
>> to do as much of the package maintenance automatically, so I don't
>> have a particular routine that I regularly follow.
> 
> My reason for doing it in three separate steps is so that I don't do
> the cleanup until after the reboot, if one is needed.
> 
>> I would note that apt doesn't default to caching downloaded packages
>> after they've been installed, so "apt clean" seems a bit superfluous.
> 
> I figured it could be handy in case one or more of the updates
> installs some necessary packages. Is that unlikely?
> 

If you use apt exclusively to manage packages, then apt clean isn't 
necessary because apt doesn't keep downloaded packages. If you use 
anything else, then its likely they will saved to the cache directory 
unless you set an apt config directive that says not to.

-- 
Keith