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

pixels-to-pdf failed #781

Closed
wolffi opened this issue Apr 18, 2024 · 7 comments
Closed

pixels-to-pdf failed #781

wolffi opened this issue Apr 18, 2024 · 7 comments

Comments

@wolffi
Copy link

wolffi commented Apr 18, 2024

The first stage (doc-to-pixels) completes successfully, [doc xxxxxx] 48% Converted document to pixels.
The second stage (pixels-to-pdf) stops at 0% with ERROR [doc xxxxxx] 0% Unknown error code '1'

I tried different converting different documents. The error is the same.

@apyrgio
Copy link
Contributor

apyrgio commented Apr 18, 2024

Thanks for this bug report @wolffi. Let's find out more about your environment. Can you let us know about the following:

  • What is your Operating System (macOS, Windows, Debian, Fedora, Qubes, etc.) and its version?
  • What is your Dangerzone version? It's the 0.x.y number you see when opening the app. You can also check with dangerzone-cli --version.

@wolffi
Copy link
Author

wolffi commented Apr 18, 2024

This is on Fedora 38, kernel-6.8.6 and dangerzone 0.6.0. I tried the GUI as well as dangerzone-cli.

@apyrgio
Copy link
Contributor

apyrgio commented Apr 18, 2024

My money is on SELinux, we've had similar issues in the past (see #517). Can you check:

  1. If SELinux is in enforcing mode? You can check with sestatus.
  2. If journalctl or /var/log/audit/audit.log have logged any SELinux policy violation?
  3. For kicks, is your user ID 1000? Run id to check it out.

We try to play by SELinux rules when mounting directories to the container, by relabeling the temp dir with the :Z flag (see Labeling Volume Mounts in the podman-run manpage). However, we are aware that this can still fail in some configurations. This issue will be fully resolved once we merge #748.

@wolffi
Copy link
Author

wolffi commented Apr 18, 2024

  1. SELinux is in enforcing mode, changing to permissive doesn't help.
  2. I don't see any recent entries in journalctl nor audit.log related to SELinux policy violation (nor any other hint regarding the error of dangerzone).
  3. My uid is NOT 1000, should I change it to 1000?

@apyrgio
Copy link
Contributor

apyrgio commented Apr 18, 2024

Yeah, that's the second known issue (see #624) that will be fixed by #748. If it's possible to switch to the user with UID 1000, just before invoking Dangerzone (e.g., with sudo -iu <user> dangerzone), that would help. Can you give it a shot?

@wolffi
Copy link
Author

wolffi commented Apr 18, 2024

Thanks @apyrgio for your help. I was able to convert the PDF using a newly created user account with UID=1000. Thanks a lot!

@apyrgio
Copy link
Contributor

apyrgio commented Apr 18, 2024

That's good to know, and hopefully we'll soon update Dangerzone so that you can use your regular user account.

If you don't have an objection, I'll now mark this issue as completed, and leave the parent issue (#624) open. I'll add a pointer to this issue, so that other users can see this workaround. Cheers!

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