On Thu, Aug 2, 2012 at 6:41 PM, Guillaume Brunerie <guillaume.brunerie@xxxxxxxxx> wrote: > 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. I was just bitten by this too, and I can confirm it strikes both through Ctrl+P and when clicking on "print links". I've searched for a bug reported upstream on this, but can't find one, has anyone with a stronger goggle-fu had more success finding one? /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@xxxxxxxxxxxx jabber: magnus@xxxxxxxxxxxx twitter: magthe http://therning.org/magnus
