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

Convert to trusted pdf in R4.0 not working - Request refused #3818

Open
umbratic opened this Issue Apr 13, 2018 · 4 comments

Comments

Projects
None yet
3 participants
@umbratic

Qubes OS version:

R4.0

Affected component(s):

  • AppVM Convert to Trusted pdf
  • TemplateVM: fedora-26

Steps to reproduce the behavior:

  • In AppVM, Files, click right on pdf-file, select Convert to Trusted pdf >> nothing
  • $ qvm-convert-pdf returns: Request refused

Expected behavior:

Convert pdf-file to trusted pdf, as in R3.2

Actual behavior:

  • Does not convert pdf
  • Error message: Request refused

General notes:

  • This is fresh install R4.0. All updates done:
  • dom0: $ sudo qubes-dom0-update
  • fedora-26 TemplateVM: $ sudo dnf update
  • Reboot

Related issues:

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Apr 13, 2018

Member

Can't reproduce. It might be about not enough memory to start DispVM. See journalctl in dom0.

Member

marmarek commented Apr 13, 2018

Can't reproduce. It might be about not enough memory to start DispVM. See journalctl in dom0.

@umbratic

This comment has been minimized.

Show comment
Hide comment
@umbratic

umbratic Apr 13, 2018

Ah, I didn't realize that the default AppVMx (e.g. personal) feature a new parameter Default DispM = default (none) (current). So it does not know how to start a DispVM. If I set this to fedora-26-dvm it works. Excellent - thanks!

However, I noticed in journalctl the following:

  • WARNING: Sum of all thin volume sizes (646.22 GiB) exceeds the size of thin pool qubes_dom0/pool00 and the size of whole volume group (465.56 GiB)!
  • No longer monitoring thin pool qubes_dom0-pool00-tpool.

That sounds scary but I do not understand what it means. Is this related to above? Do I have to modify something?

Ah, I didn't realize that the default AppVMx (e.g. personal) feature a new parameter Default DispM = default (none) (current). So it does not know how to start a DispVM. If I set this to fedora-26-dvm it works. Excellent - thanks!

However, I noticed in journalctl the following:

  • WARNING: Sum of all thin volume sizes (646.22 GiB) exceeds the size of thin pool qubes_dom0/pool00 and the size of whole volume group (465.56 GiB)!
  • No longer monitoring thin pool qubes_dom0-pool00-tpool.

That sounds scary but I do not understand what it means. Is this related to above? Do I have to modify something?

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Apr 13, 2018

Member

That sounds scary but I do not understand what it means. Is this related to above? Do I have to modify something?

That's ok.

Member

marmarek commented Apr 13, 2018

That sounds scary but I do not understand what it means. Is this related to above? Do I have to modify something?

That's ok.

@andrewdavidwong andrewdavidwong added this to the Release 4.1 milestone Apr 14, 2018

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Apr 14, 2018

Member

Leaving this open as a UX enhancement for more informative error messages.

Member

andrewdavidwong commented Apr 14, 2018

Leaving this open as a UX enhancement for more informative error messages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment