Automatic update was enabled by 5.8.3

[kneekoo]

Describe the bug I didn't have automatic updates on the PC I found the option enabled. I noticed the update manager having something new, so I checked it out. It said that the Update Manager needs to be updated, so I applied that update. Once it updated and refreshed, two updates showed up as available: qemu and libssl, both marked as security updates.

I checked their change logs, which took me a few seconds, then I clicked Install Updates, and I got a message that the package manager was already in use. I refreshed, I had the same 2 updates in the list, and I got the same "already in use" message. A few refreshes later they were gone. I went to the History of Updates, and noticed they were installed. So I went to Edit -> Preferences -> Automation and I found that the automatic updates were enabled.

Then I can here to see what new PRs were added to the latest releases, and found nothing relevant. I never had this issue before. Please look into this.

Expected behavior Clearly, if I have automatic updates disabled, it shouldn't be enabled automatically.

Distribution:

• Linux Mint 20.3 Cinnamon

Software version: 5.8.3

Log: /var/log/apt/history.log

Start-Date: 2022-06-20  13:41:25
Commandline: /usr/sbin/synaptic --hide-main-window --non-interactive --parent-window-id 85983246 -o Synaptic::closeZvt=true --set-selections-file /tmp/tmp2pydv9wh
Requested-By: nicu (1000)
Upgrade: mintupdate:amd64 (5.8.1, 5.8.2)
End-Date: 2022-06-20  13:41:27

Start-Date: 2022-06-20  13:41:43
Commandline: /usr/sbin/synaptic --hide-main-window --non-interactive --parent-window-id 127926285 -o Synaptic::closeZvt=true --set-selections-file /tmp/tmp07aoci9r
Requested-By: nicu (1000)
Upgrade: apturl-common:amd64 (0.5.2+linuxmint11, 0.5.2+linuxmint12), apturl:amd64 (0.5.2+linuxmint11, 0.5.2+linuxmint12)
End-Date: 2022-06-20  13:41:45

Start-Date: 2022-06-20  17:55:08
Commandline: /usr/sbin/synaptic --hide-main-window --non-interactive --parent-window-id 127926285 -o Synaptic::closeZvt=true --set-selections-file /tmp/tmp_a_til38
Requested-By: nicu (1000)
Upgrade: apturl-common:amd64 (0.5.2+linuxmint12, 0.5.2+linuxmint13), apturl:amd64 (0.5.2+linuxmint12, 0.5.2+linuxmint13)
End-Date: 2022-06-20  17:55:09

Start-Date: 2022-06-21  17:54:36
Commandline: /usr/sbin/synaptic --hide-main-window --non-interactive --parent-window-id 127926285 -o Synaptic::closeZvt=true --set-selections-file /tmp/tmp71avoben
Requested-By: nicu (1000)
Upgrade: mintupdate:amd64 (5.8.2, 5.8.3)
End-Date: 2022-06-21  17:54:40

Start-Date: 2022-06-21  17:54:52
Commandline: apt-get install --assume-yes --option Dpkg::Options::=--force-confnew openssl libssl1.1 libssl1.1:i386 qemu-system-x86 qemu qemu-system-data qemu-utils qemu-kvm qemu-block-extra qemu-system-common qemu-system-gui
Upgrade: openssl:amd64 (1.1.1f-1ubuntu2.13, 1.1.1f-1ubuntu2.15), qemu-system-x86:amd64 (1:4.2-3ubuntu6.21, 1:4.2-3ubuntu6.23), qemu:amd64 (1:4.2-3ubuntu6.21, 1:4.2-3ubuntu6.23), qemu-system-data:amd64 (1:4.2-3ubuntu6.21, 1:4.2-3ubuntu6.23), qemu-utils:amd64 (1:4.2-3ubuntu6.21, 1:4.2-3ubuntu6.23), qemu-kvm:amd64 (1:4.2-3ubuntu6.21, 1:4.2-3ubuntu6.23), libssl1.1:amd64 (1.1.1f-1ubuntu2.13, 1.1.1f-1ubuntu2.15), libssl1.1:i386 (1.1.1f-1ubuntu2.13, 1.1.1f-1ubuntu2.15), qemu-block-extra:amd64 (1:4.2-3ubuntu6.21, 1:4.2-3ubuntu6.23), qemu-system-common:amd64 (1:4.2-3ubuntu6.21, 1:4.2-3ubuntu6.23), qemu-system-gui:amd64 (1:4.2-3ubuntu6.21, 1:4.2-3ubuntu6.23)
End-Date: 2022-06-21  17:55:07

Start-Date: 2022-06-21  18:06:16
Commandline: /usr/sbin/synaptic --hide-main-window --non-interactive --parent-window-id 115343373 -o Synaptic::closeZvt=true --set-selections-file /tmp/tmpi2tyrhkr
Requested-By: nicu (1000)
Upgrade: brave-browser:amd64 (1.39.122, 1.40.105)
End-Date: 2022-06-21  18:06:26

As you can see, all except qemu and libssl were Requested-By: nicu (1000). How did this happen?

[mtwebster]

A couple devs experienced this also - can you run the following:

journalctl | grep mintupdate-automation

5.8.3 was released today that should prevent this ever happening, though we're still looking into why it happened in the first place.

Once you install 5.8.3, make sure the service has been disabled:

systemctl disable mintupdate-automation-upgrade.service

Once you do that, run:

systemctl status mintupdate-automation-upgrade.service

You should see something like this:

○ mintupdate-automation-upgrade.service - Update Manager automatic upgrades
     Loaded: loaded (/lib/systemd/system/mintupdate-automation-upgrade.service; static)
     Active: inactive (dead)

Sorry about this - it definitely wasn't something deliberate by us.

[kneekoo]

nicu@nas:~$ journalctl | grep mintupdate-automation
Feb 23 17:45:55 nas pkexec[2385720]: nicu: Executing command [USER=root] [TTY=unknown] [CWD=/home/nicu] [COMMAND=/usr/bin/mintupdate-automation autoremove enable]
Feb 23 17:46:01 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Feb 28 02:15:21 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Feb 28 05:34:04 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Mar 01 00:43:06 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Mar 08 00:54:25 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Mar 15 00:52:26 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Mar 15 15:15:11 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Mar 15 18:24:36 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Mar 22 00:18:59 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Mar 29 00:12:48 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Mar 30 07:31:19 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Mar 30 08:02:04 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Mar 30 08:08:06 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Mar 30 12:05:22 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Apr 05 00:56:09 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Apr 12 00:02:50 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Apr 14 12:38:53 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Apr 14 12:52:11 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Apr 14 15:59:45 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Apr 19 00:16:11 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Apr 22 09:15:50 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Apr 22 12:55:15 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Apr 26 00:24:18 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
May 03 00:40:55 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
May 10 00:19:58 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
May 17 00:22:17 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
May 22 13:29:12 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
May 22 13:48:00 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
May 22 18:01:04 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
May 24 00:20:41 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
May 31 00:54:05 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Jun 07 00:22:14 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Jun 10 19:27:19 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Jun 10 19:30:39 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Jun 10 19:43:34 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Jun 10 23:40:44 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Jun 14 00:18:26 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Jun 21 00:05:10 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Jun 25 18:19:26 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Jun 25 18:38:49 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Jun 25 21:55:15 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Jun 28 00:00:28 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Jul 05 00:42:29 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Jul 06 09:16:06 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Jul 06 12:57:07 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Jul 08 15:55:25 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Jul 08 19:27:26 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Jul 12 00:17:11 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Jul 19 00:39:41 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Jul 21 09:10:21 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Jul 21 09:24:36 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Jul 21 12:46:13 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Jul 25 01:13:49 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Jul 25 01:34:46 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Jul 25 01:38:13 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Jul 25 05:17:11 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Jul 26 00:01:23 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Aug 02 00:43:41 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Aug 09 00:22:31 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Aug 16 00:47:07 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Aug 23 00:55:39 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Aug 30 00:40:17 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Sep 03 02:46:21 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Sep 03 05:53:48 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Sep 06 00:58:42 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Sep 13 00:43:57 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Sep 14 15:34:17 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Sep 14 15:49:32 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Sep 14 19:43:46 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Sep 20 00:38:11 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Sep 27 00:52:37 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Oct 03 01:10:37 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Oct 03 01:20:52 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Oct 03 04:33:17 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Oct 03 09:53:27 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Oct 03 10:08:30 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Oct 03 14:00:41 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Oct 04 00:17:09 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Oct 11 00:38:23 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Oct 18 00:33:12 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Oct 23 20:07:52 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Oct 23 20:22:43 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Oct 23 20:23:21 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Oct 23 20:55:34 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Oct 24 00:16:55 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Oct 25 00:26:04 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Oct 28 17:25:51 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Oct 28 22:16:56 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Oct 29 19:10:50 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Oct 29 22:29:32 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Nov 01 00:35:52 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Nov 08 00:10:00 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Nov 09 23:27:19 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Nov 09 23:34:22 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Nov 10 03:23:04 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Nov 15 00:02:43 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Nov 22 00:31:22 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Nov 29 00:47:40 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Dec 06 00:03:53 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Dec 13 00:07:54 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Dec 16 12:25:34 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Dec 16 12:26:06 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Dec 16 12:48:42 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Dec 17 15:38:24 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Dec 20 00:29:31 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Dec 24 19:57:13 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Dec 24 23:33:25 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Dec 27 00:08:57 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Jan 03 00:21:23 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Jan 08 16:00:40 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Jan 08 16:28:10 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Jan 08 20:11:39 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Jan 10 00:58:00 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Jan 13 13:14:18 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Jan 13 16:52:01 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Jan 17 00:34:34 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Jan 17 10:46:17 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Jan 17 14:27:53 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Jan 19 11:18:44 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Jan 19 11:30:41 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Jan 19 14:50:47 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Jan 24 00:04:36 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Jan 31 00:51:35 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Feb 04 22:08:35 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Feb 04 22:29:07 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Feb 05 04:35:49 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Feb 07 00:46:58 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Feb 14 00:44:21 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Feb 21 00:50:47 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Feb 21 11:00:06 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Feb 21 15:00:23 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Feb 28 00:10:56 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Feb 28 04:20:58 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Feb 28 04:35:32 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Feb 28 08:05:32 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Mar 07 00:40:53 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Mar 12 20:27:36 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Mar 14 00:49:59 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Mar 18 08:06:25 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Mar 18 11:54:49 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Mar 21 00:48:15 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Mar 28 00:06:29 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Apr 04 00:53:48 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Apr 09 19:39:18 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Apr 09 19:41:23 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Apr 09 20:20:44 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Apr 09 23:53:48 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Apr 11 00:56:27 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Apr 18 00:26:42 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Apr 20 08:24:21 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Apr 20 08:41:46 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Apr 20 12:41:13 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Apr 25 00:20:41 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
May 02 00:29:06 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
May 09 00:50:20 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
May 16 00:54:03 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
May 23 00:38:35 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
May 30 00:01:34 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Jun 06 00:04:24 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Jun 13 00:51:59 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Jun 18 02:46:21 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Jun 18 03:22:54 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Jun 18 07:19:33 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Jun 20 00:40:18 nas systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
Jun 21 17:54:39 nas systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
Jun 21 17:55:11 nas systemd[1]: mintupdate-automation-upgrade.service: Succeeded.
nicu@nas:~$ systemctl disable mintupdate-automation-upgrade.service
nicu@nas:~$ systemctl status mintupdate-automation-upgrade.service
● mintupdate-automation-upgrade.service - Update Manager automatic upgrades
     Loaded: loaded (/lib/systemd/system/mintupdate-automation-upgrade.service; static; vendor preset: enabled)
     Active: inactive (dead) since Tue 2022-06-21 17:55:11 CEST; 1h 57min ago
TriggeredBy: ● mintupdate-automation-upgrade.timer
   Main PID: 286845 (code=exited, status=0/SUCCESS)

Jun 21 17:54:39 nas systemd[1]: Starting Update Manager automatic upgrades...
Jun 21 17:54:39 nas sudo[286870]:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/mint-refresh-cache
Jun 21 17:54:39 nas sudo[286870]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 21 17:54:46 nas sudo[286870]: pam_unix(sudo:session): session closed for user root
Jun 21 17:55:11 nas systemd[1]: mintupdate-automation-upgrade.service: Succeeded.
Jun 21 17:55:11 nas systemd[1]: Finished Update Manager automatic upgrades.

The options is still active in mintUpdate. Was that supposed to be disabled too, or I have to manually disable it?

[clefebvre]

The bump to debhelper 10 caused this regression. debhelper 10 basically enables all services/timers behind your back.

This was reverted in 5.8.4 which was pushed just a minute ago, so people who didn't update to 5.8.3 won't be impacted.

We've got a WIP to refactor how this is enabled/disabled, so that it no longer relies on systemd (which as we can see debhelper likes to mess with): https://github.com/linuxmint/mintupdate/pull/737. This will make the mechanism safer. debhelper/systemd couldn't enable it anymore... but If we merge this though, people who previously enabled automated updates will need to do so again. We could cover this in the monthly news.

For now, the workaround for people impacted with the 5.8.3 update is to restore the previous snapshot and to jump straight from 5.8.2 to 5.8.4. Or alternatively, to update to 5.8.4 and disable automated updates using the UI.

[kneekoo]

Thanks, updated to 5.8.4 and manually disabled automatic update from the UI.

[Perkolator]

I was hit with this too. Package auto-updates was turned on automatically.

journalctl (only few recent):

kesä 06 00:26:16 sys systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
kesä 13 00:35:11 sys systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
kesä 20 00:29:35 sys systemd[1]: mintupdate-automation-autoremove.service: Succeeded.
kesä 21 17:11:34 sys systemd[1]: mintupdate-automation-autoremove.timer: Succeeded.
kesä 21 20:39:31 sys systemd[1]: mintupdate-automation-upgrade.service: Succeeded.
kesä 21 20:45:06 sys pkexec[2043853]: user: Executing command [USER=root] [TTY=unknown] [CWD=/home/user] [COMMAND=/usr/bin/mintupdate-automation upgrade disable]
kesä 21 20:45:06 sys systemd[1]: mintupdate-automation-upgrade.timer: Succeeded.

systemctl (didn't need to disable, I guess that was done when I turned package updates off again in mintupdate settings):

● mintupdate-automation-upgrade.service - Update Manager automatic upgrades
     Loaded: loaded (/lib/systemd/system/mintupdate-automation-upgrade.service; static; vendor preset: enabled)
     Active: inactive (dead)

kesä 21 20:39:24 sys 30utility[2038046]: debug: /dev/nvme0n1p3 is not a FAT partition: exiting
kesä 21 20:39:24 sys 50mounted-tests[2038047]: debug: running subtest /usr/lib/os-probes/mounted/40lsb
kesä 21 20:39:24 sys 50mounted-tests[2038049]: debug: running subtest /usr/lib/os-probes/mounted/70hurd
kesä 21 20:39:24 sys 50mounted-tests[2038051]: debug: running subtest /usr/lib/os-probes/mounted/80minix
kesä 21 20:39:24 sys 83haiku[2038055]: debug: /dev/nvme0n1p3 is not a BeFS partition: exiting
kesä 21 20:39:25 sys os-prober[2038166]: debug: running /usr/lib/os-probes/mounted/20macosx on mounted /dev/nvme0n1p5
kesä 21 20:39:25 sys os-prober[2038169]: debug: running /usr/lib/os-probes/mounted/20microsoft on mounted /dev/nvme0n1p5
kesä 21 20:39:25 sys 30utility[2038174]: debug: /dev/nvme0n1p5 is not a FAT partition: exiting
kesä 21 20:39:31 sys systemd[1]: mintupdate-automation-upgrade.service: Succeeded.
kesä 21 20:39:31 sys systemd[1]: Finished Update Manager automatic upgrades.

Update history:

• I think I updated the apturl updates manually (between mintupdate 5.8.2 and 5.8.3).
• After mintupdate 5.8.3 the nvidia drivers and the kernel were automatically updated according to that update history list.
• The ssl updates I did update manually. After this I finally noticed that a kernel update wasn't listed anymore (which I was postponing) and I started investigating what had happened and noticed that the package auto-updates was turned on.

The nvidia updating automatically is a big mystery to me because I had blacklisted that version that is shown in the update history list.

I know I'm using an old version but it was the best driver version with less problems than with other versions (even some newer that I have tested). The mintupdate hasn't offered me any newer nvidia drivers, otherwise I would have tested them and put them to the blacklist as well if not working well. BUT, this gets more interesting, this is what I see in Driver Manager:

It says that my current nvidia driver version is 470.129.06. I haven't rebooted yet. The update history shows a completely different "new version" (460.91.03) the automatic update did. So, what did happen with nvidia driver update? I don't understand.

Too bad nvidia drivers are so bad in linux that they can't be updated worry free. I have had serious problems when coming back from hibernate state, all hardware-accelerated software (chromium family, electron) have serious window/screen drawing problems, Xid errors in logs (with newer versions), and with many nvidia versions, even freezing computer completely. The 450.119.03 version has been the last version that gives the least amount of problems, but still after hibernate, some hw-accelerated software could sometimes freeze for minutes until working again. :( I guess I have to test newer versions again after I reboot.

[clefebvre]

Note that the root blacklist is distinct from the user's, that's why there's a button in preferences -> automation to sync them. Without that the automation would have run without any blacklist.

[Perkolator]

Note that the root blacklist is distinct from the user's, that's why there's a button in preferences -> automation to sync them. Without that the automation would have run without any blacklist.

Ok. Maybe the system could be made easier to understand? On the blacklist tab, there's no mention of them applying only to current user. Maybe the manual sync feature/button on automation tab should be removed and adding a new "apply system wide" checkbox to blacklist tab? That way the blacklisting would be done from single place, and there would be no need to try to remember to manually sync the blacklist (if using autoupdate for packages).

---

But what about the nvidia update version confusion? I had 450.119.03 installed, automatic update updated it, the history of updates window shows an update from 450.119.03 to 460.91.03, but it was actually updated to 470.129.06. Something is not right here. At least the history of updates window shows wrong "new" version. Should I open a new issue or is this a known problem?

[kneekoo]

Note that the root blacklist is distinct from the user's, that's why there's a button in preferences -> automation to sync them. Without that the automation would have run without any blacklist.

Ok. Maybe the system could be made easier to understand? On the blacklist tab, there's no mention of them applying only to current user. Maybe the manual sync feature/button on automation tab should be removed and adding a new "apply system wide" checkbox to blacklist tab? That way the blacklisting would be done from single place, and there would be no need to try to remember to manually sync the blacklist (if using autoupdate for packages).

Yeah, this feature needs a second look. I also assumed the blacklist would do just that, prevent certain packages from being installed as updates, no matter if from mintUpdate GUI, the terminal, or any automated way.

Would the OS keep the old version for the user who blacklisted the newer one, so that user can keep using the old one while all other users (without blacklists) would use the newer one? If not, how is the blacklist supposed to work, and why not apply it system-wide by default? What valid case would there be for automation to ignore the blacklist? If there's none, the export feature could just go away.

[Moini]

I wonder why the newsletter recommended resetting the whole system instead of just disabling it by moving a slider button, which is much easier, much more user friendly, and associated with less data loss.

Is there a reason for that?

[Moini]

(I mean, unless it already has done any damage, that is)