linuxmint / linuxmint/mintupdate

Upgrade to Xia: throwing prompt to switch to a local mirror; 'requirements is not responding'

Open
#911 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

BUG
Dominant language
Python
Stars
425
Forks
190
PR merge metrics
No merged PRs in 30d

Description

Describe the bug
I initiated this upgrade: to Mint 22.1; from Mint 21.0 (Cinnamon). The result seemed to be a bug, or two.

Screenshots

Image

To Reproduce

  • Use the Update Manager to initiate the upgrade.
  • See what I saw - perhaps; I do not know exactly what is involved in reproducing the bug. The computer at issue is capable and was not under heavy load.

Expected behavior
I expect no message about a mirror and no confusing message about 'Requirements' not responding.

Distribution:

  • [X ] Linux Mint

Software version:
6.1.5

Logs:
01.17@03:45 ++ Launching Update Manager
01.17@03:45 ++ Changes to the package cache detected; triggering refresh
01.17@03:45 ++ Initial refresh will happen in 0 day(s), 0 hour(s) and 10 minute(s)
01.17@03:45 ++ Inhibited power management
01.17@03:45 ++ Starting refresh (local only)
01.17@03:45 ++ Tracker: APT upgrades were taken recently: 0 days ago
01.17@03:45 ++ System is up to date
01.17@03:45 ++ Refresh finished
01.17@03:45 ++ Resumed power management
01.17@03:49 ++ Changes to the package cache detected; triggering refresh
01.17@03:49 ++ Inhibited power management
01.17@03:49 ++ Starting refresh (local only)
01.17@03:49 ++ Found 1 software updates
01.17@03:49 ++ Refresh finished
01.17@03:49 ++ Resumed power management
01.17@03:55 ++ Update Manager window is open; skipping initial refresh
01.17@03:55 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
01.17@03:56 ++ Update Manager window is open; delaying recurring refresh by 60s
01.17@03:57 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
01.17@03:58 ++ Update Manager window is open; delaying recurring refresh by 60s
01.17@03:59 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
01.17@04:00 ++ Update Manager window is open; delaying recurring refresh by 60s
01.17@04:01 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
01.17@04:02 ++ Update Manager window is open; delaying recurring refresh by 60s
01.17@04:03 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
01.17@04:04 ++ Update Manager window is open; delaying recurring refresh by 60s
01.17@04:05 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
01.17@04:06 ++ Update Manager window is open; delaying recurring refresh by 60s
01.17@04:07 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
01.17@04:07 ++ Changes to the package cache detected; triggering refresh
01.17@04:07 ++ Inhibited power management
01.17@04:07 ++ Starting refresh (local only)
01.17@04:07 ++ System is up to date
01.17@04:07 ++ Refresh finished
01.17@04:07 ++ Resumed power management
01.17@04:08 ++ Update Manager window is open; delaying recurring refresh by 60s
01.17@04:09 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
01.17@04:10 ++ Update Manager window is open; delaying recurring refresh by 60s
01.17@04:11 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
01.17@04:12 ++ Update Manager window is open; delaying recurring refresh by 60s
01.17@04:13 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
01.17@04:14 ++ Update Manager window is open; delaying recurring refresh by 60s
01.17@04:15 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
01.17@04:16 ++ Update Manager window is open; delaying recurring refresh by 60s

Additional information

I clicked 'Wait' and was told that the upgrade had succeeded.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Update Manager upgrade flow and the supplied refresh log; attempt the reported Linux Mint 21.0-to-22.1 Cinnamon upgrade using software version 6.1.5. Compare the mirror prompt and “Requirements” not responding message with the expected upgrade outcome. Done means the upgrade completes without those confusing messages.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.