Update Manager automatically checks for updates no matter the configuration
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- python
- Domain
- desktop, operating-systems
Research direction
Start by reproducing the issue in Linux Mint 7.1.4 with Auto-Refresh disabled or set to a longer interval, then compare the observed notifications with the logged refresh times. Trace the Update Manager's refresh scheduling from the initial refresh through subsequent checks; done means checks and notifications follow the configured Auto-Refresh options.
Written by the indexing model from the issue text.
Description
Describe the bug
No matter how the Update Manager is configured, it checks for updates very regularly all day long.
Screenshots
To Reproduce
Steps to reproduce the behavior:
- Configure Update manager Auto-Refresh options as desired, even disabled.
- Wait
- Observe update notifications that do not align to configured settings
Expected behavior
Update notifications in alignment with Auto-Refresh configuration
Distribution:
- [x ] Linux Mint
Software version:
7.1.4
Logs:
2026.07.18@08:01 ++ Launching Update Manager
2026.07.18@08:01 ++ Initial refresh will happen in 0 day(s), 0 hour(s) and 10 minute(s)
2026.07.18@08:01 ++ Inhibited power management
2026.07.18@08:01 ++ Checking for updates
2026.07.18@08:01 ++ Found 5 software updates
2026.07.18@08:01 ++ Refresh finished
2026.07.18@08:01 ++ Resumed power management
Additional context
It can take several days to confirm the bug as observation requires updates to be available (i.e., if it is checking more frequently than configured, but no updates are available, then new updates available notification cannot appear).
- Dominant language
- Python
- Stars
- 425
- Forks
- 190
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from linuxmint/mintupdate
-
BUG
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
linuxmint/mintupdate#1089 ·
-
BUG
Difficulty 1/5 Under an hour Newbie friendliness 88/100
linuxmint/mintupdate#1062 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
linuxmint/mintupdate#1041 · 1 comment ·
-
FEATURE REQUEST
Difficulty 1/5 Under an hour Newbie friendliness 65/100
linuxmint/mintupdate#910 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
linuxmint/mintupdate#903 ·
All issues in linuxmint/mintupdate
Similar issues
-
pydanty:is-working
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pydantic/pydantic-ai#8843 ·
Maintainers usually reply within 1 day
-
breaking change enhancement server
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sktime/sktime#11310 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day