Erik Moeller
Erik Moeller
Hitting the same issue on a Debian AppVM with Podman, at the same step as in the output above. @deeplow were you ever able to find a workaround
The only way I was able to quickly get it to start up was to do two inadvisable things: 1) run it as root, 2) ditch the `--userns=keep-id`. Neither of...
I've not been able to reproduce this with non-LibreOffice file types yet (PDF, JPG, ZIP). Very curious if others can repro.
@marmarek We're seeing this message now with standard LibreOffice document open operations. We'll look into upstream changes, but curious if you're aware of simple mitigation steps we can take to...
Still an issue (noticing this during QA for 0.5.0), we should try to resolve as this warning may suggest malware or other malfeasance during normal use of LibreOffice as a...
(Still an issue on Qubes 4.0, haven't tested in 4.1 yet.)
As one data point, most of my recent updater run failures have been due to update failures specifically on the Whonix templates, usually due to an "Invalid response from proxy:...
I can't speak to the corollaries, but otherwise this looks consistent with what we discussed, thanks for the recap. We also briefly touched on the steps users would need to...
I've tested this PR with Cerebras and can confirm that the user experience is much improved - requests do get throttled, but you no longer get a timeout pretty much...
I like the general idea of flagging a review for moderator attention and putting those reports in a queue (maybe sending an email too - if only account holders can...