You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

robvr

Beginner

  • "robvr" started this thread

Posts: 1

Location: Best, The Netherlands

  • Send private message

1

Thursday, November 2nd 2006, 8:13am

wrecked KDE printer config

I was having trouble printing from KDE apps, so I fired up the control center, which gave me the choice of 'generic UNIX LPD system', CUPS, and a few others. Since there's a CUPS server on my network that all non-KDE apps on the same computer are happily printing to, I selected CUPS. The control center showed 'initialising manager' or some such phrase, and then became non-responsive, so I had to resort to kill -9 tactics. I then tried again, but this time the printer configuration immeditely went to 'initialising manager' - non responsive. Fine, killed it again, deleted the corresponding config file in ~/.kde, tried again, and everything was back to square one.
I then made a catastophic mistake: I went into administrator mode, and there tried to select CUPS, thinking there was perhaps a privilege problem somewhere. This led to the same non responsive configuration screen. I thought I could fix this the same way as before, but no such luck. I can't find the blasted configuration file that I need to delete for a renewed attempt at configuring a printer. I'm now completely stuck. I can't fix or remove the configuration file manually, and the configuration tool hangs, at least in administrator mode.
Given that this is a Redmont style problem, I could try the classical Redmont fix, and delete everything that so much as smells of KDE and re-install, but that really goes against the grain, not to mention that it will take a day of compiling.
Does anyone out here know which file I should vent my by now considerable anger on, to at least get back where I started? Or even what the name of the offending file is, so that I can have 'find' hunt it down for me?

Rob