Skip to content

quick fix to run archinstall and enable systemd services - #3815

Merged
svartkanin merged 1 commit into
archlinux:masterfrom
blzrosa:brunolzrosa-2025-09-18-quick-fix
Sep 19, 2025
Merged

quick fix to run archinstall and enable systemd services#3815
svartkanin merged 1 commit into
archlinux:masterfrom
blzrosa:brunolzrosa-2025-09-18-quick-fix

Conversation

@blzrosa

@blzrosa blzrosa commented Sep 18, 2025

Copy link
Copy Markdown
Contributor

PR Description:

Just inserted a direct call to SysCommand instead of self.arch_chroot, with the flag --root={self.target}.
This fixed the issue, at least for me.

Tests and Checks

  • [ X ] I have tested the code!

@blzrosa
blzrosa requested a review from Torxed as a code owner September 18, 2025 23:21
@correctmost

Copy link
Copy Markdown
Contributor

There was a similar suggestion on the Arch GitLab: https://gitlab.archlinux.org/archlinux/packaging/packages/systemd/-/issues/54#note_322382

@btantlinger

Copy link
Copy Markdown

The fix partially works, in that I am able to get Arch installed using archinstall... but still seems like something is broken. If I arch-chroot into the system after the install and run my post-install script, any systemctl command is failing with:

Failed to connect to system scope bus via local transport: No data available

This worked before the systemd update.

@correctmost

Copy link
Copy Markdown
Contributor

The fix partially works, in that I am able to get Arch installed using archinstall... but still seems like something is broken.

There's an underlying issue in systemd: systemd/systemd#39021

@YHNdnzj YHNdnzj left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Note that I've updated the PR description to highlight it's not a systemd bug after all. arch-chroot needs to be fixed and the systemd change just revealed the flaw there.


try:
self.arch_chroot(f'systemctl enable {service}')
SysCommand(f'systemctl --root={self.target} enable {service}')

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

This operates on a chroot in a way native to systemd tools and should be done regardless of arch-chroot working or not.

@Torxed Torxed Sep 19, 2025

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

We have to remember that we're on Arch Linux and the recommended way (by our own Wiki) is/was to configure the system using arch-chroot, generally speaking.

It's unfortunate that this issue happens, and we'll try to work around it.
But we wish to use native tooling with default values wherever possible and not use workarounds or too many custom parameters (again, if possible).

@svartkanin
svartkanin merged commit 792db9e into archlinux:master Sep 19, 2025
9 checks passed
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.

6 participants