deeplow
deeplow
That's true. This is a temporary solution. So as long as it is an improvement and satisfies the requirements, we should be fine.
I just came across a limitation of the Qt dialog compared to the GTK one: > ℹ️ **update**: the Qt dialog cannot handle when the printer is disconnected and reconnected...
Thanks for taking a look. Sadly I spoke too soon about the Qt implementation. For some reason I forgot to test if it actually printed correctly. It turns out that...
After deciding to go the GTK print dialog route, I investigated the best way to implement it (turns out there are many print dialogs in GTK) and the whole ecosystem...
We may want to do this one in coordination with https://github.com/freedomofpress/securedrop-client/milestone/14, since diverless printing support will require adding the `avahi` qubes service.
It's just just that the way we go about setting Qubes services is via salt. So we need to do a workstaiton release. We can do an individual one just...
> @deeplow is the driverless printing workflow finalized, even if the code is not? I think the workflow is pretty much the same as we have now. So I would...
Sounds good. I think it's just a matter of adding the `avahi` service. Everything is a matter of configuration, which we can do in a later release. That's a requirement...
This ended up no making it to 1.2.0, so I have moved its dedicated milestone.
> ❓ (1 with whonix and 1 **without** whonix installed?) Now thinking more about whether or not we should run a scenario without whonix installed (even though we do not...