Skip to content

Discussion: giving users a real clue when an update fails, not just a file list #1067

@martin152

Description

@martin152

Opening this for discussion rather than as a concrete request. I started a related thread on aptkit about the backend side (linuxmint/aptkit#18), and this is the Update Manager half.

Recently an update failed here. The error told me which files couldn't be fetched but not why. No reason, no next step. I eventually traced it to a mirror that was syncing, but only because I went into the apt logs by hand. A regular user can't do that, and they shouldn't have to.

Older versions of Update Manager used to show more. Issues #116 and #120 from years back show the dialog printing reasons like "Could not resolve". Some of that detail seems to have been lost over the various backend changes. There are also open issues like #888 where a failure shows only a cryptic line with no actionable cause.

So my question to other users and the maintainers: when an install or update fails, how much should the dialog tell someone who isn't comfortable in a terminal? I'd love to see at least a plain-language reason and a hint at what to try, even if the deep detail stays tucked away. Curious what others think before anyone proposes a specific change.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions