KDE and CUPS upgrade problem (was: Re: Problem with printing in konqueror?)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sunday 11 May 2003 22:29, Donald Spoon <dspoon@astcomm.net> wrote:
> I DO have the old cupsd.conf file around (I saved it), and also have
> a moderately "clean" cupsd.conf file on other computers that could
> act as a baseline for all my edits. Guess I could do the scut-work
> and make the comparisons. Time to brew up some coffee and post-pone
> a few "combat naps" and get to work <grin>. I can forward the files
> to anyone who might want to put a second set of eyes on it. I am NOT
> a "programmer" so maybe someone better qualified than I should look
> also.
Can you forward them to me, please?
> BTW, I use the KDE config "wizzard" almost exclusively to set up
> CUPS. I mention this because this introduces another possible
> variable into the problem. I started off with KDE from Debian
> "Stable" and upgraded almost immediately to the version in "testing".
> I have been following that version until about 2 weeks ago, when I
> upgraded to KDE 3.1.1 from "ustable". The CUPS config wizzard has
> changed along the way, and I really don't know if those changes
> contributed to what I saw. All I can say for sure is that the
> current KDE 3.1.1 from "unstable" works OK for me with CUPS from
> "unstabe" starting from the packager's version of cupsd.conf. The
> version currently in "testing" seems to me to be broken with respect
> to setting up a LAN server. Config of a local printer is OK.
Personally, I suspect that cupsd.conf generated by the old kprinter
configuration tool are the most suspect part of this equation so far.
Perhaps with further analysis of the files generated by the various
tools (and upstream/package maintainers version) we will be able to
solve this. It is obviously biting a number of people, and will almost
certainly be a Woody->Sarge upgrade issue.
Paul Cupis
- --
paul@cupis.co.uk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE+vsbkIzuKV+SHX/kRAhysAJwNh25SUeMsr/X9xk30aL0C/E2RTwCfQ6Rs
Avpr5kuTjalaWJA2gKSCBY8=
=4zb6
-----END PGP SIGNATURE-----
Reply to: