Erik Moeller

From 2022-08-15 review with @gonzalo-bulnes @eloquence: - Keeping open for discussion purposes, but it would be best to chat about this with upstream as well, as any monochromatic logo would...

Keeping open for discussion purposes; this is a good polish issue to consider for beta/final version of the rewrite.

All I did in the `dpkg --configure -a` run is to confirm that the existing version of the file can be used. Would it be possible to automate the answer...

Do you still have any output from the `dpkg --configure -a` run about which package required manual attn?

Discussed a bit more; Kunal made the point that the layered behavior is desirable and that (in the current case) we should bump the version number in the `securedrop-client` `main`...

@almet Did you mean to comment the above on #873? Just checking to make sure I understand the separate issues correctly. Happy to try with a nightly.

I think that's a good idea. Perhaps we can edit the body of this issue with a "Temporary workaround" section similar to what we did with the previous macOS issue,...

Unfortunately, the temporary workaround does not work for me _consistently_. I tried with a batch conversion of a docx and ppt file. Here's the output from the GUI-on-terminal run of...

I can confirm that on macOS, downgrading to 4.38.0 resolves the issue for me, and the various conversion options (with OCR, without, etc.) all work without issue.

Keeping open: probably not something we need for the legacy client at this point, but we may want it in some form for the new app. See also https://github.com/freedomofpress/securedrop-dev-docs/issues/245 for...