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

Updating using pkcon fails with error exit status 29 #74

Closed
UriHerrera opened this issue Jul 30, 2022 · 0 comments
Closed

Updating using pkcon fails with error exit status 29 #74

UriHerrera opened this issue Jul 30, 2022 · 0 comments
Labels
upstream-bug Issues that are determined to not be caused by our configuration. wontfix Issues determined to not be a problem to fix

Comments

@UriHerrera
Copy link
Member

UriHerrera commented Jul 30, 2022

Describe the bug
After running pkcon update, an error is displayed with the following text: subprocess returned error exit status 29.

To Reproduce
Steps to reproduce the behavior:

  1. Open Station
  2. Run pkcon update
  3. Error is displayed

Expected behavior
No error is displayed

Screenshots
295345496_1207733100070460_6166895848558534522_n

Desktop (please complete the following information):

  • Nitrux > 2.1.1

Additional context
The reason why this error occurs is that post-installation scripts in Debian packages make use of systemctl for a variety of reasons, such as enabling services. As it is the fact that we do not use systemd, these maintainer scripts fail, causing pkcon to display this error.

This issue is an upstream problem as Debian specifically targets systemd, even if other init systems such as SysV, OpenRC, or runit are available in their repositories.

However, it does not mean something has broken; Users can resume the process by running pkcon repair and then pkcon update, which will result in a success message.

Note: We do not develop PackageKit, nor its backend APTCC.

@UriHerrera UriHerrera added wontfix Issues determined to not be a problem to fix upstream-bug Issues that are determined to not be caused by our configuration. labels Jul 30, 2022
@UriHerrera UriHerrera pinned this issue Jul 30, 2022
@UriHerrera UriHerrera unpinned this issue Dec 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upstream-bug Issues that are determined to not be caused by our configuration. wontfix Issues determined to not be a problem to fix
Projects
None yet
Development

No branches or pull requests

1 participant