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

Change the order of possible issues in start-up initialization failure dlg #919

Closed
tparchambault opened this issue Oct 4, 2023 · 0 comments · Fixed by #920
Closed

Change the order of possible issues in start-up initialization failure dlg #919

tparchambault opened this issue Oct 4, 2023 · 0 comments · Fixed by #920
Assignees
Milestone

Comments

@tparchambault
Copy link
Contributor

We provide a list of possible issues to investigate if the fapolicy-analyzer doesn't complete initialization correctly. Since we don't explicitly specify our dependency on fapolicyd in the rpm spec file, the installation of fapolicyd should be the first thing the user verifies, and our troubleshooting suggestions should consequently list that first.

@tparchambault tparchambault self-assigned this Oct 4, 2023
@jw3 jw3 closed this as completed in #920 Oct 5, 2023
jw3 pushed a commit that referenced this issue Oct 5, 2023
Changed ordering of the first two hints in the initialization failure
dialog.

We are now starting with the daemon installation as it is logically the
first thing to check on.

Closes #919
@jw3 jw3 added this to the v1.2 milestone Oct 6, 2023
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 a pull request may close this issue.

2 participants