[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: KDE and CUPS upgrade problem (was: Re: Problem with printing in konqueror?)



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

El Domingo 11 de Mayo de 2003 23:55, Paul Cupis escribió:
> 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

  This may be slightly off topic of this thread but it is certainly related to 
KPrinting. I am using KDE 3.1.1a in Woody and I still have some problems with 
KPrinter, even with the latest patch included in KDE 3.1.1a. The printers 
with CUPS work fine but I always get the following message error:

kdecore (KSocket): ERROR: KExtendedSocket::connectionEvent() called but no 
data available!

 I have not been able to add printers with CUPS using the KPrinter wizard in 
some computers in my LAN, because the wizard freezes in the process. In that 
case I use the web interface and the address: "localhost:631" and setup them 
from there, and later I can use kprinter. In any case when printing I always 
get the error I have written in the previous paragraph.

  What is clear is that printing in KDE 3.1.x with CUPS in a LAN is not 
working perfect, as with previous versions of KDE. Some kind of bug has 
arisen that either did not exist or did not show up in previous versions. And 
the latest patch has sort of fixed it, but not totally.

Pablo de Vicente
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+v2SQSItUpHl6kJERAoTlAJ9uD9VSqweKHkgNbQpPQkMjvNjQtQCdG6+R
hxhyOYn/g1wz1QZLaQSay7k=
=iu/+
-----END PGP SIGNATURE-----



Reply to: