Version: (using KDE Devel) Installed from: Compiled sources in kcontrol, set your cups printserver to blank (or to a host that doesn't exist). When it tries to connect, it'll try to connect for a very long time, leading to what appears to be forever... and probably is. I left it for a couple hours once.
What you probably experience is a DNS timeout, which occurs in a CUPS library call (this is not directly in kdeprint's code). At work, I tried to enter wrong server name, but I get immediately an error message (either because the hostname doesn't exist, or because the port 631 is closed). But on some systems, this results in a DNS timeout; I guess this is related to the network configuration. What you could test is to start the print manager in gdb, let it hang up and then CTRL-C + backtrace to locate the timeout. Normally it should be in the CUPS library (as kcontrol forks itself, it's easier to use "gdb kcmshell" + "run printmgr").
this is very much a crash. If you want to print a document, and the print dialog blocks forever, and you didn't save before you started printing. Well, that's data loss. That's also as good as the program locking up. I'm changing it back to crash, and I'll hope that in the future you give a reason to your changes.
Charles, is this still a problem with KDE 3.5.6? ------------------ (Note to self: close this bug as WORKSFORME if there is no feedback by reporter until end of April)
Can't reproduce it anymore. It's still kinda annoying that I can't cancel the print dialog while the "connecting to cups server" (or whatever) little box is up.
Closing old Resolved status bug.