Mandriva 2006 / KDE 3.4 Printer Configurator utility freezes session
MandrivaThis Forum is for the discussion of Mandriva (Mandrake) Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Mandriva 2006 / KDE 3.4 Printer Configurator utility freezes session
I'm having a problem with a new install of Mandriva 2006.
I'm trying to add a network printer to my mandriva.
When I ran the system->configuration->printer (which launches Mandriva Linux Control Center 2006) the first time as non-root, it complained that CUPS wasn't installed.
I decided to install CUPS via this window, and it asked me for the sys admin password.
It started to install CUPS, but eventually the window "froze" - i.e., no screen refreshes, dragging the window causes the dreary grey background to consume the entire window, etc. I waited a good amount of time for this to clear up, but it never did
At this point, I could still access the KMenu "start" button, and launch other apps.
I logged out and logged back into KDE as root, and attempted to re-run the printer configuration again (via Mandriva Linux Control Center 2006 - same as when I was non-root). Now, the window starts up and stays "grey" for a long amount of time, and then eventually the window repaints. however, I cannot click on anything in the window (frozen), and visiting the KMenu "start" button again will eventually cause the desktop session to freeze. I can create new sessions with alt+ctrl+bkspc or the alt+ctrl+function keys, but I cannot unlock the current session. Num lock and Caps lock still work as well.
I did try installing CUPS via the software mgmt utility provided in the GUI, and that seemed to take ok.
Not that it entirely matters (since I haven't gotten this far yet) but the printer I plan on installing is a HP LaserJet4050N running a jetDirect card, with a print queue managed by a dedicated windows print server.
I'm kind of at a loss - when I had Mandrake 10.1 Official a few months ago, I went thru this process fine and hooked this exact same printer up to the exact same machine.
Does anyone have any suggestions to try?
Any ideas/advice would be appreciated.
If anyone needs more info to help me remedy this problem, please let me know.
Ok, I figured out how to remedy the problem, but I'm still not sure why it caused the printer config utility to freeze.
Apparently, the first time I used the utility, and put in the Windows print server name, it caused CUPS to keep searching for the print server.
I tried running 'printerdrake' from the console, but this would cause the same freeze although I would eventually get a "process not responding" and allow me to KO the process from the console.
On a whim, I went into the CUPS configuration directory (I think it's /etc/CUPS) and did a grep for the print server name. I believe it gets entered into the clientd.conf file.
I went into that file, removed the entry, and that FIXED the problem.
I still don't understand why typing in an invalid printserver name would cause the utility to freeze - that seems like a bug to me. Yes, I understand the printserver name was wrong, but freezing the GUI / system? I think it's a mistake some people will make, and it certainly does not handle it gracefully.
Anyways, that was my fix in case anyone had a similar problem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.