Skip to content

Conversation

@nachtjasmin
Copy link

After finding out that the kdump-tools package is actually installed and that the problem is more Arch-related (#21006), I added this small notice to the view to prevent further confusion of other users.

Still unsure

I'm not sure whether just checking for Arch is sufficient or if the substring should be expanded to Arch Linux. The /etc/os-release for reference is:

NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://gitlab.archlinux.org/groups/archlinux/-/issues"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=archlinux-logo

Screenshot

Screenshot of the change on a running Arch Linux system. It now links to the GitHub issue I mentioned earlier when visiting the kdump subpage.

After finding out that the kdump-tools package is actually installed and
that the problem is more Arch-related (cockpit-project#21006), I added this small
notice to the view to prevent further confusion of other users.
martinpitt
martinpitt previously approved these changes Jan 7, 2026
Copy link
Member

@martinpitt martinpitt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Sorry for the delay, long xmas break. This looks good enough, and I triggered tests. I left a suggestion for improvement, if you want to push it, please rebase to current main.

</>
);
}
} else if (this.state.os_release.NAME?.includes('Arch')) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think an .ID == "arch" check would be more robust?

@martinpitt martinpitt dismissed their stale review January 8, 2026 05:48

Should also get a test.

@martinpitt
Copy link
Member

Let's also add a test for this. I'll fix this up.

@martinpitt
Copy link
Member

Wait, I thought about this again. This still isn't really helpful for users, we already have the "currently not supported" message, and the refered GitHub issue isn't really actionable from an upstream Cockpit point of view. I prefer to just disable kdump on Arch for the time being. I sent PR #22741 that does that, what do you think?

@martinpitt martinpitt marked this pull request as draft January 8, 2026 08:45
@nachtjasmin
Copy link
Author

nachtjasmin commented Jan 9, 2026

@martinpitt I'm fine with that! We can close this PR in favour of #22741 👍

@martinpitt martinpitt closed this Jan 10, 2026
@martinpitt martinpitt reopened this Jan 10, 2026
@martinpitt
Copy link
Member

Wait, we'll let that auto-close, #22741 still needs review. @jelly will be back next week.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants