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

qubes-dom0-update fails #9365

Closed
unman opened this issue Jul 20, 2024 · 3 comments
Closed

qubes-dom0-update fails #9365

unman opened this issue Jul 20, 2024 · 3 comments
Labels
affects-4.2 This issue affects Qubes OS 4.2. C: updates P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. R: cannot reproduce Resolution: Attempts to replicate the problem have not been reliably successful enough to proceed. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.

Comments

@unman
Copy link
Member

unman commented Jul 20, 2024

How to file a helpful issue

Qubes OS release

4.2 updated with testing repositories

Brief summary

qubes-dom0-update fails to update

Steps to reproduce

Attempt to update dom0
Updated packages are downloaded, but error:
'/usr/lib/qubes/qrexec-client-vm dom0 qubes.ReceiveUpdates /usr/lib/qubes/qfile-agent /var/lib/qubes/dom0-updates/packages/*.rpm' failed with exit code 1!

Expected behavior

Update succeeds

Actual behavior

Update fails

updatevm is debian-12 based.
Full system updates succesfully completed with same configuration 15 Jul

@unman unman added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists. labels Jul 20, 2024
@marmarek
Copy link
Member

Can you check /var/log/qubes/qrexec.VMNAME.log for your updatevm, and/or journalctl in dom0 about qubes.ReceiveUpdates service?

@andrewdavidwong andrewdavidwong added needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. C: updates affects-4.2 This issue affects Qubes OS 4.2. labels Jul 21, 2024
@unman
Copy link
Member Author

unman commented Jul 21, 2024 via email

@unman unman closed this as completed Jul 21, 2024
@andrewdavidwong andrewdavidwong closed this as not planned Won't fix, can't repro, duplicate, stale Jul 22, 2024
@andrewdavidwong andrewdavidwong added R: cannot reproduce Resolution: Attempts to replicate the problem have not been reliably successful enough to proceed. and removed needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. labels Jul 22, 2024
Copy link

This issue has been closed as "cannot reproduce." This means that attempts have been made to replicate the problem, but such attempts have not been reliably successful enough to proceed with fixing the problem.

We respect the time and effort you have taken to file this issue, and we understand that this outcome may be unsatisfying. Please accept our sincere apologies and know that we greatly value your participation and membership in the Qubes community. If the problem becomes reliably reproducible in the future, please let us know in a comment below, and we will reopen this issue.

If anyone reading this believes that this issue was closed in error or that the resolution of "cannot reproduce" is not accurate, please leave a comment below saying so, and we will review this issue again. For more information, see How issues get closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-4.2 This issue affects Qubes OS 4.2. C: updates P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. R: cannot reproduce Resolution: Attempts to replicate the problem have not been reliably successful enough to proceed. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
Projects
None yet
Development

No branches or pull requests

3 participants