I have gotten some reboot required alerts so believe it is at least partially working but I continue to get updated notices for security updates. Is there a way to make them auto update also?
// Automatically upgrade packages from these (origin:archive) pairs
//
// Note that in Ubuntu security updates may pull in new dependencies
// from non-security sources (e.g. chromium). By allowing the release
// pocket these get automatically pulled in.
Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}";
"${distro_id}:${distro_codename}-security";
// Extended Security Maintenance; doesn't necessarily exist for
// every release and this system may not have it installed, but if
// available, the policy for updates is such that unattended-upgrades
// should also install from here by default.
"${distro_id}ESMApps:${distro_codename}-apps-security";
"${distro_id}ESM:${distro_codename}-infra-security";
// uncomment next 3 lines 3-16-24
"${distro_id}:${distro_codename}-updates";
"${distro_id}:${distro_codename}-proposed";
"${distro_id}:${distro_codename}-backports";
};
// Python regular expressions, matching packages to exclude from upgrading
Unattended-Upgrade::Package-Blacklist {
// The following matches all packages starting with linux-
// "linux-";
// Use $ to explicitely define the end of a package name. Without
// the $, "libc6" would match all of them.
// "libc6$";
// "libc6-dev$";
// "libc6-i686$";
// Special characters need escaping
// "libstdc\+\+6$";
// The following matches packages like xen-system-amd64, xen-utils-4.1,
// xenstore-utils and libxenstore3.0
// "(lib)?xen(store)?";
// For more information about Python regular expressions, see
// https://docs.python.org/3/howto/regex.html
};
// This option controls whether the development release of Ubuntu will be
// upgraded automatically. Valid values are "true", "false", and "auto".
Unattended-Upgrade::DevRelease "auto";
// This option allows you to control if on a unclean dpkg exit
// unattended-upgrades will automatically run
// dpkg --force-confold --configure -a
// The default is true, to ensure updates keep getting installed
//Unattended-Upgrade::AutoFixInterruptedDpkg "true";
// Split the upgrade into the smallest possible chunks so that
// they can be interrupted with SIGTERM. This makes the upgrade
// a bit slower but it has the benefit that shutdown while a upgrade
// is running is possible (with a small delay)
//Unattended-Upgrade::MinimalSteps "true";
// Install all updates when the machine is shutting down
// instead of doing it in the background while the machine is running.
// This will (obviously) make shutdown slower.
// Unattended-upgrades increases logind's InhibitDelayMaxSec to 30s.
// This allows more time for unattended-upgrades to shut down gracefully
// or even install a few packages in InstallOnShutdown mode, but is still a
// big step back from the 30 minutes allowed for InstallOnShutdown previously.
// Users enabling InstallOnShutdown mode are advised to increase
// InhibitDelayMaxSec even further, possibly to 30 minutes.
//Unattended-Upgrade::InstallOnShutdown "false";
// Send email to this address for problems or packages upgrades
// If empty or unset then no email is sent, make sure that you
// have a working mail setup on your system. A package that provides
// 'mailx' must be installed. E.g. "user@example.com"
Unattended-Upgrade::Mail "dan.mcmanus5@gmail.com";
// Set this value to one of:
// "always", "only-on-error" or "on-change"
// If this is not set, then any legacy MailOnlyOnError (boolean) value
// is used to chose between "only-on-error" and "on-change"
//Unattended-Upgrade::MailReport "on-change";
// Remove unused automatically installed kernel-related packages
// (kernel images, kernel headers and kernel version locked tools).
//Unattended-Upgrade::Remove-Unused-Kernel-Packages "true";
// Do automatic removal of newly unused dependencies after the upgrade
//Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
// Do automatic removal of unused packages after the upgrade
// (equivalent to apt-get autoremove)
//Unattended-Upgrade::Remove-Unused-Dependencies "false";
// Automatically reboot *WITHOUT CONFIRMATION* if
// the file /var/run/reboot-required is found after the upgrade
//Unattended-Upgrade::Automatic-Reboot "false";
// Automatically reboot even if there are users currently logged in
// when Unattended-Upgrade::Automatic-Reboot is set to true
//Unattended-Upgrade::Automatic-Reboot-WithUsers "true";
// If automatic reboot is enabled and needed, reboot at the specific
// time instead of immediately
// Default: "now"
//Unattended-Upgrade::Automatic-Reboot-Time "02:00";
// Use apt bandwidth limit feature, this example limits the download
// speed to 70kb/sec
//Acquire::http::Dl-Limit "70";
// Enable logging to syslog. Default is False
// Unattended-Upgrade::SyslogEnable "false";
// Specify syslog facility. Default is daemon
// Unattended-Upgrade::SyslogFacility "daemon";
// Download and install upgrades only on AC power
// (i.e. skip or gracefully stop updates on battery)
// Unattended-Upgrade::OnlyOnACPower "true";
// Download and install upgrades only on non-metered connection
// (i.e. skip or gracefully stop updates on a metered connection)
// Unattended-Upgrade::Skip-Updates-On-Metered-Connections "true";
// Verbose logging
// Unattended-Upgrade::Verbose "false";
// Print debugging information both in unattended-upgrades and
// in unattended-upgrade-shutdown
// Unattended-Upgrade::Debug "false";
// Allow package downgrade if Pin-Priority exceeds 1000
// Unattended-Upgrade::Allow-downgrade "false";
// When APT fails to mark a package to be upgraded or installed try adjusting
// candidates of related packages to help APT's resolver in finding a solution
// where the package can be upgraded or installed.
// This is a workaround until APT's resolver is fixed to always find a
// solution if it exists. (See Debian bug #711128.)
// The fallback is enabled by default, except on Debian's sid release because
// uninstallable packages are frequent there.
// Disabling the fallback speeds up unattended-upgrades when there are
// uninstallable packages at the expense of rarely keeping back packages which
// could be upgraded or installed.
// Unattended-Upgrade::Allow-APT-Mark-Fallback "true";
If I understand correctly, the commands you list will update the system. However, I would like the system to automatically update with no interaction from me. That is what Iām trying to accomplish.
Youāre not the first person to show up here after that (awful) link.
We can help you do it right.
Please show us the complete output of sudo apt update
Also, keep in mind that security updates are ALREADY automatically installed on every release of Ubuntu. The notifications are separate from Unattended Upgrades, and occur at different times, so you may still get notifications even if āauto-updateā is working properly.
It is interesting that wine showed up on here because I thought I deleted it. I got an update alert for it and I believe I downloaded it from a non official distribution site. (there must be a better term) I was not using it so tried deleting as a fix.
Hit:1 https://dl.winehq.org/wine-builds/ubuntu focal InRelease
Hit:2 https://dl.winehq.org/wine-builds/ubuntu jammy InRelease
Ign:3 https://ppa.launchpadcontent.net/gezakovacs/ppa/ubuntu jammy InRelease
Err:4 https://ppa.launchpadcontent.net/gezakovacs/ppa/ubuntu jammy Release
404 Not Found [IP: 2620:2d:4000:1::81 443]
Hit:5 http://us.archive.ubuntu.com/ubuntu jammy InRelease
Get:6 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease [128 kB]
Get:7 http://us.archive.ubuntu.com/ubuntu jammy-security InRelease [129 kB]
Hit:8 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease
Reading package lists... Done
E: The repository 'https://ppa.launchpadcontent.net/gezakovacs/ppa/ubuntu jammy Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Maybe you did uninstall the package.
But installing the package does not remove the source that package came from.
You can delete the sources using the Software & Updates application.
Desktop Search ā Software & Updates
While you have Software & Updates open, delete that source too. It does not have 22.04 packages. Thatās why you got a 404 error.
Uninstalling the actual software package is optional.
I have removed that and will see what happens. To clarify, the list I posted from the Update Notifier are likely upgrades that can not automated. Is that correct? IIRC, earlier versions of Ubuntu did not ping for upgradesā¦or maybe they just pinged less.
While you do that, letās look at one random pick from your list: gnupg.
Thatās in the Ubuntu repositories, so if Unattended Upgrades is working properly, it should have upgrades automatically already and no longer pester you. Letās check that:
Please also show us the complete output of apt list gnupg
Incorrect, sorry. Everything marked as a security upgrade that is in the Ubuntu repositories should be automatic. Notification might happen even if everything is working correctly. Thatās what we are checking.
ā¦
dan@dan-nc715aarabaa6712f:~$ sudo apt update
[sudo] password for dan:
Hit:1 https://dl.winehq.org/wine-builds/ubuntu focal InRelease
Hit:2 https://dl.winehq.org/wine-builds/ubuntu jammy InRelease
Hit:3 Index of /ubuntu jammy InRelease
Hit:4 Index of /ubuntu jammy-updates InRelease
Ign:5 http://www.deb-multimedia.org jessie InRelease
Hit:6 Index of /ubuntu jammy-security InRelease
Err:7 http://www.deb-multimedia.org jessie Release
404 Not Found [IP: 2607:5300:120:e71::1 80]
Hit:8 Index of /ubuntu jammy-backports InRelease
Reading package listsā¦ Done
E: The repository āhttp://www.deb-multimedia.org jessie Releaseā does not have a Release file.
N: Updating from such a repository canāt be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
dan@dan-nc715aarabaa6712f:~$ apt list gnupg
Listingā¦ Done
gnupg/jammy-updates,jammy-updates,jammy-security,jammy-security,now 2.2.27-3ubuntu2.3 all [installed,automatic]
N: There is 1 additional version. Please use the ā-aā switch to see it
dan@dan-nc715aarabaa6712f:~$ Hit:1 https://dl.winehq.org/wine-builds/ubuntu focal InRelease
Hit:2 https://dl.winehq.org/wine-builds/ubuntu jammy InRelease
Hit:3 Index of /ubuntu jammy InRelease
Hit:4 Index of /ubuntu jammy-updates InRelease
Ign:5 http://www.deb-multimedia.org jessie InRelease
Hit:6 Index of /ubuntu jammy-security InRelease
Err:7 http://www.deb-multimedia.org jessie Release
404 Not Found [IP: 2607:5300:120:e71::1 80]
Hit:8 Index of /ubuntu jammy-backports InRelease
Reading package listsā¦ Done
E: The repository āhttp://www.deb-multimedia.org jessie Releaseā does not have a Release file.
N: Updating from such a repository canāt be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
dan@dan-nc715aarabaa6712f:~$ apt list gnupg
Listingā¦ Done
gnupg/jammy-updates,jammy-updates,jammy-security,jammy-security,now 2.2.27-3ubuntu2.3 all [installed,automatic]
N: There is 1 additional version. Please use the ā-aā switch to see it
dan@dan-nc715aarabaa6712f:~$ sudo apt update
[sudo] password for dan:
Hit:1 https://dl.winehq.org/wine-builds/ubuntu focal InRelease
Hit:2 https://dl.winehq.org/wine-builds/ubuntu jammy InRelease
Hit:3 Index of /ubuntu jammy InRelease
Hit:4 Index of /ubuntu jammy-updates InRelease
Ign:5 http://www.deb-multimedia.org jessie InRelease
Hit:6 Index of /ubuntu jammy-security InRelease
Err:7 http://www.deb-multimedia.org jessie Release
404 Not Found [IP: 2607:5300:120:e71::1 80]
Hit:8 Index of /ubuntu jammy-backports InRelease
Reading package listsā¦ Done
N: There is 1 additional version. Please use the ā-aā switch to see it2.27-3ubuntu2.3 all [installed,automatic]
ā¦
Tip: Donāt add Debian sources. It can cause huge problems.
Remove that www.deb-multimedia.org source. Recommend to uninstall all packages from that source.
Using the terminal, review the directory /etc/apt/sources.list.d/ . Look for the files from dl.winehq.org. rm those files (touch nothing else).
This is all basic maintenance stuff, which you can avoid in the future by sticking to the Ubuntu repositories. We have yet to get into the actual Notification/Unattended-Upgrade issue that you asked about.
How do I know what came from deb-multimedia? I do have Pithos but donāt remember where it came from.
That directory contains other things that look like they should be deleted. Should it all go except for the Google stuff? I did use RM for the wine files but am wondering if simply deleting those files from the directory does the same thing.
I donāt understand that format. It seems to be some kind of embedded commands. Running just dpkg -l gives a very large list but does not show where anything comes fromā¦or I donāt understand
Your suggestion runs but produces no output. Does that mean there is nothing from that source?
While you get your sources problem straightened out, circling back to your original question:
Are you still getting such notifications?
Do notifications include the same packages, day after day?
Or do some vanish from the list daily, replaced by others?
