On 1/27/11 1:59 AM, perryh@xxxxxxxxxxxxxx wrote:
James Mckenzie<jjmckenzie51@xxxxxxxxxxxxx> wrote:
Do you have ANY networked printers that can be accessed by your
system? This will cause Wine to start VERY slowly ... this is
a known problem with the CUPS printer access system ... there
is not much that Wine can do about this.
Is there some reason why Wine needs to communicate with CUPS _at
all_ during startup? I'd think it could wait until there is an
actual need to print something (which will be "never" for many
gamers). Alternatively, do the "establish CUPS communication"
work in a separate task or thread rather than holding the entire
session hostage.
Submit a bug report asking for this. Right now, Wine runs a printer
check, just like Windows does (you ever wonder why it takes so long to
boot up in a networking environment).
James McKenzie
