bluesdog
07-07-2006, 01:40 PM
wtf is going on with kde print manager? :!:
On three different systems, all running etch/testing, with cups already installed and accessible via the cups web interface, when accessing kde control panel >peripherals >printers, the system would hang for an indeterminate, (looooong), time, attempting to launch the print manager. (initialising print manager).
This seemed to be caused by the URI to the print server being incorrectly listed as /var/run/cupsd Port:631 (or something similar. I worked on this quite late, and neglected to take note of the incorrect location..), rather than localhost:631
Manually editing /home/userlogin/.kde/share/config/kprinterrc fixed the setting for user, but the problem resurfaced when attempting to access the global administrator level settings.
Since I don't know where the global configuration file is located -- and Google didn't help me (!), simply killing kcontrol, then restarting it a few times, seemed to do the trick, by eventually allowing me to make the changes in the server config settings, (Print server > Configure server):
After a long wait, the informational box, 'initializing print manager' vanished, an error message appeared and once that was dismissed, I accessed the print server dialog, and changed the entry to default, so the system listened to *:631 == which allowed it to be satisfied when it found 'localhost:631', the port where CUPS was waiting to get noticed. Oddly, the change did not immediately take effect, and the system displayed another error message, but cancelling out of the administration level, and then re-entering it showed that the settings were now correct.
I had to do this for each machine.
REAL annoying, having to wait for kcontrol to give up and allow me to access the damn buttons!
So, if anyone knows where the global printer configuration file lives.... :?:
Would an alternative be to make a symlink in whatever location kcontrol thinks the cups server should be? (I never thought of trying that) :?
On three different systems, all running etch/testing, with cups already installed and accessible via the cups web interface, when accessing kde control panel >peripherals >printers, the system would hang for an indeterminate, (looooong), time, attempting to launch the print manager. (initialising print manager).
This seemed to be caused by the URI to the print server being incorrectly listed as /var/run/cupsd Port:631 (or something similar. I worked on this quite late, and neglected to take note of the incorrect location..), rather than localhost:631
Manually editing /home/userlogin/.kde/share/config/kprinterrc fixed the setting for user, but the problem resurfaced when attempting to access the global administrator level settings.
Since I don't know where the global configuration file is located -- and Google didn't help me (!), simply killing kcontrol, then restarting it a few times, seemed to do the trick, by eventually allowing me to make the changes in the server config settings, (Print server > Configure server):
After a long wait, the informational box, 'initializing print manager' vanished, an error message appeared and once that was dismissed, I accessed the print server dialog, and changed the entry to default, so the system listened to *:631 == which allowed it to be satisfied when it found 'localhost:631', the port where CUPS was waiting to get noticed. Oddly, the change did not immediately take effect, and the system displayed another error message, but cancelling out of the administration level, and then re-entering it showed that the settings were now correct.
I had to do this for each machine.
REAL annoying, having to wait for kcontrol to give up and allow me to access the damn buttons!
So, if anyone knows where the global printer configuration file lives.... :?:
Would an alternative be to make a symlink in whatever location kcontrol thinks the cups server should be? (I never thought of trying that) :?