Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sudo pacman -Su results in errors #343

Open
olsonpm opened this issue Jan 12, 2024 · 2 comments
Open

sudo pacman -Su results in errors #343

olsonpm opened this issue Jan 12, 2024 · 2 comments

Comments

@olsonpm
Copy link

olsonpm commented Jan 12, 2024

IMPORTANT
Please read README and Docs before creating the issue.

Please fill out the below information:
Describe the issue
A clear and concise description of what the bug is.

when setting up a new instance, I get a couple errors upon running sudo pacman -Su

( 1/13) Creating system user accounts...
Failed to take /etc/passwd lock: Invalid argument
error: command failed to execute correctly
...
( 7/13) Creating temporary files...
/usr/lib/tmpfiles.d/journal-nocow.conf:26: Failed to resolve specifier: uninitialized /etc/ detected, skipping.
All rules containing unresolvable specifiers will be skipped.
/usr/lib/tmpfiles.d/shadow.conf:1: Failed to resolve group 'groups': No such process
error: command failed to execute correctly

full command output here

To Reproduce
Steps to reproduce the behavior:

go through steps as described in docs. Error occurs in the last command at Initialize Keyring

Expected behavior
A clear and concise description of what you expected to happen.

I expected the output to not contain errors

Screenshots
If applicable, add screenshots to help explain your problem.

Enviroment:

  • Windows build number: [e.g. 10.0.17134.228] (Type ver at a Command Prompt)
    Microsoft Windows [Version 10.0.19045.3930]

  • Security Software: [e.g. ESET Internet Security]
    builtin windows defender ? Not sure what this is asking

  • WSL version 1/2: [e.g. WSL1]
    Should be wsl 1 but I'm not entirely sure how this is working. For example the command wsl --set-version arch 1 results in

λ wsl --set-version arch 1
Conversion in progress, this may take a few minutes.
The distribution is already the requested version.
Error code: Wsl/Service/WSL_E_VM_MODE_INVALID_STATE

however wsl --version results in

λ wsl --version
WSL version: 2.0.14.0
Kernel version: 5.15.133.1-1
WSLg version: 1.0.59
MSRDC version: 1.2.4677
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.3930

so let me know if this is an invalid setup. Working with this has been extremely frustrating.

  • ArchWSL version [e.g. 19.3.7.0]
    22.10.16.0

  • ArchWSL Installer type zip/appx/other clean/update [e.g. appx update]
    zip

  • Launcher version [e.g. 19030700] (Type Arch.exe version at a Command Prompt)
    wsldl2, version 22020900 (amd64)

Additional context
Add any other context about the problem here.
this is on an azure windows vm provided by my employer so I'd have to ask for additional details surrounding the vm if that info is needed

@LighghtEeloo
Copy link

Try these:

sudo pacman -S archlinux-keyring
sudo pacman -Syyu

@olsonpm
Copy link
Author

olsonpm commented Jan 13, 2024

here's the full output of those two commands

but the issue is with the original sudo pacman -Syu, i.e. if I rerun sudo pacman -Syu then the output says everything's fine - the same way sudo pacman -Syyu does. However when further trying to use arch, clearly things aren't working properly as I run into a lot of issues such as being unable to install packages. The original hint that things aren't working like they should is with the first run of sudo pacman -Syu

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

No branches or pull requests

2 participants