I had this problem (or a very similar one). It was due to evince being unable to connect to the cups server (connection refused). This was apparent when I ran evince under strace.
The problem it seemed was due to an error in my hostname aliasing in the networking configs. Initially, for some reason, I had my hostname pointing at 127.0.1.1 and no alias at all for localhost. I *think* the problem was caused when I changed localhost to 127.0.0.1. The problem was solved by changing both my hostname and localhost to be aliases for 127.0.0.1 and restarting. I wonder if evince attempts to access cups with a different server string to most programs. -- evince does not enable print https://launchpad.net/bugs/66379 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
