2012/8/2 Ray Kohler <ataraxia937@xxxxxxxxx>: > On Thu, Aug 2, 2012 at 3:43 AM, Scott Weisman <sweisman@xxxxxxxxx> 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? Indeed, that’s the problem. On my system I also have a pure openbox x86_64 environment but without cups and without systemd (yet), and I noticed the same freeze when pressing Ctrl-P. But then I installed cups and started the daemon and now the print dialog shows immediately and there is no freeze anymore. So a workaround is to install cups and start the daemon at boot.
