Update Manager uses the wrong destination for keyrings

Open
#1,036 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
linux, python
Domain
desktop, operating-systems

Research direction

Reproduce the issue through Software Sources > Maintenance > Add missing keys and inspect the Update Manager code handling keyrings. Check whether other keyring-related tools use the old destination; done means missing keys are placed in /usr/share/keyrings and related tools no longer write to /etc/apt/trusted.gpg.d/.

Written by the indexing model from the issue text.

Description

BUG

Describe the bug
The "Add missing keys" button adds keys to /etc/apt/trusted.gpg.d/. This is wrong, because the keyrings have been moved to /usr/share/keyrings. The apt command does not look in /etc/apt/trusted.gpg.d/, so this button doesn't do anything useful.

Furthermore, this may impact other tools within Update Manager that interact with keyrings.

Screenshots

Image

To Reproduce

  1. Software Sources > Maintenance > Add missing keys
  2. ls -l /etc/apt/trusted.gpg.d/
  3. See keys updated in bad location

Expected behavior
Keys in /usr/share/keyrings

Distribution:
Linux Mint

Software version:
7.1.4

Logs:
Nothing relevant.

Dominant language
Python
Stars
425
Forks
190
No merged PRs in 30d

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.

More from linuxmint/mintupdate

All issues in linuxmint/mintupdate

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.