2 Aug
2012
2 Aug
'12
3:26 p.m.
On Thu, Aug 2, 2012 at 3:43 AM, Scott Weisman <sweisman@pobox.com> wrote:
I should have added more details. I am using OpenBox on an X86_64 install.
Two different systems (desktop and notebook) but otherwise largely similar setups.
I'm also using Chromium in a pure Openbox environment on x86_64, and I don't see this problem. I notice that the first time I show the print dialog, cups is started (by systemd's socket activation) if it wasn't running already. I wonder if the hang comes when cups isn't available? Do you have it running, or at least available for socket / path activation if you're on systemd?