From kde-core-devel  Mon Mar 24 15:03:17 2003
From: George Staikos <staikos () kde ! org>
Date: Mon, 24 Mar 2003 15:03:17 +0000
To: kde-core-devel
Subject: Re: Fwd: kprinter crashes with KDE 3.1.1 + woody
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=104851827200899


Try this patch to see if it helps.  In any case it means that your printer in 
not available.

Index: kmcupsmanager.cpp
===================================================================
RCS file: /home/kde/kdelibs/kdeprint/cups/kmcupsmanager.cpp,v
retrieving revision 1.44.2.6
diff -u -3 -p -r1.44.2.6 kmcupsmanager.cpp
--- kmcupsmanager.cpp   27 Feb 2003 17:27:18 -0000      1.44.2.6
+++ kmcupsmanager.cpp   24 Mar 2003 15:02:12 -0000
@@ -283,6 +283,8 @@ bool KMCupsManager::completePrinterShort
                        while (!m_lookupDone && (QDateTime::currentDateTime() 
< tm))
                                qApp->processEvents();

+                       kes->cancelAsyncConnect();
+
                        delete kes;

                        if (!m_lookupDone)


On Monday 24 March 2003 09:25, George Staikos wrote:
> On Monday 24 March 2003 02:29, Stephan Johach wrote:
> > Hi!
> >
> > > kdecore (KSocket): ERROR: KExtendedSocket::connectionEvent() called but
> > > no data available!
> >
> > I have the same error here. Printing in kde is impossible at the moment.
> > The printer dialog opens and after a few seconds the app crashes with the
> > above error message on the console.
> >
> > I tried to get a complete backtrace but after recomiling kdelibs/kdebase
> > with full debug info the problem vanished. It's back now after
> > recompiling again without debug info. :(
>
>    I added the code that is related to this, and it works fine for me.  It
> was reviewed by Michael as well.  Unless you can reproduce this with a
> proper backtrace I'm not sure what I can do.

-- 

George Staikos