Skip to content

Automatic updates take very long to complete #1030

Open

Description

@MinuteNewt

Describe the bug
Automatic updates for Linux Mint Cinnamon 22.3 take a very long time to complete. I have a fast broadband connection and I've enabled mirrors close to me. I'm trying to install a 400 MB Nvidia drivers update. When installed manually, this would take me 2 minutes at most. Now that it's trying to update it automatically, the update has taken 30 minutes, and it is not completed yet. I very much doubt that this is a connection speed or mirror issue. I noticed this issue in previous versions of Linux Mint.

Edit 1: the update finished on 8.26 AM, two minutes ago.
Edit 2: Why is update manager detecting the update three times, and not updating it right away?

Screenshots
If applicable, add screenshots to help explain your problem, you can just drag & drop them here.

To Reproduce
Steps to reproduce the behavior:

  1. Have automatic updates enabled
  2. Wait for an update to appear
  3. Do not update, let automatic updates kick in
  4. Slow update

Expected behavior
A clear and concise description of what you expected to happen.

Distribution:

  • [x ] Linux Mint
  • LMDE
  • Other (please specify)

Software version:
7.1.4

Logs:
2026.03.10@07:22 ++ Launching Update Manager
2026.03.10@07:22 ++ Initial refresh will happen in 0 day(s), 0 hour(s) and 10 minute(s)
2026.03.10@07:22 ++ Inhibited power management
2026.03.10@07:22 ++ Checking for updates
2026.03.10@07:22 ++ System is up to date
2026.03.10@07:22 ++ Refresh finished
2026.03.10@07:22 ++ Resumed power management
2026.03.10@07:22 ++ Tracker: Mintupdate update button was pressed recently: 1 days ago
2026.03.10@07:32 ++ Update Manager is in tray mode; performing initial refresh
2026.03.10@07:32 ++ Auto refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
2026.03.10@07:32 ++ Inhibited power management
2026.03.10@07:32 ++ Refreshing cache
2026.03.10@07:32 ++ Refreshing cache for Cinnamon updates
2026.03.10@07:32 ++ Refreshing cache for Flatpak updates
2026.03.10@07:32 ++ Checking for updates
2026.03.10@07:32 ++ Found 1 software updates
2026.03.10@07:32 ++ Refresh finished
2026.03.10@07:32 ++ Resumed power management
2026.03.10@07:33 ++ Update Manager is in tray mode; performing auto refresh
2026.03.10@07:33 ++ Auto refresh will happen in 0 day(s), 1 hour(s) and 59 minute(s)
2026.03.10@07:33 ++ Inhibited power management
2026.03.10@07:33 ++ Refreshing cache
2026.03.10@07:33 ++ Refreshing cache for Cinnamon updates
2026.03.10@07:33 ++ Refreshing cache for Flatpak updates
2026.03.10@07:33 ++ Checking for updates
2026.03.10@07:33 ++ Found 1 software updates
2026.03.10@07:33 ++ Refresh finished
2026.03.10@07:33 ++ Resumed power management
2026.03.10@07:35 ++ Inhibited power management
2026.03.10@07:35 ++ Checking for updates
2026.03.10@07:35 ++ Found 1 software updates
2026.03.10@07:35 ++ Refresh finished
2026.03.10@07:35 ++ Resumed power management
2026.03.10@08:26 ++ Changes to the package cache detected; triggering refresh
2026.03.10@08:26 ++ Inhibited power management
2026.03.10@08:26 ++ Checking for updates
2026.03.10@08:26 ++ System is up to date
2026.03.10@08:26 ++ Refresh finished
2026.03.10@08:26 ++ Resumed power management

11 MB update took 30 minutes to install

Logs 2
2026.03.14@09:05 ++ Launching Update Manager
2026.03.14@09:05 ++ Initial refresh will happen in 0 day(s), 0 hour(s) and 10 minute(s)
2026.03.14@09:05 ++ Inhibited power management
2026.03.14@09:05 ++ Checking for updates
2026.03.14@09:05 ++ System is up to date
2026.03.14@09:05 ++ Refresh finished
2026.03.14@09:05 ++ Resumed power management
2026.03.14@09:05 ++ Tracker: Mintupdate update button was pressed recently: 1 days ago
2026.03.14@09:15 ++ Update Manager is in tray mode; performing initial refresh
2026.03.14@09:15 ++ Auto refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
2026.03.14@09:15 ++ Inhibited power management
2026.03.14@09:15 ++ Refreshing cache
2026.03.14@09:15 ++ Refreshing cache for Cinnamon updates
2026.03.14@09:15 ++ Refreshing cache for Flatpak updates
2026.03.14@09:15 ++ Checking for updates
2026.03.14@09:15 ++ Found 2 software updates
2026.03.14@09:15 ++ Refresh finished
2026.03.14@09:15 ++ Resumed power management
2026.03.14@09:16 ++ Update Manager is in tray mode; performing auto refresh
2026.03.14@09:16 ++ Auto refresh will happen in 0 day(s), 1 hour(s) and 59 minute(s)
2026.03.14@09:16 ++ Inhibited power management
2026.03.14@09:16 ++ Refreshing cache
2026.03.14@09:16 ++ Refreshing cache for Cinnamon updates
2026.03.14@09:16 ++ Refreshing cache for Flatpak updates
2026.03.14@09:16 ++ Checking for updates
2026.03.14@09:16 ++ Found 2 software updates
2026.03.14@09:16 ++ Refresh finished
2026.03.14@09:16 ++ Resumed power management
2026.03.14@09:46 ++ Inhibited power management
2026.03.14@09:46 ++ Refreshing cache
2026.03.14@09:46 ++ Refreshing cache for Flatpak updates
2026.03.14@09:46 ++ Refreshing cache for Cinnamon updates
2026.03.14@09:46 ++ Checking for updates
2026.03.14@09:46 ++ System is up to date
2026.03.14@09:46 ++ Refresh finished
2026.03.14@09:46 ++ Resumed power management
2026.03.14@09:46 ++ Inhibited power management
2026.03.14@09:46 ++ Refreshing cache
2026.03.14@09:46 ++ Refreshing cache for Cinnamon updates
2026.03.14@09:46 ++ Refreshing cache for Flatpak updates
2026.03.14@09:46 ++ Checking for updates
2026.03.14@09:46 ++ System is up to date
2026.03.14@09:46 ++ Refresh finished
2026.03.14@09:46 ++ Resumed power management

Screenshot

Image

Activity

  1. bgottschall commented on Apr 20, 2026

    @bgottschall

    I can confirm. For me it is compiling the nvidia kernel modules right now for a kernel update. But according to htop it is not using much of the CPU time. All 12 CPU cores are mostly idle around 2 to 10% during the compilation. So something is definitly off here.

    One can follow what automatic updates is doing with

    tail -f /var/log/mintupdate.log
    
  2. bgottschall commented on Apr 20, 2026

    @bgottschall

    Yeah no wonder why it takes very long. According to the cgroup cpu.max the whole auto update process is only allowed to take half of ONE cpu core. While I understand that the automatic update should not affect the performance in any major way this is kind of ridiculous for kernel update and kernel module compilations.

  3. MinuteNewt commented on Apr 21, 2026

    @MinuteNewt
    Author

    Yeah no wonder why it takes very long. According to the cgroup cpu.max the whole auto update process is only allowed to take half of ONE cpu core. While I understand that the automatic update should not affect the performance in any major way this is kind of ridiculous for kernel update and kernel module compilations.

    Thanks for looking into this. I've resorted to turning off automatic updates for the time being, because updating three or four updates manually (as the accumulate) is quicker than allowing the automatic updater to run.

    I hope now that you've replied this is going to get some visibility.

  4. MinuteNewt commented on Oct 26, 2026

    @MinuteNewt
    Author

    Bump. Still relevant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions